Definition of Ready.

Slides:



Advertisements
Similar presentations
Connect Team Connect Team Outside Contrib Outside Contrib Unscheduled Backlog Bugs Feature Requests BA Review Requirement Docs Epic Large Tasks or Features.
Advertisements

Acceptance Testing.
Interoperability. What is testing? Where have we come from? Where are we now? Why is nFocus at MSAIC? Overview.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Stoimen Stoimenov QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Alternate Software Development Methodologies
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
 What is Software Testing  Terminologies used in Software testing  Types of Testing  What is Manual Testing  Types of Manual Testing  Process that.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Release & Deployment ITIL Version 3
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Estimation Wrap-up CSE 403, Spring 2008, Alverson Spolsky.
Michael Burnside Blog: Software Quality Assurance, Quality Engineering, and Web and Mobile Test.
What is Scrum Process? Where is it used? How is it better?
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Mobile Aps: Agile Mentoring Review
Continuous Deployment JEFFREY KNAPP 8/6/14. Introduction Why is it valuable How to achieve What to consider.
Viking Quality Report Team Assignment 9 Team 2-1.
Applied Software Project Management
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
With a hint of HP Quality Center Agile development and functional testing: friend or foe? Tom Vercauteren, June 26th, 2009.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.
Cultivating Agile Requirements
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Who is Gregg? 1 Mile
REGRESSION TESTING Software Quality Engineering NC Zunaira Tariq Bese 19B Software Quality Engineering NC Zunaira Tariq Bese 19B.
HPE ALM Octane.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
User Stories > Big and Small
Project Management with VSTS
Scrum and TargetProcess
Exam 0 review CS 360 Lecture 8.
Agile Training – Agile Overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Integrate Agile Testing into the Process
Dr. Rob Hasker SE 3800 Note 3 Ch. 4, 5.
SAFe Workshop - Oct 17 Presenter: Ray Brederode
Requirements and User Stories
Pega 9/14/2018 8:48 AM Definition of Done = ready for PO acceptance
CEN 4010 Intro to Software Engineering Professor Alex Roque
X in [Integration, Delivery, Deployment]
Johanna Rothman Agile Team Measurements Chapter 12
Johanna Rothman Know What “Done” Means Chapter 11
© University of Liverpool
Automating Profitable Growth™
Agile practices for documentation teams
Sprint Planning April 2018.
Program Prioritization
Introduction to Agile Blue Ocean Workshops.
<<Project Name>>
CSE 303 Concepts and Tools for Software Development
The Agile Inception Deck
Open Source Tool Based Automation solution with Continuous Integration and end to end BDD Implementation Arun Krishnan - Automation Manager Maria Afzal-
Agile Development – a new way of software development?
Looking at XP, Scrum, Kanban or Lean
Walking dead. How to save project?
Automating Profitable Growth
Agile Development.
Definition of Done – why it matters
Are you measuring what really counts?
Story Writing.
Open Source Tool Based Automation solution with Continuous Integration and end to end BDD Implementation Arun Krishnan - Automation Manager Maria Afzal-
Evolving a Continuous Improvement System
Presentation transcript:

Definition of Ready

Definition of Ready Why? One reason teams don’t complete stories, features or epics is because they are poorly understood before starting work and as a result the effort is underestimated. In this situation often teams find clearly defining a “definition of ready” will help to make sure things are understood prior to commencing work Why?

Backlog Prioritization New Description Acceptance Criteria Sized Prioritized Next WSJF In Process Done Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Meets definition of ready

When is an Epic/Feature “ready”? Has Definition statement Has acceptance criteria Sized and broken down to take 1-3 sprints roughly Has WSJF calculation Prioritized by leadership What else would you add?

Example Epic Description For (customers) Who (do something) The (solution) is a (how) that (provides some value) Unlike (competition or current solution) Our solution (does something better, why?)

Connected Kanban's Epics at Portfolio Level Features at Program Level New Prioritized In Process Done Features at Program Level New Prioritized In Process Done Stories at Team Level New Prioritized In Process Done

Who should be pulled in to participate in the process that gets Epics and Features to a state of ”ready”?

When is an Story “ready”? Has user story statement Has acceptance criteria Gherkin defined Sized and broken down to take 1-3 days roughly What else would you add?

Discussion When would tasking be part of the definition of ready? What are pro’s and con’s? How would using spikes or enabler stories work with your model for definition of ready? How will your team work together to help stories get to a “ready” state?

Definition of Done

Definition of Done Newly formed teams will often have a broad variety of ideas when it comes to what constitutes “done”. As larger buckets of work are shipped this can create significant issues if assumptions go unexpressed and worse unfulfilled. Having a clear definition of ready at the Epic, Feature and Story level will help ensure expectations are met. Why?

When is a Epic/Feature “done”? Passes all acceptance criteria No must fix defects Pass E2E integration tests in staging Release documentation updated NFR’s met, engineering standards followed Accepted by Product Manager What else would you add?

Discussion Are there other non IT teams you need to engage? (ex: Would sales marketing need to build documentation to support the release?) What cadence will you demo these larger buckets of work?

When is a story “done”? When is a Story “done”? Passes all acceptance criteria and Gherkin Automated tests written Checked into version control NFR’s met, engineering standards followed Accepted by PO What else would you add?

Examples

Story Examples

Epic Format Feature Format In-Service Software Update Acceptance Criteria Nonstop routing availability Automatic and Manual Update Rollback Capability Support through existing admin tools All enabled services are running after the update Benefit Hypothesis Significantly reduce planned downtime More Content on Epics More Content on Features