Create User Journey Design and Umbrella Documentation #85
Description
Description
As a user I can find a guided journey through the portfolio of app and infrastructure patterns where I am presented with principled recommendations backed by examples and case studies at key technical/implementation/deployment decision points
Acceptance Criteria
One, or more, articles that explain how to build contemporary applications whose infrastructure is managed via Cobalt. Such articles would either need to explain Cobalt, or describe how "advocated patterns," or "templates," are leveraged (preferably across a set of applications).
The stories need to be short enough to be appealing to read (quickly) and just detailed enough to provide a working relationship between the reader and Cobalt.
Tasks
- enumerate existing usages of Cobalt, and derive story ideas from them.
- write some outlines / quick 'sketches' of some of usage patterns, then have the team of contributors and users provide feedback and direction (and writing assistance)
- write stories/articles!
Again, I'd like to keep these short, but valuable.
Resources
Technical Design Document
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