How to plan releases across teams
Last updated: April 2024
A product manager’s job includes managing product releases and leading cross-functional teams to ensure greatness. But what exactly is a release? Does every team need to have releases — even agile teams? How is a release different from a sprint?
From the customer’s perspective, a release is any new functionality that improves how they interact with the product. From the organization’s perspective, a release (also called a launch) is all the work that must be completed to deliver this new experience by a planned date. Regardless of the development methodology, releases are critical to providing customers with a Complete Product Experience (CPE), in which every customer touchpoint is optimized to deliver the best holistic experience possible.
Create. Ideate. Roadmap. Build. Do it all with Aha! — free for 30 days.
Providing the best new customer experience requires coordinating the participation of multiple groups within an organization. The individuals responsible for planning, communicating, executing, and collaborating on a release are known as the cross-functional product team.
A release is more than a brief development sprint, and a cross-functional team is more than a development team. Although some organizations may release weekly or monthly (on a sprint-like cadence), it is important to remember that a release comprises all the work that goes into a new product experience — including the work of groups such as UX, sales, marketing, support, and operations.
Jump ahead to learn more:
Building the cross-functional release team
When organizing a release, think about all the jobs that need to be done to provide customers with a great new experience — from design and go-to-market activities to sales enablement and support documentation. The cross-functional product team includes representatives from each of these key functions. Members of the cross-functional team own the work of their functional group and ultimately are responsible for the release’s success. These team members should be strong leaders and subject matter experts in their field. They should also have the authority to make decisions for the functions they represent.
These are the departments and roles that participate on a cross-functional team at a standard midsize or large company:
Department or group | Team role or function |
Documentation | Writes and updates technical documentation, such as release notes or support content |
Engineering | Owns the work of development teams, including estimation, sprint planning, and acceptance criteria |
Finance | Represents the financials and resource allocation — will likely not attend every meeting |
Legal | Represents product and company legal interests — will likely not attend every meeting |
Marketing | Communicates product positioning and awareness — may include product marketing, field marketing, and public and analyst relations |
Operations/IT | Assists with deployment of the release features |
Project management | Handles day-to-day advancement of work and unblocks team members (could also be scrum master) |
Product management | Leads the product team in planning, managing, and delivering the new product experience |
QA | Ensures product quality |
Sales | Prepares the sales team to communicate changes in the value proposition or demo flow |
Support | Prepares messaging and training about the release experience in support of customers |
UX | Researches and designs optimal customer interactions with the new product experience |
So who plans and manages the release process? This can vary from company to company based on size and organization. Though large organizations often have designated project managers, release managers, delivery managers, or program managers who own this effort, the product manager will always have an instrumental role and often performs overarching project management tasks as well.
Managing the cross-functional team
Cross-functional product teams work best when they feel invested in the product, have clear goals, are stable for the duration of the release, and meet regularly. Each member of the team is responsible for two-way communication: sharing perspective and bringing important information about the release back to their group. The product manager ensures that team members collaborate, work through dependencies, and meet target dates. Product managers are responsible for the success of the group, so it is incumbent on them to lead the product team with a clear vision and help resolve conflicts.
Harnessing the participation of various stakeholders can be challenging, but the result is organizational support and better products that delight customers. Product managers can motivate their teams by defining the strategy behind their plans, collecting feedback, and communicating broadly and frequently.
Related:
Managing the release
If great products start with a well-defined strategy, then coordination is the crux of a well-managed release. Managing a release means turning product strategy into planned work, then coordinating the work and the team against a timeline. Building an action-oriented and repeatable release management process requires carefully planning the scope and phases of work, identifying risks and dependencies, and setting clear expectations.
A release plan is essential. This helps every member of the team know what they need to do and when. Regardless of development methodology, a release plan provides a concise way to manage work, while addressing the inevitable risks of bringing a product to market. Product managers can harness their team's input to develop a release plan that all members can commit to.
Planning a release starts with the end goal and launch date in mind. Teams that do effective planning are more likely to meet their release dates and deliver valuable experiences to customers. An effective release plan takes into account:
The product’s strategic goals and roadmap
Which features will deliver a delightful new customer experience
Feature scope, estimates, and engineering capacity
Estimates on deliverables from marketing, sales, and other groups
The ideal sequence of phases between work
Milestones (fixed dates) that influence the release
Dependencies between the phases or groups
It is critical to have a single source of truth where the team can track all the work in the release plan — both technical and non-technical. A single, shared platform keeps everyone in sync, provides visibility into the release status, holds the product team members accountable for their commitments, and makes it easier for the product manager to coordinate and track the work.
Whether planning release dates based on a regular cadence (e.g. monthly or quarterly) or based on time estimates for the work to be completed, it is necessary to communicate these dates both internally and externally. A release roadmap helps keep all the stakeholders informed of the plan and its progress. It gives the cross-functional team a guide for what needs to be discussed in weekly communications.
A release roadmap can also help the team track important dependencies and milestones. For example, the team will need to know that if it takes a few days longer than estimated to complete the UX research, the development phase will slip by a few days too. Or maybe marketing will need to have its product messaging ready a week before the launch so it can be used during the scheduled day of sales training. For complex releases to succeed, it is crucial to make these dependencies and milestones visible so that the team can coordinate.
Creating a repeatable process
As product managers gain experience launching products that impact large groups of customers and a dynamic organization, you will develop a set of best practices for a successful release. A template or checklist that standardizes the release process builds trust on the cross-functional team and helps create happy customers. A template can also set expectations and facilitate communication with external stakeholders — who may not be active with the core product team but whose support is essential.
If your team wants a simple and repeatable way to coordinate dates and visualize release plans, you can also use an expert-crafted template like the release roadmap template in Aha! software. This Gantt-style template is useful for showing the "what" and "when" of your plans — including features, milestones, dependencies, and your timeline for delivery. This helps everyone on the team understand exactly what needs to be done and when in order to launch on schedule.
A successful release can make all the difference between happy customers and disgruntled ones. Managing a successful release requires skillful coordination of dates, tasks, and people. Effective product managers build releases and lead their cross-functional product teams to move the work forward as planned and collaborate to deliver customer value.
