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.
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.
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.
User Stories may be written at various sizes and levels, and there are different terms for them – so what should you call yours?
There’s not a one-size-fits-all project management approach, but I think that Agile can co-exist with Waterfall, albeit with some difficulty.
There are many ways to document Acceptance Criteria for your user stories. But what’s the best way? Check out some different methods.
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.
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.
The International Institute of Business Analysis (IIBA®) is the premier organizing body for the Business Analysis profession. Their Certified Business Analysis Professional (CBAP®) certification is regarded as the “gold standard” and the highest achievement for business analysts. The requirements to sit this exam are substantial – for a reason. The IIBA® wants the certification to …