Mission-Centered Design · Part 7 of 9

Release and Support

Releasing, documenting and validating what you built, then supporting it in the field.

Release

  • Consult everyone involved, early: release coordinators, infrastructure, documentation, QA, the project manager, other development teams with dependencies, and marketing. Releases look like fires because people talk to each other at the last minute. Ask at the start of the project how it will be released, to which product versions and on which platforms; the answers can nearly double the work, which is far better to learn at the estimate than at the end.
  • Know the release type. A major release goes to every customer, is big, risky and coordinated across teams, and is the most important effort in the company while it happens. A minor patch goes only to the customers who need it and is coordinated by the teams involved.
  • Documentation is your responsibility. Every product change should be documented: feature documentation, release notes and use cases. Capture screenshots and video as you go.
  • Validate every requirement. For contract work, check that each requirement was met using acceptance test procedures, plus playtesting by use case. Validation can start early but must be re-confirmed at the end, because new work can break old work.
  • Playtest the use case before the customer does. Requirements can all pass while the customer’s real scenario still fails. Find the gaps before acceptance testing does.

Maintenance and Support

  • Customer acceptance testing. After delivery, customers test against the requirements and produce a list of defects. Attend if you can, and bring people who know the design; it’s far easier to resolve misunderstandings in person. The development team estimates each item and gives an opinion on whether it’s in scope.
  • Unclear bugs. When it isn’t clear what the “correct” behavior is, it isn’t a bug yet. It needs investigation, design discussion and a product decision first.
  • Support requests. As a rule, if you can solve it in under an hour, do it. If it’s bigger, get your lead’s approval. Either way, ask the question behind the question; people rarely explain their real use case unless you ask.
  • “How long would it take?” from support is a red flag. It often means a fixed-price service contract is being started. Escalate instead of answering, because such mini-projects come at the cost of current ones.
  • Customers rarely upgrade. For defense customers running fleets of simulators, the risk of upgrading usually outweighs the reward. Keep every past version’s documentation online, and check the customer’s version before answering “does it do X?”
  • Small paid requests are mini-projects: the same lifecycle on a much shorter timeline. Keep scope minimal and suggest alternatives.

Key Techniques

Requirements traceability, playtesting, external coordination and item tracking. See the technique library.

Let’s Talk

I am open to senior product roles in defense tech. I also enjoy hearing from fellow Operation Flashpoint and VBS veterans, and from anyone writing or podcasting about simulation or war in games.

info [at] andrewbarron.net