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

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.