Go/No-Go: Green-lighting the Release
Overview
Mobile releases generally occur
frequently, necessitating faster approval cycles than console games.
Nevertheless, releasing an app before it is ready can be detrimental to a small
mobile game developer. The Go/No-Go review is a good way to ensure release readiness
in a thorough, yet agile manner.
The
Craft
Up to one week before the scheduled
submission, key stakeholders meet to determine readiness of the release. This
review should include a playthrough of the release content (a playtest or Daily
is a good idea here), a review of outstanding defects, and any known exceptions.
To ensure there is an optimal
understanding of the state of the game, it is important that key disciplines
are involved in product development are also involved in the Go/No-Go process.
Depending on the makeup of the team this should include, at minimum: Software
Architect, Product/Feature Owner, QA Lead, Design/Creative Director and any
discipline leads who had a hand in the release.
With input from all involved, output
is the Approval/Denial of the release content and next steps (if any).
Ultimately, the Product/Feature Owner makes this call.
Possible Outcomes:
- Delay the release until
outstanding issues are addressed.
- Release the app with known
issues, which may be addressed in a subsequent release.
- Shelve the release.
Scaling
for Success
Small Scale - Go/No-Go reviews are a
must for small teams who need to “get it right the first time” for the sake of
their business success.
Large Scale - Avoid decision by
committee by limiting the size of the review participants. If multiple teams
are working on features for the release, one or two representative from each
can be the voice of their team. This necessitates some preparation, so it is
useful to review content before the Go/No-Go meeting occurs.
Additional
Experiments to Try
- Conduct the Go/No-Go after a
routine playtest or Daily. The content will have just been reviewed with
feedback provided. This can make the decision go much faster.
- Use a thumbs up/thumbs down
method (aka Roman Vote) for a quick decision. Allow the dissenting
voter(s) to take the floor and discuss their concerns. This can focus the
discussion more efficiently.
Comments
Post a Comment