Let's start by looking at
When do we say that a project has been completed?
The answer to this question varies as this question is present. The project manager will usually say that the project has been successful if the project has been completed within the scope of time, time and cost and, of course, has delivered the required quality. Some may say that the project is successful if the customer is satisfied at the end of the project.
Think of a scenario where the project reached scope, time, and cost criteria, but the underlying software architecture and design were not under the brand, so when a product needs to be expanded or maintained, a lot of issues are required. Do you want to call this project success?
So you see that the project may not be successful in all areas and there are different views to eliminate project success.
How do we define a successful project?
The definition of success varies from project to project. In order to set criteria to clear success in the project, we first need to do "stakeholder analysis". The main stakeholders and the viewpoints of those who need to be covered by most projects are
* Business: Business Need the project to fulfill.
* Tasks: The scope of the project will be delivered within the agreed time, cost and quality parameters.
* Individual / Group: Perspective of people directly or indirectly linked or affected by the project. For example, Society as a whole, End Users etc.
You need to take into account many perspectives and agree to define "Success Criteria", also known as Key Objectives (KPIs) or Key to Success (KSI).
Success criteria should
* be based on the views that are important for the performance of the project.
* Should be simple, accurate and measurable.
* Must be defined correctly when the project begins.
* Be ranked by priority.
* Should be consistent throughout the project.
Basically, record the items that are important to your project performance and how they would measure.
Priority is important because in spite of the best intentions, there is a tendency to trouble and make decisions. For example, if your performance requirements give priority to quality of delivery over time, you can respond accordingly and spend more time to achieve the required quality, even if it might be at the expense of delay in delivery.
Some examples of performance criteria in the projects and perspectives they cater to …
* Achieving "such as" accreditation. Business
* Client Adequate Index should be at least x%. Business
* Work overtime does not exceed plans of more than x%. Tasks
* At least x% of the code can be used. Tasks
* The average product setup time should be less than X minutes. Tasks
* Type of post should not take more than x minutes. Individual / group
Success is an obvious goal of all projects and as it should not be an unimaginable goal. It should be defined at the start of the project in consultation with all stakeholders of the project. If you take time to consider performance from multiple angles, you will make the odds of future projects easier and easier to achieve. Even though meeting the success criteria, it does not necessarily mean the satisfaction of all owners or "customer satisfaction". All that means is that the criterion identified for the proposed stakeholders has been achieved and the project has been successful in these criteria.