A successful project is much more than code. No matter what size.

A successful project addresses all of the points below. Even if some may be obvious.

Business analysis skills and the right level of competency are required to judge the feasibility. Knowing solutions and the technology context, a second opinion can be provided mostly right away. Otherwise, research validates the approach.

A proof of concept allows to focus the business objectives, synchronize stakeholders and finish at the first shot. A prototype sells the project internally and recruits the sponsors to support the finished product go in production.

Specifications make sure that the business expectations are understood and the objectives can be met. The mental process during writing fills the gaps, clears the underestimation of complexity, fixes the mindset and attitude, clarifies to non-technical actors that their business objectives can be met so business users can validate them and stakeholders commit the funding.

A roadmap defines precise cycles and quality checks. Bigger projects can be split and start small with a clear future scope. Long haul projections anticipate the maintenance costs over many years of exploitation.

The skills of each player are as much important as the effectiveness of the team. Involved people must be available, with enough space and time to be able to focus, be responsible and commit themselves from the beginning to the end of the project. Animosities must be discovered and re-consolidated, the communication between parties smoothed.

During development code is written and improved to implement the required functionalities. The code must be clean: readable, maintainable, following well known patterns whenever possible, with exceptional test coverage.

Crisis are common during development. The true status of the project must be clear at any time and mechanisms must exist to confirm the alignment with business expectations and identify budget glitches and timetable shifts early. An agile way to manage the crisis brings more success.

Testing, testing and more testing prevents larger reworking and is the key to a cost effective go in production as often the first impression counts.

A site on the Web or the Intranet explaining the project purpose along with an easy understandable user help will rise the adopter figure. A technical reference makes the project viable over a long time.

Mock-ups, online demos and other technical sales support can significantly increase the financial turnout.

Maintenance is much more than first level support. Along with second and third level support, assuring that the know-how is maintainable over the product life span is the key factor to product continuity.

Finally, completing all open issues allows to conclude the project or a project phase, leaving the mind open for other undertakings.

Our ultimate goal is to finalize the project with

“A pleasure doing business with you”