A recent project in which I was involved in was done in an Agile manner, which included getting in ThoughtWorks devs and BA’s as mentors and coach for the team. Just recently there was a PIR (post implementation review) and I thought it was worth sharing the results.
In a nutshell, the project was a success. The significant failures occurred in the up-front processes by trying to be too predictive (initial estimates were poorly done, giving incorrect information about project cost/benefits) and some of this filtered through to the rest of the project.
These were the general findings from the project:
- Use of the Agile Methodology within the project was successful and well received by business customers.
- End user involvement throughout the process meant that there were no surprises and the application was well received.
- Daily stand-up status meetings supported open and effective communication within the project team.
- Agile testing practices, such as the use of automated testing tools were affectively adopted by the project team.
- Final code was of a high quality.
- Successful knowledge transfer of J2EE coding and Agile development to Bangalore resources assigned to the project.
The following selection of quotes came primarily from the business sponsors and some of the technical review components of the project. It shows that doing a project well, even done technically well, can be observed by many stakeholders.
Some quotes have been edited which I felt were sensitive to my organisation, I’ve not done any creative editing to change the meaning of the quotes, just to sanitise for public consumption
“The project was very good at identifying and managing risks. Constant communication of these risks was imperative to the success of the team….”
“The use of Agile techniques, particularly test-driven development and full automation of testing allowed the project to deliver very few bugs and fewer design errors. Use of experienced Java developers and automated Java style checking tools … allowed quality to be measured. The same metrics collection occurred at each increment for defects. This project was outstanding from a quality perspective….”
“Due to the high level of business-technology interaction throughout the entire project, the quality of the final product was extremely high. There were no surprises to any of the key business stakeholders or the technical team.”
“Using user stories, and delivering them in two week development cycles meant the project had a very good understanding of how they were tracking, and what could be achieved in the timeframes. The project regularly made adjustments to either scope or resources to ensure that would meet the mandatory requirements by the fixed deadline.”
“Throughout the life of the project, the use of user stories made scope management a perfectly manageable task. It gave ownership of the project scope and deliverables back to the customer for prioritisation and delivery.”