This article contains a description of the rules and meaning of the elements of Nomtek Standard Workflow.
The states within the workflow refer to general Items, which can take the form of User Stories, Bugs, Improvements, Releases and other.
States within the Specification stage:
- To Specify
- The Item is not yet fully specified. The Product Owner should provide additional specification and move it to the next required state.
- Will See
- The Item is not important now, but the Product Owner does not want to close it yet as it might be helpful in the future.
- To Estimate
- The Product Owner requests an estimation of the Item from the Team.
- The Item is well specified and waits to be prioritized by the Product Owner.
- To Do:
- The Item is prioritized by the Product Owner. Its implementation has not been started yet, so the Product Owner can change its priority at any time.
- An available Team Member takes the first Item from the top of the To Do list and performs the final check whether it meets the Definition of READY. If it does, then he moves it to the In Progress state and starts the work. In other case, the Team Member asks for clarification or asks to resolve the impediments by assigning the Item to the Product Owner.
States within the Implementation stage:
- In Progress:
- The Item meets the Definition of READY and is being worked on by the Team Member.
- Every Team Member has more or less one Item in this state – the amount of concurrent work in progress is minimized.
- After the ‘Implementation’ part of the Definition of DONE is fulfilled, the Item is moved to QA state.
- Quality assurance tasks are in progress – the Delivery Leader approves the quality and Fit for Purpose with help of his team of developers, testers, graphics designers and usability experts.
- After the ‘QA’ part of the Definition of DONE is fulfilled, the Delivery Leader moves the Item to the Acceptance state and assigns it to the Product Owner.
States within the Acceptance stage:
- The Item meets the full Definition of DONE and waits for the acceptance from the Client, usually performed by the Product Owner.
- The Client reviews the Item and can either accept it by moving to the Closed state or reject it for quality reasons by moving back to QA state.
- The Item is finished and accepted by the Client.
- The Item cannot be reopened – a new Item has to be created if needed.
Each Item is always assigned to the next person who has to take action on it. In particular, if a developer’s work is blocked due to some unexpected impediment, the Item should be reassigned to the Product Owner. In some cases the Item may be not assigned to anyone, for example items in the To Do state are waiting for the first available Team Member to take care of them. The Items that wait for the Product Owner’s action in To Specify, Waiting and Will See states also may be unassigned.