Portfolio for JIRA Presentation - Elastic Gridsites.elasticgrid.com/.../pdfs/portfolio-for-jira_presentation.pdf · • Pain point: This often means structure and consistency in applications

Empowering enterprise agility / visibility Portfolio for JIRA

VISIBILITY VS AUTONOMY

ATLASSIAN

Agenda

D E M O

PA N E L & N E T W O R K I N G

B R E A K

P O R T F O L I O F O R J I R A 2 . 0

STATE OF SOFTWARE

AgendaAT L A S S I A N

V I S I B I L I T Y V S A U TO N O M Y

D E M O


B R E A K


6 offices worldwide

1,300+ Atlassians

Before we get to the products, I’d like to talk a little about Atlassian’s approach to building great software.

A bit of background - there are currently more than 1,300 Atlassian’s working in offices in Sydney (HQ), San Francisco, Austin, Amsterdam, Manila and Tokyo to develop, support and market their products.

5

We believe behind every great human achievement, there is a team.

Our mission is to unleash the potential in every team.

5

Atlassian believes nearly all great human achievement is the result of teamwork. Even where we celebrate the lone genius, there are usually teams working hard to make great ideas real. Flight, landing on the moon, the eventual cure for cancer - all advances made only possible by people working together.

It’s a belief that inspired their origins. Atlassian makes software for teams, and their mission is a simple one: to unleash the potential in teams. Teams in more than 50k companies turn to Atlassian to improve how they work together and it’s a responsibility they care deeply about.

Customers of all sizes in every industry

Atlassian has grown quite a customer franchise over time. They are 50,000 strong, with customers innovating in every industry, empowering their teams to do incredible things.

5,000Enterprise Companies

Including teams at over

Out of our 50k customer base - 5,000 are teams at Enterprise Companies.

• Roughly 60% of all of our licensed users are Enterprise users • Among those customers, are 78 of Fortune 100 companies who trust Atlassian with their business - including 7 of the top 10 largest banks in the world. These are

massive teams that have been required to scale their business as they’ve grow. • At Atlassian, we consider a customer an Enterprise company when they have more than 1,000 employees

What Atlassian does for teams

DISCUSS

ORGANIZE

COMPLETEWITH YOUR TEAM

Atlassian products help teams organize, discuss, and complete work. They offer the flexibility to support teams at every stage of modern development adoption, encourage collaboration throughout your process, and provide both autonomy for teams and visibility for stakeholders.

Built for teams Using the insights of

50,000 customers, we design products that help teams

work better together

Easy to use & adopt We invest in making products

that are easy to access, easy to use, and immediately put

to work

Versatile & adaptable Our products are designed to be useful in a broad range of

workflows and projects

Integrated & open Our products are designed to work well together, and with critical third-party platforms/

applications

Atlassian’s product portfolio is focused on helping teams organize, discuss, and complete work

Atlassian’s focus is to build software for teams that can easily be used by any kind of team. Every organisation is different and their products are designed to be highly adaptable and extendable to integrate with 3rd applications.

Atlassian for software teams

Plan & track Adopt agile best practices.

Plan projects, manage dependencies and track team

progress.

Build & ship Collaborate on code with inline comments and pull requests. Manage and share your Git and Mercurial repositories.

Automate & deploy Embrace continuous delivery. Automate builds, tests and

releases in a single workflow.

Collaborate & document Keep teams connected with chat. Collaborate on product requirements, roadmaps and

technical documentation.

For software teams in particular Atlassian tools help plan, track, build & ship software faster and smarter.

Atlassian helps software teams with better agile planning & tracking issues. Developers can connect their code changes to issues and deployments. By using our tools together, the development process is becomes fully transparent from Agile story creation through it’s ultimate deployment to production.



D E M O


B R E A K


Teams

Let's continue where we started in the introduction: with teams.

Empowered teams move fast, but at what cost?

AUTONOMY

• Atlassian tools are designed to empower teams.• Teams crave freedom and flexibility to work the way they want• Empowered teams are able to innovate and move fast.

Alignment is challenging for many organizations

• Main point: For large companies, tracking progress across teams is difficult.

• Pain point: Alignment is hard! But critical

Alignment requires insight without stifling innovation

VISIBILITY

• Main point: Key people in the development process need visibility without limiting the autonomy of teams

• Key stakeholders like the dev team lead, management and release managers must be able to see find out what’s going on • A unified view of what the teams are doing and how they're doing it• Contextual traceability from each stage of the process• Centralized information

• Pain point: This often means structure and consistency in applications and process, which limits autonomy and innovation

Autonomy

and

Striking a balance is key to innovate at scale

Visibility

