GearUp - Agile Creative Crafts

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