Explore  

Aha! Roadmaps | Aha! Develop connection best practices

Your connected Aha! account creates a unified product development environment — but what that actually means in terms of account configuration is up to you. Here are a few best practices:

Click any of the following links to skip ahead:

General

  • Capacity planning: Users in both products can update a record's Estimate. Make sure both products are using the same capacity unit — story points or time.

  • Releases: Releases exist in Aha! Develop, but the majority of Aha! Develop teams would do better to use Aha! Roadmaps releases rather than trying to use releases in both products at once.

Top

Single workspace, single team

If your connected account includes a single Aha! Roadmaps workspace and a single Aha! Develop team, here is how the two should work together:


Aha! Roadmaps

Aha! Develop

Definition

  • Define strategic work and link it to goals and initiatives

  • Assign strategic work to the Aha! Develop team

  • Define technical work (that does not need to be included in a roadmap).

Backlog management

  • Score work items using Aha! scorecards

  • Prioritize work into releases

  • View a list of work assigned to your team from the Needs review backlog.

  • Use the unified backlog to view work in Roadmaps releases.

  • Break features down into requirements as needed.

  • Add or adjust each record's effort estimate.

Work in progress

  • Update Aha! Roadmaps workflow statuses and complete to-dos assigned by Aha! Develop users as necessary.

  • Once work is completed in Aha! Develop, the Aha! Roadmaps workspace status will update as well.

  • Manage development progress in sprints or the workflow board.

  • Update Aha! Develop workflow statuses.

  • Assign to-dos to Aha! Roadmaps users as necessary.

Top

Many workspaces, single team

If your connected account includes many Aha! Roadmaps workspaces and a single Aha! Develop team, here is how the two products should work together:


Aha! Roadmaps

Aha! Develop

Definition

  • Define strategic work in the cross-functional workspaces. Then, you have a choice:

    • Move work to a core workspace, then link it to goals and initiatives.

    • (Enterprise+) Create a work request for the core workspace.

  • Assign strategic work to the Aha! Develop team.

  • Define technical work (that does not need to be included in a roadmap).

Backlog management

  • Score work items using Aha! scorecards

  • Prioritize work into releases

  • Align cross-functional teams on a prioritized list.

  • View a list of work assigned to your team from the Needs review backlog.

  • Use the unified backlog to view work in Roadmaps releases.

  • Break features down into requirements as needed.

  • Add or adjust each record's effort estimate.

Work in progress

  • Update Aha! Roadmaps workflow statuses and complete to-dos assigned by Aha! Develop users as necessary.

  • Once work is completed in Aha! Develop, the Aha! Roadmaps workspace status will update as well.

  • Manage development progress in sprints or the workflow board.

  • Update Aha! Develop workflow statuses.

  • Assign to-dos to Aha! Roadmaps users as necessary.

Top

Single workspace, many teams

If your connected account includes a single Aha! Roadmaps workspace and many Aha! Develop teams, here is how the two products should work together:


Aha! Roadmaps

Aha! Develop

Definition

  • Define strategic work and link it to goals and initiatives.

  • Assign strategic work to the Aha! Develop team.

  • Define technical work (that does not need to be included in a roadmap).

Backlog management

  • Score work items using Aha! scorecards.

  • Prioritize work into releases.

  • View a list of work assigned to your team from the Needs review backlog.

  • Use the unified backlog to view work in Roadmaps releases.

  • Break features down into requirements as needed.

  • Add or adjust each record's effort estimate.

Work in progress

  • Update Aha! Roadmaps workflow statuses and complete to-dos assigned by Aha! Develop users as necessary.

  • Once work is completed in Aha! Develop, the Aha! Roadmaps workspace status will update as well.

  • Manage development progress in sprints or the workflow board.

  • Update Aha! Develop workflow statuses.

  • Assign to-dos to Aha! Roadmaps users as necessary.

Top

Suite overview
Aha! Roadmaps
    Overview
      Knowledge
      Integrations
      Aha! Ideas
      Aha! Whiteboards
      Aha! Develop
      Release notes