The document discusses Agile planning practices. It outlines the levels of planning in Agile from product down to the day level. It describes how stories are used in Agile planning and how they should be independent, negotiable, valuable, estimable, small, and testable. It provides tips for splitting large stories, such as by functionality, priority, vertical slices, or separating CRUD operations. Finally, it gives an example of user stories for an app store and how those stories could be split or reordered for estimation and planning purposes.

1. Agile Planning
Invest in Stories
Raluca Breaur
26.11.2011

2. Traditional planning

3. Agile Planning Onion
PRODUCT
ROADMAP
RELEASE
ITERATION
DAY

4. Agile Planning
Release Planning
Iteration Planning

5. Release Planning
Vision STORY 1
Fixed in TIME or SCOPE MMF 1 STORY 2
Release anytime STORY 3
Product Owner
Release 1
MMF2 STORY 4
Product
STORY 5
MMF3
STORY 6
Minimal Marketable Feature
Epic
Feature

6. Story
Not requirements
Not use cases
1-2 line description of the work
“Promissory notes for a future
conversation”
(Alistar Cockburn)

7. Creates
Story
Product Owner

8. Story
Product Owner
Team

9. 1, 2, 3, 5, 8, 13, 20, …
S, M, L
XS, S, M, L, XL
1, 2, 3, 4, 5
3
Sizing `
13
8
Team

10. 3 5 13
3
` ` `
` 13 1 2
13
8 20 8
8
Product Owner
Product backlog
Sized stories Release backlog

11. Velocity = 22
3
3 5 13
`
5
` ` `
13 1 2
`
13
8 20 8
`
1
Product backlog
Iteration backlog

12. Story
Èngineering tasks
Team

13. DONE DONE
Developed
Tested
…
Story

14. Iteration Planning
Iteration TIMEBOXED
Velocity Engineering
Task
 Initial estimates STORY 2
 Done Done Stories Engineering
Task
Sized stories STORY 3
Stories -> smaller stories Engineering
Task
Stories -> tasks
Engineering
Tasks – estimated (hours) Task
Tasks are NOT allocated
Commit

15. Story

16. Product Owner Team

17. Ce informatii trebuie
introduse pentru a
crea un cont?
Product Owner Team

18. Doar emailul si Ce informatii trebuie
That’s easy, It’s a 5
o parola. introduse pentru a
crea un cont?
Product Owner Team

19. Trebuie sa trimitem un
mail si sa adaugam
userul in CRM
Product Owner Team

20. Trebuie sa trimitem un Hmm...Este prea
mail si sa adaugam mare ca sa pot
userul in CRM estima.Ar trebui sa
impartim storiul.
Product Owner Team

21. E ok daca facem doar
prima parte acum?
Product Owner Team

22. Da
Product Owner Team

23. Atunci e simplu. E un
3.
Product Owner Team

24. Story - Invest
Independent
Negotiable
Valuable
Estimable
Small
Testable

25. Split Stories – WHY ?
 2 components with different priorities
 Too big to estimate
 Too big compared to the iteration
 4-10 stories per iteration

26. Split Stories - HOW

27. Split Stories - HOW
Large stories – Vertical slices
Along the boundaries of the data

28. Split Stories - HOW
Large stories – Vertical slices
Based on the operations that are performed

29. Split Stories - HOW
Large stories – Vertical slices
Separate CRUD operations

30. Split Stories - HOW
Remove cross-cutting concerns
(security, logging)
Create 2 version of the story one with the
cross-cutting concern and one without

31. Split Stories - HOW
Large story – functional and non functional

32. Split Stories - HOW
Large story – smaller stories with different
priorities

33. Special stories
Documentation
Nonfunctional
Bug stories
Spike stories

34. Example – App Store
As a user I want to create an account so that I
can log in the application.
As a user I want to view and search for
applications so that I can see their details.
As a user I want to download an application so
that I can use it.
As a user I want to rate an application and
view ratings so that I can decide easier.
As a user I want to receive recommendations
so that I am informed.
As a user I want to see latest downloads.
As a user I want to manage a wish list.

35. Example – App Store
As a user I want to create an account so that I
can log in the application.
As a user I want to view and search for
applications so that I can see their details.
As a user I want to download an application so
that I can use it.
As a user I want to rate an application and
view ratings so that I can decide easier.
As a user I want to see latest downloads.
As a user I want to manage a wish list.
As a user I want to receive recommendations
so that I am informed.

36. Example AppStore – Velocity
15
As a user I want to create an account so
that I can log in the application.
As a user I want to view and search for
applications so that I can see their details.

37. Example AppStore – Velocity
15
As a user I want to create an account so
that I can log in the application.
As a user I want to view all applications so
that I can see their details
As a user I want search for applications so
that I can see their details.

38. Questions

39. Please fill your evaluation
form
Thank you!
Raluca Breaur