WMS Workflow
The second of four (1 of 4) Work Management System topics describes the Workflow used to manage Solution Work.
the basic workflow used to manage change and version control for Solutions following the Iterative Transformation Model (ITM).
Managing and Communicating Progress
to migrate
On This Page
Add a header to begin generating the table of contents
| State Name | Description | Solution Features | Solution Stories & Bugs | Portfolio Features | Portfolio Stories | |
|---|---|---|---|---|---|---|
| 1 | Open | The initial state of an Object. Typically, associated with adding a new Object to a Portfolio Backlog or Solution Backlog. | Y | Y | Y | Y |
| 2 | In Analysis | Typically, state in which analysis and design occur. Also, when the primary capture of most requirements, of all types, occurs. | Y | Y | Y | Y |
| 3 | In Review | State for reviewing previously completed analysis and design work. | Y | Y | Y | Y |
| 4 | Ready | State indicating the Object has been properly prepared for a transition to subsequent work. Most often, this refers a transition from Analysis & Design to Build, Test & Deploy in a Solution perspective. It can also mean a transition from Intake & Ideate on to Elaborate in a Portfolio perspective. | Y | Y | Y | Y |
| 5 | To Do | State indicating the Object is prioritized for work. Typically, for Stories this means their selection for work during a Sprint Planning Event. For Features, it means their addition a Portfolio Roadmap or Solution Roadmap. | Y | Y | Y | Y |
| 6 | In Progress | Similar to In Analysis, here the State indicates someone is actively working on an Object, or building its related artifact(s). | Y | Y | Y | Y |
| 7 | Technical Review | Following their production, a review of an Object, or related artifact(s), from an IT, or technical, perspective. | - | Y | - | - |
| 8 | Functional Review | Following their production, a review of an Object, or related artifact(s), from an Business, or functional, perspective. | - | Y | - | Y |
| 9 | Ready for Test | State indicating that Objects or related artifacts produced are available for subsequent testing. | - | Y | - | - |
| 10 | In Testing | State indicating that Build or Certification testing of an Object or its artifact(s) is underway. | Y | Y | - | - |
| 11 | Ready for Sign-Off | State indicating all expected analaysis, design, build, test and other efforts related to the Object, or related artifact(s), is complete. Now, final approval or sign-off is sought. | Y | Y | Y | Y |
| 12 | Move to Prod | State indicating receipt of approval to move a Feature, along with its related Stories, into Production. | Y | - | Y | - |
| 13 | Inactive in Prod | State indicating the Objects related to a Feature, including related artifacts, are now in Production. However, they are not yet avaiable for use. In other words, they are "Toggled Off". | Y | - | - | |
| 14 | Active in Prod | State indicating the Objects related to a Feature, including related artifacts, are now in Production. Additionally, they are now avaiable for use. In other words, they are "Toggled On". | Y | - | Y | - |
| 15 | Done | State indicating that no further work is anticipated on an Object or its related artifact(s). | Y | Y | Y | Y |
| 16 | Closed | The final state of an Object. Typically, this state does not appear on most management boards. Thus, placing something in this state removes it from further management attention. | Y | Y | Y | Y |
Mention use of States for progress rather than Tasks to sequence individual efforts.