What's Important at the End of a Sprint?

The end of the sprint involves a demonstration of each story for approval. Once this session is complete, you will know which stories were accepted (approved) and which ones need more development work in a future sprint.

Again, for the change management work, model a similar approach. Schedule a separate Key Stakeholder demonstration within a few days of the end of each sprint to demonstrate the user-facing stories just approved. Attendees should include the change management team, key business, process, and system Subject Matter Experts (SMEs) and decision makers.

These sessions provide an opportunity for these stakeholders to provide feedback and build ownership of the new system. If an “ah ha!” moment occurs during these sessions, don’t get discouraged –it’s progress! If it’s something the system could address, a story can be written and put in the Backlog for a future sprint. If it’s something a process can fix, the process owners can take action. If it is something change management needs to address, include the necessary activities or content in the readiness initiatives. Legal, Compliance, and the business leaders should also be in attendance to help drive any high-level decisions needed.

And finally, remember how change management assessed impact from those same user-facing stories at the beginning of the sprint? (see Part 1 of this blog series). These demonstration sessions at the end of the sprint provide the opportunity to see the stories “live”, and validate, or adjust, the readiness activities generated from those impact assessments.

"Rinse and repeat" these important steps (beginning, middle, and end) sprint by sprint and the change journey will unfold.

(If you missed them, check out Part 1 and Part 2 of this series.)