Project Retrospective for Beginners: Team Emotion Curve Board for Mood Highs and Lows

Project & Development

Project Retrospective for Beginners: Team Emotion Curve Board for Mood Highs and Lows

A team of four to seven people uses this beginner project retrospective template for 60 to 90 minutes after a months-long project, charting everyone's mood as an emotion curve. The whiteboard has four A4 pages. Page 1 sets the period, key events, member colors, and no-blame promises. Page 2 is a mood chart where each person places face stamps in their own color, joins them with a line, and writes the events behind highs and lows. Page 3 rates the low-point events, has each person vote with two circle stamps, and sorts them into fix by a system, prevent by personal habit, or skip this time. Page 4 gathers a KPT and sets what, who, by when, how to check, and the next date. The task board has four columns - Prepare, Reflecting, Promises in progress, and Checked - with four parent tasks and three subtasks each. Look at events and systems instead of blaming people, and fix first the period when everyone's mood dropped.

0 Likes 0 Copies Author: WeProcess
project retrospective emotion curve KPT team improvement for beginners
Other language versions
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Project Retrospective for Beginners: Team Emotion Curve Board for Mood Highs and Lows
Sign up free and use this template

Whiteboard preview

① Period and goal of the retrospectiv... ③ Members and colors (stamp and pen c... ④ No-blame promises (read aloud befor... ⑤ Promises from the last retrospectiv... ⑥ Mood chart (in the columns from ②, ... ⑦ Join the lines and read the wave (c... ⑧ Events in the high periods ⑨ Events in the dip periods ⑩ Events when everyone dipped ⑪ Rating table for low-point events (... ⑫ Fix by a system (most votes first) ⑬ Prevent by personal habit ⑭ Skip this time ⑯ Promises for the next project (deci... ⑰ Next retrospective (date and what t... Project Retro Emo... How to use (4 pag... Highs / what went... Decisions / promises Dips / troubles Insights / system... 1/4 Align period and ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Layer everyone's ... ↙ 3/4 Project and periode.g. Member site renovationApril 1 to July 20 (16 weeks) Today's goale.g. Set two promises so we do not create the same dip in the next project Time split (90 minutes in total)e.g. Page 1: 10 min, page 2: 25 min, page 3: 30 min, page 4: 25 min ② Timeline (line ... Start e.g. Apr 1 Kickoff and client interviews Phase 1 e.g. Apr-May Design and screen drafts Phase 2 e.g. May-Jun First half of build and reviews Phase 3 e.g. Jun Spec changes keep coming and overtime grows Phase 4 e.g. Early Jul Testing and bug fixes Goal e.g. Jul 20 Launch and team celebration e.g. Red = A (design) e.g. Blue = B (development) e.g. Green = C (planning) Change a face stamp to your own color before placing it (use the same color for your pen) e.g. Write about events and systems, not people e.g. Assume each decision was the best one with the information at the time e.g. Place your mood honestly. A low spot is fine e.g. What is said here stays inside the team Last time's promisee.g. Everyone writes their workload every Monday Did we keep it?e.g. Kept until week 8. It stopped in the busy Phase 3 Keep it this time?e.g. Yes. Move the place to write it to the task board Start Phase 1 Phase 2 Phase 3 Phase 4 Goal High mood e.g. Red A, Blue B e.g. Red A, Green C e.g. Blue B (none) e.g. Green C e.g. All three Neutral e.g. Green C e.g. Blue B e.g. Red A, Green C (none) e.g. Red A (none) Low mood (none) (none) (none) e.g. All three e.g. Blue B (none) Periods when mood was high (highs)e.g. Goal: all three high. Start and Phase 1 also fairly high Periods when someone dipped (dips)e.g. Phase 4: only B is low Periods when everyone dipped (deep dips)e.g. Phase 3: all three are low e.g. Goal: page load speed doubled after launch e.g. Phase 1: the client replied to the screen draft the same day e.g. Start: roles were settled at the first meeting Write who did what and what came of it e.g. Phase 4: B handled the bug fixes alone e.g. Phase 4: reviews waited 2 days on average e.g. Phase 4: the test environment was down for 2 days and checks stopped Make the event, not a person, the subject e.g. Phase 3: the spec changed in 3 places two weeks before launch e.g. Phase 3: overtime went over 10 hours a week e.g. Phase 3: the reasons for changes did not reach everyone Write only one event per note 3/4 Find why the dips... → 4/4 4/4 Decide the next p... Likely again? Can we act? Why it happened Circle stamp count e.g. Spec changes e.g. High. Happens on every project e.g. Yes e.g. No rule for deciding with the client e.g. 3 votes e.g. More overtime e.g. High e.g. Partly e.g. Cleanup after the spec changes in ⑩ e.g. 1 vote e.g. Reasons not ... e.g. High e.g. Yes e.g. Changes were only told verbally e.g. 2 votes e.g. Review waits e.g. Medium e.g. Yes e.g. Only one person could review e.g. 0 votes e.g. Handling alone e.g. Medium e.g. Yes e.g. It was hard to ask for help e.g. 0 votes e.g. Spec changes: decide changes with the client once a week e.g. Reasons not shared: write each change with its reason in one fixed chat place A system is a way of working that continues when people change Put the events with the most votes in first e.g. More overtime: say so the same day when you feel short-handed e.g. Everyone writes their workload every Monday Write habits that are not worth turning into a system Write whose habit it is by name e.g. Review waits: the next project has two people who can review e.g. Handling alone: it happened only once this time Add a short reason for skipping Look at it again in the next retrospective ⑮ KPT (sum up the... Keep (continue) e.g. Settle roles at the first meeting (from ⑧) e.g. Show screen drafts to the client early Problem (what went wrong) e.g. Spec changes kept coming right before launch (from ⑩) e.g. The reasons for changes did not reach everyone Try (what to test) e.g. Decide changes together in one weekly meeting (from ⑫) e.g. Write each change with its reason in a fixed chat place What Who By when How to check Promise 1 e.g. Decide changes once a week e.g. A e.g. By the first meeting e.g. Count the changes made before launch Promise 2 e.g. Write each change with its reason in a fixed place e.g. B e.g. By Friday of the first week e.g. Ask everyone if they can state the reason for changes Promise 3 e.g. Write your workload every Monday e.g. Everyone e.g. Every Monday e.g. Check that overtime stays within 5 hours a week Promise 4 e.g. Settle roles at the first meeting e.g. C e.g. On kickoff day e.g. Check that the roles table exists that day Next retrospective datee.g. Friday of week 4 of the next project, 60 minutesFacilitator: ____ What to look at firste.g. Whether the promises in ⑯ were kept. Copy them into ⑤ on page 1 next time Carried overe.g. Decide whether to take up the review waits skipped in ⑭ again next time → 2/4 Layer everyone's ... ↙ 3/4 Find why the dips... → 4/4 Decide the next p...
100%

Drag to move, scroll to zoom

Task board contents

Prepare 16 items

Align on basics
Layer the moods
Understand dips
Set next promises
Write period & goal
Line up key events
Choose colors
Place face stamps
Join lines, read it
Note highs and lows
Fill rating table
Vote with circles
Sort by fix type
Summarize in KPT
List the promises
Set next date

Reflecting 0 items

Promises in progress 0 items

Checked 0 items

Related templates

← Back to templates