Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

BigPicture modules explained. A “sequence” of modules matches your workflow

In order to deliver the projects on time, it is necessary to organize and manage the whole project management process in the right way. BigPicture has nine modules plus the Overview “umbrella” module on top of them to support project management in every phase and every aspect. Let’s have a closer look at all 10 modules.
Agile project management has progressively spread, however, most companies don’t use the Classic or Agile approach exclusively. They create or try to create their own blend of Hybrid methodologies. BigPicture with all ten modules is ready for all leading agile, classic, and hybrid management frameworks. The good news is that the same set of ten project portfolio management modules is available both in BigPicture and BigPicture Enterprise. Both apps allow you to enable/disable modules for each initiative (project) separately, so the modules set can be fully adjusted to the actual needs. For instance, for a classic project, you can enable just Scope, Gantt, Resources, Risks, and Calendar modules and hide the rest. At the same time, for an agile project – you could have Roadmap, Board, Teams, and Reports modules turned on, while the others might be off for simplicity. A hybrid project could have a selection, or even all the modules active.
Take a look at figure 1. Can you notice how the Classic Project has a set of modules, unlike the one of the Less Requirement Area?
Figure 1. BigPicture command center (Overview module) lets you step down to the actual nine project management modules. Note how the Classic Project has quite a different set of modules than the Less Requirement Area. Some of the items in the two drop-down menus are merely aliases of the very same modules (Gantt -> Roadmap, WBS -> Backlog, Reports -> Charts). In contrast, other modules are unique for the Classic Project (Workload, Calendar) and for the Less Requirement Area (Sprints, Objectives). The screenshot comes from BigPicture Enterprise.
This is how we got to the advantage BigPicture Enterprise offers: it is out-of-the-box compatible with SAFe, LeSS, hybrid management, etc. BigPicture Enterprise arrives with pre-configured SAFe ARTs, LeSS Requirement Areas, Hybrid Projects, and others. For example, the SAFe ART “template” has ‘Program Board’ and ‘Objectives’ modules, as per Scaled Agile Framework terminology. In addition, you can change modules' names to adjust them to any business need. Very often the Gantt module is renamed to the ‘Roadmap’, or the Roadmap module to the ‘Goals’.

Enable/disable – turn on/off modules

You can enable and disable modules and rename them – see figure 2.
Figure 2. Turn on/off modules in both BigPicture and BigPicture Enterprise. Rename them in BigPicture Enterprise only. The figure exhibits the ‘Template level’ – read below.
Adjusting modules can be done on the template level – for all future clones of Agile project, Classic project, or whatever templates you maintain. We call these templates ‘Box types’, as this is a “time saving” approach. In order to edit templates, you need to be a BigPicture admin. However, you can make changes only on a specific project' level. Then permission of a particular project admin is sufficient (typically, a project manager will have suitable rights).
Which of the two is more productive? BigPicture (not Enterprise) users might prefer to control modules at the ‘specific project’ level. That’s because the regular BigPicture has just three slots for templates, so naturally, there is less room for extensive pre-configuration.
Meanwhile, BigPicture Enterprise, with its unlimited number of templates, makes it easy to extensively pre-configure agile projects, classic projects, hybrid projects, and other templates to facilitate launching real-life initiatives on the fly.
 image - 2022-01-20T111015.926.png

Why modular and not monolithic architecture?

Many project management apps have opted for homogeneity, while BigPicture has its distinctive modular design. How come?
  1. Back when we launched BigPicture, it was already clear that a hybrid, mixed, agile-classic approach would eventually prevail. Some charts, matrices, or reports fit agility better than others – predictive management.
  2. Modular design allows smoothing workflow by freely choosing 3, 5, 7, or whatever number of the 10 BigPicture modules and disabling the rest.
  3. Gantt, Resources, Board, Teams, and Risks modules made the original BigPicture, which was first released on Atlassian Marketplace. Roadmap, Scope, Reports, Overview, and Calendar modules are followed throughout BigPicture 6, 7, and 8.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events