The second of eight (8) steps in Story Build identifies changes currently underway.
Story Build - Step 2 of 8: In Progress
What's Before
Prior to this step, in IT4 - Step 1 of 8: To Do, a Story (or Bug) had been selected into a Sprint and added to the Sprint Backlog.
It's now time for the planned change(s) defined by the Story to be made.
What's Happening Now
Step-by-Step
To Gain this State
While in this State
To Attain the Next State
- To progress to this state a Story is selected from the Sprint Backlog by a Business / Functional-, Solution- or Test Analyst to be worked.
- A Story may regress to this state from Technical Review or Functional Review ('Desk Check’) if more work is needed to make it correct and complete.
- A Story may regress to this state from ‘In Testing’ or ‘Ready for Sign Off’ if errors are found which need to be fixed.
- Stories in this state are those undergoing development and/or configuration, typically by the Solution Analyst.
- When and where appropriate, the individual making the changes should also be creating and executing related Unit Testing (UNT).
- In parallel, Stories in this state are also undergoing Functional Testing (FNC) by the Test Analyst.
- As code / configuration is being written, the Functional Test Cases should also be created and executed.
- As more code / configuration is produced, more testing of available functionality should occur.
- Do not wait for all / final functionality to be produced before starting Functional Testing.
- Stories are worked in the DEV1 environment.
- To progress to the next state:
- Development / configuration needs to be complete; and
- Operating Procedures must be created / updated where appropriate;
and - Functional Testing needs to be well underway.
- Functional Testing need not be complete to progress to ‘Code Review’, but will need to be complete prior to ‘Desk Check’.
Parallel Dev / Config and Test Activities
Iterative Changes and Tests
The task flow will actually see the Story through several steps as it progresses through the build task.
Build Progression and Tasks
The figure below shows the beginning of the build progression. This flow will expand over the sections below as additional work is completed on the path towards "Done".
Dev / Config and Functional Testing of a Story
The graphic below introduces Code Sets and Branches. For additional information refer to Version Control and Solution Environments.
Dev / Config and Functional Testing of a Solution
Again, we're depicting Branches and Environments to explain how multiple Stories within a Sprint all funnel to the same location for Functional Testing. For additional information refer to Version Control and Solution Environments.
Participation & Updates to the WMS
Typically the Solution Analyst is the Team member responsible for this step, although, depending upon the change(s) required any member of the Delivery Team could have ownership.
As bandwidth permits, the Delivery Team member taking responsibility will move the Story from the 'To Do' column of the Story Build Board into the 'Work in Progress' column.
What's Next
Once development and/or configuration is complete the Story progresses on to IT4 -Step 3 of 8: Technical Review.