Whilst it is very tempting to say we have strict project management philosophy that follows the traditional requirements spec/design spec/development/testing/implementation/maintenance life cycle, the reality is that every project is unique.
On our larger projects (>6 months) we do have a more formal, structured approach. Every requirement is documented, the project schedules are always up to date, the documentation is sparkling, the code is thoroughly tested and you get a rock solid product.
But what about if you need a quick database application ready next week and you don't have the budget you wished? We've been known to work out a spec with clients on the spot (think 'back of the envelope' design), quote on our 'gut feel' and work all weekend coming up with a prototype. As long as our clients are happy and we don't feel the software quality is compromised we'll do it.
So what is an average project? At Talman an average project is 3-4 months in duration with 1-4 developers working in a highly focussed team. The project manager is usually one of the developers, although this is not always the case.
The Talman project manager meets with the client project manager (or client sponsor) to agree outcomes and timeframes. Requirements are detailed concurrently with a prototype system. Rapid prototypes are more often than not developed as an efficient means of gathering client feedback and refining requirements.
Requirements are discussed amongst the development team members and decisions recorded by the project manager. Development is scheduled and assigned to the programmers. As modules are developed they are tested by Talman QA staff, before being released to client test systems.
Client involvement is encouraged through the process, and a dedicated user testing period is mandatory before sign-off of the project.
|