Home > Categories > Project Portfolio Management > Atlassian Embraces Continually Changing Plans With Portfolio for Jira Server and Data Center 3.0

Software Category

Project Portfolio Management

Write Review

Atlassian Embraces Continually Changing Plans With Portfolio for Jira Server and Data Center 3.0

Portfolio for Jira Server and Data Center 3.0 (called “Portfolio 3.0”) provides improved capabilities enabling easier modification, communication, and collaboration on team roadmaps.

Atlassian accomplishes this via three key changes:

  • Greater visualization of plans
  • Set a plan that reflects organizational reality
  • Ability to respond to change quickly and effectively

According to Atlassian, Portfolio 3.0 enables users to better surface and understand cross-project and cross-team dependencies through a clearer visualization at any level of hierarchy (from initiative down to user story).

Additionally, changes to your plan can quickly be evaluated through leveraging of scenarios (or sandboxes according to Atlassian) to see best- and worst-case options. Nothing is committed until it is reviewed and adjustments are completed. As new items get added to the backlog, roadmap plans will be automatically re-generated for evaluation and commitment.

As plans change, new dependencies and issues may emerge. Portfolio 3.0’s new interface surfaces these items quickly and effectively, thereby allowing the team to take action to ensure value is delivered to stakeholders on schedule.

Our Take

Successful delivery is not just a problem for the project manager. Business, IT, and Operations continue to align closer together than ever. This requires all team members to have a shared understanding of requirements, outcomes, and timing of deliverables.

Atlassian enables teams to effectively respond to business changes that impact requirements and scope. Those impacts can be surfaced in an actionable, easy-to-understand way that enables greater collaboration on requirements and improved delivery outcomes.

Source: Atlassian at SoftwareReviews, Accessed September 27, 2019


Want to Know More?

Tools are only valuable when the contributing practices and processes are robust. We suggest the following research:

Build a Better Backlog – A well-built backlog helps facilitate effective product planning and delivery.

Build a Product Roadmap – A roadmap is only effective when it can be communicated to the organization.

Other Recent Research in Project Portfolio Management

Project Portfolio Management

IBM Raises Price on Software Support; Shoves Customers Toward the Cloud

IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.

Project Portfolio Management

The Many Flavors of Application Rationalization

The application portfolio management (APM) tool space can be a confusing one, as many software vendors offer their own take of what APM is. Enterprise architecture, application management and project portfolio management tools offer an APM use case, but these are often quite skewed the primary function of the tool.

Project Portfolio Management

KeyedIn Announces Improved Support for Agile Portfolio Management

KeyedIn released version 7.0 of its flagship product, KeyedIn Projects, featuring support for the transition to an increasingly Agile-focused IT shop. Work is assigned to Agile teams when the individual assignment is impractical.

Project Portfolio Management

Planview and Tasktop Announce Strategic Partnership to Enable Portfolio Management for Agile Organizations

To provide a single pane of glass for the work done across disparate teams, Planview announced a strategic partnership with Tasktop to expand its Agile Scaler offering. Now, organizations can aggregate the work of various teams into a portfolio and assess status and the financial impact to business objectives and analyze dependencies across different teams.