Back in June we introduced versioning which enabled our customers to easily document the evolution of their tracking plan. Our latest feature is similarly inspired by software development best practice.
Branching in Iteratively works just like branching in your version control system. The feature lets you and your teams work on tracking plan changes in parallel and in isolation until they're ready to merge back into the main tracking plan (just like in Git).
If you’re not familiar with branching, the best way to understand how it works is to visualize it. You’re essentially creating a copy of your main tracking plan that you can make changes to, without impacting your tracking plan in production. A branch is like a point-in-time snapshot of your tracking plan. You can make your own changes to it without those changes being immediately visible to everyone else, and only merge them back into the main tracking plan when they're ready (and approved by others, depending on your workflow).
When you’re just getting started with Iteratively or if you have a small team, working in branches might not be needed (leveraging our versioning feature will suffice). But as soon as multiple teams need to make and test changes to a tracking plan at the same time, making sure they can do this without running into each other can become a challenge. Rather than trying to coordinate these parallel efforts, each team can create their own isolated working area.
Branches also become useful as you mature your tracking plan definition process with formal reviews and approvals. As changes to your tracking plan typically impact the broader business, getting feedback becomes important. You solicit reviews by creating a Merge Request and depending on your settings (the required number of approvers, for example) you’ll only be able to merge into main once additional stakeholders approve your changes. Be sure to describe the changes you’re proposing and why and @mention any specific reviewers or approvers you'd like to take a look.
Branching is live in the Iteratively UI and you can get started today. Check out our documentation for more details on working with branches and typical workflows. And if you have any questions about how this will work for your team, join our Slack community or reach out directly here.
As always, we’d love to hear your feedback and any ideas that would improve how you use Iteratively. You can send us feedback in-product or by getting in touch directly.