Page History

...

This project contains four 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:

Image RemovedImage Added

These workflow steps are intended for:

• Backlog: work has not started (work can always move back to this status);
• In progress: a developer builds & unit tests their own work to meet acceptance criteria (work can always move back to this status);
• Review: a peer reviews any code & functionality;
• Ready for test: waiting for a QA officer (this step can be skipped);
• In test: QA officer is performing integration test & regression test;
• In UATValidation: PO/business validate validates that the functionality is as required, or provide provides feedback;
• Done: the work is completed without deployment needed; or
• Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete; or
• Ready for deployment: the work is done & documented, but deployment to production is needed;
• Scheduled for deployment: deployment date is set;
• Done deployment: the solution is available and working on production.

The steps in italics are shown on the deployment board, while "Ready for Deployment" or Done or Canceled is the final state on development boards.

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

...

• 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;
• Done: the work is completed without deployment needed;
• Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete.

The sub-task workflow is exactly the same, except that it pre-fills the Yamaha Team entry from its parent.

Epics focus on Product Owners preparing the workrequirements:

Image RemovedImage Added

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: Secondly, 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,  it make sense to involve a development team.
• In progress: a developer builds & unit tests their own work the development team is working to meet acceptance criteria;Review: a peer reviews any code & functionality;
• Done: the work is completed without deployment neededwith deployments done on underlying items;
• Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete.

...