This presentation explains how the proper use of a definition of done can help a team to deliver software that really matches the customer needs in the fastest way possible.
The definition of done is not just a to do list but a tool to deliver software faster with better quality, and spending less money. Moreover it can help to improve the agility of your team.
The essence of this is to make use of feedback given by the customer, tests, processes and all systems involved.
The exact reasons why to use a definition of done is explained and how to implement it in a software development team. It is demonstrated how the planning process will improve and how it will keep the product owner posted on what exactly is delivered this and coming iterations.
ALE15 The real value of a definition of doneChristian Vos
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Definition of Done and Acceptance Criteria Dan Popescu
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Definition of Done and Product Backlog refinementChristian Vos
The document discusses product backlog refinement and the definition of done in agile software development. It emphasizes that product backlog refinement is an important meeting to clarify and estimate user stories and work items to have a ready backlog for iteration planning. It also stresses that having a clear definition of done helps improve team quality, transparency for stakeholders, better release planning, and minimizing risks. Regular product backlog refinement coupled with a well-defined definition of done are key practices for achieving agility.
The document discusses defining the "Definition of Done" (DoD) which establishes the quality standards and activities required to consider a user story or increment of work complete. It notes problems that can occur without a DoD such as technical debt, unpredictable delivery dates, and overcommitting work. The document recommends that the team, including the product owner, define the DoD during backlog estimation and that the definition evolves over sprints based on the team's experience. It provides some examples of DoD criteria for user stories and sprints.
The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.
This document discusses definitions of done at the sprint and release levels in Scrum. It provides examples of what could be included in a definition of done at the sprint level, such as code being complete, passing unit tests, and product owner acceptance. It distinguishes acceptance criteria, which ensures the right functionality is built, from the definition of done, which ensures quality. The document concludes by providing instructions for an exercise where a team discusses and creates their own definition of done, capturing deliverables needed at each level.
This document discusses the concept of "READY" in agile development. It defines READY as having clear goals and criteria, understanding how to complete the work, having the ability to complete it in the sprint, and managing risks and dependencies. Work that is not READY causes problems like missed deadlines and unclear acceptance criteria. The document recommends using READY as a quality gate to prevent unprepared work from being committed to sprints. It provides examples of how to structure product backlogs and incrementally prepare stories to become READY. The results section notes low adoption rates for READY compared to definitions of done.
ALE15 The real value of a definition of doneChristian Vos
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Definition of Done and Acceptance Criteria Dan Popescu
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Definition of Done and Product Backlog refinementChristian Vos
The document discusses product backlog refinement and the definition of done in agile software development. It emphasizes that product backlog refinement is an important meeting to clarify and estimate user stories and work items to have a ready backlog for iteration planning. It also stresses that having a clear definition of done helps improve team quality, transparency for stakeholders, better release planning, and minimizing risks. Regular product backlog refinement coupled with a well-defined definition of done are key practices for achieving agility.
The document discusses defining the "Definition of Done" (DoD) which establishes the quality standards and activities required to consider a user story or increment of work complete. It notes problems that can occur without a DoD such as technical debt, unpredictable delivery dates, and overcommitting work. The document recommends that the team, including the product owner, define the DoD during backlog estimation and that the definition evolves over sprints based on the team's experience. It provides some examples of DoD criteria for user stories and sprints.
The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.
This document discusses definitions of done at the sprint and release levels in Scrum. It provides examples of what could be included in a definition of done at the sprint level, such as code being complete, passing unit tests, and product owner acceptance. It distinguishes acceptance criteria, which ensures the right functionality is built, from the definition of done, which ensures quality. The document concludes by providing instructions for an exercise where a team discusses and creates their own definition of done, capturing deliverables needed at each level.
This document discusses the concept of "READY" in agile development. It defines READY as having clear goals and criteria, understanding how to complete the work, having the ability to complete it in the sprint, and managing risks and dependencies. Work that is not READY causes problems like missed deadlines and unclear acceptance criteria. The document recommends using READY as a quality gate to prevent unprepared work from being committed to sprints. It provides examples of how to structure product backlogs and incrementally prepare stories to become READY. The results section notes low adoption rates for READY compared to definitions of done.
The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
5th Scrum Meetup Greece - Getting to a shared definition of "done" with ATDDpvratsalis
The document summarizes an Agile Greece Meetup that took place on February 11, 2014 in Athens. The meetup discussed using Acceptance Test Driven Development (ATDD) to help bridge communication gaps between product owners and developers. ATDD involves transforming user story examples generated by product owners into automated tests for developers to guide implementation using test-driven development practices.
This document discusses the importance of team charters and definitions of ready and done in Agile development. It defines key elements of a team charter such as goals, success criteria, constraints, and team rules/working agreements. It also explains what a definition of ready and definition of done are, providing examples of criteria that could be included in each. The document emphasizes that definitions of ready and done are not static and should be informed by the team's experience. It poses questions about why teams should create charters and who is accountable for ensuring teams follow their charters.
One of the core values expressed in the agile manifesto is “working software over comprehensive documentation” because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of “Done” is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls.
The document discusses the Definition of Done (DoD) in the context of Scrum. It states that the DoD is a checklist of activities that must be completed to produce software, such as writing code, testing, and creating documentation. The DoD adds verifiable value and serves as the primary reporting mechanism for team members. Additionally, the DoD helps ensure transparency in the work being done. The document emphasizes that software is not considered "done" until it is deployed to production and being monitored.
Agile for the Masses: How to Make Any Team More Effective - John WetenhallAtlassian
In this talk, we will demonstrate how Atlassian's Collaboration Product Marketing Team has adopted the agile methodology. We'll cover how we think about "shipping products," how we plan our work with quarterly goals and biweekly sprints, and how we reflect with retrospectives.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Ensuring Efficiency and Speed with Practical Solutions for Clinical OperationsOnePlan Solutions
Clinical operations professionals encounter unique challenges. Balancing regulatory requirements, tight timelines, and the need for cross-functional collaboration can create significant internal pressures. Our upcoming webinar will introduce key strategies and tools to streamline and enhance clinical development processes, helping you overcome these challenges.
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...Luigi Fugaro
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
Penify - Let AI do the Documentation, you write the Code.KrishnaveniMohan1
Penify automates the software documentation process for Git repositories. Every time a code modification is merged into "main", Penify uses a Large Language Model to generate documentation for the updated code. This automation covers multiple documentation layers, including InCode Documentation, API Documentation, Architectural Documentation, and PR documentation, each designed to improve different aspects of the development process. By taking over the entire documentation process, Penify tackles the common problem of documentation becoming outdated as the code evolves.
https://www.penify.dev/
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
Software Test Automation - A Comprehensive Guide on Automated Testing.pdfkalichargn70th171
Moving to a more digitally focused era, the importance of software is rapidly increasing. Software tools are crucial for upgrading life standards, enhancing business prospects, and making a smart world. The smooth and fail-proof functioning of the software is very critical, as a large number of people are dependent on them.
Enhanced Screen Flows UI/UX using SLDS with Tom KittPeter Caitens
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻campbellclarkson
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Stork Product Overview: An AI-Powered Autonomous Delivery FleetVince Scalabrino
Imagine a world where instead of blue and brown trucks dropping parcels on our porches, a buzzing drove of drones delivered our goods. Now imagine those drones are controlled by 3 purpose-built AI designed to ensure all packages were delivered as quickly and as economically as possible That's what Stork is all about.
Alluxio Webinar | 10x Faster Trino Queries on Your Data PlatformAlluxio, Inc.
Alluxio Webinar
June. 18, 2024
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
- Jianjian Xie (Staff Software Engineer, Alluxio)
As Trino users increasingly rely on cloud object storage for retrieving data, speed and cloud cost have become major challenges. The separation of compute and storage creates latency challenges when querying datasets; scanning data between storage and compute tiers becomes I/O bound. On the other hand, cloud API costs related to GET/LIST operations and cross-region data transfer add up quickly.
The newly introduced Trino file system cache by Alluxio aims to overcome the above challenges. In this session, Jianjian will dive into Trino data caching strategies, the latest test results, and discuss the multi-level caching architecture. This architecture makes Trino 10x faster for data lakes of any scale, from GB to EB.
What you will learn:
- Challenges relating to the speed and costs of running Trino in the cloud
- The new Trino file system cache feature overview, including the latest development status and test results
- A multi-level cache framework for maximized speed, including Trino file system cache and Alluxio distributed cache
- Real-world cases, including a large online payment firm and a top ridesharing company
- The future roadmap of Trino file system cache and Trino-Alluxio integration
Superpower Your Apache Kafka Applications Development with Complementary Open...Paul Brebner
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
5th Scrum Meetup Greece - Getting to a shared definition of "done" with ATDDpvratsalis
The document summarizes an Agile Greece Meetup that took place on February 11, 2014 in Athens. The meetup discussed using Acceptance Test Driven Development (ATDD) to help bridge communication gaps between product owners and developers. ATDD involves transforming user story examples generated by product owners into automated tests for developers to guide implementation using test-driven development practices.
This document discusses the importance of team charters and definitions of ready and done in Agile development. It defines key elements of a team charter such as goals, success criteria, constraints, and team rules/working agreements. It also explains what a definition of ready and definition of done are, providing examples of criteria that could be included in each. The document emphasizes that definitions of ready and done are not static and should be informed by the team's experience. It poses questions about why teams should create charters and who is accountable for ensuring teams follow their charters.
One of the core values expressed in the agile manifesto is “working software over comprehensive documentation” because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of “Done” is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls.
The document discusses the Definition of Done (DoD) in the context of Scrum. It states that the DoD is a checklist of activities that must be completed to produce software, such as writing code, testing, and creating documentation. The DoD adds verifiable value and serves as the primary reporting mechanism for team members. Additionally, the DoD helps ensure transparency in the work being done. The document emphasizes that software is not considered "done" until it is deployed to production and being monitored.
Agile for the Masses: How to Make Any Team More Effective - John WetenhallAtlassian
In this talk, we will demonstrate how Atlassian's Collaboration Product Marketing Team has adopted the agile methodology. We'll cover how we think about "shipping products," how we plan our work with quarterly goals and biweekly sprints, and how we reflect with retrospectives.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Ensuring Efficiency and Speed with Practical Solutions for Clinical OperationsOnePlan Solutions
Clinical operations professionals encounter unique challenges. Balancing regulatory requirements, tight timelines, and the need for cross-functional collaboration can create significant internal pressures. Our upcoming webinar will introduce key strategies and tools to streamline and enhance clinical development processes, helping you overcome these challenges.
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...Luigi Fugaro
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
Penify - Let AI do the Documentation, you write the Code.KrishnaveniMohan1
Penify automates the software documentation process for Git repositories. Every time a code modification is merged into "main", Penify uses a Large Language Model to generate documentation for the updated code. This automation covers multiple documentation layers, including InCode Documentation, API Documentation, Architectural Documentation, and PR documentation, each designed to improve different aspects of the development process. By taking over the entire documentation process, Penify tackles the common problem of documentation becoming outdated as the code evolves.
https://www.penify.dev/
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
Software Test Automation - A Comprehensive Guide on Automated Testing.pdfkalichargn70th171
Moving to a more digitally focused era, the importance of software is rapidly increasing. Software tools are crucial for upgrading life standards, enhancing business prospects, and making a smart world. The smooth and fail-proof functioning of the software is very critical, as a large number of people are dependent on them.
Enhanced Screen Flows UI/UX using SLDS with Tom KittPeter Caitens
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻campbellclarkson
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Stork Product Overview: An AI-Powered Autonomous Delivery FleetVince Scalabrino
Imagine a world where instead of blue and brown trucks dropping parcels on our porches, a buzzing drove of drones delivered our goods. Now imagine those drones are controlled by 3 purpose-built AI designed to ensure all packages were delivered as quickly and as economically as possible That's what Stork is all about.
Alluxio Webinar | 10x Faster Trino Queries on Your Data PlatformAlluxio, Inc.
Alluxio Webinar
June. 18, 2024
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
- Jianjian Xie (Staff Software Engineer, Alluxio)
As Trino users increasingly rely on cloud object storage for retrieving data, speed and cloud cost have become major challenges. The separation of compute and storage creates latency challenges when querying datasets; scanning data between storage and compute tiers becomes I/O bound. On the other hand, cloud API costs related to GET/LIST operations and cross-region data transfer add up quickly.
The newly introduced Trino file system cache by Alluxio aims to overcome the above challenges. In this session, Jianjian will dive into Trino data caching strategies, the latest test results, and discuss the multi-level caching architecture. This architecture makes Trino 10x faster for data lakes of any scale, from GB to EB.
What you will learn:
- Challenges relating to the speed and costs of running Trino in the cloud
- The new Trino file system cache feature overview, including the latest development status and test results
- A multi-level cache framework for maximized speed, including Trino file system cache and Alluxio distributed cache
- Real-world cases, including a large online payment firm and a top ridesharing company
- The future roadmap of Trino file system cache and Trino-Alluxio integration
Superpower Your Apache Kafka Applications Development with Complementary Open...Paul Brebner
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
DECODING JAVA THREAD DUMPS: MASTER THE ART OF ANALYSISTier1 app
Are you ready to unlock the secrets hidden within Java thread dumps? Join us for a hands-on session where we'll delve into effective troubleshooting patterns to swiftly identify the root causes of production problems. Discover the right tools, techniques, and best practices while exploring *real-world case studies of major outages* in Fortune 500 enterprises. Engage in interactive lab exercises where you'll have the opportunity to troubleshoot thread dumps and uncover performance issues firsthand. Join us and become a master of Java thread dump analysis!
8. @voschristian
The real value of a definition of done
Business value is an informal
term that includes all forms of
value that determine the
health and well-being of the
firm in the long run
14. @voschristian
The real value of a definition of done
Nature uses empirical management
successfully for million of years
and what do we do ?
Look deep into nature, and
then you will understand
everything better.
- Albert Einstein -
15. @voschristian
The real value of a definition of done
Not only Feedback
from product owner but also
from:
•System
•Tests
•Process
•Team
16. @voschristian
The real value of a definition of done
We want to get feedback as much
and as quick as possible
The more you inspect and adapt,
the more you improve and learn
by using feedback.
And what do we want to inspect
adapt and improve ?
Well, that is stated on the dod !
17. @voschristian
The real value of a definition of done
Better said :
List of items you want to get feedback
on when working on a user story
18. @voschristian
The real value of a definition of done
All to prevent the famous saying :
IT WORKS ON MY MACHINE !
19. @voschristian
The real value of a definition of done
definition of done is feedback
• Specification Satisfaction
• Specification Robustness
definition of done is securing quality
20. @voschristian
The real value of a definition of done
definition of done
• Faster delivery
• Spending less energy
21. @voschristian
The real value of a definition of done
Progressive insight sometimes
tell that certain lowprio features
are not necessary anymore
The effect of using a complete
DoD, is that the PO is aware
that implemented features are
really working
22. @voschristian
The real value of a definition of done
Transparency :
Almost done is not done at all
• Is it done ?
• Yes, almost
• Can we go to production ?
• No, not yet
• Why not ?
• Some bugs, some tests, not sure it works on prod, web service not reachable in business
domain, manual has to be written, etc.
• When can we go to production ?
• I am not sure…..
PO and Team in discussion
23. @voschristian
The real value of a definition of done
To avoid miscommunication
between the product owner and
the dev team there must be
a common understanding what is
meant by done software !
24. @voschristian
The real value of a definition of done
Better release planning
•Estimate on iterations
•No need for hardening sprints
???
Iterations where bugs are solved,
tests are done
and deployment is prepared
26. @voschristian
The real value of a definition of done
1 2 3 4
undone
work
undone
work undone
work undone
work
Unsolved Bugs
Integration/Regression Test
Deployment packages
Documentation
Performance issues
Etc…….
Release
27. @voschristian
The real value of a definition of done
1 2 3 4
undone
work
undone
work undone
work
undone
work
ReleaseRelease
Iteration
28. @voschristian
The real value of a definition of done
You are not as good as possible
in something
that you do for the first time
(Taking luck out of the quotation)
29. @voschristian
The real value of a definition of done
1 2 3 4
undone
work
undone
work undone
work
undone
work
Release
Release
Iteration
Release
Iteration
unsolved bugs,
untested work
30. @voschristian
The real value of a definition of done
Using a DoD can improve release
planning because all the work
necessary releasing the software is
done when working on a feature,
within the iteration, no further
work is needed and therefore no
need for extra release iterations.
31. @voschristian
The real value of a definition of done
Definition of Done defines team (agile) competence
When is a team
considered to be agile ?
32. @voschristian
The real value of a definition of done
• Adaptive planning
• Evolutionary development
• Early delivery
• Continuous improvement
• Rapid and flexible response
to change
33. @voschristian
The real value of a definition of done
Agility : Release one or more
features every iteration.
Quality : Number of steps in the
dod applied when releasing
this feature.
Does agility also imply delivering quality ???
34. @voschristian
The real value of a definition of done
The number of steps in the
definition of done is an indicator
of the team’s competence
35. @voschristian
The real value of a definition of done
Competence is essential
to deliver one of more complete
increments of done software
with the best quality possible
every iteration !
36. @voschristian
The real value of a definition of done
Start using Definition of Done
Use two version !
Competence – Can’t
Maturity – Won’t
37. @voschristian
The real value of a definition of done
1. In process definition of done
• Transparency
• Represents the capability of the team
• What to improve
2. Ideal definition of done
• Where to go
38. @voschristian
The real value of a definition of done
Code checked in
Code build green on build server
Coding Quality Check Green(er) (Sonar)
Unit Test build server OK
Unit Test build server OK (Code Coverage 80 %)
Peer reviewed
(Automated) Deployed on CI Server
One click on Demo Server
(Automated) Integration Test run on CI
(Automated) Acceptance Test run on CI
(Automated) Performance Test run on CI
(Automated) Deployed on ST Server
(Automated) Deployed on UAT Server
Full Load Test
Exploratory testing done on ST Server
Integration (chain) testing done on UAT Server
Demo-ed and approved by Product Owner
All bugs solved
Deployment Guide up to date
Interface documentation up to date
Use Cases up to date
Release Notes up to date
User Manual up to date
Iteration Test Rapport (up to date)
Technical Design updated (when absolutely necessary)
Product Backlog up to date
Code checked in
Code build green on build server
Coding Quality Check Green(er) (Sonar)
Unit Test build server OK
Peer reviewed
(Automated) Deployed on CI Server
(Automated) Integration Test run on CI
(Automated) Acceptance Test run on CI
(Automated) Deployed on ST Server
Exploratory testing done on ST Server
Demo-ed and approved by Product Owner
All bugs solved
Deployment Guide up to date
Interface documation up to date
Use Cases up to date
Product Backlog up to date
• Undone work
• Delay of Risk
(manifestation in production)
Ideal In process
39. @voschristian
The real value of a definition of done
Code checked in
Code build green on build server
Coding Quality Check Green(er) (Sonar)
Unit Test build server OK
Unit Test build server OK (Code Coverage 80 %)
Peer reviewed
(Automated) Deployed on CI Server
One click on Demo Server
(Automated) Integration Test run on CI
(Automated) Acceptance Test run on CI
(Automated) Performance Test run on CI
(Automated) Deployed on ST Server
(Automated) Deployed on UAT Server
Full Load Test
Exploratory testing done on ST Server
Integration (chain) testing done on UAT Server
Demo-ed and approved by Product Owner
All bugs solved
Deployment Guide up to date
Interface documentation up to date
Use Cases up to date
Release Notes up to date
User Manual up to date
Iteration Test Rapport (up to date)
Technical Design updated (when absolutely necessary)
Product Backlog up to date
Code checked in
Code build green on build server
Coding Quality Check Green(er) (Sonar)
Unit Test build server OK
Peer reviewed
(Automated) Deployed on CI Server
(Automated) Integration Test run on CI
(Automated) Acceptance Test run on CI
(Automated) Deployed on ST Server
Exploratory testing done on ST Server
Demo-ed and approved by Product Owner
All bugs solved
Deployment Guide up to date
Interface documation up to date
Use Cases up to date
Product Backlog up to date
Ideal In process
Quality
40. @voschristian
The real value of a definition of done
The real value of a Defintion of Done
Remarks, Questions or Endorsements ?
Feedback : @voschristian