Using Scrum to Improve Teamwork, Communication, Quality and Speed

STEM Projects Over the Years

Partnering with Industry for Help Challenges Time Finding Right Match Who am I to ask…? What made it work STEM Fair summer 2014 organized by the South Metro- Salem STEM Partnership: A venue for meeting several people from industry in a short period of time Connected with Industry Partner: Max Arbow, ADP at the time

Goals for this session You will have a basic understanding of… –The Principle behind Scrum: Agile Manifesto –The People: Committed vs. Involved –The Plane: Hands on Example –The Process: From idea to product –The Potential: You can see how it could help you develop a quality product

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. Scrum is one application of Agile product development.

Why Scrum? Yahoo’s Survey of Teams that Switched to using 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 prefer to continue using Scrum

Some Companies that use Scrum

What is Scrum? Scrum is a way for teams to work together to develop a product. Product development, using Scrum, occurs in small pieces, with each piece building upon previously created pieces. Building products one small piece at a time encourages creativity and enables teams to respond to feedback and change, to build exactly and only what is needed.

From Industry to Classroom 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

Role: Product Owner Represents the Customer to the Scrum Team. Decides what will be built and in which order. (Organizes Product Backlog) Maximizes the Return on Investment (ROI) of the team. Decides when something is ‘Done.’ Class: Role rotates between team members.

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 distractions. Class: Runs the team meetings and helps eliminate impediments.

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 Class: Your Student team.

Scrum Process 1) A Project Begins “We want to build a robot to …” 2) Product Owner with help from the team, prioritizes list of tasks into a ‘Product Backlog.’ 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. 5) Sprint Review: Demonstrate potentially shippable product. 6) Sprint Retrospective What went well? What did not go well? What changes need to occur? Yesterday Today In the Way

Tracking Progress Product Backlog To do Sprint Backlog Doing (Tasks) Done (Tasks) Retrospective: End of Sprint Problems: Impediments Prioritized list of tasks Prioritized list of tasks the team has committed to complete in this Sprint. The Tasks currently in progress. After the Sprint answer the questions: What went well? What did not go well? What can we do better? Approved by the Product Owner

1)Yesterday 2)Today 3)In the way

Applying this to your Project In your Project PowerPoint include a slide that lists the tasks you intend to complete by 5/20/2016. (See next slide) Populate the To Do list with the tasks to be completed by the end of the Sprint. Continue to update your PowerPoint daily with What did you accomplish last class. What do you intend to accomplish this class. What is impeding you from succeeding. On 5/20/2016 you will conduct a Sprint Reflection demonstrating the tasks you have completed in the last Sprint. Your team will also conduct a Sprint Retrospective: What went well What did not go well What changes need to occur

Tracking Progress Product Backlog To do Sprint Backlog Doing (Tasks) Done (Tasks) Retrospective: End of Sprint Problems: Impediments Prioritized list of tasks Prioritized list of tasks the team has committed to complete in this by 5/20/2016 The Tasks currently in progress. After the Sprint answer the questions: What went well? What did not go well? What can we do better? Approved by the Product Owner

Sprints Reflection/Retrospectives 5/20/2016 6/3/2016 Seniors will present their final product on 6/7/2016