Un autre article intéressant sur le rôle de l’analyste en mode Agile, qui met bien l’accent sur l’importance de bien « posséder » le produit/système/projet sur lequel on travaille afin de pouvoir maintenir un niveau de qualité irréprochable.

Requirements engineers make decisions, they are not just documenters. Expect to see that product owners are the BAs. They will less often be called systems analysts, and more often called product owners. A few years ago, we shifted from calling our requirements team members “Business Analysts” and started calling them “Product Managers” because that’s really what they have to do – own the product, even if it’s just an internal IT system.

The business is not always right, so you still need to ask questions. BAs/Product Owners must push back when something doesn’t make sense.

Agile is actually seen to increase the value of requirements – just make them more solution focused, and not just about doing lots of documentation.

Ceci pourrait vous intéresser...

  • Aucune publication intéressante

« »