Methodology for project delivery success
In my experiences, you must evaluate 3 important points before selecting a methodology for your project. 1) Organization maturity meaning clear project definition and repeatable project processes 2) Resistance to change 3) Project size and business impacts
In my career, a methodology is a structured approach for project delivery; in the 1990’s we were talking about XP (Extreme programming) it faded a bit, but has made resurgence lately with agile gaining momentum also very popular in those times was prototyping. Early 2000’s, Sigma Six, ITIL, CMM and Waterfall became very popular.
I was asked the question which methodology would you use to increase your probability of success.
My definition of project success is defined as getting the project built on time and on budget.
Failure from a management perspective is based upon exceeding initial budget, exceeding initial schedule, or not completing initial scope.
Also Failure from a business value perspective is when the cost of the project exceeds its benefits. Usually, an ROI or a TCO is done based on a defined time period. I have not seen many organizations ever bother to measure actual return following deployment but this practice seems to gain popularity.
We always assume that we have an A team, the answer is not "agile " vs. "waterfall" development -- some experts like one, and some like another method. Organization maturity, clear project definition and repeatable project management processes often have much greater impacts on product delivery success.
While experts differ on the best software development method, most would agree that successful projects share the following characteristics (mentionned in the project survival handbook):
- project is approved and funded
- project has a business sponsor
- project has an IT sponsor
- project has clear objectives
- requirements are clearly written
- requirements are traced throughout the project life cycle
- key stakeholders are involved, and kept involved, throughout the project life cycle e.g., business, operations, subject matter experts, software end-users, etc.
- project plan is defined and adjusted as needed (see change management below)
- responsibilities are clearly defined
- people are held accountable for certain activities and deliverables
- project documentation is prepared and project risks and contingencies are defined
- communication and training occur at various steps of the project life cycle
Do not get bogged down which methodology you should use they all work, just make sure which one fits the best with your organization maturity and structure, the most important aspect do not expect any major difference on the project outcome when selecting one methodology over another.