返回提示词目录第 1403 页

项目团队规模与交付周期估算

综合工作量、关键路径和入职磨合时间,比较人员配置方案并估算交付区间与人月成本。

完整提示词

<context>
Dividing total effort by the weeks available gives a headcount that is almost always wrong. Work does not split evenly: the critical path sets a floor on duration no matter how many people join; each new engineer needs weeks to become productive and takes time from existing staff while ramping up; communication paths grow roughly with the square of team size; and hiring takes months before anyone starts. Adding people late to a late project makes it later (Brooks's law). The honest answer is usually a range of team shapes with trade-offs, plus the date below which no team size helps.
</context>

<task>
Project: {{project}}
Target date: {{target_date}}
{{#current_team}}Current team: {{current_team}}{{/current_team}}

1. If there is no effort estimate, build a rough one: list the major workstreams and give each an effort range in engineer-weeks, and say the estimate is rough. If the work is too vague, ask the three questions that matter most.
2. Find the critical path: the chain of dependent work that cannot be parallelised. Its length is the shortest possible duration; compare it with the time to the target date.
3. Count the usable weeks: time to the target date minus hiring and onboarding lead time for new people, holidays, and a stabilisation period before launch.
4. Work out effective capacity per person: about 60 to 70% of a week on project work for existing staff after meetings and support; new hires at roughly a quarter, then a half, then full productivity over their first two to three months (state your assumption), plus the time they cost a mentor.
5. Give two or three team options (for example lean, balanced, fast), each with headcount by skill, expected finish range, cost in person-months, and the coordination overhead it adds. Note where a workstream can only absorb a certain number of people.
6. Name the skills that are scarce (one person who knows the payments code, no mobile engineer) and whether to hire, borrow, contract or descope.
7. Say plainly if the date cannot be met by any team size, and what scope cut would make it reachable.
</task>

<constraints>
- Do not divide effort by weeks and call it a team size.
- Every productivity and ramp-up figure is an assumption; label it and let the user replace it.
- Do not invent salaries or rates; give cost in person-months unless rates are provided.
- Treat contractors and new hires as needing onboarding too.
{{> output/uncertainty}}
</constraints>

<output_format>
## Answer
Two sentences: the recommended team shape and the date it likely reaches, or that the date is not reachable.
## Effort and calendar
Effort range, critical path length, usable weeks, with the arithmetic.
## Team options
Table: Option | People by skill | Likely finish | Person-months | Coordination cost | Main risk.
## Skills needed
Bullets, with the scarce skills flagged and how to cover them.
## Risks of adding people
Bullets.
## What would change it
The three assumptions that move the answer most.
</output_format>

可替换内容

  • {{project}}
  • {{target_date}}
  • {{#current_team}}
  • {{current_team}}
  • {{/current_team}}
  • {{> output/uncertainty}}

分类与标签

办公效率、项目排期、人力配置、关键路径、工作量估算

前往 AI 图片创作