Agenda for Day #2
| 9:10 - 12:00 | Cycle Planning Part |
| 12:00 - 13:00 | Lunch 🥗🍔 |
| 13:00 - 16:30 | Iteration Planning |
| 16:30 - 17:00 | Closing 🍻 |
Get Some XP™
Cycle Planning
Use common sense
Post-beer principles
Agile =/= Loose interpretation of the methodology
Don't stick to exceptions
How to define/write
good user story?
How to define
good user story?
-
Have customer value
(even if it's small and temporary) -
Possibly optional, independent
-
Small enough to fit 2-3 stories in an iteration
-
It can be estimated
How to write
good user story?
-
Have a short and precise name/identifier
Eg. "Add refresh button" -
Then add details:
-
Whose problem is solved by this story?
-
What problem is addressed in the story?
-
Why to do that? What is the value?
-
-
One template:
“As a <particular class of user>, I want to <be able to perform/do something> so that <I get some form of value or benefit>”
How to write
good user story?
Unread notification number on badge
I as the Marketer want to see the number of unread notifications on the NC badge so that I can see how many messages I didn't read yet and read if I want.
~1 day
How to write
good cycle plan?
How to write
good cycle plan?
-
Incrementally bring customer value
(even if it's small and temporary) -
Items can be swapped or replaced
-
Have realistic milestones with clear acceptance criteria, and business value
Cycle Planning @ Get Some XP
By drawain
