Debate #12 – What’s the best way to estimate User Stories?
Modified Fibonacci, T-shirt Sizes, Dog Breeds, Ideal Days, and Story Counts are different ways to size User Stories. Which one is the best?
What is an Agile User Story? A User Story is a statement, written from a user’s perspective, about a specific capability s/he needs to achieve a goal.
Modified Fibonacci, T-shirt Sizes, Dog Breeds, Ideal Days, and Story Counts are different ways to size User Stories. Which one is the best?
User Stories may be written at various sizes and levels, and there are different terms for them – so what should you call yours?
Is there is a “right” way to write User Stories? It sounds simple, but like Agile, User Stories are easy to learn but difficult to master.
Sprint 0 is a hot topic amongst debated by Agile practitioners. So, should you have a Sprint 0? Check out these arguments for and against it.
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 …
A Product Owner and a Business Analyst make a winning team by working together to achieve the best and most valuable outcomes.