Atlassian Platimum Experts Badge

Before we begin…

Before I join the already crowded fray of folks chiming in on Jira Portfolio, a quick update is due on my last post.
Here Be Dragons: hic sunt dracones
Atlassian has a little series of activities to get people used to administering their suite of apps. It takes you on a whirlwind tour of both the UI and backend. Some of us here are planning to do it just for the exercise (and the free t-shirt, see pic below). I’m starting to get some interest in making this a Geek Night at our Tempe HQ, so I’ll throw it out there, if you want in please ping me by October 15th. If there’s enough interest I’ll see what I can do to make this a bigger event.
atlassian expert

Back to the show

OK, now back to business.

What’s In Your Portfolio?

If you are looking for “more” info on what it is, what it does, or how to use it ping me personally or check out these links:

So if I’m not gonna talk about what it is, what it does, or how to use it, “Why bring it up Kevin?” Exactly! The point I’m trying to make here is that before you launch into a fast and furious “Ooooh shiney, must buy…” moment, please take a breath.
This product is going to elevate Jira to a whole new level at many medium and large businesses and will really help crack deeper into Enterprise. There’s no doubt of the success Jira Portfolio is going to have in further bridging the gap between the business and IT units, so why am I saying “Hold Please.”

Measure Twice, Cut Once

Anyone remember their mom, dad, grandparents, someone else saying this phrase? Well, I think it is time to bring it up.
Implementing Jira Portfolio should be an initiative that brings business and technology partners together. The data created and curated with this plugin is going to allow greater transparency and collaboration. So… take… the… time… to… do… it… right… the first time.
Key Ideas

  1. Ensure that Jira Administrators, IT Leadership, PMO Leadership are all involved. Don’t leave anyone behind, this is a great opportunity!
  2. What you are currently doing is just a starting point. Document what it ‘really’ looks like and then paint a picture of what you want it to be.
  3. Make the easy changes now. In step 2 you’ll probably end up with 3 or 4 things that ‘could’ be better with a lot of effort and even more small things in your PMO that could use a little tweak. Tweak them now, include that in the rollout or it will probably just end up at the bottom of a backlog again.
  4. Make a plan for the hard changes. You have everyone at the table, you’ve agreed to move forward, and how to do so. Use that momentum to drive lasting change and build or reinforce relationships.

People make Atlassian great. Your people can make using Atlassian products great as well!