Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.
|
|
- Clifford Patrick
- 4 years ago
- Views:
Transcription
1 Agile Notetaker & Scrum Reference Designed by Axosoft, the creators of OnTime the #1 selling scrum software.
2 Scrum Diagram: Team Roles: roduct Owner: Is responsible for what goes into the product backlog and prioritizes it. Would probably make 1 hour a good dictator 2 hours if given 4 hours the chance. 8 hours Scrum Master: A team facilitator. Ensures teams have what they need to get the job done. Also, sets up meetings and monitors everything. Also, kicks ass when necessary. Developers & Testers: They write code and make sure it does what it's suppose to do. Duh! For more info: For more info: Intro to Scrum Video: Intro to Scrum Video: This work is licensed under a Creative Commons This work is 2012 Attribution-NoDerivs Axosoft, LLC and 3.0 can Unported be reused License Axosoft, LLC. under a Creative Commons Attribution-NoDerivs 3.0 Unported License. 1 roduct Backlog The roduct Backlog contains a wish list of all the User Stories of a product. 2 Release Backlog The goal of a given release is to deliver a subset of the roduct Backlog, known as the Release Backlog. 3 Sprint Backlogs Each Sprint (or short duration milestone) takes a small chunk of the Release Backlog and gets it Ship-Ready! 5 Daily Scrum Meetings Short daily standup meetings ensure everything is on track and everyone has the tools they need. Estimation Techniques: Hours: When estimating work, it's important to have the entire team use some standards. Use 1h, 2h, 4h, 8h, etc. No estimations in-between. 1h 2h 4h 8h 2d 3d 5d Story oints: You can also estimate work in comparison to the complexity of a well known but simple component. 1 Story oint 2 Story oints 4 Story oints 8 Story oints Remember that in Scrum, the estimates are only part of the story. The Burndown Velocity is the true indicator of whether or not the project is on track. 4 Burndown Chart The progress of the team is monitored using a Burndown Chart. 6 Sprint Retrospective After each sprint, a longer retrospective meeting helps fine-tune the process.
3 Shipping software on time and on budget is tough. There are a lot of variables with rapidly moving parts. Everything, from the what should be delivered to the ideal technologies used to deliver it, is constantly changing. If it takes too long to ship, the product may be obsolete before it gets to market. If it ships early but with poor quality, it will have to fight an uphill battle to overcome its first impression. To balance these tradeoffs, an iterative agile development technique has become the new standard of shipping software on time. Within the agile world, scrum has emerged as the leading methodology for building efficient self-organizing teams and monitoring the progress of those teams using proven techniques that help make adjustments along the way. The concepts of agile and scrum are simple. In the first few pages of this agile notetaker, my team and I have broken down these concepts into manageable chunks of bite-sized knowledge. Each time you sit in a conference room waiting for a meeting to start, review a page from the concepts explained in this book. Over time, you will notice that your team will ship software faster and with better quality than ever before. Agile/Scrum Reference The concepts are solid and proven by thousands of dev teams worldwide. We have been using these techniques to build software at Axosoft for more than a decade now with fantastic results. I hope you enjoy this book as much as we enjoyed creating it. As always, we love to hear from you. Feel free to me directly with your comments about this book. Sincerely, Hamid Shojaee Axosoft, LLC Building Software Solutions for Agile Businesses
4 1 roduct Backlog The roduct Backlog contains the wish list of all the User Stories that would make the product great. roduct Backlog User Story As (role), I want (feature), so that (benefit). In Scrum, features are known as User Stories and they are written from the perspective of the end-user. The roduct Owner, representing the users and customers of the product, decides which User Stories or items make it into the roduct Backlog.
5 2 Release Backlog The goal of a given release is to deliver a subset of the roduct Backlog, known as the Release Backlog. roduct Backlog After identifying which User Stories will go into a particular Release, the User Stories become part of a Release Backlog... Release Backlog...which are then prioritized by the Development Team, who also estimate the amount of time involved to complete each item. see ro Tip- Estimation Techniques Release Backlog 4h 2h 1h 8h 8h 1h 3days 4h 2days 4h
6 3 Sprint Backlog Each Sprint (or short duration milestone) takes a manageable chunk of the Release Backlog and gets it to a Ship-Ready state! Sprint 01 Sprints generally range from a couple of days to 30 days in length. Remember- The shorter the Release Cycle, the shorter each Sprint should be, with two to a dozen Sprints in a given Release. At the end of each Sprint, you should have a fully tested product with all the features of the Sprint 100% complete.
7 4 Burndown Charts The progress of the team is monitored using a Burndown Chart, one of the best project visibility tools, to ensure a project is progressing smoothly. The Burndown Chart provides a day-by-day measure of the amount of work that remains in a given Sprint or Release. General Trend towards zero ç Estimated completion date The slope of the graph, or Burndown Velocity, is the average rate of productivity for each day. Work Remaining Rate = Days to Completion on time late Knowing whether or not the roject is on time early in the schedule, can help teams make the proper adjustments necessary to get the project on-track.
8 5 Daily Standups Short daily standup meetings (aka The Daily Scrum) ensure everything is on track and everyone has the tools they need. It is an essential tool to have information flow freely between team members. Team members list the work they have completed since the last meeting, any obstacles in their way, and what they are going to do next. This is what I have done since we last met... These are the obstacles I have encountered... This is what I plan to do today...
9 6 Sprint Retrospectives After each Sprint, a longer Retrospective meeting helps fine-tune the process. This is a time for each team member to reflect on what went right and areas of improvement. What went right? What went wrong? What can we improve the next time around? Scrum Master After all, Scrum is a flexible Agile development method that needs constant improving and tweaking for every team.
10 Reference: Team Roles roduct Owner: Is responsible for what goes into the product backlog and prioritizes it. Scrum Master: A team facilitator. Ensures teams have what they need to get the job done. Also, sets up meetings and monitors everything. Developers & Testers: They write code and make sure it does what it s suppose to do. ro Tip- Estimation Techniques While most estimates are inaccurate, there are things you can do to help improve your team s estimation techniques. For example, a simple technique is to create estimating buckets where User Stories fall into a complexity bucket such as: or: 1h 2h 4h 8h 2d 3d 5d 1 Story oint 2 Story oints 4 Story oints 8 Story oints No item would be estimated at fractional time or any numbers in between the buckets. For example, a 6-hour estimate would fall into the 8-hour bucket and therefore would have an 8-hour estimate. Regardless of whether you use Hours or Story oints for your estimations, be sure to always maintain the same unit for estimating across the board. Remember that in Scrum, the estimates are only part of the story. The Burndown Velocity is the true indicator of whether or not the project is on track.
11 Expectation Charts One of the most important tasks of any development team is to appropriately set expectations. An important tool to help set expectations with stakeholders is to use the charts below and ask them to choose Fixed Date Delivery or Fixed Scope Delivery but that they can t have both. With a fixed date delivery, what can be delivered is unknown, but the team should be able to provide low expectations and high expectations estimates (a lower and upper scope boundary). Fixed Date Delivery High Expectation User Stories Low Expectation Fixed Date Time With a fixed scope delivery, when the project will be delivered is unknown, but the team should be able to provide slow expectations and fast expectations estimate (a lower and upper time boundary). Fixed Scope Delivery Fast Expectation Fixed Scope Slow Expectation User Stories Time
12 Scrum + Kanban = Agile Awesomeness A Kanban is a lean scheduling system in manufacturing that utilizes visual cues. When adapted to software development, Kanban systems usually start with a board and visual cards that represent items in your product backlog. On the board, you place the cards into columns that represent their current step in the workflow, ranging from New to Complete. ro Tip: The steps in-between are entirely up to you, so keep it simple and efficient. It s easy to find out: what s going to be started next what s in progress what s already been done So long as your team keeps finishing work, those cards keep moving to the right, and more importantly, you keep delivering features to your customers. Customer
13 Kanban WI Limits To help ensure items are being completed at a steady pace, Kanban can impose limits on the number of items that can live in any one workflow step at any given time. Work in rogress (WI) Limits If your team runs into a problem, these limits will bring it to light very quickly by creating a visible bottleneck. This allows the entire team to collaborate or swarm on the problem. Bottleneck
14 Kanban Software Development WI Limits help you: Keep Work Flowing Save Time by eliminating too much task switching Complete Tasks Kanban is fantastic in it s own right and on many projects may be all that you need, but when paired with a good Scrum framework and a great Scrum tool, Kanban really shines. Scrum provides the structure for organizing feedback, short-term planning, stack ranking, an inspect-and-adapt mindset, and other organizational improvements. Kanban provides a steady flow of tasks that reach 100% completion by helping your team manage day-to-day development with a minimum of overhead and blocking issues.
15 Agile Manifesto by Kent Beck, et al.* We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions Working software Customer collaboration Responding to change over over over over rocesses and tools Comprehensive documentation Contract negotiation Following a plan That is, while there is value in the items on the right, we value the items on the left more. Customer s Bill of Rights by Steve McConnell** I have the right: To set objectives for the project and have them followed. To know how long the software project will take and how much it will cost. To decide which features should be included in software. To make reasonable changes to requirements throughout the course of the project and to know the costs of making those changes. To know the project s status clearly and confidently. To be apprised regularly of risks that could affect cost, schedule, or quality, and to be provided with options for addressing potential problems. To have ready access to project deliverables throughout the project. roject Team s Bill of Rights by Steve McConnell** I have the right: To know the project objectives and to clarify priorities. To know in detail what product I m supposed to build and to clarify the product definition if it is unclear. To have ready access to the customer, manager, marketer, or other person responsible for making decisions about the software s functionality. To work each phase of the project in a technically responsible way, especially to not be forced to start coding too early in the project. To approve effort and schedule estimates for any work that I will be asked to perform. This includes the right to provide only the kinds of cost and schedule estimates that are theoretically possible at each stage of the project; to take the time needed to create meaningful estimates; and to revise estimates whenever the project s requirements change. To have my project s status reported accurately to customers and upper management. To work in a productive environment free from frequent interruptions and distractions, especially during critical parts of the project. *(2001) Manifesto for Agile Software Development. Agile Alliance. Retrieved 14 June ** Software roject Survival Guide by Steve McConnell...a must read.
16 Glossary of Agile/Scrum Terms* Agile Software Development- methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. Burndown Chart- a graphical representation of work left to do over time. Daily Standup- a short, daily meeting, during sprints, for team communication. Development Team- a cross-functional group of people responsible for delivering potentially shippable iterations of roduct at the end of every Sprint. Impediment- anything that prevents a team member from performing work as efficiently as possible. Iteration- the sum of all the roduct Backlog Items completed during a Sprint and all previous Sprints. Kanban Software Development- a method for developing software products and processes with an emphasis on just-in-time delivery while not overloading the software developers. roduct Backlog- a prioritized list of high-level requirements. roduct Owner- the person responsible for maintaining the roduct Backlog by representing the interests of the stakeholders, and ensuring the value of the Development Team s work. Release Backlog- a prioritized subset of the roduct Backlog. Retrospective- a meeting held by a project team at the end of a project to look for ways to improve the process for the next Iteration. Scrum Software Development- an iterative and incremental Agile Software Development framework for managing software projects, and product or application development. Scrum Master- the person responsible for the Scrum process, making sure it is used correctly and maximizing its benefits. Scrum Team- consists of the roduct Owner, Scrum Master and Development Team. Sprint- a time period (typically 1 4 weeks), committed to by the team, in which development occurs on a set of backlog items. Sprint Backlog- a prioritized list of tasks to be completed during the Sprint. Sprint Burndown Chart- daily progress for a Sprint over the Sprint s length. User Story- a feature that is added to the backlog that follows a specific suggested structure: As (role), I want (feature), so that (benefit) Velocity- the rate at which a team gets work done. Example: 50 hours per day. *
LEAN 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
AGILE - 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
Scrum. 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
Waterfall 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
Would 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
www.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
The 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
Issues 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
D25-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
Agile 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
Sometimes: 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
1. Sprint Planning. Agile Ceremonies Demystified. A four part series written by Angela Boardman, CSM, CSP. www.atginfo.com 1-866-805-4ATG (4284)
www.atginfo.com 1-866-805-4ATG (4284) Agile Ceremonies Demystified A four part series written by Angela Boardman, CSM, CSP 1. Sprint Planning Agile.maybe you have heard of it. Does your company want to
Agile 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
Introduction 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
Scrum vs. Kanban vs. Scrumban
Scrum vs. Kanban vs. Scrumban Prelude As Agile methodologies are becoming more popular, more companies try to adapt them. The most popular of them are Scrum and Kanban while Scrumban is mixed guideline
Introduction 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
Vision 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!
An Introduction to Agile Performance Management
! 1 An Introduction to Agile Performance Management by Jeffrey B. Rothman, Ph.D. An Introduction to Agile This is a high level introduction to Agile -- a well known productivity framework for software
Agile 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
Overview of Scrum. Scrum Flow for one Sprint. 2015 SCRUMstudy.com. All Rights Reserved. Daily Standup. Release Planning Schedule. Create.
Overview of Scrum Scrum is the most popular Agile framework. It is an adaptive, iterative, fast, flexible, and effective method designed to deliver significant value quickly and throughout a project. Scrum
Scrum 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
This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:
AGILE HANDBOOK OVERVIEW WHAT IS THIS? This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people: Someone who is looking for a quick overview on
26 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
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization Secrets of a Scrum Master: Agile Practices for the Service Desk Donna Knapp Curriculum Development Manager, ITSM Academy
EXIN 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
Managing 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...
Lean Software Development and Kanban
1 of 7 10.04.2013 21:30 Lean Software Development and Kanban Learning Objectives After completing this topic, you should be able to recognize the seven principles of lean software development identify
The 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
Agile So)ware Development
Software Engineering Agile So)ware Development 1 Rapid software development Rapid development and delivery is now often the most important requirement for software systems Businesses operate in a fast
EXIN 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
FREE 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
Agile 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
Agile 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:
Scrum. 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,
Mastering the Iteration: An Agile White Paper
Rally Software Development Corporation Whitepaper Mastering the Iteration: An Agile White Paper Dean Leffingwell Abstract: The heartbeat of Agile development is the iteration the ability of the team to
Agile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 27.01.2012 1 Lifecycle model To support the planning and management of activities required in the production of e.g.
MTAT.03.094 Software Engineering
MTAT.03.094 Software Engineering Lecture 12: Lean & Flow-based (KANBAN) Principles and Processe Fall 2015 Dietmar Pfahl email: dietmar.pfahl@ut.ee Structure of Lecture 12 KANBAN Case Study: Scrum vs. KANBAN
A 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
Agile 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
Scrum Is Not Just for Software
Scrum Is Not Just for Software A real-life application of Scrum outside IT. Robbie Mac Iver 2/9/2009. Agile methods like Scrum can be applied to any project effort to deliver improved results in ever evolving
No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Scrum
No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Helge Eikeland, Statoil, October 2010 Today s challenge is complexity
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
Scrum. in five minutes
Scrum in five minutes Scrum and agile methods are hot topics these days A simple method for the management of complex projects... Older methods focus on staying on track; Scrum is aimed at delivering business
Getting Started with Agile Project Management Methods for Elearning
Getting Started with Agile Project Management Methods for Elearning Megan Torrance TorranceLearning Training2013 Session 108 February 18, 2013 8am Megan Torrance has 20 years of experience in the learning
What 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
Capstone Agile Model (CAM)
Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and
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. Total questions
Kanban vs Scrum Making the most of both
Kanban vs Scrum Making the most of both JAOO, Aarhus Oct 6, 2009 Henrik Kniberg Agile/Lean coach @ Crisp, Stockholm Board of directors henrik.kniberg@crisp.se +46 70 4925284 Purpose of this presentation
Agile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 24.01.2013 1 Application development lifecycle model To support the planning and management of activities required in
Scrum 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:
ScrumMaster 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
Managing 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
XP & Scrum. extreme Programming. XP Roles, cont!d. XP Roles. Functional Tests. project stays on course. about the stories
XP & Scrum Beatrice Åkerblom beatrice@dsv.su.se extreme Programming XP Roles XP Roles, cont!d! Customer ~ Writes User Stories and specifies Functional Tests ~ Sets priorities, explains stories ~ May or
How 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
Getting 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
Moderator: Albert Jeffrey Moore, ASA, MAAA. Presenters: Albert Jeffrey Moore, ASA, MAAA Kelly J. Rabin, FSA, MAAA Steven L. Stockman, ASA, MAAA
Session 59 PD, The Need for Agile Actuaries: Introduction to Agile Project Management Moderator: Albert Jeffrey Moore, ASA, MAAA Presenters: Albert Jeffrey Moore, ASA, MAAA Kelly J. Rabin, FSA, MAAA Steven
When 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
Agile Beyond The Team 1
Agile Beyond The Team 1 Dilbert Agile 2 What Does Your Organization Value? Projects over Teams? Do new teams spools up for new projects? On-Time/On-Budget Delivery over Zero Maintenance Products Deliver
PLM - 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
When User Experience Met Agile: A Case Study
When User Experience Met Agile: A Case Study Michael Budwig User Experience Manager PayPal 2211 North 1 st Street, San Jose, California 95131 USA mbudwig@paypal.com Soojin Jeong Manager, User Interface
Course 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
Scrum 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
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.com 1 About Coveros Coveros helps organizations accelerate the delivery
Scrum in a Large Project Theory and Practice
Scrum in a Large Project Theory and Practice Agile World 2012 Munich, July 12, 2012 Dr. Sebastian Stamminger Scrum in Large Projects Agenda Theory Case Study Teams Our Process Challenges Lessons Learned
Introduction to Agile Software Development Process. Software Development Life Cycles
Introduction to Agile Software Development Process Presenter: Soontarin W. (Senior Software Process Specialist) Date: 24 November 2010 AGENDA Software Development Life Cycles Waterfall Model Iterative
Frank Cervone Vice Chancellor for Information Services and Chief Information Officer Purdue University Calumet January 17, 2012 CARLI Anatomy of a
Frank Cervone Vice Chancellor for Information Services and Chief Information Officer Purdue University Calumet January 17, 2012 CARLI Anatomy of a Digital Project webinar series An overview and background
A 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
Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
The Agile PMO. Contents. Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404
The Agile PMO Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404 Kevin.thompson@cprime.com Abstract The development of Agile processes
Agile Methodologies XP and Scrum
Agile Methodologies XP and Scrum Introduction into Software Engineering Lecture 22 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Problem: How to we Control Software Development?
Agile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010
Agile Project Management and the Real World Emily Lynema DLF Fall 2010 November 1, 2010 Outline Why care about project management? Traditional vs. Agile What is Agile? What is Scrum? Agile case study:
Lean 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
Agile Scrum Foundation Training
IMPROVEMENT BV Liskesweg 2A 6031 SE Nederweert www.improvement-services.nl info@improvement-services.nl Tools for Optimum Performance tel: 06-55348117 Agile Scrum Foundation Training Agile Foundation Examination
CSPO 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
Development. Lecture 3
Software Process in Modern Software Development Lecture 3 Software Engineering i Practice Software engineering practice is a broad array of principles, concepts, methods, and tools that must be considered
Basic Trends of Modern Software Development
DITF LDI Lietišķo datorsistēmu programmatūras profesora grupa e-business Solutions Basic Trends of Modern Software Development 2 3 Software Engineering FAQ What is software engineering? An engineering
Agile Scrum Training. Nice to meet you. Erik Philippus. Erik Philippus (1951) www.improvement-services.nl www.agile-architecting.com.
Erik Philippus IMPROVEMENT BV erik@agile-architecting.com 1 IMPROVEMENT BV Nice to meet you Erik Philippus (191) IMPROVEMENT BV 3 years of experience in industrial automation Foxboro, ESA, Philips Medical,
Introduction 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
Scrum 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
The 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
Adapting 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
Agile Project Management in a Regulated Environment
Paper AD06 Agile Project Management in a Regulated Environment Alistair Dootson, d-wise, Manchester, UK ABSTRACT Scrum is an agile approach to project management for software development or implementation,
The style is: a statement or question followed by four options. In each case only one option is correct.
AGILE FOUNDATION CERTIFICATE SAMPLE FOUNDATION QUESTIONS WITH ANSWERS This document is a set of sample questions, in the style of the Agile Foundation Certificate Examination, which is a 60 question, 1
There 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
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014 1 Goals Cover Material from our User Stories Book Chapter 15: Using Stories With Scrum Chapter 16: Additional
Agile Overview. 30,000 perspective. Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013
Agile Overview 30,000 perspective Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013 Agenda 30,000 Perspective The Players Initiating a Project Agile Estimating Agile Communications
Lean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.
Lean Agile Scrum Business Value Development and Delivery using Agility Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.net High yield software engineering team Active Customer Involvement
Introduction to Scrum for Managers and Executives
Introduction to for Managers and Executives goodagile> Certified Training and Consulting in India and Asia www.goodagile.com The Problems Many Companies Face Time-to-market for products is too long Project
IMPLEMENTING SCRUM. PART 1 of 5: KEYS TO SUCCESSFUL CHANGE
IMPLEMENTING SCRUM GUIDE PART 1 of 5: KEYS TO SUCCESSFUL CHANGE Created by Axosoft, makers of the #1 Scrum software, in collaboration with writer and coach, Tirrell Payton. A STORY ABOUT NIC AND SKIP I
EPL603 Topics in Software Engineering
Lecture 3 Agile Software Development EPL603 Topics in Software Engineering Efi Papatheocharous Visiting Lecturer efi.papatheocharous@cs.ucy.ac.cy Office FST-B107, Tel. ext. 2740 Topics covered Agile methods
Iteration 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
Scrum 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
UC Santa Barbara. CS189A - Capstone. Christopher Kruegel Department of Computer Science UC Santa Barbara http://www.cs.ucsb.
CS189A - Capstone Christopher Kruegel Department of Computer Science http://www.cs.ucsb.edu/~chris/ How Should We Build Software? Let s look at an example Assume we asked our IT folks if they can do the
Integrating PRINCE2 and Scrum for successful new product development
1 Goal Professional Services Pty Ltd 2 Renewtek Pty Ltd Integrating PRINCE2 and Scrum for successful new product development Rankins G J 1 and Kearns M 2 This paper was presented at the Australian Institute
Agile 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
Measuring ROI of Agile Transformation
Measuring ROI of Agile Transformation Title of the Paper: Measuring Return on Investment (ROI) of Agile Transformation Theme: Strategic & Innovative Practices Portfolio, Programs & Project (PPP) Management
Agile 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
Adopting Agile Testing
Adopting Agile Testing A Borland Agile Testing White Paper August 2012 Executive Summary More and more companies are adopting Agile methods as a flexible way to introduce new software products. An important
Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT
Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT Information Technology 2013 KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT Mannila, Jukka Satakunnan ammattikorkeakoulu,
www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Created by Stephen Barkar - www.stephenbarkar.se
1 www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Purpose with the material 2 This material describes the basics of Agile and Lean and the similarities and differences between