Certified Scrum Master Class - Practice Test /Pre-class test
|
|
- Neil Hampton
- 7 years ago
- Views:
Transcription
1 Name: Your Score: Multiple Choice: For each of the following questions, circle the letter of the answer that best answers the question. 1. Which of the following is NOT an Agile Manifesto Value? A. Individuals and interactions over monitoring and control. B. Working software over comprehensive documentation. C. Customer collaboration over contract negotiations. D. Responding to change over following a plan. 2. Which of the following is an Agile Manifesto Principle? A. Business People and developers must work together daily throughout the project. B. Business People and developers must work together thru the Product Owner. C. Business People and developers must work together frequently throughout the project. D. Business People and developers must work together from early on the project. 3. Which of the following is NOT an Agile Manifesto Principle? A. Welcome changing requirements, early in development. Agile processes harness change for the customer's competitive advantage. B. Working software is the primary measure of progress. C. Simplicity--the art of maximizing the amount of work not done--is essential. D. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 4. Which of the following is NOT typically identified as a Scrum value? A. Trust B. Courage C. Commitment D. Respect 5. The pillars or foundations of Empiricism are? A. Transparency, Inspection, and Adaptation. B. Plan, Do, Check, Act. C. Commitment, Action, Inspection, and Correction. D. Hope, Honesty, and Hard-work.
2 6. After the third iteration of the project, it is found that the team is behind schedule per the release plan. What should the ScrumMaster do? A. Review task assignments and reconsider or reorganize the team to make the best use of the team with historical data about people and skill set. B. Bring the Executives in for an all-hands meeting with the project team to explain the priority and importance of the project so that the team get energized and motivated to work harder for the common goal. C. Communicate to the team members about the importance of the original schedule and importance of commitment. Be Present in the next Sprint Planning meeting to make sure team is pushed harder but in a healthy way to get more accomplished. D. Communicate to the team. Ask the team how and if this problem can be solved. Help the team in removing impediments. Help the team with administrative work. 7. An agile team is planning the tools they will use for the project. They are debating how they should show what work is in progress. Of the following options, which tool are they most likely to select? A. User story backlog B. Product roadmap C. Task board D. Work breakdown structure 8. In what order the team work on features in a project? A. The order specified by the project management office (PMO) B. The Product Owner and the Team collaboratively order the Product Backlog C. The Team order the Product Backlog D. The order specified by the project architect 9. What does incremental delivery mean? A. Team release working software to the testing group at the end of each sprint. B. Team deliver nonfunctional increments before every iteration retrospectives. C. Team improves and elaborates our agile process with each increment delivered. D. Team deploys functional increments of the product over the course of the project. 10. Which of the following is NOT a Scrum Role? A. Product Manager B. Team C. ScrumMaster D. Product Owner 11. Which of the following is NOT one of the responsibilitis of the ScrumMaster? A. Assigning tasks to team members at the Sprint Planning meeting. B. Helping the Team & Product Owner to follow Scrum values and practices. C. Facilitate the meetings in Scrum. D. Helping the organization learn about Scrum.
3 12. Which of the following is NOT one of the responsibility of the Product Owner? A. Accepting or Rejecting work product in a Sprint. B. Prioritizing Product Backlog items. C. Maximizing the business value. D. Making sure that the team and organization understand the Scrum framework. 13. Which of the following is NOT one of the characteristics of the Team? A. The Team in Scrum is Self Organizing. B. The Team selects how much work they can do in a Sprint. C. The Team tracks progress of the work in a Sprint. D. The Team prioritizes Product Backlog items in a Product Backlog. 14. The ideal size of the Team in Scrum is A. In Scrum, Team size does not matter. B. 5 to 9 people. C. No more than 100. D. 10 to 20 people. 15. Who is responsible for helping team and organization learn Scrum? A. Agile Coach or Scrum Coach. B. ScrumMaster. C. Scrum Manager ( previously known as Project Manager) D. The Team. 16. Who makes plans for Sprint including creating Tasks in a Sprint backlog? A. ScrumMaster. B. Product Owner. C. Technical team lead & Test team lead D. The Team. 17. The Sprint Backlog is A. Similar to the WBS ( Work breakdown structure) and is a list of tasks that the Project Manager creates to accomplish the Spring Goal. B. The list of tasks that the team created at the Sprint planning meeting in order to deliver the selected Product backlog items in the sprint according to the definition of done. C. The list of items that the team will not be able to complete during the sprint because of time and/ or resource constraints. D. A list of tasks that the Scrum Master created at the sprint planning meeting. The ScrumMaster reviews the list with the team but will be managed by only the Scrum Master. It is used to monitor and control the work defined in the Sprint. 18. How is the Role Project Manager defined in Scrum? A. ScrumMaster and Product Owner report to the Project Manager. B. The Project Manager manages the team, assigns work to the team, and oversees the team. C. There is no Project Manager defined in Scrum. D. Reports to the Product Owner and is responsible for managing the stakeholders.
4 19. What is expected at the end of the Sprint Planning meeting? A. A Sprint Goal & a Sprint Backlog enough for team to make plans for the sprint. B. Sprint backlog with Tasks and resource assignments. C. Sprint backlog with tasks & dependencies. D. Updated Project plan on Microsoft Project or similar tools. 20. Which output from a Sprint Planning Meeting provides the Development Team with a target and overarching direction for the Sprint? A. The sprint goal B. The release plan C. The sprint backlog D. The sprint task list 21. Which of the following may be used as a tool to assess the progress of a Sprint by an Agile team A. A task board B. WBS on MS Project C. User Stories in Product backlog D. Release plan 22. The Primary purpose of a Sprint Burn-down chart is A. To help see the amount of work remaining in a Sprint. B. To help see the amount of work completed in a sprint. C. To help the product owner to see if the team will meet the release date. D. To help the functional manager to assess the performance of a team member. 23. Which of the following is NOT a ceremony in Scrum? A. Sprint Planning meeting. B. The Daily Scrum meeting. C. The Sprint Test planning meeting. D. The Sprint Retrospective meeting. 24. Which of the following is NOT True about Sprint? A. The length of a Sprint 30 days or less. B. The length of the Sprint changes from Sprint to Sprint to accommodate large user stories. C. The team delivers Potentially shippable product increment in every sprint. D. Sprint is a fixed period of time. 25. Which of the following is NOT True about Sprint Planning meeting? A. Every Sprint Starts with a Sprint Planning meeting. B. The Product Owner, Scrum Master, and Technical and test leads attend the Sprint Planning meeting not all the team members. C. During the Sprint Planning meeting, the team and the team alone determine how much work the team can do in a Sprint. D. Sprint Planning meeting is time boxed meeting.
5 26. Which of the following is NOT True about Sprint Planning meeting? A. Sprint Planning meeting has two parts; first for the team to work with the Product Owner to determine what needs to get done and second for the team to determine how to get the work done. B. In the first part of the meeting, the Product Owner presents ordered Product Backlog items to the Development Team, and the whole Scrum Team collaborates to understand the work. C. In the second part of the meeting, the team does sufficient design and planning to be confident of completing the work during the Sprint. D. In the second part of the meeting, the ScrumMaster make sure that every task is assigned to the right team member in the team. 27. Which of the following is NOT True about how much work get done in a Sprint? A. It is solely up-to the team to decide how much work is undertaken in a Sprint. B. It is upto the Product Owner and the Release team to decide how much work is undertaken in a sprint to be in line with the Release plan and the contractual agreements. C. The team considers the current state of the Product Increment, the past performance of the team, the team's current capacity, and the ordered Product Backlog in order to determine how much work the team can undertake in a sprint. D. The Team alone decides how much work to take on in a Sprint. Neither the Product Owner, nor any other agency, can push more work onto the Team. 28. Which of the following IS True about Daily Scrum Meeting? A. The daily Scrum Meeting is a status meeting for Scrum Master and Product Owner but not for any other stakeholders who are not involved in a day to day basis. B. The daily Scrum meeting is a communication and coordination meeting for the Team. C. The daily Scrum meeting is a Problem solving meeting for the team to discuss and resolve issues every day so problems do not stay unresolved for longer period of time. D. The daily Scrum meeting is a status meeting for the Scrum Master not anyone else including the Product Owner. 29. How does the team decide when a Product Backlog item is done? A. When the tester has signed off the product increment after testing in the agreed up on environment. B. When the Sprint timebox has ended. C. When the product increment meets the current definition of done. D. When the Scrum Master decides that the Product Backlog items are done. 30. Scrum is... (select the best answer from the list) A. A methodology with many rules, roles, and many defined best practices. B. A software development approach sometime correctly referred to as cowboy process where programmers create products without involving the customers because customers do not know what they want anyway. C. WA process control framework where the work is planned from start to finish in detail at the beginning of the project. D. A simple process framework for developing products with only a few roles, a few artifacts, and few defined ceremonies. It is an empirical process control approach that is based on Agile Values.
6 31. A Product backlog is... (select the best answer from the list) A. A prioritized list of functional and non-functional business needs. The Product Owner is responsible for creating and managing this list. B. A list of detailed functional and non-functional requirements. The Product Owner is responsible for creating and managing this list. C. A list of detailed functional and non-functional requirements that the team has determined that it will not complete in the sprint / project because of schedule and budget constraints. D. A prioritized list of tasks to realize the business / product needs. The Technical team is responsible for creating and managing this list. 32. The Sprint Review is A. A meeting at the end of every sprint where the team reviews the past Sprint for lessons learned during the sprint. B. A meeting at the end of every sprint where the team demonstrates the product increment that they created in-order-to get feedback from the stakeholders. Anyone interested in the product is invited to the meeting. C. A meeting at the end of every sprint that will act as a phase gate where the team working with the product owner to come up with a list of product backlog items that are ready for the testing phase. D. A meeting at the end of every sprint where the Project Manager reviews the progress of the product development with the stakeholders. 33. The Sprint Retrospective meeting is A. A meeting at the end of every sprint where the team reviews individual performance with metrics such as defects per person per user story in-order to improve team performance. B. A meeting at the end of every sprint where the team demonstrates the product increment that they created in-order-to get feedback from the stakeholders. Anyone interested in the product is invited to the meeting. C. A meeting that follows the Sprint Review meeting where the team reflects on the Sprint to improve their process. D. A meeting that follows the Sprint review meeting where the Project Manager or their delegate collects the lessons learned so that it can be documented in the process audit documentation. 34. Who has the authority to cancel a Sprint? A. It is a collaborative decision but the authority rests upon Product Owner. B. It is a collaborative decision but the authority rests upon ScrumMaster. C. It is a collaborative decision but the authority rests upon Project Manager. D. A Sprint is never cancelled for any reason. It is against the Scrum Value Commitment. 35. The definition of Done in Scrum is? A. A checklist of criterion conforming to the organization s standards, conventions and guidelines that is mutually agreed between the Team and Product Owner. For a product backlog items to be considered done, it needs to meet this criteria. A. A checklist defined by the Program management Office. B. It can change during the sprint. C. The test team s definition of when the product increment is considered done. D. The test scenarios that needs to pass upon which the Product increment is considered done and ready for production migration.
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage
More informationCertified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions
More informationScrum. SE Presentation. Anurag Dodeja Spring 2010
Scrum SE Presentation by Anurag Dodeja Spring 2010 What is Scrum? Scrum is an agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically
More informationAgile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
More informationD25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
More informationAgile Project Management By Mark C. Layton
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
More informationSometimes: 16 % Often: 13 % Always: 7 %
SCRUM AT RIIS A Standish study found that only 20% of features in a typical system were used often or always and 45% of features were never used at all. The ability to embrace change is critical to reducing
More informationPLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan
PLM - Agile Agile Development Evolved in the 1990s as a response to heavyweight methodologies. In 2001 representatives of various new methodologies met to discuss the need for lighter alternatives. The
More informationSCRUM 1. Upon what type of process control is Scrum based? a. Empirical b. Hybrid c. Defined d. Complex
SCRUM 1. Upon what type of process control is Scrum based? a. Empirical b. Hybrid c. Defined d. Complex 2. The three pillars of empirical process control are: a. Respect for People, Kaizen, Eliminating
More informationEXIN Agile Scrum Foundation. Sample Exam
EXIN Agile Scrum Foundation Sample Exam Edition June 2016 Copyright 2016 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing system
More informationWould you like to have a process that unlocks ability to learn and produce faster?
Would you like to have a process that unlocks ability to learn and produce faster? Agile - your unfair advantage in the competition. BUILD LEARN MEASURE DEFINED MEASURABLE REPEATABLE COLLABORATIVE IMPROVABLE
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationScrum methodology report
Scrum methodology report Author: Tsholofelo Eunice Moitsheki Student number Tsholofelo Moitsheki (463642) Project Source and Documentation: http://kenai.com/downloads/dotsboxes/group%20report/dab5_scrum
More informationScrum In 10 Slides. Inspect & Adapt
Scrum In 10 Slides Inspect & Adapt Why Scrum? 52.7% projects cost 189% of their original estimates 60% of functionality delivered is rarely or never used 80% of the value comes from 20% of the functionality
More informationScrumMaster Certification Workshop: Preparatory Reading
A S P E S D L C Tr a i n i n g ScrumMaster Certification Workshop: Preparatory Reading A WHITE PAPER PROVIDED BY ASPE ScrumMaster Certification Workshop: Preparatory Reading Greetings, Potential Certified
More informationLEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
More informationWhat is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process
What is Scrum? From http://www.scrumalliance.org/pages/what_is_scrum A lean approach to software development Scrum is an agile software development framework. Work is structured in cycles of work called
More informationEXIN Agile Scrum Foundation
Sample Questions EXIN Agile Scrum Foundation Edition September 2013 Copyright 2013 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing
More informationAGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
More informationScrum. Speaker: Dan Mezick Email: info@newtechusa.com. URL: NewTechUSA.com. http://www.newtechusa.com Copyright 2002: All rights reserved
3 Roles, 3 Ceremonies, 3 Artifacts, 3 Best Practices Scrum Speaker: Dan Mezick Email: info@newtechusa.com Phone: 203-234-1404 URL: NewTechUSA.com Scrum s THREE ROLES The actors in Scrum: Product Owner,
More informationIntegrating Scrum with the Process Framework at Yahoo! Europe
Integrating Scrum with the Process Framework at Yahoo! Europe Karl Scotland Yahoo! Europe kjscotland@yahoo.co.uk Alexandre Boutin Yahoo! International alexandre.boutin@yahoo-inc.com Abstract Large enterprise
More informationT14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM
BIO PRESENTATION T14 6/21/2007 1:30:00 PM "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development Better Software Conference & EXPO June 18-21, 2007 Las Vegas, NV USA
More informationAgile Systems Engineering: What is it and What Have We Learned?
Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman Suzette.Johnson@ngc.com Getting To Know You! Dr. Suzette Johnson Northrop
More informationCSPO Learning Objectives Preamble. Scrum Basics
CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and
More informationA Glossary of Scrum / Agile Terms
A Glossary of Scrum / Agile Terms Acceptance Criteria: Details that indicate the scope of a user story and help the team and product owner determine done-ness. Agile: the name coined for the wider set
More informationAdapting Agile Software Development to Regulated Industry. Paul Buckley Section 706 Section Event June 16, 2015
Adapting Agile Software Development to Regulated Industry Paul Buckley Section 706 Section Event June 16, 2015 Agenda FDA s expectations for Software Development What is Agile development? Aligning Agile
More informationFREE ONLINE EDITION. (non-printable free online version) Brought to you courtesy of Sprint-IT &
FREE ONLINE EDITION (non-printable free online version) If you like the book, please support the author & InfoQ by purchasing the printed version: www.sprint-it.de/scrum-checklists (only 19,90 euro) Brought
More informationReferences: Hi, License: Feel free to share these questions with anyone, but please do not modify them or remove this message. Enjoy the questions!
Hi, To assist people that we work with in Scrum/Agile courses and coaching assignments, I have developed some Scrum study-questions. The questions can be used to further improve your understanding of what
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )
ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM ) Contents Homework Assignment for 2 PDUs... 1 Chapter Close-Out... 2 Terminology Matching Exercise...
More informationThe Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July 2013. Developed and sustained by Ken Schwaber and Jeff Sutherland
The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide... 3 Definition of
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 4 Scrum: Current Framework 1 Scrum: New Process Framework 1. A people-centric framework based on a set of values, principles, and practices that
More informationAgile Information Management Development
Agile Information Management Development Agile Project Management Characteristics Acceptance and even welcome of changing requirements Incremental product delivery Define, develop and deliver early and
More informationAgile Project Management with Scrum
Agile Project Management with Scrum Resource links http://www.agilealliance.org/ http://www.agilemanifesto.org/ http://www.scrum-master.com/ 1 Manifesto for Agile Software Development Individuals and interactions
More informationCertified Scrum Master Workshop
Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, selfmanagement, and visibility. Even projects that have solid, well-defined project plans encounter
More informationScrum Guidelines. v.2 2011 W W W. S C R U M D E S K. C O M
Scrum Guidelines v.2 2011 W W W. S C R U M D E S K. C O M WHY Agile Ceremonies Agile project is developed in repeatable ceremonies that give rhythm to delivery. Product Strategy Once per year Release Planning
More informationAgile Development Overview
Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others
More informationUsing Scrum to Streamline Web Applications Development and Improve Transparency. Michelle Frisque
Using Scrum to Streamline Web Applications Development and Improve Transparency Michelle Frisque September 2010 OVERVIEW! Background! The problem! The proposed solutions:! Creation of Web Committee! Implementing
More informationAgile Team Roles Product Owner & ScrumMaster. Brian Adkins Rick Smith
Agile Team Roles Product Owner & ScrumMaster Brian Adkins Rick Smith Agenda Scrum & Team Roles Overview Product Owner ScrumMaster Existing Roles Scrum Teams Optimally about 7 people Sponsor Stakeholders
More informationAgile Metrics. It s Not All That Complicated
Agile Metrics It s Not All That Complicated Welcome About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach Certified Scrum Master Certified Scrum Product Owner Led teams/org s to
More informationScrum. The Essence. Tobias Mayer, http://agilethinking.net. Sonntag, 19. Februar 12
Scrum The Essence What is Scrum? Scrum is a framework that allows you to create your own lightweight process for developing new products. Scrum is simple. It can be understood and implemented in a few
More informationHow To Plan An Agile Project
GAO Scheduling Best Practices Applied to an Agile Setting by Juana Collymore and Brian Bothwell April 15, 2015 Outline Why is scheduling important? GAO Schedule Assessment Guide Overview Status of the
More informationSCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON
SCRUM A Tool from the Software World Can Improve Analytical Project Outcomes By KyMBER WALTMUNSON When jurisdictions undertake analytical work such as audits, budget analysis, program evaluation, and special
More informationThe Agile Manifesto is based on 12 principles:
The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered
More informationAgile Software Development in the Large
Agile Software Development in the Large Jutta Eckstein 1 Large Large in... Scope Time People Money Risks We concentrate on Large Teams Large is relative 1, 2, 10, 100, 2000 People 2 Principles behind Agile
More informationAgile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield
Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise:
More informationIssues in Internet Design and Development
Issues in Internet Design and Development Course of Instructions on Issues in Internet Design and Development Week-2 Agile Methods Saad Bin Saleem PhD Candidate (Software Engineering) Users.mct.open.ac.uk/sbs85
More informationWaterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
More informationManaging a Project Using an Agile Approach and the PMBOK Guide
Managing a Project Using an Agile Approach and the PMBOK Guide Kathy Schwalbe, Ph.D. schwalbe@augsburg.edu Augsburg College Minneapolis, Minnesota September 25, 2012 Abstract This paper includes excerpts
More informationGetting Agile with Scrum
Getting Agile with Scrum Mike Cohn November 11, 2008 1 Mike Cohn - background 2 Agenda Overview of Scrum Product backlogs Sprints and sprint backlog Tracking progress Scrum meetings 3 The Agile Manifesto
More informationScrum Guide. By Ken Schwaber, May, 2009
Scrum Guide By Ken Schwaber, May, 2009 Scrum has been used to develop complex products since the early 1990s. This paper describes how to use Scrum to build products. Scrum is not a process or a technique
More informationCourse Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
More informationAgile Methods for Analysis
Agile Methods for Analysis Lightweight Concepts for Team-Based Projects Sebastian Neubert CERN PH-LBD Sebastian Neubert Agile Analysis 1/22 Introduction: Data Analysis as a Continuous Improvement Loop
More informationAgile project portfolio manageme nt
Agile project portfolio manageme nt Agile project & portfolio summit at Harrisburg University May 9, 2016 Agile project portfolio management Agenda Portfolio management challenges Traditional portfolio
More informationLean QA: The Agile Way. Chris Lawson, Quality Manager
Lean QA: The Agile Way Chris Lawson, Quality Manager The Quality Problem Agile Overview Manifesto Development Methodologies Process Agile QA Lean QA Principles An Agile QA Framework Summary Q & A Agenda
More informationIntroduction to Agile Practices
Introduction to Agile Practices Phyllis Marbach, INCOSE Agile Systems & Systems Engineering Working Group February 2, 2016 INCOSE INSIGHT July 2014 1 Current State of Intelligent Transportation Systems
More informationProduct Development: From Conception to Execution. Slide 1
Product Development: From Conception to Execution Slide 1 Product Development: From Conception to Execution Becky Lester, CPCU GAINWeb Product Owner Grange Insurance Damon Lay, ACAS, MAAA Director Business
More informationIntroduction to Agile Scrum
Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum
More informationScaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London 2007. conchango 2007 www.conchango.com
Scaling Scrum Colin Bird & Rachel Davies Scrum Gathering London 2007 Scrum on a Slide Does Scrum Scale? Ok, so Scrum is great for a small team but what happens when you have to work on a big project? Large
More informationThere are 3 main activities during each Scrum sprint: A planning meeting where: the Product Owner prioritizes user stories in the product backlog
There are 3 main activities during each Scrum sprint: A planning meeting where: the Product Owner prioritizes user stories in the product backlog that need to be implemented during the sprint the Team
More informationVision created by the team. Initial Business Case created. Cross functional resource meeting held. Agile alignment meeting
Help Tips Agile SDLC Product Backlog Daily Standup Sprint 1 Show and Tell 2 Week Sprint Sprint 2 Release1 (must haves) Retrospective Sprint 1 DONE! Sprint 3 Sprint 2 DONE! Sprint Backlog Sprint 3 DONE!
More informationSCRUM BODY OF KNOWLEDGE (SBOK Guide)
A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK Guide) 2013 Edition A Comprehensive Guide to Deliver Projects using Scrum TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 Overview of Scrum...
More informationScrum includes a social agreement to be empirical as a Team. What do you think an empirical agreement is?
Scrum Discussion Questions For the Facilitator These questions and subsequent discussion points are designed to help you and your Team more efficiently implement Scrum. The following are discussion points
More informationIteration Planning. also called Iteration Kickoff
Agile Practices also called Iteration Kickoff Iteration Planning Purpose: Discuss detailed requirements of the stories to be built in the iteration. Review and refine the acceptance criteria for each story
More informationEvaluation of agility in software development company
Evaluation of agility in software development company Gusts Linkevics Riga Technical University, Riga, Latvia, gusts@parks.lv Abstract Organization s and team s experience in agile methodology can be more
More informationAtern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.
THE AGILE PROJECT LEADER S DICTIONARY This dictionary attempts to de-mystify the jargon around the world of Agile projects. Part 1 translates common Agile terms into more traditional words. Part 2 translates
More informationCase Study on Critical Success Factors of Running Scrum *
Journal of Software Engineering and Applications, 2013, 6, 59-64 http://dx.doi.org/10.4236/jsea.2013.62010 Published Online February 2013 (http://www.scirp.org/journal/jsea) 59 Case Study on Critical Success
More informationAgile Project. Management FOR DUMME&* by Mark C. Layton WILEY. John Wiley & Sons, Inc.
Agile Project Management FOR DUMME&* by Mark C. Layton WILEY John Wiley & Sons, Inc. Table of Contents»#» « Introduction / About This Book 1 Foolish Assumptions 1 Conventions Used in This Book 2 How This
More informationFebruary 2010. Scrum: Developed and sustained by Ken Schwaber and Jeff Sutherland
February 2010 Scrum: Developed and sustained by Ken Schwaber and Jeff Sutherland Acknowledgements General Scrum is based on industry-accepted best practices, used and proven for decades. It is then set
More informationAGILE & SCRUM. Revised 9/29/2015
AGILE & SCRUM Revised 9/29/2015 This Page Intentionally Left Blank Table of Contents Scrum Fundamentals Certified Course... 1 Scrum Developer Certified (SDC)... 2 Scrum Master Certified (SMC)... 3 Scrum
More informationAgile Software Project Management with Scrum
Agile Software Project Management with Scrum Viljan Mahnic, Slavko Drnovscek University of Ljubljana, Faculty of Computer and Information Science Trzaska 25, SI-1000 Ljubljana, Slovenia viljan.mahnic@fri.uni-lj.si,
More informationCourse Title: Planning and Managing Agile Projects
Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course
More informationAgile in Financial Services A Framework in Focus
Agile in Financial Services A Framework in Focus John B. Hudson, B.Sc, PMP, CSM PMI NJ Chapter February 19, 2013 19 Feb 2013 1 Objectives 1. Agile Development an Overview 2. The Agile Enterprise Infrastructure
More informationThe Agile Service Management Guide. By Jayne Gordon Groll
The Agile Service Management Guide By Jayne Gordon Groll Sources and Acknowledgements The Scrum Guide by Ken Schwaber and Jeff Sutherland, July, 2013 The ITSM Process Design Guide by Donna Knapp, ISBN:
More informationIntroduction to Agile
Chapter 1 Introduction to Agile Objectives: Define Agile software development Explain differences and similarities between various lightweight methodologies Learn the core principles of Agile Dispel common
More informationIntroduction to Scrum
Introduction to Scrum Recorded by Michael James [Existing slide with MJ] Welcome to Module 1 of CollabNet s Scrum Training Series: Introduction to Scrum. This is a brief introduction to topics that are
More informationAgile Project Management A Primer. Brian Stewart AVU ACEP Nairobi 17 th 2013
Agile Project Management A Primer Brian Stewart AVU ACEP Nairobi 17 th 2013 http://www.coleyconsulting.co.uk/images/waterfall-model.gif Problems with waterfall model Over-planning Insufficient Communication
More informationDevelopment phase 1.3. isupport. Project Name: isupport Date: 24-6-2015 Release: 1.3. Document Name: HCCH isupport Development phase project team 1
cross-border recovery of maintenance obligations pour le recouvrement transfrontière des obligations alimentaires Development phase Project Name: Date: 24-6-2015 Release: 1.3 Authors: Brigitte Voerman
More informationwww.testing-solutions.com TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes
www. TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes What is Agile Development? There are various opinions on what defines agile development, but most would
More informationMariusz Chrapko. Before: Software Quality Engineer/ Agile Coach, Motorola, Poland. My Public Profile: http://www.linkedin.
Gathering Customer Requirements in an Agile Environment Mariusz Chrapko ReConf 2009, Munich Mariusz Chrapko Now: Process Consultant/ Agile Coach@Kugler Maag CIE, Stuttgart Supported Areas: - CMMI - SPICE/
More informationRoles: Scrum Master & Project Manager
Roles: Scrum Master & Project Manager Scrum Master: Facilitate collaborative meetings Track team performance Remove impediments (Risk, Issue) Validate team alignment to Agile framework and scope Drive
More informationAgile Scrum and PMBOK Compatible or Contrary?
Agile Scrum and PMBOK Compatible or Contrary? Paul Despres PMI Emerald Coast Panama City Branch June 26, 2014 Meeting Overview Agenda Topics: Review Agile/Scrum Methods Review PMBOK Structure Demonstrate
More informationCertified ScrumMaster Workshop
Certified ScrumMaster Workshop Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, self-management, and visibility. Even projects that have solid, well-defined
More informationBCS Foundation Certificate in Agile
S Foundation ertificate in gile Specimen Paper Record your surname/last/family name and initials on the nswer Sheet. Specimen paper only. 20 multiple-choice questions 1 mark awarded to each question. Mark
More informationCertified Scrum Developer (CSD) Course Description
Certified Scrum Developer (CSD) Course Description The Certified Scrum Developer workshop is an intensive five-day session that teaches programmers and quality assurance professionals to work in self-organizing,
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationAgile Practitioner: PMI-ACP and ScrumMaster Aligned
Agile Practitioner: PMI-ACP and ScrumMaster Aligned The PMI Agile Certified Practitioner (PMI-ACP) ScrumMaster credential validates your ability to understand agile principles, agile concepts, and establishes
More information26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: 224-595-8846 AGILE THROUGH SCRUM
26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: 224-595-8846 AGILE THROUGH SCRUM 1 AGENDA & LEARNING POINTS 1. Open 2. Agile Overview 3. Scrum Basics Learning
More informationBridging the Gap Between Acceptance Criteria and Definition of Done
Bridging the Gap Between Acceptance Criteria and Definition of Done Sowmya Purushotham, Amith Pulla sowmya.sudha@gmail.com, amith.pulla@intel.com Abstract With the onset of Scrum and as many organizations
More informationAgile Project Management
Agile Project Management with Bill Doescher, PMP, MBA, CSM Pi Principal i lconsultant tand Product tdevelopment tdirector Bill Doescher, PMP, CSM Bill Doescher is a Principal Consultant and Product Development
More informationA Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)
A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering
More informationScrum for Managers, Zurich March 2010
Scrum for Managers Microsoft Corporation / TechTalk Zurich Switzerland March 2010 About Mitch Lacey Mitch Lacey 13+ years of program and project management experience Microsoft Program Manager 2001 2006
More informationAgile with XP and Scrum
Agile with XP and Scrum Amit Goel National Agile Software Workshop @ Indore Agile India Conference Agile Software Community of India Disclaimer and Credits Most of material in this presentation has been
More informationManaging Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
More informationSmartBear Software Pragmatic Agile Development (PAD) Conceptual Framework
Pragmatic Agile Development (PAD) Conceptual Framework This document describes the Pragmatic Agile Development framework, a Scrum based development process. SmartBear Software 3/10/2010 Pragmatic Agile
More informationIMQS TECHNOLOGY AGILE METHODOLOGY
IMQS TECHNOLOGY AGILE METHODOLOGY OVERVIEW Agile software development refers to a group of software development methodologies that promotes development iterations, open collaboration, and process adaptability
More informationGetting Agile with Scrum. Mike Cohn - background
Getting Agile with Scrum Mike Cohn Mountain Goat Software mike@mountaingoatsoftware.com 1 Mike Cohn - background 2 We re losing the relay race The relay race approach to product development may conflict
More informationScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016
ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016 As a ScrumMaster, one of your responsibilities is "Causing change that increases the productivity of the Scrum Team." What
More informationWhen is Agile the Best Project Management Method? Lana Tylka
When is Agile the Best Project Management Method? Lana Tylka Staged Incremental Deliveries Prototypes Plan Develop Design Deploy Test Maintain Sequential Steps Multiple Iterations Waterfall Sprints, Spirals
More informationScrum and Kanban 101
Scrum and Kanban 101 www.bebetterleader.com @jfiodorova What are your expectations What are the differences between Agile and Traditional? What do you know about Agile Two approaches to control any process:
More information