The Enterprise’s ability to deliver new functionality with the shortest sustainable lead time, and adapt to rapidly changing business environments, depends on quality.
Built-in Quality is a critical principle of agile teams that ensures the quality of their product. A robust Definition of Done is key as is a common understanding of what it means to turn items from the Product Backlog into something that is of high enough quality that it can be handed over or used by customers.
What DevOps can teach teams about improving their agility.
Built-in Quality is a critical principle of agile teams that ensures the quality of their product. A robust Definition of Done is key.
If you are unable to deliver a “Done” increment during a Sprint, you are not doing Scrum
What is the Definition of Done and how do you use it to improve quality and reduce rework?
The Definition of Done is a vital part of Sprint Planning, indicating the quality, standards, and compliance criteria for an Increment of Done
Get the most out of the latest version of the IT service management (ITSM) and agile frameworks
Learn to identify and reduce waste to increase throughput and flow of the team’s work.
Learn to improve ‘unevenness’ to increase throughput of work.
Learn to improve ‘overburdenning’ the team and its members to increase throughput of work.
When quality slips, defects and rework increases, it’s important to look at the Definition of Done in the Retrospective.
What is technical debt, what problems does it cause, and how can you remove it?
When a Story doesn’t get finished by the end of the Sprint, what happens to it, its Story Points, and velocity?
Why QA becomes a bottleneck and what to do about it.