20 Myths About Business Analysis
In my nearly 20 years as a Business Analyst, I have witnessed many different myths come and go about this role. 20 years – 20 Myths Debunked!
Requirements are the stated (or unstated) needs of stakeholders or an organization necessary to accomplish a specific goal; there may be multiple models that represent the same set of requirements.
In my nearly 20 years as a Business Analyst, I have witnessed many different myths come and go about this role. 20 years – 20 Myths Debunked!
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
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.
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.
So, can you add items to the Sprint Backlog during the Sprint? The Scrum Guide states that you can, but you may not want to do it. Learn why.
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.
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 …