• Main point: You must have a balance of both in order to be successful

• Often times that balance though involves trade-offs• It’s also about removing the trade-off between these two; making them a frictionless and integrated experience

..to solving real, day to day challenges in visibility and coordination across teams

From scaling agile..

The keyword that is often tossed around in this context is " How can we scale agile?" At Atlassian, we believe it is not about scaling agile. Our focus is on solving the day to day challenges teams face in getting visibility and staying coordinated across teams and projects.

TEAM A

Capacity and release planning

When can we deliver?

What dates can I commit to my stakeholders?

How do I avoid bottlenecks?

Roadmap

How do I create a visual roadmap everyone understands?

Challenges start with a single team which plans their sprints, track tasks day to day, Monitor team progress, get releases ready

Relevant challenges: Dependencies- In-Team: “We can’t start build a new search box in the frontend until we’ve build an API for that in the backend”- Other Teams: “We need to integrate with your search service, when will it be ready for us to start integrating and testing internally?”Capacity and release planning- Not everyone can do every type of work, how do I avoid bottlenecks?- I have some planned vacations, and 1 team member got sick, can I actually keep my commitments? - We have this big customer conference coming up, what can we ship until then? - My marketing and sales teams need to know when we can deliver a very important improvement in the product to align their dates, what can i commit to? Roadmap for stakeholders- How do I share with stakeholders what we build, and when? How do I have that available and always up-to-date? How do I present it in a format everyone understands

TEAM C

TEAM B

TEAM A

Visibility and status

What are my teams working on?

What’s the status and progress across these teams?

When can team A start integrating team B’s work?

Dependencies

Are all dependencies on other teams roadmaps and still on track?

Release planning and coordination

How can I align all teams for a joint delivery date?

How do I keep everyone informed if a team’s dates slip?

Visibility- We have 16 developers in this program, what are we actually working on right now? - What’s the status of all the big initiatives we have going on? Does anything require my attention?Dependencies- Across teams: “Team A and C need to integrate the platform changes Team B is making, is this on everyone’s roadmap?”- Constant changes: “Team A planned to integrate the platform changes in March, but Team B isn’t ready yet, what does that mean?”Release planning- The platform changes of Team B need to be shipped together with the frontend integrations done by Team A and Team C - when can we ship/deploy? - How can I see if one teams’ date slips and make sure everyone is up to date? Resourcing decisions- Do all teams have the funding they need to deliver on their goals? - I need to fund this new corporate initiative, from where can I shift resources and what’s the impact?

Visibility and status

What are we actually working on?

What’s the status and progress of all key initiatives?

Which projects need my attention?

Resourcing decisions

How can we fund this new initiative?

Are all teams focused on the right priorities?

Focus and progress towards goals

Are we on track to deliver on our goals?

Visibility and Status- What are we actually working on right now?- What’s the status of all the big initiatives we have going on? Who owns them? Does anything require my attention?Focus and progress towards goals- Are all teams working on the right priorities? - How much are we investing on our strategic focus areas? (Are we doing the right things?)- Are we making progress towards our focus areas for this year? Are we on track to hit these high-level goals? Any roadblocks?Resourcing decisions- Can we fund this new initiative XYZ, from where can we shift resources and what would be the impact?

In practice, to answer these questions today, we see many teams spending countless hours in spreadsheets and other workaround solutions. The problem is: they are not purpose-built for the task. They are not integrated and become outdated as soon as the actual work starts.

Get visibility across all teams and projects

Portfolio for JIRA

So thats why Atlassian is now offering Portfolio for JIRA. A purpose-built solution to get visibility and plan across all teams and projects.

Data-driven planning

Roll-up reporting

Realistically, what can we deliver, and when?“ ”

What are we working on, and how do things progress?“ ”

Portfolio for JIRA allows you to do data-driven reporting, so you can see what you can deliver and when. And roll up-reporting, so you can see what you’re working on and the progress.

Portfolio rolls up the data from multiple teams into one combined view. It provides visibility into the status and progress of your projects.. .. and helps you plan and forecast realistically.

Let’s see how it looks in real life.

One view across multiple teams and projects

Realistic planning andforecasting

Additional hierarchy means project- and program managers are now able organize data from across multiple JIRA projects into one view.

The automatic scheduling provides a realistic forecast for important releases so all stakeholders have full visibility can react in time when things change.

Additional hierarchy means project- and program managers are now able organize data from across multiple JIRA projects into one view.

The automatic scheduling provides a realistic forecast for important releases so all stakeholders have full visibility can react in time when things change.

A realistic forecast can cause temporary shocks and feelings of disillusion

CAUTION

