Slide 1

Slide 2 1 1 Test the Scrum Knowledge of your team. Play by the rules of Jeopardy Play in two teams Assign a score keeper All answers have to be in the form of a question Once you have completed all of the main questions, you select Final Question and decide how much you team wants to wager. The arrow icon is the correct answer: The home icon brings you back to the main page: This game is the Day 2 Review from our Scrum Master Certification Training: http://AgileProjectManagementTraining.com http://AgileProjectManagementTraining.com Slide 3 2 2 Final Question Product Management Scrum Roles Scrum Events Potpourri 100 200 300 400 500 Slide 4 3 3 May be difficult to understand relationship between stories Not suitable for requirements traceability (if required by process) Can be difficult scaling to large teams Slide 5 4 4 Why not to use User Stories? Slide 6 5 5 Agreement between customer and developer to have a conversation. Slide 7 6 6 What are User Stories? Slide 8 7 7 Independent Negotiable Valuable Estimable Small Testable Slide 9 8 8 What does INVEST stand for? Slide 10 9 9 User interviews Prototyping Questionnaires Observation Story-writing workshops Slide 11 10 What are techniques for gathering User Stories? Slide 12 11 Fictitious users who help define a system Slide 13 12 What are Personas? Slide 14 13 Champion of Scrum within the Organization Slide 15 14 Who is the Scrum Master? Slide 16 15 Establishes the product vision with stakeholders Slide 17 16 Who is the Product Owner? Slide 18 17 Provides all project status reporting Slide 19 18 Who is the Scrum Master? Slide 20 19 Self-organizes/self-assigns Slide 21 20 Who is the Development Team? Slide 22 21 Creates the project plan and dashboard report. Slide 23 22 What role is not defined by Scrum? Slide 24 23 15 minutes every day Slide 25 24 What is the Daily Scrum? Slide 26 25 Product Vision Product Roadmap Release Plan Sprint Plan Daily Plan Slide 27 26 What is the Product Lifecycle in Scrum? or What is Progressive Elaboration? Slide 28 27 Inspect and adapt Be transparent The Art of Possible Self-organizing teams Slide 29 28 What are core principles of Scrum? Slide 30 29 Sprint Planning Sprint Duration Daily Scrums Sprint Review Sprint Retrospective Slide 31 30 What components of Scrum are time-boxed? Slide 32 31 Most often the biggest change Full of Scrumbuts Highlights and exacerbates existing problems Slide 33 32 What are challenges of the self-organizing team? Slide 34 33 Tracks work remaining Slide 35 34 What is a burndown chart? Slide 36 35 Face-to-face Osmotic communication Active listening Distributed teams Slide 37 36 What are the best ways to communicate on Agile teams? Slide 38 37 The list of activities (coding comments, unit testing, integration testing, release notes, design documents, etc.) which supports the expected business value. Slide 39 38 What is the Definition of Done? Slide 40 39 Define the target of change Identify which are driving and restraining forces Analyze the forces to identify which can be changed Create an action plan to make the changes to the forces Slide 41 40 What is a Force Field Analysis? Slide 42 41 Easy to read Can be understood at a glance Can change frequently Easy to manage Slide 43 42 What are Information Radiators? Slide 44 43 Please determine your wager with your team. Topic: Estimating Slide 45 44 Each team member sequences a subset of the product backlog from smallest to largest user story Slide 46 45 What is Affinity Estimating? Slide 47 Copyrighted material. 2011 46