Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
More than anything, reading the detailsMore than anything, reading the details in the article suggests that Agile was definitely not used effectively (obviously from the results!) or properly. The front-end system design and deployment was done in a incremental and iterative fashion, but in this instance there was so many complex dependencies that more rigorous analysis and upfront planning should have been done.
This article from GCN seems to indicate that its use (or misuse) was the cause of the deployment fiasco.
More than anything, reading the details in the article suggests that Agile was definitely not used effectively (obviously from the results!) or properly. The front-end system design and deployment was done in a incremental and iterative fashion, but in this instance there was so many complex dependencies that more rigorous analysis and upfront planning should have been done.
I've personally seen these type of situations happen where the adaptive, flexible processes most effective for an Agile deployment are not applied at the appropriate situation. For large, very complex systems, a more systematic use of planning is often necessary then during the deployment, utilize Agile's principles of "inspect and adapt". This is the most effective and optimal combination of traditional and Agile most suited for these kinds of projects.
It will be interesting to see how this all works out!
I've personally seen these type of situations happen where the adaptive, flexible processes most effective for an Agile deployment are not applied at the appropriate situation. For large, very complex systems, a more systematic planning is often necessary then during the deployment, utilize Agile's principles of "inspect and adapt" is most effective and optimal. in the article suggests that Agile was definitely not used effectively (obviously from the results!) or properly. The front-end system design and deployment was done in a incremental and iterative fashion, but in this instance there was so many complex dependencies that more rigorous analysis and upfront planning should have been done.
I've personally seen these type of situations happen where the adaptive, flexible processes most effective for an Agile deployment are not applied at the appropriate situation. For large, very complex systems, a more systematic planning is often necessary then during the deployment, utilize Agile's principles of "inspect and adapt" is most effective and optimal.
Posted on: November 09, 2013 11:11 AM |
Permalink