Girl Geeks Dinner - Scrum 101
•Transferir como PPT, PDF•
1 gostou•1,306 visualizações
I gave this talk at the Auckland Girl Geek Dinner (organised by Amanda Jackson) on 24 September 2009. To sign up for other GGD events go to girlgeekdinners.co.nz.
![Today – Scrum end to end ,[object Object],[object Object],[object Object],[object Object],[object Object],Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Girl Geeks Dinner - Scrum 101
Semelhante a Girl Geeks Dinner - Scrum 101 (20)
Último
Último (20)
Girl Geeks Dinner - Scrum 101
- 1. Carolyn Sanders - Fronde Scrum 101 – end to end, minus the hype
- 6. Agile Landscape Agile Manifesto and Values Agile Project Management (process) Agile Delivery (process) Agile Programming (engineering practices) Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 8. Agile Delivery Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited Traditional Project Agile Project Iterations – Design/Develop/Test First chance to see Last chance to change First chance to see Last chance to change Idea Business Case Reqts Design and Develop Test Train Deploy Idea Bus. Case HLR / Design / Setup 1 2 3 4 5 6 Deploy
- 10. 2. Scrum on one page © Pete Deemer and Gabrielle Benefield, The Scrum Primer Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 12. “ Individuals and Interactions” – Scrum Roles Product Owner: get all the stakeholders’ input, prioritise the outputs Team: build the output. Self Organising, Cross Functional Scrum Master: get the process going well Stakeholders: have their say and do their bit Project Manager: not specified in Scrum Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 13. Our team room Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 15. The Product Backlog – how we did it Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 16. The Product Backlog – estimation with Planning Poker The Fibonacci series: 1, 1, 2, 3, 5, 8, 13, 21, 34, 55… Planning Poker cards: 0, ½, 1, 2, 3, 5, 8, 13, 29, 40, 100, ?, ∞, coffee/pie James Grenning & Mike Cohn Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 18. Sprint Planning – “Working Software” means what, exactly? Defining “Done” – hanselminutes.com Podcast 119 Quality (of the product) Support Documentation Content Testing Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 19. Sprint Planning again – what we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 21. Daily Scrum – what we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 22. Daily Scrum – what we did (the task wall) Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 23. Daily Scrum – what else we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 24. Behind the Daily Scrum – what else we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
- 28. The big secret Don’t tell anyone, but… Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
Notas do Editor
- Agile Alliance came up with this manifesto. Note that we value the left hand items MORE, not INSTEAD.
- Product Owner. Owns the business problem and makes all priority decisions. Come back to this with our experiences. Will do this a bit, so save your questions because I’ll probably answer them. In our case, the senior BA played this role. Team. Pigs and Chickens. The team are the pigs. Scrum Master. Serve and protect the team. Help them understand and follow the practice of Scrum (including product owner). Not the PM role! Stakeholders: first big learning – projects still have lots of these. Product owner must listen & engage. Project Manager (come back to this)
- Here’s our team room. Colocate! Note the lack of windows. Good things: we were all together, had heaps of wall room, had a door we could shut. Not ideal, but way better than not being in a room together. Ideal room has more people space, a whiteboard, more desk space. And windows. This is the reason the rest of the photos are a bit grey.
- The theory… Note the actual mechanism for creating a good PB is outside Scrum per se, and where you have to slot in other techniques eg use case, user stories, reqts analysis, solution design Mention User Stories here
- Photo of a PB card, and photo of site map, and photo of a PB list on a wall. We did start with a big idea and wind up with a list of things to do. How we did that, is not specifically prescribed in the Scrum methodology and it deserves its own place. Once we had the list, here’s how we prioritised it. We were building an intranet site, and we had the sitemap by this point. So … list of non-site-map items and then a site map. Got the stakeholders with the product owner to move the sitemap and non-sitemap items into the sprints. At this point we’d also decided how many sprints and how long: driven entirely by budget. So anything that didn’t go into the sprint was left on the “Later” list. Note: not thrown away.
- It’s really about micromanagement. But in a good way.