..a word of caution from our legal team

No longer can project managers and directors etc. pick dates out of the air for delivery "targets". Senior stakeholders can work together to figure out how to shuffle priorities. There is no escape from the plan!

- A CURRENT PORTFOLIO USER (ANONYMOUS SURVEY)

“

”

Visibility

Multiple projects, one view

Status and roll-up progress

Data-informed planning

A clear, visual roadmap

What’s the plan? How are we tracking?

Transparent resource planning Themes and resource allocation

Portfolio for JIRA gives you visibility, so you can see the plan and know how you’re tracking

Portfolio for JIRA customers3000+

Rosetta Stone are teaching the world to speak, read, and write with confidence.Portfolio for JIRA helps Rosetta Stone scale their agile practices across the organization.

Rosetta Stone are using Portfolio for JIRA to scale their agile practices.

Klarna are making buying and selling online simple.Portfolio for JIRA helps Klarna combine their long-term planning with their agile practices.

Before using Portfolio for JIRA, planning at Klarna was challenging and very waterfall -- Project Managers were using Microsoft Excel and Google Docs in-conjunction with JIRA Software – so they needed a real-time planning solution to save them from this overload of manual processes.Since introducing Portfolio for JIRA, planning has become much more structured and traceable. Rather than planning and reporting across multiple tools that require constant manual updates, the team now uses JIRA Software with Portfolio for JIRA to easily combine their long-term planning with their agile practices.The biggest benefit Klarna have found with using Portfolio for JIRA is being able to keep business stakeholders and development teams in the loop. Before Portfolio for JIRA, business stakeholders were always asking “What’s the plan? When are we going to finish? Are we going to be on time?" but now with Portfolio for JIRA, the answers are already in the plan and business and technical stakeholders have access to it so they have complete context whenever they need it.



D E M O


B R E A K


REAL-T IME PLANNING, BUILT FOR J IRA

Portfolio 2.0LABS

Seamless integration

In Portfolio for JIRA 2.0, the focus is on seamless integration with JIRA Software.

Every change that happens on the boards and projects you’ve selected in Portfolio, gets automatically reflected in Portfolio for JIRA. Add a story to a sprint? It’ll show up in Portfolio. Change the rank of a story? It’ll update in Portfolio. Change the release date of your version? It’ll be reflected in Portfolio.

Plug and plan Play in a sandboxForecast dynamically

In Portfolio for JIRA 2.0, you can:

Plug and plan: With the new seamless integration experience, you can instantly create a plan from your existing data in JIRA Software and know that it'll always be up to date in real-time.

Play in a sandbox: Have the freedom to play, create what-if scenarios, and only commit to JIRA Software when you're ready. You have complete visibility of all changes made before committing them back to JIRA Software.

Dynamically forecast: Forecast realistic release dates so you know when you can deliver, and then optimize your schedule in real-time.

Load data dynamically from boards, projects

or custom filters

Load data dynamically from boards, projects or custom filters

And get a Portfolio plan (in under a minute!)

Available today for Cloud and Server!

LABS

Portfolio for JIRA 2.0 (dubbed Live Plans) is currently a labs feature available for Cloud and Server.



D E M O


B R E A K


Basic concepts

Before we jump into the demo of Portfolio, let’s quickly talk about the basics of planning so you can understand the fundamental principles of Portfolio


Roll-up reporting



Roll-up reporting

Plan


PeopleResources

ScopeWork

ReleasesTime

Plan

A plan is comprised of work, resources and time - and in a Portfolio world - these map to scope, people and releases.

PeopleResources

ScopeWork

ReleasesTime

PeopleResoures

ScopeWork

ReleasesTime

Initiative Theme

Story

Story

Epic

Epic

Scope is the work to be done - the epics and stories you have in JIRA Software. In Portfolio, you can roll these up to higher level views such as initiatives.

PeopleResoures

ScopeWork

ReleasesTime

Initiative Theme

Story

Story

Epic

Epic

You can also use themes in Portfolio to map your organization-wide focus areas to your teams work.

Themes essentially categorize or label the backlog by strategic focus areas, value streams, or investment categories and are great for stakeholders to see where the organization is spending time vs. what was planned.

PeopleResoures

ScopeWork

ReleasesTime

Initiatives Theme

PeopleResources

ScopeWork

ReleasesTime

Team

Member

In portfolio people map to the teams completing the work. These teams can also be broken down into team members.

PeopleResources

ScopeWork

ReleasesTime

Release

ProjectProject 1

Project 2

Project 3Cross-project

releasecross-project release

Cross-project releases allow grouping releases from multiple JIRA projects and managing them from a single place. They also give you an overview of the individual releases' statuses and allows you to align the release dates in a single step.

