Page History

...

This project contains three workflows, with the distinction being made whether an item contains a software release (development workflow) or not (four step workflow).

Any work that can require a deployment uses the "Development" workflow:

These workflow steps are intended for:

• Backlog: work has not started;
• In progress: a developer builds & unit tests their own work to meet acceptance criteria;
• Review: a peer reviews any code & functionality;
• Ready for test: waiting for a QA officer;
• In test: QA officer is performing integration test & regression test;
• In UAT: PO/business validate that the functionality is as required, or provide feedback;
• Done: the work is completed without deployment needed; or
• Ready for deployment: the work is done & documented, but deployment to production is needed;
• Scheduled for deploymen: deployment date is set;
• Done deploymen: the solution is available and working on production.

Any issue-type that will not include a deployment uses the simplified "Four-step" workflow:

Epics have three additional statusses for Product Owners to prepare the work:

These workflow steps are intended for:

• Epic created: work has not yet started (this specific status allows easy searching for open Epics);
• Define business case: the goal of the epic needs to be made clear - what is the current situation, and why do we need to change this?
• Define acceptance criteria: we can only celebrate the success of an initiative, if we make clear how we will measure success - what is the acceptance criteria?
• Assign team: only after the business case and acceptance criteria are clear, does it make sense to involve a development team.

Field configuration

Yamaha Teams

...