2014-04-16 Dev tools and data/resource management¶

Retrospective notes¶

Timing

• Longer review meeting (always goes into overtime) → extended to 1.5 hours.
• Later review meeting (Pacific Time friendly) → moved.

Kick-off

• Focus on assigning stories

Demos presented by individual developers

• Explicit preparation
• Make screen shots along the way (even during development!) so you have material to present
• Add "screen shots" to before-you-merge checklist?

Backlog visibility

• Update the story progress better! Lots of stuff sticks at "New" when it's actually inprogress or done.

FINISH EARLIER DANGIT¶

Tuesday night is the end. Wednesday sprint review

In review, "almost done" is pronounced "not done".

Branches and stories

• Review comments generally go on stories
• But if you have a big story, you might not want a giant branch/review/merge
• Then you shouldn't have a big story! Recognize that, and split the story.