Our work relies on a lightweight RUP-like methodology. We don't believe in Extreme Programming, but we embraced some of its practices (test-driven programming, iterations, code standards, no overtime).

INCEPTION. At the end of this phase we have several work products baselined such as the the Vision and Scope, the Customer Requirements, graphic design propositions, scenarios and an initial set of the core Use Cases. A Glossary and a Requirements Traceability Matrix are also started. A high-level Project Plan is created. The Inception team carries out a Risk Analysis, also detailing the risk mitigation actions.

ELABORATION. We set up the Change Control Board. The Software Architect designs the Product Specifications and all the application screens, additional activity and state diagrams, class architecture and O-R tables etc.

Staffing the team is finished, the Readiness Analysis is performed, and the gaps found are resolved by training. We can already start programming for features or functions that can be started in this phase, or which present a high risk.

The Project Plan is detailed and baselined.

CONSTRUCTION. Based on the Project Plan and their assigned tasks, Programmers start writing the tests, then implementing the code. After coding, the tests are executed and the code is fixed. The Project Manager checks the progress against the Project Plan daily and takes measures when the two are not in sync. Any Change Request is carefully analyzed and managed by the Change Board, affecting the estimations if an implementation decision is made.

STABILIZATION AND DEPLOYMENT. The product is tested by test engineers and reviewed by the Software Architect, Usability Specialist and by the client. Any issues are fixed by the programmers. The product is finally delivered to the customer, or deployed at the production site.