Open jwoodman5 opened 2 weeks ago
@jwoodman5 - Do you have silent failures that you are remediating? "ZSF:Incident" is for epics tracking the work to respond to a specific incident of silent failures. I'm realizing that probably wasn't clear in my announcement today.
Status
Problem Statement
In a couple of sentences, describe the Who, What, Why, and Where of the challenge / pain point you seek to address.
Follow your problem description up with a "How might we... ___" statement re-framing that challenge as an opportunity. Don't hint too much at what the solution might be, you should have enough of a focal point here to guide your ideas, but plenty of freedom to think laterally and innovatively as you experiment and prototype later.
Hypothesis or Bet
How will this initiative impact the quality of VFS or Platform teams' work? How will this initiative be easy for VFS or Platform teams? Or how will it be easier than what they did before?
We will know we're done when... ("Definition of Done")
What requirements does this project need to meet for you to finish this initiative?
Known Blockers/Dependencies
List any blockers or dependencies for this work to be completed
Projected Launch Date
Launch Checklist
Guidance (delete before posting)
This checklist is intended to be used to help answer, "is my Platform initiative ready for launch?". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given Platforminitiative. All links or explanations can be provided in Required Artifacts sections. The items that can be skipped are marked as such.
Keep in mind the distinction between Product and Initiative --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. VSP Product Terminology for details.
Is this service / tool / feature...
... tested?
... documented?
... measurable
When you're ready to launch...
Required Artifacts
Documentation
PRODUCT_NAME
: directory name used for your product documentationTesting
Measurement
TODOs