Scrum is an agile framework for managing product development. It involves self-organizing cross-functional teams who break their work into actions that can be completed within timeboxed iterations, called sprints, no longer than one month to build usable software. Key roles include the Product Owner who manages priorities from stakeholders, the Scrum Master who ensures Scrum is followed, and the Development Team. Artifacts include the Product Backlog of features, Sprint Backlog of tasks, and increments of functionality delivered each sprint. The process consists of sprints, daily stand-ups, sprint planning and review meetings, and retrospectives for continuous improvement.
What is SCRUM?SCRUMis 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 Timeline1986 - Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach for product development1991 - 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
Sprint Planning isa one-day meeting timeboxed to 8 hours that initiates every Sprint.
20.
Sprint - A30 calendar day time box, where teamdevelops product backlog items selected into a shippable product.
21.
Burn Down Chart work remaining across time in asprint, a release, or a product.
22.
Done – Workcompleted and agreed by all stake holders and conforms to organization processes , conventions and guidelinesImage - http://www.sxc.hu/profile/svilen001
23.
Daily Scrum Meetingis 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 Meetingis 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.
Hurray! Finally thispresentation is over Images by www.sxc.huwww.dreamstime.com
28.
About SriramSriram has15 years of information technology industry experience, where he has played various roles in delivering multimillion dollar projects. You can reach him at: Mobile : 8122597519Mail :ssram37@gmail.comwww : www.iamsriram.comTwitter : www.twitter.com/sriramsLinkedIn : www.linkedin.com/in/ssramFB : www.facebook.com/ssram37