As a Platform team member, I need style guidelines so I can write effective documentation and avoid launch blockers.
Hypothesis or Bet
If improve style guidelines then we expect fewer launch blockers and decreased deployment times.
OKR
Launch process for creating/maintaining quality docs that support VFS Core Tasks.
Definition of done
All issues completed
Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.
How to configure this issue
[ ] Labeled with Team (product support, analytics-insights, operations, Console-Services, tools-fe,content-ia, service-design, vsa-*)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
Status
Product Outline
Link
High Level User Story/ies
As a Platform team member, I need style guidelines so I can write effective documentation and avoid launch blockers.
Hypothesis or Bet
If improve style guidelines then we expect fewer launch blockers and decreased deployment times.
OKR
Launch process for creating/maintaining quality docs that support VFS Core Tasks.
Definition of done
All issues completed
Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.
How to configure this issue
product support
,analytics-insights
,operations
,Console-Services
,tools-fe
,content-ia
,service-design
,vsa-*
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)