I often talk with clients about what makes a project successful for them. Obviously of importance are:
- Finishing on time
- Staying with the budget
- Ensuring stakeholder satisfaction
- Ensuring a quality project
These are always at the top of the list certainly – for any project without doubt. But then we start talking about past projects and what made a particular project a success in the eyes of the organization and the internal and/or external client, I heard some of the following from clients:
- The project went above and beyond expectations for a difficult client.
- While over budget, the value received from the project made the additional cost worthwhile.
- The strides made by the team in improving the outcome of a difficult project was extremely impressive.
- The team pulled together during a difficult time to overcome lots of adversity.
- Each stakeholder really felt like his/her needs were met on the project.
- The project enabled the team members to learn new skills and build their knowledge.
- The project manager was able to focus the stakeholders and develop a project plan and scope of project everyone could agree on.
- The team was able to ensure more functionality for the project than was expected, while keeping within budget and meeting the timeline.
- Even though the stakeholders were unhappy with the project initially, the project manager did a great job working with them to truly understand their needs and all in all, the end result was great.
- The project manager did a great job working with an untrained project team and still coming close to meeting the timeline and budget.
- The project team did an amazing time working under such a tight timeframe. They didn’t make the timeline desired (they came close!), but kept a positive attitude throughout the project and really handled the situation well.
- Difficult lessons learned captured from one project really helped another difficult project that was in progress – since lessons learned had never been shared before, this was considered a success!
- The team really came together to manage a project when the project manager obviously wasn’t able to handle it. They didn’t fall apart or complain, they just did what had to be done.
As you can see, in some situations, success was measured by an accomplishment the team made, or by how well the project manager handled a difficult client, or the ultimate satisfaction of the client. Success was not necessarily based on meeting a budget or a timeline. In some situations, the project was over budget and/or over the timeline desired – but something occurred that made the project a success in the eyes of the client.
Your thoughts? What makes a project successful in your eyes – above and beyond meeting the budget and timeline requirement? Share your thoughts, ideas and stories in the Comments field below. Thanks!
Hi Mikko,
If a project manager is able to work with the stakeholders to make adjustments or changes to the project to better meet their needs, with their support, you are likely to have a much happier stakeholder group at the end of the project. This does require communication with the stakeholder as to the affect on the budget and timeline by making changes (although sometimes there is no affect because of efficiencies, etc.)
Thanks for your comment!
Best regards,
Gina
I feel that measuring project success is a two fold issue. You can either fullfill the predefined set of demands and specifications or you can during the project truly understand the need for the outcome and adjust your project to meet that.
I mean that in project world – especially in traditional waterfall projects but also in agile development – the project manager and the team usually are so focused in fullfilling the orginal demands that they oversee the possibility to challenge the specifications though they learn very much of the issue at hands during the project.
I have found that in the end most successfull projects are such that because of open mind of the demander and project manager can surpass the original goal because of learning and understanding the real nature of the task and adjusting the project to that. Even though the original timeline and budget may not be met.
Hello Sean,
Completely agree – every project I start off with includes a discussion with stakeholders around “what does success look like” and “how are we going to measure success” (what is the baseline). I do get at times that “we aren’t as concerned with the timeline as we are about quality/cost/ and that usually prompts me to ask whether there have been issues in the past with quality/cost/ and if they have seen those issues particularly when they are forcing a timeframe for completion. In some situations it is a matter of improper planning up front – just throw a due date out there without real consideration for the actual time for the project.
Many thanks for your thoughts!
Best regards,
Gina
I think it helps to agree on some ‘measures of success’ up front with stakeholders. I’m always surprised that finishing on time is not as important to a lot of stakeholders I’ve run across v. quality or ROI.