Product room (Jira Align labs)

• Prerequisites
• Dashboard
• Business model canvas

The product room is a centralized dashboard for Product Managers to tie investment back to vision, ensure strategic alignment, and track all work in process from one comprehensive view. It provides a better experience for Product Managers throughout Jira Align by making Product a first-class citizen. The product room serves as an information radiator for all facets of your products, including effort distribution, theme effort distribution, effort vs. value, and delivery statistics.

To navigate to the product room:

If you’re using the new navigation:

1. Select Product in the top navigation bar and select the product you want to view information about; the product room displays.
   Note: When on another product page, select Product room (beta) from the list of options on the sidebar to get back to the product room.

If you’re using the old navigation:

1. Select Product from the left Nav menu.
2. Under the Product section, select Product Room (Beta); the product room page displays.

Prerequisites

1. Portfolio must be created in the system.
2. Program must be created and tied to a portfolio.
3. Personas must exist in the system and be tied to a product.
4. Product vision must exist in the system and be tied to a product.
5. PIs and release vehicles must exist in the system.
6. Themes must be created, tied to the PI, and have % allocations per program set up.
7. Epics must be created, tied to themes and the PI, and have an estimate set for the PI.
8. Features must be created and tied to the epics, PIs, products, and product objectives.
9. Stories, with point values, must be created and tied to features.
10. Teams must be created for the program.
11. At least one sprint must be completed with completed story points for at least one team.
12. Team members must be assigned to the completed sprint(s) and have allocations set for the sprint(s).
13. The team burn hours setting must be set to indicate average daily hours a team member works.
14. The teams must have the proper track by setting selected, either:
    1. Track by Hours, for teams that are using tasks under stories and entering hours against them.
    2. Track by Points, for teams that are only using story points and not tracking hours against tasks.
15. An hourly rate must exist. Depending on the portfolio setting for Costing Method, either:
    1. A blended rate, which is entered on the PI.
    2. Cost center rate, which is determined by the cost centers assigned to the team members.

Dashboard

On the toolbar, you can use direct links to go to a feature backlog, product roadmap, and product vision filtered by the selected product, as well as the product details panel.

Investment distribution by persona 

View effort rollup by persona tied to the product and ensure work is being executed against the audience your product is addressing.

Personas associated with the selected product appear here. Unassigned are stories under features associated with the product but without a persona.

• Accepted = Accepted story points from all stories under features associated with a given persona.
• Investment = Percent of the total LOE story points: add up all LOE story points associated with the product and its children, take the LOE story points associated with the particular persona, and then divide to get the LOE invested in each persona. Stories do not have to be accepted when calculating this investment.

Product objectives

Link your product back to the vision via product objectives to track progress against a unified product strategy.

You need to tie a vision to a product for the Product Objectives cards to appear. The Product Objectives cards come from the Product Vision page.

Delivery

Track work in flight across the organization for full transparency into what is being worked on, what is up next, and what might be at risk. Always know where the work is.

• Top Features in the Backlog are the features tied to this product in your backlog. You can view their state, name, and product objectives tied to them. This shows you exactly what you would see in the backlog taking into account your portfolio/program/program increment/release vehicle/product selections.
• Features for the Release Vehicle are the features planned to be delivered in ongoing release vehicles. By default, the features are filtered by a release vehicle with the closest end date. You can view their state, name, and product objectives tied to them. Click the gear icon to select a different release vehicle.
• Features for the Program Increment are the features planned to be delivered in ongoing program increments. By default, the features are filtered by a PI with the closest end date. You can view their state, name, and product objectives tied to them. Click the gear icon to select a different PI.
• Stories for Active Sprints are the stories being delivered in ongoing sprints. This shows all stories for all sprints that are currently in progress for the selected product. You can view stories’ state, name, and related team. Click the gear icon to select any other future sprints.

Effort vs. value

Track effort rollup against realized value. Using value engineering, effort can automatically convert to cost and value is defined by key metrics. The basic goal of value engineering is to improve efficiency and decrease operating costs through analysis.

The Value Engineering Only view shows effort rollup from work items measuring value.

• Effort = Accepted story points from all stories under features converted to cost.
• Value = Rollup of cumulative value in dollars from value engineering on the underlying features (Value Engineering set up on the feature’s Value tab).

The Cumulative view renders a full burnup across all points tied to this product. It shows an effort point burnup against a value point burnup.

Theme effort distribution

Ensure your product aligns with the strategic themes of your organization and align your localized vision and product strategy with the priorities of the Enterprise.

This pie chart shows the percentage of efforts invested in each theme. The effort is counted by the number of features associated with the product. The Unassigned section includes the features that are not associated with any theme.

Effort distribution 

Track real-time investment by release vehicle across personas or product objectives and quickly identify where efforts are focusing against your product vision.

This table shows the percentage of points associated with a given product objective or persona out of total assigned points. You can toggle between product objectives and personas.

Product objectives show effort distribution across product objectives.

• Y-axis = Product objectives.
• X-axis = Release vehicles in chronological order by their end date. This shows the latest delivered release vehicle, all release vehicles in progress, and the upcoming release vehicle with features tied to the product.
• Each cell = Percentage of story points across all features in the release vehicle tied to product objectives.

Personas show effort distribution across personas.

• Y-axis = Personas.
• X-axis = Release vehicles in chronological order by their end date. This shows the latest delivered release vehicle, all release vehicles in progress, and the upcoming release vehicle with features tied to the product.
• Each cell = Percentage of story points assigned to the given persona in the given release vehicle.
• Other Personas/Unassigned = Percentage of story points assigned to the given persona in the given release vehicle but not assigned to products.

Business model canvas

Use this page as a strategic management and lean startup template for developing new or documenting existing business models. Create a visual chart with elements describing a product's value proposition, infrastructure, customers, and finances.

See also

Business model canvas

Manage features

Create personas to represent user types

View the big picture with the vision report