• Like
  • Save
Scrum - a lightweight customer-provider environment
Upcoming SlideShare
Loading in...5
×
 

Scrum - a lightweight customer-provider environment

on

  • 383 views

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

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

Statistics

Views

Total Views
383
Views on SlideShare
378
Embed Views
5

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 5

http://www.linkedin.com 2
https://www.linkedin.com 2
http://agiletrainers.pl 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum - a lightweight customer-provider environment Scrum - a lightweight customer-provider environment Presentation Transcript

    • Scrum – a lightweight customer-provider environment Mateusz Srebrny <mateusz@srebrny.net> II konferencja ”Zarządzanie Projektami IT” Warsaw, March 23-24, 2010
    • 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
    • '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
    • Scrum Management inside a small team Management of communication between customer and provider mateusz@srebrny.net, Warsaw, March 23-24, 2010
    • 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
    • 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
    • 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
    • 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
    • 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
    • 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
    • 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
    • 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