Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
7. Planning Coupons Returns Sprint backlog Team builds Code the UI 2 hours Database design 1 hours Service + JUnit 1 hours DAO + DBUnit 1 hours Tasks Visual Design 4 hours JSP GUI 2 hours Service classes 2 hours Test cases 3 hours
8. Daily Scrum What did I do yesterday? What will I do today? Is there anything in my way? Max. 15 minutes
9. After the sprint Sprint Review Sprint Retrospective Present what team accomplished. Demo new features developed or underlying architecture. Invite whole world. Whole team discusses the results of last sprint Start doing Stop doing Continue doing
13. Scrum is Agile Delivers highest customer value first. Focuses on planning than on plan. Builds working software at rapid and repetitive pace. Builds Self-organizing teams
14. Need more info? Agile and Iterative Development: A Manager’s Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Development by Mike Cohn Lots of weekly articles at www.scrumalliance.org Slides created by Mike Cohn ( http://www.mountaingoatsoftware.com/presentations ) Scrum and XP from trenches: Henrik Kniberg, Free PDF at infoQ.com http://www.infoq.com/minibooks/scrum-xp-from-the-trenches
Daily Scrums are 15 minutes long. Why not then have a one-time 15 minute Scrum meeting to introduce Scrum. I prepared these slides after I failed to attract PMs in my organization to attend my first Scrum presentation which was 1.5 hours long. Now, I am using these slides to introduce Scrum to as many teams as possible in an attempt to spread the word. All these slides are based on the work of Mr. Mike Cohn, Mountain Goat Software. You are free to reuse these slides and modify it any manner. Srikanth Shreenivas (http://www.srikanthps.com, srikanthps@yahoo.com)