Scrum Basics Prof. Casper Lassenius Aalto University
Goals of This Lecture Teach you Why you need a process for working in your projects Basics of the Scrum process Roles Process steps Terminology After this lecture You are able to participate in the Scrum game You know the basics of Scrum This lecture is based on Scrum Primer (Scrum Guide)
Scrum Process:
Scrum Roles
Scrum Team Scrum team = Team + Scrum Master + Product Owner
Product Owner Is responsible for maximizing return on investment, thus has the final authority Identifies product features Prioritizes the features Interacts regularly with the team, e.g. reviews the Sprint results Product Owner Product Manager Customer
The Team Develops the product and provides ideas to the Product Owner about how to make the product great 7 ± 2 people Is cross-functional (includes all expertise necessary to deliver the potentially shippable product each sprint) Is self-managing: high degree of autonomy and accountability Every team member is just a team member, no other roles
Scrum Master Helps the product group learn and apply Scrum to achieve business value Is part of the Scrum Team Is NOT the manager of the team members, NOR a project manager OR team lead Serves the team, e.g. helps to remove impediments, protects from outside interference Is a coach and teacher, especially Scrum principles and practices Who is the project manager in Scrum??
Scrum Process
Sprint / Iteration Time-boxed development cycles No more than 4 weeks, 2 weeks most common Never extended: ends exactly when planned, contents give flexibility The output of every sprint is: Potentially Shippable Product Increment, which means that item chosen for that sprint are Done System is integrated Fully tested End-user documented Potentially shippable
Product Backlog Is a prioritized list of customercentric features Everything that could be done by the Team ever in order of priority Includes items, e.g. new customer features, major engineering improvement goals, research work, (known defects) Includes effort estimates Is detailed appropriately Is regularly refined ( grooming ) = splitting, estimating, re-estimating items
Scrum Board
Release Planning No instructions given by Scrum Needed especially in case of a new product There Product Owner and Team shape a Scrum Product Backlog, including Planning the contents of the release Estimating, refining estimates Prioritizing May take a few days or a week Not needed in continuous product development, done by product backlog refinements in every sprint
Sprint Planning I Participants: Product Owner, Team, Scrum Master Goal: understanding WHAT the Product Owner wants and WHY they are needed Discussion of the goals context of the highest priority items PO explains Team asks questions
Sprint Planning II Participants: Team, Scrum Master (Product Owner reachable for questions) Focus on HOW to implement the items the Team decides to take on Team decides how much work it will complete! May contain: Estimating the team s capacity for the next sprint Overall design Selecting and splitting product backlog items into tasks building sprint backlog! Estimating items/tasks Selecting as many items team estimates they can realistically complete: sprint commitment / forecast
Daily Scrum Meeting Participants: Team, Scrum Master (Product Owner optional) Update and coordination between team members not a status reporting to anybody else Max 15 min Each member report to the other team members: What has been accomplished since the last meeting? What will be done before the next meeting? What obstacles are in the way? If discussion needed: follow-up meetings agreed and held afterwards
Sprint Review Participants: Team, Product Owner, Scrum Master, other stakeholders invited by the Product Owner Inspection and adaption related to the product increment of functionality What is going on with the product and team What is going on with the Product Owner and the market In-depth conversation Includes hands-on inspection of the real software running live
Sprint Retrospective Inspection and adaption related to the process and environment Participants: Team, Scrum Master, Product Owner (optional) Team discusses what s working and what s not working and agree on changes to try Usually the Scrum Master facilitates Different techniques, try different ones!
Tracking Progress Burndown / burn-up charts
Scrum Game
Preparations for the Scrum Game Register for the game! Make sure that before the game you know Basic steps of the Scrum process Scrum Roles Scrum terminology Material: This lecture Scrum Guide (link in MyCourses) Scrum Primer Come with an open mind we expect that it will be fun & you will learn a lot! In the game we will not teach you Scrum, but you will use Scrum!
Course Practicalities
Scrum Game Registration In GoogleDocs ScrumGame-Sheet 4 sessions, max. 36 persons per session 4 game teams per session, max. 9 persons per game team Try to get your whole team in the same session if not possible, the individuals can register to any session, and will be assigned to some game team in the beginning of the session Register as soon as you have a few members in your team you can change your registration later please, try to fill the first sessions first Participated already the previous year? some Scrum Masters need to play in their role in the Game a developer does not have to participate 2 nd time 9.9.2015
After the Previous Lecture 16 teams/131 persons (13*8 persons + 3*9 persons) CSE-E5600 students added in MyCourses to CSE-C2610 A topic by Nokia was added on 16.9. Link to GoogleDocs was sent by e-mail on 15.9. save it! update 1) your personal prefs and 2) your team s common prefs Flowdock (communication tool) link was sent by e-mail on 16.9. one person per team signs up, and invites other members 9.9.2015
Next Steps Add your prefs to the Student list immediately work times, work language, project topics, technologies Find a team Scrum Masters and developers contact each other based on prefs in GD teacher assigns the remaining developers to the teams on Tu 22.9. 13:00 make sure your Team ID is filled in GD, if you are in a team update your Favorite Team ID column before 22.9. 13:00 Register to a Scrum Game session as soon as you have a few members in your team Lecture on We 23.9. in T4 for Scrum Masters only, in English 9.9.2015