Basic Scrum Framework
3 likes1,597 views
The document discusses Scrum, an agile project management framework. It originated from rugby and was later developed by Takeuchi and Nonaka for product development. Scrum aims to control chaos by emphasizing monitoring progress and adapting frequently. It uses short iterations called sprints and emphasizes commitment, focus, openness, respect and courage among teams. Key roles in Scrum include the Product Owner who prioritizes features, the Scrum Master who facilitates the team, and cross-functional teams who do the work.
Basic Scrum Framework
- 1. Licensed Under Creative Commons by Naresh Jain Basic Scrum Framework Control Chaos Naresh Jain [email protected] 1Tuesday, April 28, 2009
- 2. Licensed Under Creative Commons by Naresh Jain What is Scrum? An Agile Project Management framework : A wrapper for existing engineering practices A team-based approach Handles conflicting interests and needs Improves communications and maximizes cooperation Early detection and removal of obstacles Maximizes productivity Multiple, frequent feature-driven planning activities Produces potentially shippable functionality at each iteration Scalable Improves morale Disciplined approach Truth,Transparency, and Commitment 2Tuesday, April 28, 2009
- 3. Licensed Under Creative Commons by Naresh Jain Scrum Origin Rugby Hirotaka Takeuchi & Ikojuri Nonaka “The New New Product Development Game” - Harvard Business Review (Jan/Feb 1986) Companies need Speed and Flexibility Borland Quattro Pro paper by Jim Coplien Complex Adaptive Systems theory, iRobot using Prof. Rodney Brooks subsumption architecture 1995: Mike Beedle and Ken Schwaber Goldratt's ToC and focus on “muri, mura, and mudah” 3Tuesday, April 28, 2009
- 4. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with 4Tuesday, April 28, 2009
- 5. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with Ziv's law - specifications will never be fully understood. 4Tuesday, April 28, 2009
- 6. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with Ziv's law - specifications will never be fully understood. Humphrey's law - the user will never know what they want until after the system is in production (maybe not even then) 4Tuesday, April 28, 2009
- 7. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with Ziv's law - specifications will never be fully understood. Humphrey's law - the user will never know what they want until after the system is in production (maybe not even then) Wegner's lemma - an interactive system can never be fully specified nor can it ever be fully tested.This is the software analogy to Godel's theorem. 4Tuesday, April 28, 2009
- 8. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with Ziv's law - specifications will never be fully understood. Humphrey's law - the user will never know what they want until after the system is in production (maybe not even then) Wegner's lemma - an interactive system can never be fully specified nor can it ever be fully tested.This is the software analogy to Godel's theorem. Langdon's lemma - software evolves more rapidly as it approaches chaotic regions (taking care not to spill over into chaos) 4Tuesday, April 28, 2009
- 9. Licensed Under Creative Commons by Naresh Jain Scrum is Designed to deal with Ziv's law - specifications will never be fully understood. Humphrey's law - the user will never know what they want until after the system is in production (maybe not even then) Wegner's lemma - an interactive system can never be fully specified nor can it ever be fully tested.This is the software analogy to Godel's theorem. Langdon's lemma - software evolves more rapidly as it approaches chaotic regions (taking care not to spill over into chaos) Any association of predictive or defined processes with Scrum is an exercise in futility. - Jeff 4Tuesday, April 28, 2009
- 10. Licensed Under Creative Commons by Naresh Jain Controlled Chaos Scrum emphasizes on project management De-emphasis command-and-control management approach There is a strong emphasis on monitoring (features delivered) and adjusting according to the results (Inspect and Adapt) The aim is to find a balance between allowing the business to change their mind and the development team to be able to get work done on a stable scope 5Tuesday, April 28, 2009
- 11. Licensed Under Creative Commons by Naresh Jain ScrumValues Commitment. Be willing to commit to a goal. Scrum provides people all the authority they need to meet their commitments Focus. Do your job. Focus all of your efforts and skills on doing the work that you have committed to doing. Don’t worry about anything else Openness. Scrum keeps everything about a project visible to everyone Respect. Individuals are shaped by their background and their experience. It is important to respect the different people who comprise a team. Courage. Have the courage to commit, to act, to be open and to expect respect 6Tuesday, April 28, 2009
- 12. Licensed Under Creative Commons by Naresh Jain Scrum in a Nutshell Courtesy of Ken Schwaber 7Tuesday, April 28, 2009
- 13. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies 8Tuesday, April 28, 2009
- 14. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint 8Tuesday, April 28, 2009
- 15. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner 8Tuesday, April 28, 2009
- 16. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master 8Tuesday, April 28, 2009
- 17. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog 8Tuesday, April 28, 2009
- 18. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog Scrum Teams 8Tuesday, April 28, 2009
- 19. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog Scrum Teams Daily Scrum Meetings 8Tuesday, April 28, 2009
- 20. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog Scrum Teams Daily Scrum Meetings Sprint Planning Meetings 8Tuesday, April 28, 2009
- 21. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog Scrum Teams Daily Scrum Meetings Sprint Planning Meetings Sprint Review 8Tuesday, April 28, 2009
- 22. Licensed Under Creative Commons by Naresh Jain Scrum Terminologies Sprint Product Owner Scrum Master Product and Sprint Backlog Scrum Teams Daily Scrum Meetings Sprint Planning Meetings Sprint Review 8Tuesday, April 28, 2009
- 23. Licensed Under Creative Commons by Naresh Jain Key Scrum Roles and Responsibilities 9Tuesday, April 28, 2009
- 24. Licensed Under Creative Commons by Naresh Jain Key Scrum Roles and Responsibilities Product Owner ► Defines the features of the product, decides on release date and content ► Is responsible for the profitability/value of the product (ROI) ► Prioritizes features according to market and/or user value ► Can change features and priority every 30 days ► Accepts or rejects work results 9Tuesday, April 28, 2009
- 25. Licensed Under Creative Commons by Naresh Jain Key Scrum Roles and Responsibilities ► Ensures that the team is fully functional and productive ► Enables close cooperation across all roles and functions and removes barriers ► Shields the team from external interferences ► Ensures that the process is followed. Invites to daily scrum, iteration review and planning meetingsScrum Master Product Owner ► Defines the features of the product, decides on release date and content ► Is responsible for the profitability/value of the product (ROI) ► Prioritizes features according to market and/or user value ► Can change features and priority every 30 days ► Accepts or rejects work results 9Tuesday, April 28, 2009
- 26. Licensed Under Creative Commons by Naresh Jain Key Scrum Roles and Responsibilities ► Ensures that the team is fully functional and productive ► Enables close cooperation across all roles and functions and removes barriers ► Shields the team from external interferences ► Ensures that the process is followed. Invites to daily scrum, iteration review and planning meetingsScrum Master Product Owner ► Defines the features of the product, decides on release date and content ► Is responsible for the profitability/value of the product (ROI) ► Prioritizes features according to market and/or user value ► Can change features and priority every 30 days ► Accepts or rejects work results Team ► Cross-functional, seven plus/minus two members ► Selects the iteration goal and specifies work results ► Has the right to do everything within the boundaries of the project guidelines to reach the iteration goal ► Organizes itself and its work ► Demos work results to the end-user and stakeholders 9Tuesday, April 28, 2009
- 27. Licensed Under Creative Commons by Naresh Jain Books and Resources Agile Software Development with Scrum Schwaber Agile Project Management with Scrum Schwaber Scrum for the Enterprise Schwaber Agile Estimation and Planning Cohn Agile Software Development Martin Collaboration Explained Tabaka Agile Retrospectives Derby/Larsen Agile Project Management Highsmith Agile SW Development Ecosystems Highsmith Agile and Iterative Development Larman Integrating Agile Development in the Real World Schuh Leading Change or Our Iceberg is Melting Kotter Software by Numbers Denne/Huang Yahoo Group: Scrumdevelopment www.agilealliance.org www.scrumalliance.org 10Tuesday, April 28, 2009