Introduction to Scrum methodology

1. Introduction to SCRUM By Sriram Srinivasan www.iamsriram.com

2. What is SCRUM SCRUM Timeline People Artifacts Process

3. What is SCRUM? SCRUM is an agile methodology for developing software. The term is named for a formation in rugby, which is used to restart the game after an event that causes play to stop, such as an infringement.

4. SCRUM Timeline 1986 - Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach for product development 1991 - DeGrace and Stahl, in “Wicked Problems, Righteous Solutions,” referred to this approach as Scrum, a rugby term mentioned in the ‘ article by Takeuchi and Nonaka. 1995 - Sutherland and Schwaber jointly presented a paper describing Scrum at OOPSLA ’95 in Austin, TX, its first public appearance. 2001 - Schwaber teamed up with Mike Beedle to describe the method in the book “Agile Software Development with Scrum.” Source – http://en.wikipedia.org/wiki/Scrum_%28development%29

5. People

6. Product Owner is responsible for managing the Product Backlog and represents stakeholders in the project.

7. Stakeholder is someone with an interest in the outcome of the project.

8. Team - A group of people that is responsible for managing itself to develop software

9. SCRUM MASTER is responsible for making sure SCRUM is correctly implemented and the goal of using SCRUM is achieved.

10. Artifacts

11. Product Backlog - List of project requirements with estimates. This will change due to business and technology changes

12. Product Backlog Items are Functional & Nonfunctional requirements and issues, which are prioritized in order of importance

13. Sprint Backlog - A list of tasks that defines a team’s work for a Sprint.

14. Sprint Backlog Task is one of the task team needs to execute to turn product backlog into working functionality

15. Process

16. Time box is a period of time in which a planned event or meeting occurs and cannot be exceeded.

17. Increment – Product functionality developed in various stages. Each iteration results in incremental development of functionality

18. Iteration is a cycle within a project.

19. Sprint Planning is a one-day meeting time boxed to 8 hours that initiates every Sprint.

20. Sprint - A 30 calendar day time box, where team develops product backlog items selected into a shippable product.

21. Burn Down Chart work remaining across time in a sprint, a release, or a product.

22. Done – Work completed and agreed by all stake holders and conforms to organization processes , conventions and guidelines Image - http://www.sxc.hu/profile/svilen001

23. Daily Scrum Meeting is a daily status meeting held for a short period of time where, team will discuss about the work completed and planned plus let scrum master know about any impediments that needs to be removed.

24. Sprint Review Meeting a short meeting where completed product is demonstrated to and reviewed by stakeholders

25. Sprint Retrospective Meeting is a short meeting scheduled by the scrum master where just concluded sprint will be reviewed and learning‘s noted to be implemented in the next sprint.

26. SCRUM helps in achieving

27. Hurray! Finally this presentation is over  Images by www.sxc.hu www.dreamstime.com

28. About Sriram Sriram has 15 years of information technology industry experience, where he has played various roles in delivering multimillion dollar projects. You can reach him at: Mobile : 8122597519 Mail :ssram37@gmail.com www : www.iamsriram.com Twitter : www.twitter.com/srirams LinkedIn : www.linkedin.com/in/ssram FB : www.facebook.com/ssram37