2014-04-16 Dev tools and dataresource management » History » Version 6
Tom Clegg, 04/16/2014 11:33 AM
| 1 | 4 | Tom Clegg | h1. 2014-04-16 Dev tools and data/resource management |
|---|---|---|---|
| 2 | |||
| 3 | h2. Retrospective notes |
||
| 4 | 3 | Tom Clegg | |
| 5 | Timing |
||
| 6 | * Longer review meeting (always goes into overtime) → extended to 1.5 hours. |
||
| 7 | * Later review meeting (Pacific Time friendly) → moved. |
||
| 8 | |||
| 9 | Kick-off |
||
| 10 | * Focus on assigning stories |
||
| 11 | |||
| 12 | Demos presented by individual developers |
||
| 13 | * Explicit preparation |
||
| 14 | * Make screen shots along the way (even during development!) so you have material to present |
||
| 15 | * Add "screen shots" to before-you-merge checklist? |
||
| 16 | 5 | Tom Clegg | |
| 17 | Backlog visibility |
||
| 18 | * Update the story progress better! Lots of stuff sticks at "New" when it's actually inprogress or done. |
||
| 19 | |||
| 20 | h1. FINISH EARLIER DANGIT |
||
| 21 | |||
| 22 | Tuesday night is the end. Wednesday sprint review |
||
| 23 | |||
| 24 | In review, "almost done" is pronounced "not done". |
||
| 25 | 6 | Tom Clegg | |
| 26 | Branches and stories |
||
| 27 | * Review comments generally go on stories |
||
| 28 | * But if you have a big story, you might not want a giant branch/review/merge |
||
| 29 | * Then you shouldn't have a big story! Recognize that, and split the story. |