1. Scrum Science NGSS: Engineering, Technology, Applications of Science
Technology ISTE 1. Creativity and innovation
Technology ISTE 3. Communication and collaboration
Technology ISTE 4. Critical thinking, problem solving and decision making
Engineering: ENP01: Use effective communication skills with a variety of audiences.
Engineering: ENP03: Use technology such as computers and design software to solve engineering problems.
Engineering: ENP06: Use teamwork, critical thinking and problem solving skills to address complex problems in engineering.
Engineering: ENP08: Apply design principles and life-cycling methodology to create products, systems, and processes using appropriate technology. 1

2. A little background… Electrathon FRC $$$$$$ FLL Only to 14 FTC$$$ VEX2

3. Learning Objectives
Increase productivity, collaboration, and accountability.
Improve the quality of student developed products.

4. The Principle: Agile Manifesto
Scrum is one application of Agile product development.
The Principle: Agile Manifesto
We are uncovering better ways of developing products by 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 on the right, we value the items on the left more.

5. 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 prefered to continue using Scrum
Data from 5

6. Some Companies that use Scrum

7. Scrum Roles: Separating the Committed and the Involved
Image from 7

8. Roles Committed Involved
Image from 8

9. 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,… 9

10. 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. 10

11. 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.’
ROI = Return on Investment
Product Owner: The final word in prioritizing items, Quality Control, Product Manager. (One member from your team, each team member will have an opportunity to be the Product Owner)
Image: 11

12. 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)
Scrum Master: Represents Management, Servant Leader, responsible for ensuring Scrum is understood and implemented. (One member from your team. Each team member will have an opportunity to be the Scrum Master) 12

13. 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.
Scrum Team: Cross-functional group that is responsible for incrementing (finishing/improving) the product (Your robotics team)
Image: 13

14. People: Team Summary Chickens Pigs Product Owner Scrum Master Team
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…

15. Scrum Process 1) A Project Begins “We want to build a robot to …”
Yesterday
Today
In the Way
Scrum Process
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?
See more at:
Learn Scrum in 7 Minutes (
By TechExcel
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. 15

16. Tracking Progress Product Backlog To do Sprint Backlog Doing (Tasks)
Problems: Impediments
Product
Backlog
To do
Sprint Backlog
Doing
(Tasks)
Done (Tasks)
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?
Literacy/ Problem Solving
Retrospective: End of Sprint

17. The Ceremonies Sprint Planning Sprint Review Sprint Retrospective
Dailey Scrum Meeting

18. 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.

19. Sprint Review Team presents what it accomplished during the sprint
Informal
Whole team participates
Invite the World. (Pigs and Chickens)

20. 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?

21. 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?

22. 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.