Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
Creating Flawless Multi-Screen Experiences for Your Current and Future Customers
Next
Download to read offline and view in fullscreen.

0

Share

Download to read offline

Scrum

Download to read offline

  • Be the first to like this

Scrum

  1. 1. When to use Scrum ?
  2. 2. When to use Scrum ? (Continuing …. . )
  3. 3.  Product owner  Scrum master  Scrum team (5-9 people)
  4. 4. Product Owner  Maintaining the product backlog Prioritizing Presentation of product backlog to the team  Participation in sprint planning and sprint presentation  Responsible for product vision and release management  Can follow sprint via Daily Scrum, Burndown chart and via Scrum Master
  5. 5. Scrum Team  Teams of 7 +/- 2 participants  Cross-functional  Best experts in the domain area  Maintains the sprint backlog  Self-organizing Team decides who shall do what They inspect and adapt as the sprint goes along  Have most of the powers during a sprint
  6. 6.  Responsible for the process  Responsible for optimizing the Scrum environment  Responsible for Daily Scrum  Runs Sprint Retrospective  Coach
  7. 7. 1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization. 2. Team determines how much time it has available to commit during the Sprint 3. Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan - Validates commitment by breaking down into tasks with time estimates - Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth.
  8. 8. Daily Scrum  Daily Scrum must not last more than 15 minutes  Held same place, same time, every working day  Participants can not be late  Anybody can come, but only the team and Scrum Master can speak  3 questions answered by each team member What did I do yesterday? What am I going to do today? What are my impediments?
  9. 9.  Definition of the system being developed.  Create A Product Backlog list is created containing all the requirements that are currently known.  The requirements are prioritized  The effort needed for their implementation is estimated.  The product Backlog list is constantly updated .
  10. 10.  Architecture is planned based on the current items in the Product Backlog.  In case of an enhancement to an existing system, the changes needed for implementing the Backlog items are identified along with the problems they may cause.  A design review meeting is held to go over the proposals for the implementation and decisions are made on the basis of this review.
  11. 11.  This phase is entered when an agreement has been made that the environmental variables such as the requirements are completed.  In this case, no more items and issues can be found nor can any new ones be invented. The system is now ready for the release and the preparation for this is done during the post-game phase, including the tasks such as the integration, system testing and documentation.
  12. 12. Scrum Process (Continuing .. . .)
  13. 13. Who is using Scrum?  Yahoo  Sun  Simens  Nokia  Philips  BBC  IBM  US Federal Reserve  SAP  H P  Motorola  TransUnion  Google  Microsoft
  14. 14. Scrum Core Ideas – Everything is time-boxed. – Inspect & Adapt. – You can-not plan everything. – Fail early. – Shippable product at the end of every iteration/sprint. – Iterative development. – Cross-functional teams. – Self-organizing teams. – Team owns the sprint backlog.
  15. 15. Thank You 

Views

Total views

247

On Slideshare

0

From embeds

0

Number of embeds

5

Actions

Downloads

2

Shares

0

Comments

0

Likes

0

×