Petit résumé intéressant d’une conférence de Forrester sur la création de valeur par l’adoption d’une approche agile pour la définition des spécifications.
Quelques points-clés:
Friction points between traditional and Agile approaches:
- Delivers requirements vs collaboration on the product
- Where in the process you engage vs. iterative
- Requirements that are out of date, long/hard to read, solution focused, take way too long vs. collaborative and timely requirements
Often the customer has no time because they are doing their day-job (the one you are trying to help in some way with software!). There are often many customers to involve in the requirements efforts, not just one or two to quickly jot down stories with. The customers are often distributed so you have to bake in time to work with all of them alone and together. Agile is reliant on good communication but stereotypically, developers don’t communicate well.
We cannot ignore analysis – processes require analysis and solutions require thought - so take time to do these.
L’article complet est ici: http://requirements.seilevel.com/blog/2009/10/delivering-business-value-with-agile_28.html
Ceci pourrait vous intéresser...
« Le modèle d’affaires des blogueurs professionnels L’utilisation des outils de collaboration pour améliorer la productivité des employés »
