Document Version-n-go process

[ianphil]

Description

As a DevOps Engineer, I'd like to have documentation on the version-n-go process, in order to understand how to work with application teams.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

• [ ] Should ‹testable condition that should be satisfied›
• [ ] Should ‹testable condition that should be satisfied›
• [ ] …

Also, here are a few points that need to be addressed:

1. Constraint 1;
2. Constraint 2;
3. Constraint 3.

Resources

Tech Design (Link to PR until Merged into master) Mockups

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

[ThePhen]

From a conversation during planning today, it seems that this issue needs to introduce two example artifacts for consumers to take advantage. They would be described in the docs (vs shipped as two additional files).