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.

Slides:



Advertisements
Similar presentations
Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.
Advertisements

Large + successful + government + IT + Agile = Census Leon Maritz June 2014.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agile Project Management with Scrum
© 2014 Point of Sail Implementing Agile/Scrum with a Tradition PMO… and Making it Work PMI Pittsburgh Chapter Meeting 12 June 2014.
RTC Agile Planning Component
Agile methods and techniques– some method comparisons Dave Parsons Mark Cranshaw.
NAUG NAUG Knowledge Evening – th February 2007.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Agile development By Sam Chamberlain. First a bit of history..
Introduction to Agile.
Agile Methodologies for Project Management By – Komal Mehta.
Bca.co.uk 01BMW Tender Inspect & Collect bca.co.uk Scrum…Buts Joy Kelsey Agile By Example Warsaw October 16 th and 17 th 2013.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
2/18/14 copyright Quazarconsulting.com.  Understand the role of the Product Owner  Understand the role of the Product Manager  Compare and contrast.
AgileCamp Presents: Scrum. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0.
1 Agile Methodology & Programming Ric Holt July 2009.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Current Trends in Systems Develpment
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
When is Agile the Best Project Management Method? Lana Tylka.
Software Process Models.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Process Presentation 27 th May 2010 Team BASH Sher Jun Tan, Rosh Sam Abraham, Sascha Morris, Waqas Khalid Lone, Rafael.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
SCRUM.
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Geoff Davis Software Development Leader Software Development at eWater.
Delivery Method: Online Duration: 180 Days Scrum Developer Certified (SDC™)  Participants will become familiar with the concepts, advantages, and challenges.
Introduction to Agile. Introduction Who is this guy?
 SBOK™ (SCRUM Body of Knowledge)  Student course workbook  Case study booklet  Scrum in a page  Scrum Product Owner Certified physical certificate.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
Software Quality Assurance Chip Ene, February 14, 2015.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.
Barnes & Noble Alonda Morgan. Agile UX Agile.
AGILE SCRUM METHODOLOGY
Scrum.
Scrum and TargetProcess
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
By: By: Agile Scrum Master Online Training.
Scrum MODULE 3 – Part 3.
Johanna Rothman Agile Team Measurements Chapter 12
How to Successfully Implement an Agile Project
Summarizing Our Models to Date
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Scrum in Action.
Presentation transcript:

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:

2 2 Final Question Product Management Scrum Roles Scrum Events Potpourri

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

4 4  Why not to use User Stories?

5 5  Agreement between customer and developer to have a conversation.

6 6  What are User Stories?

7 7  Independent  Negotiable  Valuable  Estimable  Small  Testable

8 8  What does INVEST stand for?

9 9  User interviews  Prototyping  Questionnaires  Observation  Story-writing workshops

10  What are techniques for gathering User Stories?

11  Fictitious users who help define a system

12  What are Personas?

13  Champion of Scrum within the Organization

14  Who is the Scrum Master?

15  Establishes the product vision with stakeholders

16  Who is the Product Owner?

17  Provides all project status reporting

18  Who is the Scrum Master?

19  Self-organizes/self-assigns

20  Who is the Development Team?

21  Creates the project plan and dashboard report.

22  What role is not defined by Scrum?

23  15 minutes every day

24  What is the Daily Scrum?

25  Product Vision  Product Roadmap  Release Plan  Sprint Plan  Daily Plan

26  What is the Product Lifecycle in Scrum? or  What is Progressive Elaboration?

27  Inspect and adapt  Be transparent  The Art of Possible  Self-organizing teams

28  What are core principles of Scrum?

29  Sprint Planning  Sprint Duration  Daily Scrums  Sprint Review  Sprint Retrospective

30  What components of Scrum are time-boxed?

31  Most often the biggest change  Full of Scrumbuts  Highlights and exacerbates existing problems

32  What are challenges of the self-organizing team?

33  Tracks work remaining

34  What is a burndown chart?

35  Face-to-face  Osmotic communication  Active listening  Distributed teams

36  What are the best ways to communicate on Agile teams?

37  The list of activities (coding comments, unit testing, integration testing, release notes, design documents, etc.) which supports the expected business value.

38  What is the Definition of Done?

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

40  What is a Force Field Analysis?

41  Easy to read  Can be understood at a glance  Can change frequently  Easy to manage

42  What are Information Radiators?

43 Please determine your wager with your team. Topic: Estimating

44  Each team member sequences a subset of the product backlog from smallest to largest user story

45  What is Affinity Estimating?

Copyrighted material