Learning Objectives • Increase productivity, collaboration, and accountability. • Improve the quality of student developed products.
Scrum is one application of Agile product development. The Principle: Agile Manifesto • We are uncovering better ways of developingproductsby doing it and helping others do it.Through this work we have come to value: • Individuals and interactions over processes and tools • Working products over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan • That is, while there is value in the items onthe right, we value the items on the left more.
Why Scrum? Yahoo’s Survey of Teams that Switched to Scrum • Improved Productivity (Productivity up 38%) • Improved Morale (52% yes vs. 9% no) • Improved Accountability/Ownership (62% yes vs. 6% no) • Improved Collaboration/Cooperation (81% yes vs. 1% no) • Improved quality (44% yes vs. 10% no) • 85% of new users preferedto continue using Scrum
Roles Committed Involved
People: The Involved • Users • Stakeholders • Consulting Experts • Everyone else who is involved, engaged and interested in the project • They are not part of the Scrum process. Their ideas, desires and needs are taken into account, but are not in any way affecting or distorting the Scrum project. • Classroom: Teachers, friends, parents, administrators,…
People: The Committed • Scrum team • Product Owner • Scrum master • Rest of the team • Committed to • The project and the scrum process • Improving the product • They have ‘their bacon in the line.’ • Classroom: The student team. More details on the roles of Product Owner and Scrum Master later.
People: Product Owner (Quality Control) • Has a clear vision and expresses it well to the rest of the team. • Represents the client to the team. • Responsible for maintaining the Product Backlog (more on this later) • Helps keep the team focused • Good communicator and motivator. • Maximizes the Return on Investment (ROI) of the team. • Decides when something is ‘Done.’
People: Scrum Master (Team Leader) • Servant Leader • Conductor of Ceremonies (Meetings) • Daily Scrum • Sprint Planning • Sprint Reviews • Sprint Retrospectives • Monitoring and Tracking • Resolve Impediments/ Conflicts • Shields the Team (from Chickens)
People: Scrum Team • A Scrum Team is a collection of individuals working together to deliver the requested and committed product increments. • Scrum Master • Product Owner • All the pigs.
People: Team Summary • Chickens • Pigs • Product Owner • Quality Control • Visionary • Maximize ROI • Scrum Master • Daily Manager • Resolves conflicts • Team • Will commit to and create a shippable product by the end of the Sprint. • The Process…
Scrum Process Yesterday Today In the Way 1) A Project Begins “We want to build a robot to …” 5) Sprint Review: Demonstrate potentially shippable product. 2) Product Owner with help from the team, prioritizes list of tasks into a ‘Product Backlog.’ 6) Sprint Retrospective What went well? What did not go well? What changes need to occur? 3) Scrum Master leads team in the Sprint Planning Meeting to create a Sprint Backlog. A list of top Product Backlog entries that can be completed in the next Sprint.
Tracking Progress Prioritized list of tasks Prioritized list of tasks the team has committed to complete in this Sprint. The Tasks currently in progress. Approved by the Product Owner After the Sprint answer the questions: What went well? What did not go well? What can we do better?
The Ceremonies • Sprint Planning • Sprint Review • Sprint Retrospective • Dailey Scrum Meeting
Sprint Planning Meeting • During the Sprint Planning meeting the team agrees to the stories (tasks) that they believe they can complete within the sprint. • Officially the sprint backlog is a closed list – once its complete no more tasks can be added to it (unless the team identifies missing tasks). • A closed list provides the team with the psychology benefit of seeing a shrinking pile vs. the normal ever growing stack of features and bugs. • It provides an achievable short term goal allowing the long term to be left in the background.
Sprint Review • Team presents what it accomplished during the sprint • Informal • Whole team participates • Invite the World. (Pigs and Chickens)
Sprint Retrospective • Whole team gathers to discuss: Scrum master, product owner, scrum team and possibly customers and others. • What went well? • What did not go well? • What changes should there be for the next sprint?
Daily Scrum Meeting • Stand up meeting • Lead by Scrum Master • Whole team, but no chickens. • Each person on the team shares • What was accomplished yesterday? • What you intend to accomplish today? • What is getting in the way of your success?
Applying it to My Classroom (Robotics) • Part 1. Pre-Scrum: Determined Initial Design Direction • –Defined what the robot is to do • –Set Specifications and Constraints • –Researched and Brainstormed Solutions • –Selected the Original Design Direction • Part 2. Develop the product in Teams using Scrum • Establish Roles • Apply Process to developing a robot for competition.