Lesson Learned: Automate Project Evaluations

Jurgen! We can never find the time to evaluate our projects. How do you manage your evaluations?

Project evaluations (or retrospectives) are a nuisance. Everybody knows they are important, but nobody performs them. With at least ten new projects starting every week in our company, how can I instruct our people to get all project stakeholders together (in ten different settings) and construct a “lessons learned” list of the ten projects that were delivered the week before? Nobody is available for such meetings because they are all too busy making sure the new projects are initiated properly. Sure, this is no excuse. But it is reality.

Automate the Process
To get around this problem I have decided to automate the evaluation process. Everytime a project is deactivated in our project management system, a notification message is sent to each of its stakeholders: the project manager (or ScrumMaster for some), the business consultant (or Product Owner for some), the technical lead, the technical manager, the financial department and the quality assurance manager. Each of them is asked to rate the project on a scale of 1 (Bad) to 5 (Excellent), with the option to add some comments and lessons learned. It is similar to Amazon asking you to rate a book after you’ve purchased it. (Only in our case people don’t rate value-for-money but satisfaction-for-energy.)


No Secrets
The nice thing about this approach is that we are now starting to accumulate a queryable history of evaluations that will enable us to drill down to customers, teams and individuals. All ratings are open for everyone to read and respond to. We have no secrets. (If someone messed up completely, everyone usually already knows.) This makes sure that people’s ratings and comments are honest as well as constructive. In fact, I just posted the monthly report of our April’s ratings on our company intranet to share with everyone.

From Feedback to Action
Browsing through these evaluations regularly, I am able to pick up what the most common problems are and I can check if they are already covered by some of our quality improvement steps. In some cases the feedback still requires some face-to-face communication, as I walk up to people and ask them to elaborate on something, or to respond to someone else’s somewhat critical findings. And in some (but fortunately rare) cases, when I hear of something that makes my hair stand on end (or my jaw drops to the floor, or my brain passes out) I organize a face-to-face project evaluation meeting. And believe it or not, it turns out that these are now easier to organize now that everyone knows that these meetings are only reserved for the most serious cases. Nobody wants to miss out on a bit of flame and mud throwing. All in good fun of course.


Lesson Learned
Sometimes you have to run a process the unconventional way, or it will never run at all. For years we never could get people to organize project evaluations. But the automated project evaluation looks to be reasonably successful. In April the number of automated evaluations climbed to 117, as compared to 65 in the month before. And in the meanwhile I do my best to make people see that the evaluations are actually being read and acted upon.

Of course, automation of an important part of a project workflow can only be done for the most mundane of processes. If you cannot get people to perform their daily stand-up meetings, I wouldn’t dream of automating it!

Interesting? Not? Tell me about it! Or check out some of my other favorite articles:

Make It Simple vs. Do It Simple

AINO: Agile In Name Only

The Ethical Software Engineer (Not French!)

Met Immediate Peak’s geavanceerde technologie, ben je altijd een stap voor op de markt.

  • Top Five Reasons Why Prince2 Sucks
  • Tear Down Your Cubicle Walls
Related Posts
free book
“How to Change the World”