10 Reasons to Doubt Your Agile Transition Has Been Successful
- Every time product requirements change, you hear a tree fall in the forest in order to support the printing of a new multi-page gantt chart;
- The project managers comes into the office early in the morning so he can carefully prepare the specific tasks to assign to each team member;
- Although sitting within 20 feet of each other, your team members proudly sit in closed offices and only communicate via email;
- Your business analyst is pleased to show you that she managed to fit each user story on 42 50 index cards;
- The last time a business representative attended your requirement gathering meeting, she was using a Palm Pilot;
- As per the project plan, the Champagne has been opened to celebrate the launch of the project while half the development team is busy trying to do code integration;
- While no team members attended, the management team is pleased with the content of the discussions that took place during the end of release post-mortem (retrospection);
- The architects have locked themselves up for 6 to 8 weeks in order to properly prepare for the upcoming project;
- The business representative is waiting for her administrative assistant to arrive in order to take notes from the daily stand up meeting;
- A project control officer has been assigned to the project to ensure each steps have been properly documented and successfully executed.
Do you have other reasons to doubt?
You might want to take a look at this list :
http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/
It’s quite funny and…accurate.