Scrum gov

1. E-GOV PROJECTS FOR “FUN” (AND “PROFIT”) Govcamp 2007 Antwerp

6. E-gov Projects Scope Planned DEADLINE Scope Removed Scope Additional Scope Has a change scope, unfinished

10. Agile Tactic : Prioritize Functionality High Priority Low Priority Requirements Functionality Each new Requirement is prioritized and added to the stack Requirements may be removed at any time Requirements may be repriorized at any time Modeled in greater detail Modeled in lesser detail Product Backlog Focus on functionality not on components Better view of what is finished

11. Agile Tactic : Release Often High Priority Low Priority Requirements Modeled in greater detail Modeled in lesser detail Set of Functionality Sprint X Sprint X + 1 Fixed Length Becomes a rythm Set of Functionality Planning becomes predictable if requirements become clear. Most important first. Timeboxed Periods = Sprint

12. Agile Tactic : Planning as a TEAM Set of Functionality Fuctionality X1 = Fuctionality X2= Fuctionality X3 = Fits Sprint capacity For next Sprint 1 2 3 5 8 13 21 BIG Team thinks it can handle 12 points in a Sprint 3 5 8 50 Team does estimations in group. Relative in Size (StoryPoints) , not in Days Planning Poker Fuctionality X4 = Needs to be split 21

13. Agile Tactic: Realistic Progress Initial DEADLINE 0 50 100 1 2 3 4 130 5 6 7 8 Product Backlog Burndown Chart 9 10 11 Estimate 1 Estimate 2 Sprint Convergence to an predictable “team” velocity Remember Iron Triangle!

14. Agile Tactic : Focus High Priority Low Priority Requirements Modeled in greater detail Modeled in lesser detail Set of Functionality Sprint X No need for all design upfront Focus helps getting things done Sprint Backlog Product Owner (PO) Focus = Functionality Scrum Master (SM) Focus = Blockers Team Focus = Build Set Tasks

18. Summary : Scrum Process Copyright SoftHouse Believe me! It’s more FUN!