Introductie voor programma- en projectmanagers in Scrum. Wat is het, wat kan je ermee en hoe verhoudt het zich tot bijvoorbeeld, RUP. Ook aandacht voor Kanban.
8. UI
Planning JSP G
l
Visuee
2
Design
4
Test
e
Servic cases
s
Retouren classe 3
2
Sprint backlog Team builds Taken
UI Co de DAO +
2 DBUnit
Couponnen 1
Database Ser vice
design + JUnit
1 1
9. Daily Wat heb ik gisteren gedaan?
Wat ga ik vandaag doen?
Zie ik ergens obstakels?
Max. 15
minuten
10. Eind vd sprint
Sprint Review
• Presentatie van wat team bereikt heeft
• Demo van ontwikkelde features
Sprint Retrospectief
Hele team evalueert de resultaten van
de laatste sprint
• Wat moeten we gaan doen?
• Waarmee moeten stoppen?
• Waarmee vooral doorgaan?
13. Scrum schalen Scrum van
Scrum van
Scrum
Scrum
van
Scrum
14. Scrum is Agile
Hoogste klantwaarde eerst opleveren
Focus eerst op planning dan op het plan
Opleveren van werkende oplossingen, snel
en repeterend
Werkt met zelforganiserende teams
15. Kanban
Ook een Agile proces tool
Is veel vrijer dan Scrum
Leidende principes:
Visualiseer taken met ‘cards’
Limiteert aantal WIP’s
Meet de lead- of cycle time
16. Combineer
Miyamoto Musashi
“Raak niet teveel gehecht aan
1 wapen of vechtschool.”
17. Best of more worlds
Scrum en
XP elementen; test driven
development pair programming
RUP; Use cases
Kanban en
Scrum; stand up meeting en backlog
Daily Scrums are 15 minutes long. Why not then have a one-time 15 minute Scrum meeting to introduce Scrum.\nI prepared these slides after I failed to attract PMs in my organization to attend my first Scrum presentation which was 1.5 hours long.\nNow, I am using these slides to introduce Scrum to as many teams as possible in an attempt to spread the word.\nAll these slides are based on the work of Mr. Mike Cohn, Mountain Goat Software.\nYou are free to reuse these slides and modify it any manner.\n\nSrikanth Shreenivas (http://www.srikanthps.com, srikanthps@yahoo.com)\n
Scrum enables iterative incremental development by involving whole team.\n
\n
Sprints should be protected from changes. This is very important for team to have maintain focus within the Sprint.\n
Product owner defines product backlog, prioritizes them and is responsible for validating sprint outputs.\nScrum master enacts Scrum values and removes impediments of the team.\nTeam is cross-functional consisting of members with various skills and roles.\n
\n
Team creates Sprint backlog from product backlog items of highest priority. Team defines the Sprint goal based on the items that are planned for current Sprint.\n
Team breaks down the Sprint backlog features into tasks. Typically tasks are created in such as way that each task can be completed in one day. \nDe getallen geven de relatieve zwaarte per item weer. Door deze bij elkaar op te tellen, krijg je de ‘velocity’ \nHoeveel kan je in een sprint opleveren?\n
Team tracks Spring progress with daily scrum.\n
\n
During the Sprint, overlapping phases of requirements, design, coding and testing happens.\n
\n
\n
\n
\n
\n
\n
Scrum expresses Agile Values documented in Agile Manifesto.\n
Scrum \nRoles (product owner, scrum master, team). \n3 artifacts (product backlog, sprint backlog, sprint burndown), \n4 activities (sprint planning, daily scrum, sprint review, sprint retrospective)\n\nVrij in de samenstelling van kanban board; wie doet wat, hoeft niet altijd multi disciplinair\nMaak het proces en de doorlooptijd voorspelbaar\n\n
Scrum expresses Agile Values documented in Agile Manifesto.\n
Scrum expresses Agile Values documented in Agile Manifesto.\n