During my last projects I have been using analogies when reporting status and during project team discussions. This started when the project I was working on as a test manager was running according to the tried and true waterfall model with many, many, many test cases. So why should I report the same number that everyone could find by a quick look in Jira? I did create a nice dashboard for this.
We had a discussion within the team and came up with the car analogy as a good starting point and something that everyone can relate to. The analogy took hold and shortly was the standard starting point for discussions or answer to questions.
Some examples of how this was used
- The body has been delivered but we are still missing the wheels
- Lacking deployments from supplier
- Brake pedal starts the wipers
- the integration's are faulty
- Again we have a SUV when its a compact we need
- Misunderstood requirements
- Supplier tests the airbag, buyer test drives the car
- Difference between System test and acceptance test
- Many more examples exist, and of course other analogies as well
We used this within the team but also when reporting to management as they also had full access to Jira and could get the actual numbers, so this gave them the quick status and also explained to those who did not have or needed the technical knowledge and full disclosure.
I have seen and used similar analogies in other projects and talked to others who have used this as well.
How do you report status? Discuss the latest progress? Or just talk shop within the team?
No comments:
Post a Comment