As discussed on CRW Retrospective it would be great to align on and document the entire CRW development process on a wiki-like / Mojo page.

• Program backlog and CRW requirements process:
  a) links to artifacts and the roadmap
  b) who (which role) can create, review, set priorities and delete it
  c) when, how (regular train mtgs, signoff docs, ...)
• Sprint and team backlogs and planning process
  a) links to sprint and team backlogs artifacts
  b) who is involved in this process
  c) when and how (grooming sessions, sprint planning process)
  d) applicable for new features and bugs
• Development & QE process
  a) acceptance criteria per epics or stories
  b) Definition of Done document
  c) links to sprint schedule and demos artifacts

Such a transparency and documentation shall not be useful only for 'externals' (PST, CEE, other RH teams) and newcomers, but also for internal team members to get all details about actual work priorities and plans ahead.