Definition of Done – why it matters

Slides:



Advertisements
Similar presentations
An Effective Agile Testing Framework AN AGILE TESTING FRAMEWORK
Advertisements

> Sprint Planning Presentation API Release: Date: Presented by:
Scrum in 10 slides.
National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House Mark Parker (800)
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
The Business Analyst Role in Agile Projects
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 4: Phase Management - Elaboration.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
AGILE DELIVERY FACILITATION Agile Project Manager should see his stakeholders as kids and aim to help them be successful in their respective goals, each.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Business and Information Technology Working Together for the Regulator Stephen Hord, Director of Product Development – UBmatrix.
What Is DevOps? DevOps is "a portmanteau of 'development' and 'operations'" and is "a software development method that stresses communications, collaboration,
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Cultivating Agile Requirements
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Who is Gregg? 1 Mile
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Test all the things! Improving code quality at the OU with Continuous Integration MoodleMoot Ireland UK 2016 Mark Johnson Tony Lin.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Digital Transformation with DevOps
Figure 1. Gartner DevOps Model
Configuration Management
From manual test shop to fully automated test coverage: A How-To session to speed up your journey Jayshree Bhakta ITHAKA/JSTOR.
Agile Metrics that Matter
Office 365 Security Assessment Workshop
Requirements Determination
The Strategic Role of Information Development in Continuous Delivery
Scrum and TargetProcess
Agile Training – Agile Overview
27/05/2018.
Fundamentals of Monitoring and Evaluation
Integrate Agile Testing into the Process
Configuration Management
September 20, 2017 Agile Techniques Workshop Susan Futey
Information Technology Project Management – Fifth Edition
Pega 9/14/2018 8:48 AM Definition of Done = ready for PO acceptance
Rapid software development
Advantages OF BDD Testing
CEN 4010 Intro to Software Engineering Professor Alex Roque
Johanna Rothman Create Technical Excellence Chapter 9
Project Charter <Project Name>
How to Successfully Implement an Agile Project
Attend|Learn|Grow Taking Your Career to the Next Level
Johanna Rothman Know What “Done” Means Chapter 11
Guidance notes for Project Manager
Scrum Overview.
Definition of Ready.
Requirements Analysis
Project Ideation Agile Down-to-Earth © 2016.
Problem Solving Activities
Microsoft /27/2018 5:55 PM BRK2209 Managing the Complexity of Working Together Collaboration in the Office Apps Carol Grant – Sr. Product Marketing.
Test Driven Lasse Koskela Chapter 9: Acceptance TDD Explained
Agile practices for documentation teams
Sprint Planning April 2018.
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Real World Scrum with TFS & VSTS / Azure DevOps
Scrum Science NGSS: Engineering, Technology, Applications of Science
Agile Development – a new way of software development?
Looking at XP, Scrum, Kanban or Lean
Scrum in Action.
Agree what we will finish in the sprint
09 | Kanban Steven Borg | Co-Founder & Strategist, Northwest Cadence
Story Writing.
Presentation transcript:

Definition of Done – why it matters Helen Wassef @hw0809

About Me Helen Wassef Email: helen.wassef@gmail.com https://twitter.com/hw0809 https://www.linkedin.com/in/helen-wassef

Outcomes vs Activities Are you activity or outcome driven?

DoD – Setting Expectations Defines what conditions must be met for potentially shippable code Outcome based team vs activity based team Sets collective team expectation and eliminates assumptions Drives common understanding around quality

Crafting the Definition of Done Quality is never an accident, it is the result of an intelligent effort. – John Ruskin Get everyone in a room to brainstorm Vote and agree on an achievable DoD Document it, print it, make it visible Different levels of Definition of Done Include testing requirements Level of testing Type of testing Automated testing Include all involved roles

Building the Right Thing the Right way Driven by acceptance criteria Focus on value Solving user problems Leads to… Happy users Happy teams Strong reputation Driven by definition of done Readable code Productive code reviews Quality Gates High quality unit tests High quality automated tests Collaborative effort Culture built around preventing fires not fire fighting

Definition of Done Characteristics Criteria Inclusion List Accepted Achievable Mitigates risk how we design how we version how we code how we test how we document how we deploy Approval process

Levels of Definition of Done Release Feature User Story Compliance requirements are met Non technical work identified Supporting material & documentation published Deployment standards met All the underlying user stories are done Accepted by users Quality metrics Coding standards PO & team agreements

Integrated Teams – DoD What if multiple teams are working on same product? Do they need some level of commonality in their DoD?

Who owns DoD The development team The Product Owner Architects

During Marking User story Done When it matters Quality is not an act, it is a habit – Aristotle Grooming sessions Planning Day During the sprint During Marking User story Done

Definition of Done Evolution High performing teams will evolve the DoD

Summary DoD drives outcome focused culture vs activity focused Get together, brainstorm and outline DoD wish list Vote and publish DoD Make it visible Enforce Periodically revisit and make changes