5 Ways a Product Owner should NOT Behave, Part 2
In blog two of three, I cover five more ways a Product Owner on a Scrum Team should not behave. Watch out for these behaviors or traits.
acceptance criteria
Acceptance Criteria, otherwise known as a/c, define the boundaries of a User Story, and can serve as a checklist to know when a story is done.
When your Agile Requirements go Wrong, Part 4
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
When your Agile Requirements go Wrong, Part 3
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.
When your Agile Requirements go Wrong, Part 2
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.
Who owns Quality on a Scrum Team?
Unfortunately, quality is often skipped or overlooked when developing products using an Agile approach. So, who owns quality in Scrum?
Debate #4 – What’s the best way to write Acceptance Criteria?
There are many ways to document Acceptance Criteria for your user stories. But what’s the best way? Check out some different methods.
10 ways Poor Requirements in Agile can cause Projects To Fail, Part 1
It is well-known that poor requirements are the top reason for project failure. For many years, this has been studied by the Standish Group, which produces their famous “Chaos Report” each year. However, the focus is mainly on project failure of traditional or waterfall approaches. My question is: what requirements issues in Agile environments contribute …