Demo

Let’s switch gears and have a look where we find these concepts in the product.

We see that the main navigation is structured into planning, with the triangle of Scope, Teams and Releases, and Reporting. The visual schedule is organised by JIRA projects, and you can define releases (or milestones) along the timeline. If you have hard dates for those milestones, you’ll see them turn red if the current forecast suggests work will take longer.

Planning and scoping releases

From here, Portfolio helps to make data-informed trade-off decisions. If stakeholders are not happy with that, you can quickly try and shuffle priorities.

For example, to get coupon codes into the release, the team could de-prioritize the “Group booking experience” epic and shift that to the next release. This takes the emotion out of these discussions, and brings it down to evaluating different options and deciding for the best approach together rather than setting unrealistic targets.

Committing changes to JIRA

Up until now, we’ve played through different planning options here in Portfolio, but all these changes have not been applied back to the issues in JIRA. This has a couple of advantages: - You can try out different options without distracting your teams- No change notifications are triggered until your plan is actually ready- It is very easy to revert all of these changes

However, once you’re happy with the resulting changes and schedule and want to put these to action, it is easy to commit the changes to JIRA.

We see up at the top a list of “uncommited changes”. You can review in detail what exactly has been changed: 1 new epic is to be created in JIRA, and we see that we’ve changed the release assignment on two other epics. All looks good, so let’s commit those changes. Now, the underlying JIRA issues will get updated.

Team management

Now that we’ve seen how to turn the first of our 3 dials - scope, resources, and time - let’s move on to the second one: Teams.

After discussing with all stakeholders, the there’s an idea that Ryan, from the Android team could possibly help out here.

Let’s look at the Android teams’ schedule. To analyse the impact, we’ll add Ryan to the iOS team temporarily. To do this, we’ll add him as a team member, set his regular weekly hours to 0 (which means normally he doesn’t work for this team), and then we’ll add an exception to that for the period he is helping out. We see that this would work to get the iOS release out in time!

Releases

On to the third dimension of our planning triangle: time. Time is represented by releases and their respective dates.

Let’s go with a dynamic end date since we have the scope fixed for your beta release. Again, when we’re happy with our changes, it is easy to review all pending changes and commit back to JIRA. Releases map to versions in JIRA, so any change like this adapted release date will be committed back to the according version in the iOS JIRA project.

Cross-project releases

The releases we’ve seen so far were for a single project. But what if you need to coordinate a release across multiple projects? How can you easily which project is the current long pole, and if everyone is on track?

This is where cross-project releases come into play.

The new plan looks more solid. Once again, when planning is done we can easily commit all these changes back to the JIRA issues and versions.

Reporting

Lastly, the reporting section brings all relevant data together in one view.

Finally, we’ve got a full view of the program schedule. It can be displayed at different level of detail, sliced and diced, by teams, projects or even down to single team members.

And of course, it can be filtered. For example, in combination with our previously defined themes i could directly take a look which work is being done for “driving engagement”, by which teams, and when.

This takes us to the end of this brief product demo.

Summary

Let’s sum things up

Get visibility across all teams and projects

Portfolio for JIRA

Portfolio for JIRA is designed to provide visibility across all teams and projects. It is purpose-built by Atlassian on top of JIRA. The new live plans feature a seamless integration.

TEAM A

TEAM C

TEAM B

JIRA Software

• Plan sprints • Track tasks day to day • Monitor team progress • Get releases ready

Portfolio for JIRA

Portfolio Plan

Board

• Plan and scope releases • Build and share long-term

roadmap • Track progress on epics,

initiatives • and releases • Forecast completion dates • Coordinate cross-project releases

and dependencies

… …

Individual teams continue to do their work directly in JIRA Software, planning sprints, tracking day to day tasks, monitor team progress and health.

Data from one or multiple projects can now be rolled up into a Portfolio plan. With its automatic scheduling, it helps to - easily plan and scope releases- build and share a long-term roadmap- track aggregated progress and focus on business goals

VisibilityMultiple projects, one view

Status and roll-up progress

Data-informed planning

A clear, visual roadmap

What’s the plan? How are we tracking?

Transparent resource planning Themes and resource allocation

Autonomy

Whilst teams keep their autonomy and can stick to their preferred way of working, Portfolio for JIRA gives you visibility, so you can see the plan and know how you’re tracking.



D E M O


B R E A K


Thank you for attending!

Documents

Portfolio for JIRA Presentation - Elastic Gridsites.elasticgrid.com/.../pdfs/portfolio-for-jira_presentation.pdf · • Pain point: This often means structure and consistency in applications