Go/No-Go – That sounds like a Japanese manga character of pokemonstic proportions! 😨
It’s actually the Big Meeting that happens at the end of UAT (User Acceptance Testing).
Very Important❗
This is when the client looks at the defects found during testing to confirm if you’ve done a Good Job.
If UAT has been wobbly, then we may be at risk of getting a No-Go decision, which is Bad. 😬
Bad because it may mean that the client has no confidence that the system that we’ve built is good enough to ‘deploy’ and allow the users to use it.
As a Project Manager, my job is to manage the project so well, that we sail through that meeting. Sometimes though – I may recommend No-Go if I feel that the risks are too high, if we were to Go Live with the issues that have been found.
There have been situations where the client has made some risky decisions that we (me and my project team) have not been comfortable with.
Decisions that would result in a highly unstable system.
All we can do is to make sure the risks and issues have been highlighted and escalated through proper channels, and impact assessed properly.
So when the decision is made to GO, despite the wobblies and our concerns, all we can do is to follow instructions and then to duck very quickly when the fireworks ignite. 😣
When your project team says, “No” please listen.
We don’t gain anything by halting or delaying a project, but there are times when it’s necessary.
That’s what a Go/No-Go meeting is.
It’s where we make an important decision, based on the result of testing that will expose the quality of the delivery – good or bad.
Below is a short clip of a training I did last year. I only recorded the trainings so that I can review my training delivery style (hence the slightly unpolished look).
I’m making lot of my videos available on my membership site in a Q&A format launching on 8 Nov, and it isn’t very polished but I felt that the vaue of the content outweighed my sometimes crazy hair 😁.
So, have you ever been to a Go/No-Go meeting?
What was your experience?