A SAFe Release

For a secure release, the most important aspect is the preparation done beforehand. Let`s explore together.

Releasing in a SAFe environment requires coordination, collaboration, and transparency. With numerous stakeholders involved, this presents a significant challenge.

Here are some methods to ensure your releases are secure in any working environment, particularly if you are not utilizing CI/CD.

To enhance something, begin by identifying your issues, determining where mistakes are being made, and then strive for a 1% (or greater) improvement.

Before the release

Release Documentation - create a summary of your release process, especially if it's initiated by different individuals on a rotating basis.

If you encounter errors during the release, include a Lessons Learned section in your Documentation to help others save time when the issue recurs or to address it proactively.

A few days before the release, gather or request any relevant information during the daily Scrum-of-Scrum (15 minutes).

Ensure everyone is aware and prepared to assist if needed.

Conduct a brief pre-release session to identify any outstanding technical issues or potential obstacles.

During the release

Hold a Firefighting Chat on your release day and include your key stakeholders to assist in identifying the safest and quickest solutions to any obstacles.

After release

Record any insights or improvements for future releases.

Here are a few practical suggestions to help you make initial progress.

Keep in mind that in a complex environment with multiple teams releasing in a coordinated manner, collaboration and transparency are crucial.

Connection - bring together key individuals from each team through meetings, chats, or other tools.

Collaboration - team members should know each other and feel comfortable reaching out at any time.

Use collaboration workshops or retrospectives to learn about each other, their work, process and challenges.

Transparency - use your tools to create transparency across all teams in an effective way, ensuring everyone can see what is included in the release, along with some technical details behind the items.

Dashboards, release boards, documentation wiki in your tool

Good luck and keep it SAFe!