Great products are built when strategy and delivery stay in sync. The connection between Aha! Roadmaps and Aha! Develop or Aha! Teamwork brings everyone together in a single account — with no field mapping and no synced copies. Product, project, and development teams each work in the tool built for them, on the same records. The result is full visibility and fewer gaps between what is planned and what gets built. This article will go over the benefits of the connection.
Click any of the following links to skip ahead:
Shared records
Work on one record — not a copy. When a developer updates a requirement in Aha! Develop, it is the same requirement the product manager created in Aha! Roadmaps. Updates made in either product are immediately visible in the other, with no syncing or field mapping required.
Read more about the how each Aha! Roadmaps record type maps to Aha! Develop or Aha! Teamwork.
Unified backlog
Pull work from Aha! Roadmaps directly into your development or project team's backlog. Aha! Develop and Aha! Teamwork team members can pull from Aha! Roadmaps releases and parking lots, while Aha! Roadmaps users can assign work to a team, send records to the prioritized backlog, the workflow board, or any sprint, and display the record's location and backlog rank on customized record cards.
For details on how teams manage and prioritize their backlog together, see unified backlog management.
Unique workflows per team
Keep your team's process without compromising the other's. Even though records are shared, each product maintains its own statuses and workflows on those records, so product, project, and development teams can move through their distinct stages independently.
You can configure custom workflows for each team, and use team status mapping to define how status changes in one product are reflected in the other. See workflows and team status mapping.
Capacity planning
Capacity planning happens in both products — and each team contributes. Product managers set initial estimates in Aha! Roadmaps; delivery teams refine those estimates and log effort as work progresses. If teams plan in sprints, Aha! Develop or Aha! Teamwork can also supply capacity predictions based on historical velocity. Everything flows into the capacity report, giving both sides a shared view of what teams can realistically take on.
For configuration details, see these best practices for cross-functional capacity planning.
Reporting on delivery
Each team gets the reports built for their work. Aha! Roadmaps users can build strategic roadmaps drawing on data from either product, track value delivered across the product development journey, and report on development records using list reports, pivot tables, and charts. Aha! Develop and Aha! Teamwork teams have their own delivery-focused reports — burndowns, velocity, throughput, cycle and lead time, and value delivered — to monitor progress and improve team performance. Reports can be created from either product, on data from both.
Learn about Aha! Roadmaps roadmaps and analytics, reporting in either Aha! Develop or Aha! Teamwork, how to report on data between the products, and an overview of reporting through the connection.
User permissions and cross-product collaboration
Give users access to both products — or limit it. Users can be granted view or edit permissions on workspaces, teams, and records in either Aha! Roadmaps or Aha! Develop and Aha! Teamwork, and can assign to-dos and other records across products. Enterprise+ accounts have additional options for more granular permission control.
See user permissions in the Aha! Develop connection and Enterprise+ functionality.
Customizations
Share custom fields, layouts, and templates across both products. Aha! Develop users can also build and install extensions that modify Aha! Roadmaps data; Aha! Teamwork users have access to any official Aha! extension. Extensions are disabled by default for existing Aha! Roadmaps accounts. Review the security implications before enabling them.
Ready to get started? Use the detailed walkthrough for account configuration steps, or visit best practices once you're up and running.