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.
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
It’s a common misconception that there’s no planning in Agile (there is), and the Product Owner is responsible, but a lot can still go wrong.
My company, Core BTS, has combined my two eBooks about “Agile Transformation Pain Points” into one that contains 40 pains and how to avoid or manage them.
In this subseries’s third and last blog, I tackle the final five ways that Product Owners should not behave. Watch out for these behaviors.
The Product Owner is the most crucial member of a Scrum Team, but there are some problematic personality traits & behaviors to watch out for.
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.
If your Product Owner used to be a developer or has a technical background rather than business experience, you may run into a few issues.
A Product Owner and a Business Analyst make a winning team by working together to achieve the best and most valuable outcomes.
The creators of the Scrum Guide, Ken Schwaber, and Jeff Sutherland, released an update to the Scrum Guide in 2020. Find out what’s new!