Basic Scrum Framework

Licensed Under Creative Commons by Naresh Jain

Basic Scrum Framework

Control Chaos

Naresh [email protected]

1Tuesday, April 28, 2009

http://creativecommons.org/licenses/by-nc-sa/3.0/


http://agilefaqs.com/nareshjain.html


mailto:[email protected]

mailto:[email protected]


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 iterationScalableImproves moraleDisciplined approachTruth, Transparency, and Commitment






http://www.youtube.com/watch?v=UT4giM9mxHk

http://www.youtube.com/watch?v=UT4giM9mxHk


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”







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)











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







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







Scrum Values

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







Scrum in a Nutshell

Courtesy of Ken Schwaber








Scrum Terminologies







Scrum Terminologies

Sprint







Scrum Terminologies

Sprint

Product Owner







Scrum Terminologies

Sprint

Product Owner

Scrum Master







Scrum Terminologies

Sprint

Product Owner

Scrum Master

Product and Sprint Backlog







Scrum Terminologies

Sprint

Product Owner

Scrum Master


Scrum Teams







Scrum Terminologies

Sprint

Product Owner

Scrum Master


Scrum Teams

Daily Scrum Meetings







Scrum Terminologies

Sprint

Product Owner

Scrum Master


Scrum Teams


Sprint Planning Meetings







Scrum Terminologies

Sprint

Product Owner

Scrum Master


Scrum Teams


Sprint Planning Meetings

Sprint Review







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








►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









►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


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







Books and ResourcesAgile Software Development with Scrum Schwaber Agile Project Management with Scrum SchwaberScrum for the Enterprise SchwaberAgile Estimation and Planning CohnAgile Software Development MartinCollaboration Explained TabakaAgile Retrospectives Derby/LarsenAgile Project Management HighsmithAgile SW Development Ecosystems HighsmithAgile and Iterative Development LarmanIntegrating Agile Development in the Real World SchuhLeading Change or Our Iceberg is Melting KotterSoftware by Numbers Denne/HuangYahoo Group: Scrumdevelopmentwww.agilealliance.orgwww.scrumalliance.org






http://www.controlchaos.com/

http://www.controlchaos.com/

http://www.scrumalliance.org

http://www.scrumalliance.org

Basic Scrum Framework

Technology

Transcript of Basic Scrum Framework