Anyone who has tried to scale Scrum, with DevOps practices embedded probably knows that communication across the Scrum Teams and within the Scrum Teams is key. If you've ever used Nexus, which I highly recommend, then you already know that there are visualizations of the work which are highly effective such as the Cross Team Refinement Board. One way for the Scrum Teams to further increase their effectiveness in building working Increments of software early and often within the Sprint is to pre-agree when there will be a release to the production environment, or a release candidate cut. You have many choices as self-managed teams, and teams in a Nexus.
Don Brown mentions the use of a "Release Train" approach for cutting releases on fixed intervals throughout the day. If you have a Nexus Integration Team (NIT) you have the option of releasing at will, not necessarily at fixed intervals within a day, or a Sprint, and taking a continuous improvement approach to your DORA metric performance, your Nexus may aspire to gradually and intentionally shorting the time between releases, inspecting and adapting as you go, across several Sprints.
If that's the case, then drawing vertical lines with specific date/time indicated down your Cross Team Refinement Board and/or vertical lines inside the "Done" column of your Nexus Sprint Backlog for all stakeholders and Scrum Team members enables them to be aware of and discuss the implications in Nexus Daily Scrums, Daily Scrums and any other occasions. Signaling actions in advance prevents surprises, good and bad. Let's optimize for the whole, building trust for everyone.
Leave a Reply.