Evaluation is a very used expression, which we use all the time in working situations in connection with the solution of a task or project.
The purpose of evaluation is to accumulate the experience you have done, so successes can be repeated and mistakes can be avoided in future projects. The focal point of the evaluation is to ensure that the people involved easily can take benefit from the evaluation process. They will recognize and make it particularly important to focus on and ensure control and learning in the project. The concern regarding control of resources and its optimum allocation in a project, in the context of learning, is that it is essential to gain complete certainty that you are on the right path. In case of conflicts between the people involved in the project – evaluation helps to adjust the process itself.
As a professional IT project manager, I gained experience from large and complex organizations and have seen their limited acceptance in the use of evaluation methods. Here I have seen statements such as “The evaluations cost time, money and let us choose a supplier we already know”. ”Therefore there is no need to spend time to run a comprehensive evaluation process”. Here it turns out that some outcome from projects has a decisive impact on the company’s bottom line and their market share compared to their competitors.
Is it necessary to evaluate?
Experience shows that there definitely is a need for evaluation during and after project completion. Without evaluation, it can very easily go wrong economically for the company. In the beginning of the project it is crucial to evaluate the criteria of gain, what the gain should be and it must be defined in the requirements specification. It is legally binding and determines what vendor shall provide for the money. It is important to involve customers or users of the evaluation process during project development. First of all it is important for the involved people to know if their money and support has been used sensibly or not. Secondly their frustrations over the failures of the project during the research/developmental phase can be used constructively and can contribute to a lot of learning for the future projects.
One solution to the problem can be a so-called agile method for developing both infrastructure and research/developmental projects in private and public IT companies.
Using the agile management
The approach is to work in small iterations of 2-4 weeks duration and after each iteration the finished product is shown. It gives abundant opportunities for people involved (customers, supplier and the project team) to initiate changes as required.
A lot of positive and negative assessments will be committed in all projects. To be successful, and create a positive experience in an efficient way, you need the feedback on the choices being taken. Feedback about the choices made during the project, can easily and efficiently be visualized by using the starfish method.
The Starfish method used during the Sprint Retrospective
The article is only based on SCRUM Sprint Retrospective, and not the entire SCRUM method. Retrospective is one of the important project meetings at the end of each sprint. Here are some of the most important issues to consider and discuss during each sprint.
- Keep doing: Is a good starting point for team members to focus on typically all the good things that they liked about the project.
- More of: Is another type of focus that helps further refine or highlight practices, achievement, for an instance, that the team members might want to try more, and are not necessarily taken full advantage of.
- Start doing: Is a great opportunity for team members to suggest new things to try because of things that may not have gone so well or just for simply keeping things dynamic and fun.
- Stop doing: Obviously for things that are not very helpful to development practices or not adding much value.
- Less of: Helps to focus on practices that might need a bit more refining or actions that were simply not helpful in the current circumstance.
Experience has shown that there is more room for learning by involving people. Getting people to write on the “yellow note” and then post-it under the group area in the starfish method is also a great visual way to evaluate health in the project. It forces human capital to think creatively and act upon it, Instead of saying things that are not worked out thoroughly. The reason being; saying something verbally is much easier, compared to writing something down on a yellow note.
In several projects, I have used the methodology for both development and infrastructure projects from the public and private sectors. Here I have achieved more excellent results in project evaluations by using the method in Sprint Retrospective. In addition, the results of evaluations have continually contributed to strengthening change processes by sharing insights and results with the customer, supplier, project team and other stakeholders who adapted their activities.
The method is universal and can be used in all aspects of a project. It is highly recommended to use the method after achievement of a milestone in the project and in consultation with all stakeholders/ participants. It informs the participant about what works and that which does not. In this way they will get a better insight and understanding of the results they have achieved. This will make it possible to introduce new ideas by providing constructive feedback.
I would definitely recommend using the method in Scrum Retrospective when you need a quick and sensible evaluation here and now.