Next session
Date: 23th March, 2010
Time: 18:00 - 20:00
Place: Starduck Studios, Sumeliuksenkatu 18 B, 1st floor (map)
General
Team: Satish Bhat, Panu Puro, Santeri Vesalainen, Mikko Koljonen, Mika Impola, Pekka Virtanen, Simo Kivimäki
Scrum Master: Pekka Mattila
Product Owner: Mikko Suonio
Definition of done
A user story is done when
- acceptance tests have been reviewed with Product Owner
- acceptance tests have been implemented
- acceptance tests for this and other already implemented stories pass
- unit tests have been implemented
- all unit tests pass
- code has been implemented
- code and test code have been reviewed with another team member (pair programming or walk-through)
Product backlog
| User story |
Estimate (story points) |
| Sprint 1 |
0 |
In order to see that the coffee maker software works
As a Greedy Manufacturer
I want it to display the indicator when I press the Brew button |
13 |
| Sprint 2 |
13 |
| Sprint 3 |
0 |
In order to get warm water for my coffee
As a Regular Coffee Drinker
I want it to start heating the water when I press the Brew button |
3 |
In order to get my coffee in liquid form
As a Regular Coffee Drinker
I want it to spray boiling water over the coffee grounds |
3 |
| Sprint 4 |
6 |
In order to see that the coffee is ready for consumption
As a Eager Coffee Addict
I want it to indicate that the coffee is ready |
5 |
In order to avoid melting the coffee maker
As a Cautious Manufacturer
I want it to stop heating when all water has evaporated |
3 |
In order to avoid cleaning the mess
As a Kitchen Cleaner
I want the coffee machine to shut down water when pot is off the warmer plate |
5 |
In order to be able to steal some coffee while brewing is ongoing without disturbing the batch
As a Impatient Coffee Addict
I want it to continue brewing the coffee when I put back the pot |
5 |
In order to enjoy warm coffee without bothering to make some
As a Lazy Coffee Drinker
I want it to keep the coffee remaining in the pot warm |
13 |
Release burndown
References
- http://www.objectmentor.com/resources/articles/CoffeeMaker.pdf
TODO
Problems & Solutions
Problems that surfaced during retrospectives and possible solutions for them.
Time
Problems:
- Loosing time because context switching is needed.
- Participants are chancing too much.
- Too long planning compared to whole session length.
- Not enough time to refactor,to have a retrospective...
Solutions:
- Let's have full day sessions.
Pairing and keyboards
Problems:
- Incorrect pair programming practice.
- Different keyboard layouts (FI vs. US and mac vs. pc).
Solutions:
- In pair programming change the driver more often.
- More keyboards.
- Use "eclipse sharing" when necessary
Goal
Problems:
Solutions:
- Make acceptance tests more visible for everyone. Write them to a
whiteboard or something like that.
- Make only acceptance tests runnable or all of the tests runnable with
one simple click
Works on my machine
Problems:
Solutions:
- .settings and .project files to VCS with changes that makes them work
for everyone
Past sessions
