Posted by: Jeff Timmins | July 11, 2014

What flavor of Release status meetings do you like?

What flavor of Release status meetings do you like?

I’ll admit that I’m a fan regularly scheduled meetings but not those that fill up 8 hours a day each day of the week. Give me the 15 to 30 minute highly effective meeting a few times a day and I’m good.

For the most part Go/No-Go meetings can be those short and highly effective meetings + they greatly benefit your Release Management process. That being the case is important to note that much like Frank’s Hot Sauce, it is not the only solution for every scenario.  Sometime you need to mix it up a bit.

A typical Go/No-Go meeting is as simple as it sounds really. Inviting decisions makers and those with detailed knowledge of the Release status to share. Everyone has a voice and either majority wins or the Captain of the ship wins. This is typical for most Organizations that don’t have any other weekly status meetings. It is scheduled for the end of the Release cycle and allows everyone one chance to share status. Those meetings work as long as there are no surprises.

An example of mixing it up would be limited or going without. It is possible that an Organization’s Releases run smoothly enough that they can survive without the traditional Go/No-Go meetings. If that is the case your Org runs 2 week or less cycle and your regularly scheduled check-ins allow for Go/No-Go type conversations. Then from time to time the Release doesn’t trend well and only at those times is Go/No-Go meeting called.

Another example is the combo approach – running a weekly Cross-functional meeting that provides give general status and then adding a Go/No-Go meeting right before the Release. This works well for a 4 week Release cycle or greater. This allows people to be informed regarding the details of the Release and allows for a focused sub-set of people for the Go/No-Go decision.

If you want to get really crazy – especially if your Release cycles are greater than 2 months – you might want to try the Warm & Fuzzy approach. This approach can be inserted into the middle of the combo approach above and it provides for the “pre-Warm & Fuzzies” (checking temp of the Release, sometimes placed around Feature Freeze ). Next would be the “pre-Go/No-Go Warm & Fuzzies” meeting (sometimes placed around Code Freeze) and then followed up with the traditional Go/No-Go meeting.

Lots of options but what flavor do you like?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: