Acceptance criteria plan

1. Read the design and its goal.
2. Check clarity, hierarchy and accessibility.
3. List the issues in priority order.

Needs from you: The design and its goal.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the change.
2. Find the pages that describe what changed.
3. List the ones that are now wrong.
4. A person updates them.

Needs from you: Change history; Documentation pages.

What it needs connected: Code host, read only.

Where a person is designed to decide: A person updates them.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

1. Read the week's work items and changes.
2. Group them by shipped, in progress and blocked.
3. Write the report for the team lead.

Needs from you: Work items; Change history.

What it needs connected: Code host, read only.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.