We have just completed the build of a new application for an existing corporate client. From a development perspective, it has many of the usual attributes:
- Hosted by Ffenics
- Pan-European use by our client and their employees
- Global use by our clients’ end customers
So, what makes this project blog worthy?
It was clear that we needed an Agile approach – but what was very interesting was that we had been able to assess the impact on timescales and budgets of an Agile approach, as opposed to a traditional waterfall methodology.
Our client had an understanding of what they needed which enabled a design specification to be written, but we all agreed that, due to the nature of the application and the business processes that it supports, there were some design questions we would not be able to answer until the system was in use. Consequently, we built a pilot application (with limited reporting) based on this initial spec and trialled it in conjunction with our client and one of their customers. In light of the initial pilot feedback, we modified some of the table structures and processing functionality.
From a Project Management perspective, we split the project into the following phases.
- Design of pilot system and sufficient reports to enable the pilot to be useable
- Roll out of pilot to client and one test customer
- Agreed pilot design changes and development
- Second pilot
- Agreed final changes and develop
- Complete and go live
The net impact?
- Project cost came in at under original predictions for a traditional waterfall approach
- Pilot system delivered very quickly
- Final system operational sooner than originally planned
- The delivered solution exactly met their needs without costly and time-consuming redesign work
have just completed the build of a new application for an existing corporate client. From a development perspective, it has many of the usual