Burn Up and Burn Down An Overview of Scrum. Neal Kuhn Business Systems Architects, LLC
|
|
- Winifred Wells
- 6 years ago
- Views:
Transcription
1 Burn Up and Burn Down An Overview of Scrum Neal Kuhn Business Systems Architects, LLC Scrum Agenda (1) Setup (5) At the end of this segment, the project and slides are set up Agenda (5) At the end of this section, the team will understand the agenda of this presentation Scrum Definition (5) At the end of this section, the team will understand the name and that Scrum is a framework Roles (10) At the end of this section, the team will understand the roles in Scrum Development Team Product Owner Scrum Master Events/ceremonies (10) At the end of this section, the team will understand events in Scrum (Sprints) Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective 1
2 Scrum Agenda (2) Artifacts (15) At the end of this section, the team will understand the artifacts used in Scrum Product Backlog Sprint Backlog Product Increment Release and Sprint Burndown Monitoring Progress Burn Down vs. Burn Up Done (10) At the end of this section, the team will understand the concept of Done Definition of Done SCRUM Origin of Scrum A play in Rugby in which the two sets of forwards mass together around the ball and, with their heads down, and arms interlocked push to gain ground. How we define Scrum (n): An empirical FRAMEWORK within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. A key principle of Scrum is its recognition that during a project, customers can change their minds about what they want and need (often called requirements churn), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the group s ability to deliver quickly and respond to emerging requirements. (Agile value 2) 2
3 Scrum / Agile Benefits The Success rate of waterfall is 11% The success rate of agile is 39%. 61% of agile teams cannot deliver so many teams are "Agile in Name Only. Most of them have no working product at the end of the sprint so they do not meet the second value of the Agile Manifesto. Even then, they reduce development costs by an average of 35%. Research in Silicon Valley showed that if a bug was not found and fixed inside a sprint, it took 24 times as long to find and fix three weeks later for developers building a web operating system. This finding has been replicated in Europe. So for complex products something that could be delivered in a month with Scrum would take 2 years without. For this reason, the CEO of Microsoft banned all test teams last year. So effectively, waterfall is banned at Microsoft. They can't compete with waterfall and neither can you. - Jeff Sutherland, Inventor and Co-Creator of Scrum ( 8/3/2015) Empiricism Scrum is Founded on Empirical Process Control Theory Three Pillars Transparency - Significant aspects of the process must be visible to those responsible for the outcome. Common standards, i.e.: A common language referring to the process must be shared by all participants; A common definition of Done"must be shared by those performing the work and those accepting the work product. Inspection -Scrum users must frequently inspect Scrum artifacts and progress toward a goal to detect undesirable variances. Inspection should not be so frequent that it gets in the way of the work. Adaptation -If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation. 3
4 SCRUM ROLES Three core roles and a range of ancillary roles core roles are often referred to as pigsand ancillary roles as chickens Pigs: Development ( or Scrum) Team Product Owner Scrum Master Everyone else is a chicken Development Team The Development Team consists of professionals who do the work of delivering a potentially releasable increment of Done product at the end of each Sprint. Only members of the Development Team create the Increment. They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule; Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole; Development Teams do not contain sub-teams dedicated to particular domains like testing or business analysis. 4
5 Development Team ( 2) No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn t allowed to act on what anyone else says. Product Owner The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; Ensuring the value of the work the Development Team performs; Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Ensuring the Development Team understands items in the Product Backlog to the level needed. 5
6 Product Owner (2) The Product Owner is one person, not a committee. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner s decisions are visible in the content and ordering of the Product Backlog. Scrum Master The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master serves the Development Team in several ways, including: Coaching the development Team in self-organization and cross-functionality; Teaching and leading the Development Team to create high-value products; Removing impediments to the Development Team s progress; Facilitating Scrum events as requested or needed; and, Coaching the Development Team 6
7 Scrum Master -(2) The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team. The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Backlog management; Clearly communicating vision, goals, and Product Backlog items to the Development Team; Teaching the Scrum Team to create clear and concise Product Backlog items; Understanding long-term product planning in an empirical environment;. SCRUM EVENTS/ Ceremonies Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. Scrum uses time-boxed events, such that every event has a maximum duration. This ensures an appropriate amount of time is spent planning without allowing waste in the planning process. Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. 7
8 Scrum Events / Time Boxes Sprint Sprint Planning Meeting Developmental Work Daily Scrum / Standup Meeting Sprint Review Sprint Retrospectives Sprint The heart of Scrum is a Sprint, a time-box of one month or less during which a Done, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints contain and consist of the Sprint Planning Meeting, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. During the Sprint: No changes are made that would affect the Sprint Goal; Development Team composition remains constant; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned. 8
9 Sprint Time Length Each Sprint may be considered a project with no more than a one-month horizon. Like projects, Sprints are used to accomplish something. Each Sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product. Sprints are limited to one calendar month. When a Sprint s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints enable predictability by ensuring inspection and adaptation of progress toward a goal at least every calendar month. Sprints also limit risk to one calendar month of cost. Sprint Planning Meeting The work to be performed in the Sprint is planned at the Sprint Planning Meeting. This plan is created by the collaborative work of the entire Scrum Team. The Sprint Planning Meeting is time-boxed to eight hours for a onemonth Sprint. For shorter Sprints, the event is proportionately shorter. For example, two-week Sprints have four-hour Sprint Planning Meetings. The Sprint Planning Meeting consists of two parts, each one being a time-box of one half of the Sprint Planning Meeting duration. The two parts of the Sprint Planning Meeting answer the following questions, respectively: What will be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? 9
10 Sprint What will be done/ delivered? In this part, the Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner presents ordered Product Backlog items to the Development Team and the entire Scrum Team collaborates on understanding the work of the Sprint. The inputs to this meeting: the Product Backlog the latest product Increment, projected capacity of the Development Team during the Sprint, past performance of the Development Team. The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint. Sprint How will the work be chosen? The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work may be of varying size, or estimated effort. However, enough work is planned during the Sprint Planning Meeting for the Development Team to forecast what it believes it can do in the upcoming Sprint. Story Time As a xxx, I will be able to yyy Planning Poker, Fist of Five, (clothing sizes) Complexity vs time By the end of the Sprint Planning Meeting, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment. 10
11 Daily Scrum / Stand Up Meeting The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, each Development Team member explains: What has been accomplished since the last meeting? What will be done before the next meeting? What obstacles are in the way? Why Daily Scrum? Transparency high visibility of progress and accountability Adaptation catch problems early and allow for rapid response / change THIS IS NOT A STATUS MEETING TO COLLECT INFORMATION. It is a meeting in which every team member make commitments to each other. 11
12 Sprint Review A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done. This is an informal meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. Sprint Review (2) The Sprint Review includes the following elements: The Development Team demonstrates the work that it has Done and answers questions about the Increment; The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; The Product Owner identifies what has been Done and what has not been Done ; The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date; and, The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning Meetings. 12
13 Sprint Retrospective The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning Meeting. The purpose of the Sprint Retrospective is to: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the Definition of Done as appropriate. Scrum Artifacts Scrum s artifacts represent work or value in various ways that are useful in providing transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information needed to ensure Scrum Teams are successful in delivering a Done Increment. 3 Principal Artifacts Product Backlog Sprint Backlog Increments Monitoring Progress Release Burn down Product Burn down Story Points, not time (Information Radiators) 13
14 Information Radiator An information radiator is a large, highly visible display used by software development teams to track progress. The term was first coined by Alistair Cockburn, one of the judges for the Ultimate Wallboard contest, in his book as follows: An Information radiator is a display posted in a place where people can see it as they work or walk by. It shows readers information they care about without having to ask anyone a question. This means more communication with fewer interruptions." It is large and easily visible to the casual, interested observer It is understood at a glance It changes periodically, so that it is worth visiting It is easily kept up to date 27 Product Backlog The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, and estimate. A The Product Backlog evolves as the product and the environment in which it will be used evolves. Story points, not time ( important so I mention it again) 14
15 Product Backlog (2) The Product Backlog is often written in story format, and ordered by value, risk, priority, and necessity. Top-ordered Product Backlog items drive immediate development activities. The higher the order, the more a Product Backlog item has been considered, and the more consensus exists regarding it and its value. Higher ordered Product Backlog items are clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail. Product Backlog items that will occupy the Development Team for the upcoming Sprint are fine-grained, having been decomposed ( stories) so that any one item can be Done within the Sprint time-box. Product Backlog items that can be Done by the Development Team within one Sprint are deemed ready or actionable for selection in a Sprint Planning Meeting. Sprint Backlog The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality. The Sprint Backlog defines the work ( stories, tasks) the Development Team will perform to turn Product Backlog items into a Done Increment. The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. 15
16 Monitoring Progress At any point in time in a Sprint, the total work remaining in the Sprint Backlog items can be summed. The Development Team tracks this total work remaining at least for every Daily Scrum and projects the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress. Scrum does not consider the time spent working on Sprint Backlog Items. The work remaining and date are the only variables of interest. Monitoring Progress (2) Scrum does not consider the time spent working on Sprint Backlog Items. The work remaining and date are the only variables of interest. Terms / definitions Scope / Target Beware target fixation Velocity Efficiency Variance Efficiency / Effectiveness waterfall is efficient agility is effective Release Burn down/burn up Product Burn down/burn up 16
17 Burn Down A burn-down chart tracks how much work remains on your project and whether you ll hit your deadline. The vertical axis measures work done, and projects work remaining The horizontal axis marks your iterations After each iteration you mark your progress on the chart and you can project forward to see whether or not you ll hit your target end date (assuming no changes) Burn Down Chart 34 17
18 Burn Down Chart positive variance 35 Burn Down Chart negative variance 36 18
19 Burn Down Chart - Question What happens if complexity/task is added or a story/task is dropped? Scope has been changed. How do I indicate in the burn down? Modify initial scope of work so line is continuous? Negates planning and all tracking to date Stair step line to indicate change and notate? More accurate, but a tracking nightmare 37 Burn Down Chart - Example Scenario: Initial plan was 14 points. On day 3, a complexity was uncovered, and 2 additional points were added. On day 5, it was determined to drop the story ( return to backlog), and reduce 4 points. Burndown to date: Day BD/Hist BD/TBD Delta New TBD Day Day Day Day Day Day Use initial velocity 38 19
20 Burn Down Chart (changes) 39 Burn Down Chart (changes)? 40 20
21 Burn Up A burn-up chart tracks how much work is done. It shows more information than a burn-down chart because it also has a line showing how much work is in the project as whole (the scope as workload), and this can change. It tracks what has been done and what s remaining. More adaptable to change. Burn Up Chart 42 21
22 Burn Up Chart positive variance 43 Burn Up Chart 44 22
23 Burn Up Chart (change 1) 45 Burn Up Chart (change 2) 46 23
24 Definition of Done When the Product Backlog item or an Increment is described as Done, everyone must understand what Done means. Members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the Definition of Done for the Scrum Team and is used to assess when work is complete on the product Increment. The same definition guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning Meeting. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team s current Definition of Done. As Scrum Teams mature, it is expected that their Definition of Done will expand to include more stringent criteria for higher quality. Done DoD Dilemma DoD Dilema -Different DoD for different teams For development some code is considered done when it has been written, compiled, debugged, unit tested, checked-in in a common repository, integrated in a build, verified by a build verification tool and documented using an automatic documentation generator. For automation test cases are considered done when the corresponding automated testing scripts have been coded, unit tested and ran against a build. For quality engineering done means that the user stories received on a specific build have been tested by running testing cycles, encountered bugs have been reported using a bug tracking tool, fixes provided have been validated and the associated trackers have been closed. In consequence, test cycles include both manual and automated test case execution. For project managers done means that the sprint has ended and the user stories have been completed (not necessarily accepted by QE) and the schedule hours burned. Moreover, for managers done usually means that there s something anything that can be presented to the stakeholders in a demo. 24
25 Done DoD Dilemma (2) DoD Holes DevelopmentDoDis not enough because code was produced but not tested, at least not tested from the users perspective. Crucial tests like functionality, usability, performance, scalability and stress are still pending. Without passing all those tests, at least to a certain level, the product is simply not good enough for being shipped. A big temptation is to consider that in early stages of the product, the code is not required to pass all tests or there s no need to test it at all. This of course violates the very definition / concept of a potentially shippable product. Automation DoD is not good enough either, because it only covers code that has been written to test code, no bugs discovered, validated, retested or closed. It s very true that automated test cases save many man hours of manual testing, but it should only be used as a tool that helps Quality Engineers in their work and not as a milestone that if reached qualifies the product for release. Project Manager s DoD it s focused on metrics and high level information. The biggest risk for Project Managers is to look at the wrong metrics and try to put a product out of the door when it s not complete or stable enough. Avoiding biased perceptions that come from information collected from only one group of engineers in a team is the key for telling if the product is ready or not to go into production. Done A starting Definition Definition of Done Coming from a quality background, Quality Engineering DoD in my opinion, is the initial definition that contributes the most to the goal of having a potentially shippable product; the reason in simple, QE should be the last check point for telling if the implemented user stories are good enough for being considered as part of a potentially shippable product. Potential additions can include documentation to be provided is available and has been reviewed for technical accuracy. Another is that automated test cases have been checked for effectiveness and real contribution to bug detection and validation. 25
26 DoD -First Pass Done means that the user stories received on a specific build have been included andtested by running testing cycles, encountered bugs have been reported using a bug tracking tool, fixes provided have been validated and the associated trackers have been closed. In consequence, test cycles include both manual and automated test case execution. DOD - Summary It is evident that we need a DoD that can work for the whole team helping it to remain focused in the right direction and serving at the same time as a true enabler for the potentially shippable product concept. Start simple, and enhance as skills and capability of Team matures. 26
27 Scrum Summary Definition of Scrum (n): An empirical FRAMEWORK within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. A key principle of Scrum is its recognition that during a project, customers can change their minds about what they want and need (often called requirements churn), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the group s ability to deliver quickly and respond to emerging requirements. But, it s a FRAMEWORK, not a total solution Design Unit vs Integration Additional components to complete for the total solution I m Done Thanks nealk@isosys.com 27
28 Background - Agile Manifesto The Agile Manifesto is based on twelve principles: [15] Customer satisfaction by early and continuous delivery of valuable software Welcome changing requirements, even in late development Working software is delivered frequently (weeks rather than months) Close, daily cooperation between business people and developers Projects are built around motivated individuals, who should be trusted Face-to-face conversation is the best form of communication (co-location) Working software is the principal measure of progress Sustainable development, able to maintain a constant pace Continuous attention to technical excellence and good design Simplicity the art of maximizing the amount of work not done is essential Best architectures, requirements, and designs emerge from self-organizing teams Regularly, the team reflects on how to become more effective, and adjusts accordingly 55 28
CS314 Software Engineering Project Management
CS314 Software Engineering Project Management Dave Matthews Software process movements Predictive 1970 Waterfall Iterative 1980s, 1990s Spiral, RAD, RUP Adaptive (Agile) late 1990s XP, Scrum, Crystal,
More informationWhat is Scrum: An Introduction to the Scrum Framework
What is Scrum: An Introduction to the Scrum Framework Eric Naiburg Vice President of Marketing and Operations eric.naiburg@scrum.org April 4, 2018 @ScrumDotOrg 1 Improving the Profession of Software Delivery
More informationScrum. a description. V Scrum Alliance,Inc 1
Scrum a description V 2012.12.13 2012 Scrum Alliance,Inc 1 Scrum Principles Values from the Agile Manifesto Scrum is the best-known of the Agile frameworks. It is the source of much of the thinking behind
More informationSCRUM GUIDE SCRUM GUIDE 02. * Agile Software Development with Scrum, Ken Schwaber, Microsoft Press, 2004
SCRUM GUIDE SCRUM GUIDE This guide explains how to use Scrum to build products. In doing so, it will describe how the framework and its artifacts, time-boxes, roles and rules work together. Scrum does
More informationEvents. Artifacts. Roles. Product Owner Scrum Master Development Team. Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective
Scrum Lecture 2 1 Roles Product Owner Scrum Master Development Team Events Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Artifacts Project Charter Product Backlog Sprint Backlog
More informationAgile Methodologies. Introduction ISSSR 2013/2014
Agile Methodologies Introduction Agenda Agile Manifesto Principles Design Scrum 2 What is Agile? A set of methods for software development Iterative Incremental Assume changeability of requirements First
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 7 Agile Methodologies: Scrum 1 Agile Methodologies: Brief History First appeared in 1995. The once-common perception that agile methodologies
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More informationIntroduction to Agile (Scrum)
Introduction to Agile (Scrum) Meganadha Reddy K. Technical Trainer NetCom Learning www.netcomlearning.com Agenda Agile - Introduction Manifesto for Agile Development Agile Methodologies Scrum Roles, Artifacts,
More informationAgile Certified Professional
Certified Professional Study Guide Take the Certification Online www.scrumprofessionals.org Contents 1. AGILE PRIMER... 1 Roles in... 1 Cross-functional Team... 2 How an Team Plans its Work?... 3 What
More informationCopyright Intertech, Inc All Rights Reserved. May 18, 2011
Copyright Intertech, Inc. 2011. All Rights Reserved. May 18, 2011 About Me Dave Schueck Principal Consultant Intertech Dschueck@Intertech.com 20 years experience Variety of technologies, roles, systems,
More informationAGILE methodology- Scrum
AGILE methodology- Scrum What is Agile? This is one of the biggest buzzwords in the IT industry these days. But, what exactly is agile? The Agile model provides alternatives to traditional project management.
More informationSoftware Development Life Cycle
Software Development Life Cycle Author : harvix-distrogmail-com When people are asked to define the SDLC (Software Development Life Cycle), they often come up with something like the following: 1. Planning
More informationScrum Intro What s in it for me?
Scrum Intro What s in it for me? Prepared by Bachan Anand Please dial in to (218) 895-4640 PIN: 3289145 Agenda Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint What s in it for me Please
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 informationAGILE SOLUTIONS. Agile Basics
AGILE SOLUTIONS Agile Basics info@one80services.com one80services.com AGILE SOLUTIONS Agile Basics Table of Contents 2 Who We Are 3 What Is Agile? 4 Agile Values 5 Agile Principles 6 Agile Development
More informationScrum. Software Engineering and. The Waterfall model. The Waterfall model - some arguments. The Waterfall model - some arguments. Time.
Software Engineering and Scrum autumn 2010 Department of Computer and Information Science Linköping University, Sweden The Waterfall model Requirements One of the first life-cycle models (Royce, 1970)
More informationThis course will explore how your projects can easily and successfully make the transition to an effective Agile environment.
AGILE AGL310: Planning and Managing Agile Projects Agile Project methodology Training for Software IT Management. Learn how to apply Agile to current projects: explore how your projects can easily and
More informationScrum Team Roles and Functions
Scrum Team Roles and Functions What is a Scrum Team? The purpose of a Scrum team is to deliver products iteratively and incrementally, maximizing opportunities for feedback Scrum teams are comprised by
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 10 Scrum: Sprint Execution 1 Sprint Execution When? Sprint execution accounts for the majority of time during a sprint. It begins after sprint
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 informationKeywords: Scrum framework, agile software development, change management, iterative development.
International Journals of Advanced Research in Computer Science and Software Engineering ISSN: 2277-128X (Volume-7, Issue-7) Research Article July 2017 Implementation of Change Management in Software Development
More informationCertified Scrum Product Owner Course. Pre-Course Reading and Exercises
Certified Scrum Product Owner Course Pre-Course Reading and Exercises For course preparation, please read the Scrum Guide http://www.scrumguides.org/docs/scrumguide/v2016/2016-scrum- Guide-US.pdf and Pierluigi
More informationAgile Program Development. Agile Manifesto 9/3/2013. What is Agile Development? 12 Principles of Agile Development 1 of 4
What is Agile Development? Agile Program Development CSCI 479: Computer Science Design Project Fall 2013 Xiannong Meng Agile software development is a group of software development methods based on iterative
More informationRussell Pannone February 10, 2009
Russell Pannone February 10, 2009 webeagile@aol.com About Me 27 years of System/Software Product Development Experience Developer Data Modeler Team Lead Project Manager Certified Scrum Master/Certified
More informationgetting started with Scrum
getting started with Scrum www.agnc.cc 20/12/2017 v1.2 Scrum. A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest
More informationAgile Test Plan How to Construct an Agile Test Plan
Agile Test Plan How to Construct an Agile Test Plan XBOSoft White Paper How to Construct an Agile Test Plan www.xbosoft.com 2 Agile is changing not only the way we develop software but the way we work
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 3 Scrum Framework 1 Scrum Origins First mentioned as a development method in 1986, referring to a fast and flexible product development process
More informationScrum Testing: A Beginner s Guide
Scrum Testing: A Beginner s Guide What is Scrum? Building complex software applications is a difficult task. Scrum methodology comes as a solution for executing such complicated task. It helps development
More informationAn Introduction to Scrum
What is Scrum? Even projects that have solid, well-defined project plans encounter some degree of change. Shifting market conditions, budget cuts, staff restructuring, or any number of influences will
More informationChapter 7. Project Reporting Keeping Everything Visible
Chapter 7 Project Reporting Keeping Everything Visible A Scrum project is controlled by means of frequent inspection of the project followed by necessary adaptations Daily Scrum to get a feel for the tone,
More informationJohanna Rothman. Chapter 1 Why Agile and Lean Approaches Work. Copyright 2017
Johanna Rothman Chapter 1 Why Agile and Lean Approaches Work Copyright 2017 Agile and Lean Approaches Why such approaches exist! Software, we have a problem It was thought you could hand a software team
More information2. True or false: In Scrum all the requirements for the project are known prior to the start of development.
CTC-ITC 310 Program Management California State University Dominguez Hills Fall 2018 Instructor: Howard Rosenthal Assignment 5 A Deeper Look At Agile Methodologies Answer Sheet Each question is worth 10
More informationManaging Projects of Chaotic and Unpredictable Behavior
Managing Projects of Chaotic and Unpredictable Behavior by Richard Dick Carlson Copyright 2013, Richard Carlson; All Rights Reserved 1 Managing Projects of Chaotic and Unpredictable Behavior Dick Carlson,
More informationFIT2101 Software Engineering Process and Management
FIT2101 Software Engineering Process and Management Agile and Software Process Models Topics Covered Features of Agile What Agile Isn t Agile Process Models Software Process Models In 2001 leaders of lightweight
More informationSession 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation
Session 11E Adopting Agile Ground Software Development Supannika Mobasser The Aerospace Corporation The Aerospace Corporation 2017 Overview To look beyond the horizon and to embrace the rapid rate of change
More informationAgile Planning. Petri Heiramo. Agile Coach, CST
Agile Planning Petri Heiramo Agile Coach, CST An Agile Plan Is Not a Rough Guide Some teams think that, if they did not finish all stories, that was OK, we are agile Postponing stories was seen as an acceptable
More informationFoundations of Software Engineering. Process: Agile Practices Michael Hilton
Foundations of Software Engineering Process: Agile Practices Michael Hilton 1 Learning goals Define agile as both a set of iterative process practices and a business approach for aligning customer needs
More information"Charting the Course to Your Success!" Planning and Managing Agile Projects Course Summary
Course Summary Description This 3-day course aims at introducing its attendees to the core values, principles, and practices of Agile. This course is a more elaborate version of the Certified Scrum Master
More informationPresented by: and. Communicating. Agile. Project Status. Management. Wednesday, April 10, 13
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
More informationSoftware Development*
Software Development* Process, Models, Methods, Diagrams Software Development Life Cyles Part - IV *from http://www.cs.washington.edu/403/ What is Scrum? Scrum: It s about common sense Is an agile, lightweight
More informationSCRUM - compact The agile software development methodology
Scrum in 30 seconds Scrum is an empirical way to manage software development projects. Scrum is made up of an easy set of rules and ensures that every team member feels the responsibility of a project
More informationPresented by Only Agile. What is Agile?
Presented by Only Agile What is Agile? Myths We re Agile we don t do documentation There is no planning in Agile its just anarchy We can t give you a date we re using Agile Agile means I can change my
More informationAgile Software Development in a Regulated Environment. Natalie Custer
Agile Software Development in a Regulated Environment Natalie Custer Disclaimer This presentation represents the understanding of the presenter on the topic addressed. It does not in anyway, form or like
More informationJohanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right. Copyright 2017
Johanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right Copyright 2017 Start you Agile project right Projects need direction teams need to know where
More informationScrum Master / Agile Project Manager An Approach for Personal Competency Development
Scrum Master / Agile Project Manager An Approach for Personal Competency Development Summer 2013 www.illustratedagile.com 2013 Len Lagestee HOW TO USE THIS APPROACH There are two ways to use this document.
More informationScrum - Introduction. Petri Heiramo. Agile Coach, CST
Scrum - Introduction Petri Heiramo Agile Coach, CST Scrum Started in the Harvard BR. The relay race approach to product development may conflict with the goals of maximum speed and flexibility. Instead
More informationLecture 8 Agile Software Development
Lecture 8 Agile Software Development Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics
More informationSEPTEMBER 2018 The Agile Team s Playbook to Doing Agile
SEPTEMBER 2018 The Agile Team s Playbook to Doing Agile A how-to guide for agile practitioners Agile is an umbrella term for a variety of work-management approaches that share common principles, among
More informationUser-centered System Design. Agile
User-centered System Design Agile Department of Information Technology Methods - what are they? Why do we have them? Business modeling Usability Design Requirements Analysis & design Implementation Test
More informationAgile Introduction for Leaders
Agile Introduction for Leaders Learning Objectives Gain an understand of what is driving the need for agile Learn the fundamentals of agile: values, principles and practices Learn what managers and leaders
More informationAdvantages of Agile model:
Agile methodology Agile : We divide the application components (parts) and work on them one at a time. When one is ready we deploy it to production (live environment). Agile is very collaborative and interactive.
More informationCM MatchPoint Agile. Christoph Heinrich, CM First Plex Track A / Session 17
CM MatchPoint Agile This sessions shows how to use CM MatchPoint for the management and automated deployments in agile projects using frameworks like SCRUM Christoph Heinrich, CM First Plex Track A / Session
More information13. Team evolutionary developement
13. Team evolutionary developement Most of the software projects require a larger effort than a solo programmer can handle Programmers have to organize themselves into teams Agile teams Directed teams
More informationHELP!!! THE SCRUM MASTER IS THE IMPEDIMENT!
HELP!!! THE SCRUM MASTER IS THE IMPEDIMENT! @ryanripley PMI-ACP, PSM I, PSM II, PSE, PSPO I, PSD I, CSM, and CSPO SCRUM IN ONE SLIDE ROLES: Scrum Master, Product Owner, Developer ARTIFACTS: Product Backlog,
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 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 informationCSC301. Scrum, detailed view of an agile process. CSC301, Winter 2016
CSC301 Scrum, detailed view of an agile process CSC301, Winter 2016 Today s Tour - Scrum We will take a tour of Scrum An agile process Well More framework than process Extremely popular in the last 5-10
More informationScrum is. A framework for developing and sustaining complex products. Lightweight Simple to understand Extremely difficult to master
Scrum is A framework for developing and sustaining complex products Example: software development Lightweight Simple to understand Extremely difficult to master Scrum Is grounded in empirical process control
More information}w!"#$%&'()+,-./012345<ya
MASARYK UNIVERSITY FACULTY OF INFORMATICS }w!"#$%&'()+,-./012345
More informationAcceptance Criteria. Agile. Details that indicate the scope of a user story and help the team and product owner determine done-ness.
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 of ideas that Scrum falls within. These
More informationStakeholders. I know my stakeholders There is a clear understanding of who are the stakeholders. I know many of them personally.
Product Vision I know the purpose and motivation of creating the product I understand and can explain why the product should be developed. There is a written document that describes the reasons for why
More informationMichael Prince PMI-ACP Application Development Manager Richland County
Michael Prince PMI-ACP Application Development Manager Richland County GOALS Tell You About Agile 5000 Ft View Talk Briefly About How You As a Programmer Fit Into Agile Prepare You For The Next Session
More informationSustainable Pace How can we help our teams achieve it? http://www.bigvisible.com 2011 BigVisible Solutions, Inc. Facilitator Bob Sarni 25 years focused on team development, leadership mentoring and coaching,
More informationAgile Software Development. Agile Software Development Basics. Principles of the Agile Alliance. Agile Manifesto. Agenda. Agile software development
Agile Software Development T-110.6130 Systems Engineering in Data Communications Software P, Aalto University Agile software development Structured and disciplined, fast-paced Iterative and Incremental
More informationInternational Scrum Master Foundation. Study Guide Take the Certification online
International Scrum Master Foundation Study Guide Take the Certification online www.scrum.as Contents Chapter 1: WHAT IS SCRUM?... 3 Chapter 2: INTRODUCTION TO SCRUM - A REAL WORLD EXAMPLE... 5 Chapter
More informationWhy SCRUM I O A N N I S K O S T A R A S A G I L E C R E T E
Why SCRUM I O A N N I S K O S T A R A S A G I L E C R E T E 2 0 1 6 Agenda 2 What is SCRUM? Why it sucks? What is Scrum? 3 SCRUM is Scrum in a Nutshell a methodology an agile framework for software development
More informationScrum er ikke en religion
Scrum er ikke en religion Jesper Boeg, Agile Coach jbo@trifork.com January 25, 2011 In general Trifork Software development Coaching Workshops, seminars and conferences Please let me know if: You have
More informationApplication of Agile Delivery Methodologies. Bryan Copeland Energy Corridor Brown Bag Event August 31, 2016
Application of Agile Delivery Methodologies Bryan Copeland Energy Corridor Brown Bag Event August 31, 2016 Agenda My Background What Do We Mean by Agile? My Team s Journey Our Use of Scrum Agile Coaching
More informationAgile for Hardware Development
Agile for Hardware Development. Agile for Hardware Development PLAYBOOK PLAYBOOKHQ.co Contents Background Agile Manifesto Agile Values Cost of Delay Agile Principles Agile Methods Conclusion 3 4 6 7 9
More informationAgile 101. Brent Hurley Chief Problem Solver Gira Solutions. Values, Principles
Agile 101 Values, Principles and Brent Hurley Chief Problem Solver Gira Solutions @girabrent @GoAgileCamp Core Agile Series Sponsored by For$more$informa+on$on$Agile$Training,$contact:$info@bra6oninc.com$
More informationScrum Product Owner Course 03 - Roles and Responsibilities
Scrum Product Owner Course 03 - Roles and Responsibilities Course Slide 1 Roles and Responsibilities Topics Covered Product Owner Role Scrum Master Role Scrum Team Role Other Roles Slide 2 Learning Objectives
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationDASA DEVOPS. Glossary
DASA DEVOPS Glossary Version 1.0.0 May 2016 Agile Agile is a time-boxed and iterative approach of software delivery. It aims to build software incrementally from the start of the project. Agile Benefits
More informationEVERYTHING YOU VE HEARD ABOUT AGILE DEVELOPMENT IS WRONG
EVERYTHING YOU VE HEARD ABOUT AGILE DEVELOPMENT IS WRONG Simon O Toole Australian Astronomical Observatory SOFTWARE DEVELOPMENT QUIZ What is the Waterfall model of software development? What are the advantages
More informationHOW WE WORK: OUR SYSTEM: OUR METHODOLOGY:
HOW WE WORK: We are commonly asked about how our ticket system and workflows function, and this document addresses that in some detail. We hope the videos and text are helpful. If you d prefer a real-time
More informationSelf-Organizing Teams: What and How Nitin Mittal, Accenture, 7 January 2013
Self-Organizing Teams: What and How Nitin Mittal, Accenture, 7 January 2013 Do you have a self-organizing team? If so, half the battle is already won. But if not, beware: Creating a selforganizing team
More informationMike Vincent. mvasoftware.net
Scrum and ALM Coach Over 30 years as software developer and architect Marketing director, construction project manager and structural engineer previously Microsoft MVP - Visual Studio ALM Professional
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationIntroduction to Agile Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016
Introduction to Agile Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016 1 Goals Introduction to Agile Life Cycles The Agile Manifesto and Agile Principles Agile Life Cycles
More informationManagement by Consensus
Management by Consensus A Manager's Guide to Scrum A Presentation for The CoolTech Club Menlo Park, June 7 th, 2006 Tobias Mayer tobias@agilethinking.net Presenter: Tobias Mayer Software Developer Educator,
More informationA philosophy first and methodology second
Demystifying Agile A philosophy first and methodology second Authors: Jonathan McAllister Page 1 WHERE AGILE CAME FROM In 2001, a group of well-known software industry pundits converged on the small town
More informationAgile Development Processes. CSCE Lecture 3-08/31/2017
Agile Development Processes CSCE 740 - Lecture 3-08/31/2017 Common Practice: Code & Fix Sit down, write out the code, and fix problems as they occur. No formal structure to development. What is wrong with
More informationIntroduction. Agile overview. 12 Agile Principles
01 02 03 05 06 08 09 15 20 21 23 25 Introduction Agile overview 12 Agile Principles Agile Development Cycle Advantages & Disadvantages of Agile Top Methodologies Used to Implement Agile Top Methodologies
More information8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master
8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master 1. Introduction 1 min. 2. Waterfall vs Agile 5 min. 3. Agile - General Concepts 5 min. 4. Agile methods: Scrum vs XP vs Lean
More informationAgile Manifesto & XP
Agile Manifesto & XP Chapter 3.1-3.3 CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville. Slides 8 18-06-10 1 Topics 1) What is Agile trying to do? 2) How to choose plan-driven
More informationScaling Software Agility:
Scaling Software Agility: Best Practices for Large Enterprises Agile 201 Seven Agile Team Practices that Scale 1 Seven Agile Team Practices That Scale 2 1. Define/Build/Test Team 3 Conway s Law Organizations
More informationAgile Mindset (1/17/2019 for the Ocean State PMI)
Get connected with Leapfrog LeapFrog Systems Agile Mindset (1/17/2019 for the Ocean State PMI) Agenda 1. What is Agile? 2. Compare Agile and Traditional SDLC s 3. Agile Delivery Frameworks Scrum, Kanban,
More informationCan Your Proposal Process Be More Agile?
Can Your Proposal Process Be More Agile? 11.21.14 Maryann Lesnick Principal Consultant Lohfeld Consulting Questions to Explore Shipley and other proposal industry best practices have been around for 30
More informationA Practical Approach to Project Management in a Very Small Company
A Practical Approach to Project Management in a Very Small Company Edgar Caballero and Jose A. Calvo-Manzano Departamento Lenguajes y Sistemas Informáticos e Ingeniería del Software Universidad Politécnica
More informationAgile Development Methods: Philosophy and Practice. CSCE 315 Programming Studio, Fall 2017 Tanzir Ahmed
Agile Development Methods: Philosophy and Practice CSCE 315 Programming Studio, Fall 2017 Tanzir Ahmed History of Agile Methods Particularly in 1990s, some developers reacted against traditional heavyweight
More informationJoe s Unofficial Scrum Checklist
Joe s Unofficial Scrum Checklist This list is based off Henrik Kniberg s Unofficial Scrum CheckList. See http://www.crisp.se/scrum/checklist We recommend you use this list as basis for discussion, mostly
More informationAgile for Hardware Development
Agile for Hardware Development. Agile for Hardware Development Playbook Playbookhq.co Contents Background Agile Manifesto Agile Values Cost of Delay Agile Principles Agile Methods Conclusion 3 4 6 7 9
More informationAGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP
AGILE LESSONS FROM THE NEW PMBOK Presented by Eddie Merla, PMI-ACP, PMP 2 Agenda Summary of Changes Agile Concepts Five Mindset Shifts Agile Methods & Scrum Q&A Wrap-up 3 Summary of Changes Project managers
More informationCertified Scrum Master
Certified Scrum Master Notebook November 5, 2013 1 Overview Scrum 2 Scrum Framework What is it Scrum is an agile framework that allows us to focus on delivering the highest business value in the shortest
More informationSign up to mailing list Join Slack, teaching team is available. All links are on the course website Slides are uploaded there too
Sign up to mailing list Join Slack, teaching team is available All links are on the course website Slides are uploaded there too Week 1 (Oct 16 Oct 20) Introduction lectures Week 2 (Oct 23 Oct 27) Work
More informationCriteria. Kanban. Scrum. Acceptance. Acceptance Criteria. Kanban. Scrum. Refinement. Agile Manifesto. Acceptance Test. Product Backlog.
Scrum Scrum Kanban Kanban XP XP Acceptance Criteria Acceptance Criteria Agile Manifesto Agile Manifesto Acceptance Test Acceptance Test Backlog Refinement Backlog Refinement Burndown Chart Burndown Chart
More informationScrum an Agile Process
Topics 1) Who does what in a Scrum team? 2) What does a week as a Scrum developer look like? Scrum an Agile Process CMPT 373 Slides 01 Dr. B. Fraser 17-09-01 2 17-09-01 1 Software Development Process Recap
More informationThe Stability States of Scrum: 2 Keys to Building High Performing Teams
The Stability States of Scrum: 2 Keys to Building High Performing Teams Alicia R. McLain, Lean Agile Transformation Executive Coach E: SdAgileCoP@gmail.com #DoDbuildsHighPerformingTeams #DoRbuildsHighPerformingTeams
More informationAGILE MYTH BUSTERS- THAT S NOT AGILITY!
AGILE MYTH BUSTERS- http://pmsymposium.umd.edu/pm2017/ THAT S NOT AGILITY! Susan Parente, PMP, PMI-ACP, CSM, PSM I, PMI-RMP, CISSP, ITIL, RESILIA, MS Eng. Mgmt. 2017 Project Management Symposium Agile
More information