Capasso Cheetham DAILY Kurtz PLANET SCRUM & AGILE DEVELOPMENT SCRUM
“A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.”
A SCRUM OVERVIEW
¡ History: Developed in the late 80s & early 90s ¡ Features: Lightweight Simple to Understand, Difficult to Master The Sprint Product Backlog Sprint Backlog Scrum Roles ¡ Makes clear the relative efficacy of your product management and development practices
Scrum follows an empirical approach, accepting that a problem cannot be fully understood or defined and instead focusing on maximizing the team’s ability to deliver quickly and respond to changing requirements. HISTORY
¡ 1986: Hirotaka Takeuchi & Ikujiro Nonaka § Describe a new approach to commercial product development § “Holistic” or “Rugby” approach § One cross-functional team “tries to go the distance as a unit, passing the ball back and forth.” [1] ¡ Early 1990’s: Ken Schwaber & Jeff Sutherland § Advanced Development Methods & Easel Corporation § First to refer to method using single word ‘Scrum’ ¡ 1995: Schwaber & Sutherland publish Scrum Methodology ¡ 2001: Schwaber & Mike Beedle publish Agile Software Development with Scrum
2012: Yahoo!, a $50 billion company, has one the largest agile implementations in the world, encompassing over 150 teams containing over 1,500 employees. SIMPLIFIED PROCESS
*Permission is granted to copy, distribute and/or modify image under the GNU Free Documentation License v1.2. SPRINT
¡ Basic unit of development ¡ “timeboxed” effort of constant length [2] § 1 week – 1 month ¡ Start: Planning Meeting § Identify goal and action items for the sprint ¡ Finish: Review Meeting § Progress is reviewed and lessons for next sprint are identified ¡ Each sprint produces finished portions of the product ROLES
¡ Core Roles: § Product Owner § Owns product backlog § Responsible for delivering value Scrum Master to business § Scrum Master Product Owner Development Team § Ensures scrum process is applied correctly § Responsible for removing any obstacles hindering delivery of sprint goals § Development Team § Owns sprint backlog § 3-9 people § Self-organizing ¡ Ancillary Roles: § Stakeholders & Managers COMPLETE PROCESS[7] QUICK TERMINOLOGY[3]
¡ Sashimi § A report that a task has been completed. ¡ Epic § Group of stories that have not been analyzed enough to the point where they can be used in the sprint. ¡ Abnormal Termination § Product owner cancels the spring. ¡ Spike § Timebox to research a topic and/or create a small prototype. MEETINGS[4]
¡ During each day of a sprint teams hold a meeting called “the daily scrum” ¡ Meetings should kept to a 15 timebox. ¡ Daily scrum is not a problem solving meeting. ¡ Three questions should be answered by each team member: § What did you do yesterday? § What will you do today? § Are there any impediments in your way? ¡ Used to keep the team up to date on what progress is being made and what still needs to be done. SCRUM TOOLS[5]
¡ OnTime ¡ Scrumwise ¡ SonicAgile ¡ Agile Buddy ¡ AgileSoup ¡ Redmine ¡ BaseCamp VALUE ADDED[6]
¡ Staying in contact with customer keeps it likely that the end product will be what the customer needed rather than wanted. ¡ Scrum is focused on quick deliverables which speeds up the software development process substantially. ¡ Developers are happier and are given more room for creativity. METHODOLOGY COMPARISON[7] WORKS CITED
1. Takeuchi, Hirotaka; Nonaka, Ikujiro (January – February 1986). “The New Product Development Game” Harvard Business Review. Retrieved June 9, 2010. 2. Sprint Planning (January – February 2009). Sprint Planning Rules. Retrieved March 30, 2009. 3. Schwaber, Ken; Beedle, Mike (2002). Agile software development with Scrum. Prentice Hall. ISBN 0-13-067634-9. 4. http://www.mountaingoatsoftware.com/scrum/daily-scrum 5. http://agilescout.com/best-agile-scrum-tools/ 6. http://stackoverflow.com/questions/422876/one-advantage-an- agile-approach-using-scrum-has-over-waterfall-approaches 7. Sutherland, Jeff. The Scrum Papers: Nut, Bolts, and Origins of an Agile Framework. Version 1.1 – April 2, 2012.