Scrum for IT Project Outsourcing


Published on

Published in: Business, Technology
1 Like
  • Thank You #stevendearborn
    Are you sure you want to  Yes  No
    Your message goes here
  • This is one of the best Agile Scrum overviews I have read or participated in.

    The last slide is very good; it describes the immutability of Agile Scrum practices. I have seen and heard of a lot of projects/products 'cherry-picking' Agile parts, then expecting the chosen ones to work in isolation. They don't. This easily gets confused with the idea that Agile is typically tailored to meet business objectives which are specific to an organization or endeavor. They should. There is a difference here which comes from experienced practitioners.
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Scrum for IT Project Outsourcing

  1. 1. Agile Project Management Scrum Masoud Bolhassani PMP,PSM I
  2. 2. Software Development Iterative Incremental Agile
  3. 3. Iterative development Draft
  4. 4. Incremental development Chapter One Chapter Two
  5. 5. Agile development Agile software development employs both iterative and incremental development techniques . In any iteration, you should focus only on the functionality described by the user stories in that iteration. You should pay no attention to other user stories, not yet scheduled, which may impact how you choose to implement the current user stories. In practice, during the coding of an iteration, you often need to change or refactor code from previous iterations to accommodate new functionality.
  6. 6. Agile
  7. 7. Summary  Scrum Overview  Scrum Theory  Empirical process  Scrum framework  Roles : Scrum Team  Events : Meeting, …  Artifacts : Backlog Item , …  rules  CSS Scrum Model
  8. 8. Scrum Overview  Scrum (n):  A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.  Scrum is not a process or a technique for building products  Scrum is:  Lightweight  Simple to understand  Extremely difficult to master
  9. 9. Scrum Theory  Scrum is founded on empirical process control theory, or empiricism.  Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: 1. Transparency 2. Inspection 3. Adaptation.
  10. 10. Implementation of empirical process  Transparency  A common language referring to the process must be shared by all participants;  A common definition of “Done”  Inspection  Adaptation An adjustment must be made as soon as possible to minimize further deviation.
  11. 11. Rules Roles Events Artifacts Scrum framework
  12. 12. Role; The Scrum Team  Scrum Teams are self-organizing and cross-functional.  The team model in Scrum is designed to optimize 1. Flexibility 2. Creativity 3. productivity. Scrum Team
  13. 13. The Product Owner  The Product Owner is responsible for maximizing the value of the product and the work of the Development Team.  The Product Owner is the sole person responsible for managing the Product Backlog.
  14. 14. Product Backlog Item, PBI A Product Backlog is a list of top-level requirements that are usually associated with a single Project or Product.
  15. 15. Theme Epic User Story User Story User Story Epic User Story User Story Feature Bug Technical work Knowledge acquisition PBI Themes- very top-level requirements or objectives e.g. A new website Epics – very large user stories e.g. A new website section User Stories – an Independent, Negotiable, Valuable, Es timatable, Small, Testable (“INVEST”) piece of functionality which are short, simple descriptions of the desired functionality told from perspective of the user
  16. 16. Product Backlog Sample
  17. 17. PBI Title Business Value Story Points ROI Planning Scope Current Status Work Remaining History File Attachments Type
  18. 18. Product Backlog Database
  19. 19. CSS Scrum Model IT TeamCompany Sub Contractor (Use Agile Method : Scrum)  The Product Owner is the sole person responsible for managing the Product Backlog. The Product Owner is one person, not a committee.
  20. 20. Scrum Events Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum Scrum uses time-boxed events, such that every event has a maximum duration 1. Sprint Planning Meeting 2. Daily Scrum 3. Sprint Review 4. Sprint Retrospective
  21. 21. Scrum Process Sprint 1- Sprint Planning Meeting (2-4 Hours) Part One: What will be done this Sprint? Part Two: How will the chosen work get done? 1 2- Daily Scrum Meeting (15 m) What has been accomplished since the last meeting? What will be done before the next meeting? What obstacles are in the way? 2 3 - Sprint Review (1-2 Hours) Release “Done” Backlog 3 4 - Sprint Retro (1-2 Hours) 4
  22. 22. 24 Product Owner Responsibilities It’s called “the snowman model” (see the snowman?)
  23. 23. 25 Product Owner Responsibilities Organize the backlog into incremental releases Specify objective acceptance criteria for stories •Communicate Business Goals, Customer Goals, End User Goals •Coordinate involvement of SMEs, users, and business stakeholders •Coordinate with other product owners to insure coherence of product and releases Create and maintain the product backlog Participate daily Be available to answer questions and clarify details on user stories Verify stories are done based on acceptance criteria Evaluate product at end of Sprint and add or remove stories from backlog as necessary
  24. 24. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a backlog item’s priority must convince the Product Owner. The Product Owner may do the work, or have the Development Team do it. However, the Product Owner remains accountable. The Product Owner is one person, not a committee. For the Product Owner to succeed, the entire organization must respect his or her decisions. the Development Team isn’t allowed to act on what anyone else says.
  25. 25. The Development Team IT TeamCompany Sub Contractor OR Development Team Development Team
  26. 26. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Only members of the Development Team create the Increment. They are • self-organizing • cross-functional • Development Team as a whole
  27. 27. The Scrum Master The Scrum Master is responsible for ensuring Scrum is understood and enacted Scrum Master Service to the Product Owner Scrum Master Service to the Development Team Scrum Master Service to the Organization
  28. 28. Scrum Artifacts  Product Backlog  Monitoring Progress Toward a Goal  Sprint Backlog  Monitoring Sprint Progress  Increment
  29. 29. Definition of “Done” This is the “Definition of Done” for the Scrum Team and is used to assess when work is complete on the product Increment. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.
  30. 30. Conclusion Scrum is free and offered in this guide. Scrum’s roles, artifacts, events, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.
  31. 31. Ref: Jeff Patton, Agile Product Design, Masoud Bolhassani PMP,PSM I 2012