Scrum - a lightweight customer-provider environment

485 views

Published on

Warsaw, March 23-24, 2010, II konferencja 'Zarządzanie Projektami IT' (II conference 'IT Project Management') http://konferencje.computerworld.pl/konferencje/zarzadzanie2010/

Published in: Business, Technology, Travel
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
485
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
3
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Scrum - a lightweight customer-provider environment

  1. 1. Scrum – a lightweight customer-provider environment Mateusz Srebrny <mateusz@srebrny.net> II konferencja ”Zarządzanie Projektami IT” Warsaw, March 23-24, 2010
  2. 2. Agenda Scrum and me Scrum elements between customer and provider: Product Backlog Sprints and reviews Backlog items size estimation Retrospectives Conclusion mateusz@srebrny.net, Warsaw, March 23-24, 2010
  3. 3. 'Server' project and scrum Redesign and scaling-out of the server-side infrastructure of the biggest polish instant messenger (over 2M PCU) 3 years, a small team of developers Scrum after half a year mateusz@srebrny.net, Warsaw, March 23-24, 2010
  4. 4. Scrum Management inside a small team Management of communication between customer and provider mateusz@srebrny.net, Warsaw, March 23-24, 2010
  5. 5. Product Backlog List of things to be done functionalities, components, user stories Priorities ROI, technical complexity, technical dependencies mateusz@srebrny.net, Warsaw, March 23-24, 2010
  6. 6. Product Backlog Primary tool for communication with customer Ease of change and control Perfect visibility what is being postponed, for how long, why mateusz@srebrny.net, Warsaw, March 23-24, 2010
  7. 7. Sprints and reviews Provider demonstrates progress after each sprint Verification of mutual understanding of requirements Visibility what is done, and what is not Measure of progress: working software (potentially shippable) Communication not restricted to static requirements list mateusz@srebrny.net, Warsaw, March 23-24, 2010
  8. 8. Backlog items size estimation The provider estimates during short sessions with the customer Synchronisation of understanding of requirements Easy to predict the amount of work that can be done within a sprint Updates of the estimations mateusz@srebrny.net, Warsaw, March 23-24, 2010
  9. 9. Retrospectives Every sprint provider analyses: what was going on, how to improve performance of the next sprint Customer sees the provider uses his best effort and knowledge More trust between customer and provider mateusz@srebrny.net, Warsaw, March 23-24, 2010
  10. 10. Conclusion Visibility, flexibility, trust and cooperation In Poland it's rather a contract with static requirements and penalties than cooperation and maximisation of efficiency and profit Scrum is designed for small teams / projects Scrum does scale (Google, Microsoft, Nokia), but there is not much ready-to-use techniques to achieve that mateusz@srebrny.net, Warsaw, March 23-24, 2010
  11. 11. The end http://en.wikipedia.org/wiki/Scrum_(development) http://scrumalliance.org/ http://agilemanifesto.org/ Questions? Comments? Remarks? Thank you for your attention mateusz@srebrny.net, Warsaw, March 23-24, 2010
  12. 12. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. mateusz@srebrny.net, Warsaw, March 23-24, 2010

×