KPT Retrospective Board: From Last Try to the Next One

プロジェクト管理・開発

KPT Retrospective Board: From Last Try to the Next One

For teams that close each cycle with a retrospective, opened shortly before the session and used live during it. The whiteboard holds a frame for how the last Try went, the Keep / Problem / Try frames, a grid for sorting problems by impact and control, a 60-minute agenda, and a frame for the Try you commit to. The task board runs from raw topics through running the Try to checking its impact, and starts with four parent tasks - prepare, collect, decide, follow through - each with its own subtasks.

0 いいね 0 コピー 作者: WeProcess
retrospective KPT team improvement continuous improvement sprint practice
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 KPT Retrospective Board: From Last Try to the Next One
無料登録してこのテンプレートを使う

ホワイトボード プレビュー

1. How the Last Try Went (always star... 2. Keep (worth continuing) 3. Problem (what got in the way) 4. Try (worth testing) 5. Sorting the Problems (deciding whe... Big impact x mostly outside our control Big impact x ours to change Small impact x mostly outside our con... Small impact x ours to change 6. A 60-Minute Retro (rough timing) 7. This Cycle's Try (exactly one - yo... KPT Retrospective... How to use: 1. Wr... Keep & wins Decisions & o... Problems Try & ideas The Try we choseExample: ping the team while the work stays in progress(owner: ____ / by: __/__) What actually happenedExample: wait before review dropped from a day to half a day.We forgot to ping twice. Keep / drop / changeExample: keep it, but move the ping to a saved chat message so nobody forgets. Example: the 15-minute morning check caught blockers Example: writing a design note first cut rework Say who did what and what came of it Pick up the things that quietly went right Example: reviews waited two days on average Example: half a day lost finding who owned the spec Make the event the subject, not a person Keep facts and interpretation apart Example: add a short chat note to every review request Example: name a spec owner for each area Small enough to start tomorrow Go for volume here - you narrow it in frame 7 縦軸: Size of impac... Decide who to raise it with and what to ask for. Send it out as a request, not as this cycle's Try. Pick this cycle's Try from here. Give it an owner and a date and run it next cycle. Write it down and move on. Dig in only if it shows up again next time. Whoever notices it fixes it on the spot. Don't spend retro time here. 0-10 minReview the last TryDid it happen, did it help, and does it stay? Decide before moving on. 10-25 minCollect Keep and ProblemWrite alone first, then post. Cap each read-out at 30 seconds. 25-40 minDig into the problemsNarrow to a few, then trace why each one happened. 40-55 minDecide the TryPropose fixes, choose one, and attach an owner and a date. 55-60 minClose the sessionRead back what was decided, book the next retro, and end on time. The Try we will runExample: send review requests with a saved chat message Owner and dateOwner: ____ / By: __/__Track the progress on the task board How we'll know it workedExample: log the wait before review until the next retro and compare
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Retro Topics 16件

Prepare the retro
Post Keep & Problem
Pick one Try
Follow through
Review the last Try
List what happened
Set roles and time
Write the Keeps
Write the Problems
Sort the Problems
List Try options
Choose the Try
Set owner and date
Run the Try
Record the impact
Decide to keep it

On Today's Agenda 0件

Try In Progress 0件

Checking Impact 0件

Done 0件