Skip to content
EmeSoft Docs

How to Read These Docs

These docs are designed so you can find what you need in under a minute. Here is how they are organized and how to read a role page.

Reading paths by audience

Section titled “Reading paths by audience”

If you are a stakeholder or client, read Process Overview, the Stakeholders page, and skim Ceremonies so you know which meetings involve you. That is enough to follow any project.

If you are joining the delivery team, read the Scrum/Agile Foundation, then your own role page, then the RACI Matrix to see your hand-offs.

If you are reviewing our use of AI, the AI Tooling Map and the three Field Notes pages are written specifically for you.

Standard role-page structure

Section titled “Standard role-page structure”

Every role page uses the same eight sections, in the same order:

  1. Mission - the one-sentence reason the role exists.
  2. Responsibilities - what this role is accountable for.
  3. Inputs - what the role consumes, and from whom.
  4. Outputs - what the role produces, and for whom.
  5. AI tools & how we use them - named tools, concrete usage, example prompts.
  6. Collaboration - key hand-offs and the ceremonies the role drives or attends.
  7. Definition of Done for the role - the bar that signals the role’s work is complete.
  8. Pitfalls & anti-patterns - mistakes we have actually seen, and how to avoid them.

Conventions used throughout

Section titled “Conventions used throughout”
  • Diagrams are Mermaid - they live in the markdown as code, so anyone can edit them in a pull request. No binary diagram files to manage.
  • AI usage is always concrete - we name the tool and show how it is used, not “we use AI for X.”
  • Callouts flag the important bits: