返回提示词目录第 1418 页

设计团队看板与任务流转规则

根据团队实际流程设置看板列、在制任务上限和例会节奏,形成首月改进计划。

完整提示词

<context>
Kanban works by limiting work in progress so that items finish instead of piling up half-done. Boards fail when columns copy job titles instead of the real states work passes through, when "waiting" states such as "ready for review" are hidden inside "in progress", when WIP limits are set so high they never bite, and when nobody looks at cycle time. Little's law ties the numbers together: average cycle time equals work in progress divided by throughput, so cutting WIP is the fastest way to shorten delivery. Expedite lanes and classes of service let urgent work through without blowing up the system, as long as they are rare and capped.
</context>

<task>
<team>
{{team}}
</team>
<current_flow>
{{current_flow}}
</current_flow>

1. Map the real states work passes through, separating active states from waiting states (for example "In review" versus "Ready for review"). Keep the board to the fewest columns that show where work waits.
2. Write an explicit exit rule for each column: what must be true to pull an item to the next one.
3. Set starting WIP limits from team size (a common start is about one item per person in active columns, plus a small limit on waiting columns), and explain what the team should do when a limit is hit: swarm, review, unblock, not start new work.
4. Define classes of service such as expedite, fixed date, standard and intangible (debt), each with a cap or share and a rule for who can use expedite.
5. Choose flow metrics: cycle time with the 85th percentile, throughput per week, WIP, and item age. Say how to read each and what pattern signals trouble.
6. Give the operating routine: a daily stand-up that walks the board right to left, a replenishment meeting, and a monthly flow review.
7. Plan the first month: what to measure before tightening limits and the experiments to try.
</task>

<constraints>
- Do not prescribe a tool; describe the board so it works in any tracker or on a wall.
- Do not import sprint ceremonies the team did not ask for.
- Keep expedite rare: cap it at one item at a time unless the input justifies more.
- If team size or work mix is missing, state the assumption you used.
</constraints>

<output_format>
## Board
Columns in order, marked active or waiting.
## Column policies
Table: column | exit rule.
## WIP limits
Table: column or group | limit | reason; plus what to do when a limit is hit.
## Classes of service
Table: class | when to use | cap | rule.
## Flow metrics
Table: metric | how to measure | warning sign.
## Operating routine
Bullets per meeting.
## First month
Numbered steps.
</output_format>

可替换内容

  • {{team}}
  • {{current_flow}}

分类与标签

办公效率、团队看板、任务流转、在制任务限制、交付周期

前往 AI 图片创作