Had the founding fathers of Strategic Defense Initiative a.k.a. Star Wars properly defined the scope, this gigantic project wouldn’t have failed at the age of 10. What they saw back then was a massive scope creep. Back to reality: what can you, a project manager do to properly define and manage change of your project’s scope in Jira + BigPicture 7?
First, you need experience ;) Second, you need a tool. A flexible one.
What a Scope management tool for Jira should be able to…
Scope management is all about being able to ‘observe a project from various perspectives’. Think pyramid, think work breakdown structure, think drilling-down high-level tasks/goals, think changing order of rows, and most importantly – select columns accordingly. For instance, when doing short-term management you might want to see assignees, whereas when dealing with deliverables or sprints you might wish to see aggregated story points.
So, to effectively manage scope of a project you simply need an extremely flexible… pivot table. In Jira.
There are a couple of competitors in the ‘scope management in Jira’ game. This is one notable comparison of them and this is another one. Now let’s look closer at the new Scope module in BigPicture 7.
How to manage scope with Jira + BigPicture?
BigPicture 7 features a couple of new modules. ‘Scope’ is one of them.
Over 100,000 tasks?
Plenty of due work on the screenshot, right? How about 100,000+ tasks in a project/portfolio? We’ve estimated that the new Scope module in BigPicture is capable of handling that, or even more, in a single project or program (what’s the difference).
Custom column views in the new Scope module
Each project is different. A two-week ‘prepare for a trade show’ project needs a very different column set than a massive ‘release a new product’ program. Ever-trending fields do exist though, so let’s name just a few: key, story points, risk probability, assignee and reporter.
There are dozens of column headers available in the BigPicture’s Scope module, as seen on the below animation.
Having set up your view, you can decide whether to save that view and/or make it your ‘favourite’. See the beside image.
Aggregate values to see the big picture
‘What have we spent?’, ‘how much time do we need?’, ‘how many story points have we burnt?’ are PMs’ daily questions. You can aggregate columns in the new Scope module to get all the answers.
Besides the standard min, max, sum, avg operators, available are fancy ones, such as Avg_no_parent or Subtask_status_categories_percentage.
Narrow your focus
The big picture is almost always preferable ;) but… you may occasionally need to narrow your search. All three industry-standard search methods are available in BigPicture’s new Scope module:
- Quick Filters
- Text search
- JQL search
Agile sprints and the Scope module
Check Check Scope module Docs for more features.
See you in:
- The Hague during European SAFe Summit 2019, May 7-10
- Warsaw for Deviniti Jira Day, May 29-30 – more
Cloud version and improved Project Portfolio Management (PPM) in BigPicture Enterprise 2019. What’s changing?
The entirely new Program Board 2.0 is coming soon. It has both program increment- and sprint-level planning. Look for BigPicture 7.2 on Atlassian Marketplace. More
BigPicture / BigGantt are Jira 8 compatible. More
Scope vs. Gantt chart
BigPicture users might notice that the new Scope module looks like the left half of our proven Gantt chart module. Not entirely true. Sure, both the Scope module and the Gantt chart module feature Work Breakdown Structure, but that WBS is much more flexible in the former. Let’s look closer at how do the two modules differ…
|Gantt chart||Scope module|
|Typical activities||visualize workflow on the timeline||
* at the time of writing this is an upcoming feature
|Planning horizon||The Gantt chart is more efficient for short-term planning, or operations management.||The Scope module is equally suitable for short-, medium- and long-term planning.|
Scope and Scaled Agile Framework
The new Scope module is totally suitable for those with SAFe® background.
Think ARTs instead of projects.
Think RTEs instead of Project Managers.
Work Breakdown Structure is rarely seen in SAFe®, ‘backlog structure’ and ‘feature sttructure’ are more common.