What are Acceptance Criteria, and do you need them?
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
Requirements are the needs of an organization to develop a solution for a specific problem or opportunity; defining them is a business analysis activity.
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
The Definition of Ready confirms the suitability of a User Story for development. If you want to produce quality increments, you need one!
A Definition of Done can vary widely between organizations, departments, and even teams, but it’s crucial that you have one. Find out why.
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
The problem of Agile requirements going wrong is endemic; this is the third of a four-part series on what can go wrong, and how to fix it.
There are many ways requirements can go wrong in Agile. In Part 2 of 4, I tackle five more requirements anti-patterns so you can avoid them.
The problem of Agile requirements going wrong is endemic; this is the first of a four-part series on what can go wrong, and how to fix it.
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.
In Agile, defects can be handled in different ways – so what should you do when you discover a bug? Find out how to handle defects in Agile.
It’s a known fact that poor requirements can cause projects to fail. When using Agile, these problems can be even worse. Learn what to avoid.