1 Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield
2 Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise: The offsite customer Scrum 101 Scrum Overview Roles and responsibilities Scrum team Product Owner ScrumMaster
3 Agenda Scrum In-depth The Sprint Sprint Planning Exercise: Sprint Planning Tracking Progress Daily Scrum Exercise: Running a Daily meeting Sprint Review Sprint Retrospective The ScrumMaster role: Exercise: Great ScrumMaster scenarios Exercise: Velocity game Optional modules: Scaling Scrum Distributed Scrum
5 A Defined Process Donut Mix Yummy Donuts!
6 The Waterfall Job Function A Job Function B Job Function C Job Function D Job Function E Requirements Gathering Design Documentation, Signoffs, Handoff Development Documentation, Signoffs, Handoff Documentation, Signoffs, Handoff Testing Launch & Maintain Documentation, Signoffs, Handoff Advantage: Highly Logical Disadvantage: High failure rate, low process efficiency
7 Agile Development Feedback Feedback Feedback v1.0 v1.1 v1.2 Short Iterations of 1-4 weeks Incremental releases
8 Agile Development Feedback Feedback Feedback Plan Test Design Build Plan Test Design Build Plan Test Design Build Plan Test Design Build Do a little bit of everything every cycle
10 Agile is a great buzzword. Who doesn t want to be Agile? No one says, Thanks, I d rather be inflexible and slow to respond.
11 The Agile Manifesto 2001 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 over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
12 Agile Myths No design No planning Poor quality Cowboy Coding Only works on small projects
15 What is Scrum? A flexible framework that is: Collaborative Iterative & Incremental Commonsense Very simple but very hard; it causes change.
20 Scrum Focus Strategy Portfolio Product Vision Release Plan Iteration Plan Daily Plan
21 Scrum 101 Daily Stand-up Sprint Review Sprint Planning Product Backlog Sprint Potentially Shippable Product Increment Commitment No Changes (in Duration or Deliverable) Team Retrospective Challenges Testing Build breaks Improvement
22 Scrum Roles Product Owner The Team Determines what should be produced, to maximize ROI for the business Cross-functional and selforganizing team of 7 people +/- 2 ScrumMaster Protects and serves the Team, and supports their practice of Scrum
23 Product Backlog A prioritized list of requirements Prioritized by the product owner This is the Product Backlog
24 Sprint Planning Planning at the start of a Sprint by the whole team and Product Owner Team creates tasks, estimates, and volunteers for them This is the Sprint Planning Meeting
25 Sprints This is the sprint 4 Week Sprint 1 month timebox of work During the Sprint: Analysis Design Code Test A little bit of everything
26 Daily Stand-Up A daily team meeting Keep up to date Help each other to resolve problems This is the Daily Meeting (Stand-Up)
27 Sprint Review Review A demo by the team of: Complete Fully tested Potentially shippable features Anyone can attend This is the Sprint Review
28 Sprint Retrospective A meeting at the end of each Sprint so the team can Inspect and Adapt the process. Retrospective This is the Sprint Retrospective Challenges Testing Build breaks Improvement
29 Two week Sprint Cycle Example First Sprint M T W Th F ~ 9:00 12:00 Sprint Planning Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum 2-3pm Sprint Review pm Sprint Retrospective ~ 9:00 12:00 Sprint Planning Daily Scrum Second Sprint Etc
30 Are you doing Scrum? 1. Do you deliver working software at the end of each Sprint (less than 4 weeks) that is tested at the feature level? 2. Do you do just enough specification before starting a Sprint and are their near-term Product Backlog items small and clearly understood to be completed within a sprint? 3. Do you have a Product Owner and a Product Backlog with prioritized items estimated by the team? 4. Does the team have a release burndown chart and does the team know their velocity?
31 You know when you are not doing iterative development when: Iterations are longer than 2-4 weeks Team tries to complete specification before programming An iteration does not include testing Iteration does not produce workable code Detailed (task level) plans are accurate estimates and expected at the beginning of a project The sprint plan doesn t reflect what the team is doing.
32 You know when you are not doing agile development when: There is little co-operation within the team Design and code is produced by individual effort Progress is measures by hours spend or documents created instead of working code Builds are done once every three weeks.
34 Product Owner Product visionary Maximizes business value Prioritizes and clarifies requirements.
35 Product Owner Responsibilities Does Provide clear product direction Work with the team closely to clarify requirements Actively manages the product backlog Represents the business and customer needs. Does not Assign work to team members Give fixed date fixed scope projects without team consent Change priorities during an iteration.
36 Exercise: Choosing a Product Owner In your team come up with a list of attributes for your Product Owner Discuss who would make a good Product Owner in your organization
37 The Scrum Master Similar to a Project Manager, yet different A facilitator Removes impediments
38 The Role of the ScrumMaster The ScrumMaster does everything in their power to help the team achieve success This includes: Serving the team Protecting the team Guiding the team s use of Scrum
39 What does a ScrumMaster do? Setup meetings Facilitate meetings M T W T h F ~ 9:00 12:00 Sprint Planning Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scrum Daily Scruma 2-3pm Sprint Review pm Sprint Retrospective
40 What do they do? Coach team in Scrum values and practices 1, Protect from disruption Remove impediments Listen and help Track progress /29/06 5/6/06 5/13/06 5/20/06 5/24/06
41 Exercise: Facilitation Work with your table to describe the difference between directing and facilitating Directive: Do this task now Facilitative: What support do you need to get around this problem? Working with your table, come up with 2 directive and 2 facilitative statements.
42 Exercise: Choosing a ScrumMaster In your team come up with a list of attributes for a good ScrumMaster Discuss who could be a ScrumMaster in your organization.
43 The Scrum Team Cross-functional Self-Organizing Shared Commitment.
44 Team 7 people, + or 2 Has worked with as high as 15, as few as 3 Can be shared with other teams (but better when not) Can change between Sprints (but better when they don t) Can be distributed (but better when colocated) Cross-functional Possesses all the skills necessary to produce an increment of potentially shippable product Team takes on tasks based on skills, not just official role Self-managing Team manages itself to achieve the Sprint commitment
45 Basic truths about team motivation People are most productive when they manage themselves; People take their commitment more seriously than other people s commitment for them People do their best work when they aren t interrupted Teams improve most when they solve their own problems.
46 Ideal Environment Everyone in same location Open space without barriers Resources available; phone, whiteboards, meeting space etc
47 Collaborative workspace INSERT PHOTOS
48 What happens to the manager in Scrum?
49 Manager 2.0 Cross off the list everything that: Conflicts with Scrum Is unnecessary in Scrum Would undermine the team's self-organization and self-management
50 Decide task assignments among the team members and assign them Keep track of whether team-members have done the tasks I ve assigned to them Make commitments on behalf of the team about how much they can get done by X date Give direction to the team on how to do the work, so they can meet the commitment I made Convince team that the commitments made on their behalf are attainable Monitor the team's progress, to make sure they stay on schedule, and aren't having problems Conduct weekly update and 1:1 meetings with team, to surface issues, and provide direction Recruit, interview and hire new members of the team Fire team-members who are consistently not able to perform Provide coaching and mentorship to teammembers Surface issues to the team that they might overlook scaling, performance, security, etc. Provide input on features, functionality, and other aspects of what s being produced Do performance evaluations and provide feedback to team-members Provide advice and input to the team on difficult technical issues that come up Plan training for team, and do careerdevelopment and planning with teammembers Stay abreast of latest developments in the technology their team uses, industry news, etc. Plan and oversee budgets and financials, and think about tools, skills and other future needs Help remove impediments that the team is not able or well-placed to resolve themselves
Learn. Inspect. Adapt: An Overview of Agile Project Delivery Doug Rosenberg and Kara Silva June 19, 2008 Paper Airplanes! The Agile Manifesto We are uncovering better ways of developing software by doing
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
Introduction to Agile Software Development EECS 690 Agile Software Development Agenda Research Consent Forms Problem with Software Engineering Motivation for Agile Methods Agile Manifesto Principles into
Agile QA s Revolutionary Impact on Project Management Introduction & Agenda Rachele Maurer Agile Coach, Platinum Edge Inc. PMP, CSM, PMI-ACP Agenda A quick overview of agile Current QA practices QA using
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
PMP vs. Scrum Master Compatible or Incompatible? Presented by: Karen Little, PMP, CSM, CBAP, ITIL, MCP, MBA Copyright 2007 by Karen Little 1 Agenda Introductions Background on Agile and SCRUM Methodologies
Digital Transformation of the Enterprise for SMAC: Can Scrum help? Scope of this Report October 2015 In this paper, we consider the impact of the digital transformation on software development and whether
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
Agile Development Methods: Philosophy and Practice CPSC 315 Programming Studio Fall 2010 History of Agile Methods Particularly in 1990s, some developers reacted against traditional heavyweight software
Scrum and Agile methods The real world Claus Nyhus Christensen email@example.com Atira About me Master in CS from AAU 2001 2001-2004: Worked at Trifork as a kernel developer of a Java EE server 2004-2007: Worked
SAFETY & RESILIENCE ISSUES IN AUTOMOTIVE SOFTWARE DEVELOPMENT PANEL 1 Safety Panel when 26262 will be issued, enforced? What about 61508? by whom, which authorities? who and how will verify conformance?
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
Agile Project Management: Adapting project behaviors to the software development environment with Bill Doescher, PMP, CSM PrincipalConsultant and Product Development Director Business Management Consultants
Ingegneria del Software Corso di Laurea in Informatica per il Management Agile software development Davide Rossi Dipartimento di Informatica Università di Bologna The problem Efficiency: too much effort
Agility? What for? And how? > Warm-up Session Agile Tour Vienna 2014 Agenda Agile Software Development: reasons & goals Scrum in a nutshell Kanban in a nutshell Agility: prerequisites, limits and corporate
How You Lead Is What You Get: Empowerment is not enough Agile Arizona 2016 6801 185th Ave NE, Suite 200 Redmond, WA 98052 solutionsiq.com 1.800.235.4091 Alan Dayley, Senior Agile Coach Copyright 2015 SolutionsIQ
Project delivery: Progress report Software Engineering Process Economy & Quality ETSF 01 http://cs.lth.se/etsf01 The SPA reports you RECEIVED Your actions on received feedback Excel format preferred Lecture
Agile to the Bone Introduction to Agile by Pietari Kettunen Agenda Problem with traditional software engineering Why Agile is the solution? Roots of Agile Values of Agile Common implementations Scrum Kanban
Agile Project Management Jim Highsmith Chapter 1 The Agile Revolution Ultimate customer value is delivered at the point-of-sale, not the point-of-plan The key opportunity, uncertainty, and risk resides
by Michael Harris ARTICLE There has been much said and written about the mythical conflict between the values and principles of the Manifesto for Agile Software Development 1 (http://agilemanifesto.org/)
WHITEPAPER GET MORE WORK DONE: A MANAGER S GUIDE TO MIXING AGILE AND WATERFALL Project management is shifting. Teams that were siloed before are now asked to work together to ease reporting pains and increase
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
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
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
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
Distributed Agile Development Bapiraju Nandury Product Development Manager Bangalore Development Centre Agenda Distributed / offshore Development Agile Methods Distributed Agile Development Goals of this
Agile Execution for and Beyond IT Fred Koos, PE, PMP, CSM, Pittsburgh PMI VP of Education 31 December 2013 This is an enhanced version of the information presented in the last session at the 11/6/13 Pittsburgh
Chapter 1 Modernizing Project Management In This Chapter Understanding why project management needs to change Finding out about agile project management Agile project management is a style of project management
1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT Enterprise Software Engineering Agenda 1. CMMI and Scrum 2. Kanban Software Engineering 3. Software Development Life Cycle 4. Secure Software Engineering
STATE OF MICHIGAN SUITE Agile Process Guide Another Companion to the Systems Engineering Methodology (SEM) of the State Unified Information Technology Environment (SUITE) Michigan Department of Technology,
TecEd White Paper User-Centered Design and the Agile Software Development Process: 7 Tips for Success At-a-Glance Agile software development teams deliver successful products and applications through their
Introduction We can t solve problems by using the same kind of thinking we used when we created them. Albert Einstein One of the goals of this book is to give you a better perspective on Lean and Agile
Getting Agile with Scrum Mike Cohn Mountain Goat Software firstname.lastname@example.org 1 Mike Cohn - background 2 We re losing the relay race The relay race approach to product development may conflict
Agile Software Development in the Large GI-Vortrag Braunschweig Jutta Eckstein Nicolai Josuttis What Does Large Mean? Large in... scope time people money risks We focus on Large Teams which implies everything
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
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
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
WEBINAR: THE AGILE APPROACH TO PROCESS IMPROVEMENT AND ITS IMPACT ON PRODUCTIVITY Presented by David Consulting Group (DCG) and Computer Aid, Inc. (CAI) 0 Michael Harris President David Consulting Group
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
Incorporating Agile Methods in Large-Scale Systems April 30, 2011 Why would a large-scale software development company want to be agile? Agile methods aim to counter the tremendous costs with changes late
Agile Software Development Application in the Medical Device Industry Kelly Weyrauch Medtronic, Inc. (29 April 2008) Introduction Purpose Provide an introduction to Agile Software Development as it applies
Konferencja "Bezpieczny Projekt" Wrocław 22 czerwca 2010 www.omec.pl Software Development with Agile SCRUM Chandrashekhar Kachole 22 nd of June 2010 1 Let s keep the cell phones in Silent mode 2 Agenda
Integrating Agile into Your Company s SDLC Frank Valerius February 1, 2012 Perception vs Desired State Business perceives IS to be Rigid / inflexible Disconnected from business Slow to respond to change
How to manage agile development? Rose Pruyne Jack Reed What will we cover? Introductions Overview and principles User story exercise Retrospective exercise Getting started Q&A About me: Jack Reed Geospatial
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
BIO PRESENTATION WK2 6/28/2006 10:00 AM AGILE PRODUCTIVITY METRICS Michael Mah QSM Associates, Inc. Better Software Conference June 26 29, 2006 Las Vegas, NV USA Michael Mah Michael Mah is a contributing
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
Introduction to Agile Methods Chennai Agile User Group Kickoff Sanjiv Augustine July 08, 2006 www.ccpace.com Introduction to Agile Methods Page 1 Agenda Agile at a Glance Landscape Basics Typical Benefits
1 Agile Processes The weather-cock on the church spire, though made of iron, would soon be broken by the storm-wind if it did not understand the noble art of turning to every wind. -- Heinrich Heine Many
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
PENETRATION TESTING IN AGILE SOFTWARE DEVELOPMENT PROJECTS Martin Tomanek and Tomas Klima Department of Systems Analysis, University of Economics, Prague, Czech Republic ABSTRACT Agile development methods
Agile Information Management Development Agile Project Management Characteristics Acceptance and even welcome of changing requirements Incremental product delivery Define, develop and deliver early and
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
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
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
Scrum for Video Game Development 1 Mike Cohn - background 2 What is Scrum? One of the agile processes Iterative and incremental Produces demonstrable working software every two to four weeks Results- and
An ISC Introduction to Agile and Scrum Larissa Shapiro All Hands, 2010 Scrum? Rugby? Is this an HR policy violation? What is she on about?? The relay race approach to product development may conflict with
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
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
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
The current issue and full text archive of this journal is available at www.emeraldinsight.com/1065-075x.htm OCLC 18 Accepted October 2010 MANAGING DIGITAL LIBRARIES: THE VIEW FROM 30,000 FEET Understanding
Presented by: and Communicating Agile Project Status to Management 1 Introduction and Agenda Bill Gaiennie, Davisbase Consulting 17 years in software development. 7 years working with software development
SCRUM PRIMER By Pete Deemer and Gabrielle Benefield Pete Deemer is Chief Product Officer, Yahoo! India Research and Development. Gabrielle Benefield is Senior Director of Agile Development at Yahoo! Inc.
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
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
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
Agile Software Development Use case for Agile Software Development Methodology in an Oil and Gas Exploration environment. White Paper Introduction No matter what business you are in, there are critical
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 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
An Executive Scrum Team Alexandre Magno Figueiredo Agenda 1. What led me to use Scrum with executives? 2. Some pains in the executive world 3. The Scrum Executive Alexandre Magno, CST - novembro.2008 1.
Measuring the Impact of Scrum on Product Development at Adobe Systems Peter Green Adobe Systems email@example.com Abstract Over the past several years scrum has grown to become the most commonly used product
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:
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
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
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
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
Terry Fischer Is Agile Scrum the Right Methodology for Your BI Project? Session 3504 LEARNING POINTS What is the Agile Scrum and for what types of projects is it best utilized? How to apply general Agile
Skalierung von agilen Prozessen Ein Erfahrungsbericht OOP 2003 Jutta Eckstein Nicolai Josuttis This Talk is About Agility Large Experience Success Copyright 2003 by N. Josuttis and J. Eckstein 2 1 What
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?
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
Adopting Agile Software Development: Issues and Challenges Hassan Hajjdiab and Al Shaima Taleb College of Engineering and Computer Science Abu Dhabi University Abu Dhabi, UAE, P.O.Box 59911 firstname.lastname@example.org
State of Michigan (SOM) SUITE Agile Process Guide Version 1.0 Another Companion to the Systems Engineering Methodology (SEM) of the State Unified Information Technology Environment (SUITE) July 2012 Department
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