Issue:059

From atwg
Revision as of 20:14, 16 January 2018 by Ccicalese (talk | contribs) (CSV import)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Description mismatch between TechCom definition of when an RfC is needed (strategic/cross-cutting/hard to undo) and how some Audiences teams interpret it (no RfC if the technical changes are not large, even if it has a serious strategic impact)
High Level Properties Process, Department Alignment
Technology Properties
Customer Properties
Symptom or Cause Is Cause
Cost
Impact
Priority
Leadership Level Up
Out of Scope