Once a story has been accepted, it’s set to Work in Progress status. The developer will then review the story with the team, in particular the product owner or SCRUM master. After it’s been confirmed that the item has been completed and worked on, the changes tied to it are then made in GitHub. These changes are then moved from the Halo Dev space to the Halo MSP Test (Halo_msp_test) space, then moved to Pending Change status. A relationship is then added in the story for the RFC record connected to the changes. The changes are then pushed to production, followed by one last test for validation. Once confirmed to be working correctly, the story is then marked as having a completed status. After this, the work effort actual time is added from the drop-down menu; this is the amount of time the developer spent working on the story. The amount of time starts with 0.5 (half a day) and increases from there. The story is now done.