Purely agile projects are rare in real life. What we typically see in Jira are hybrid projects. Hybrid, or mixed project management is partially waterfall (high-level planning), and partially agile (iteration planning). Let’s look closer at how to run hybrid projects in Jira, and why is it beneficial to have a project management app, such as BigPicture on top of Jira?
Why think ‘waterfall’ in the agile world?
You could be surprised that some 89 percent of project managers still use waterfall project management to a certain extent.1 Deadlines dictated by contracts or laws, budgeting – these facts of life call for classic waterfall tools, such as Gantt charts. You’ll typically see this standpoint at the high management level, responsible for long-term planning.
At the bottom of the hierarchy, on the other hand, we have teams that consider waterfall methodologies outdated. Instead, they love to manage their work in an agile manner. Two-week iterations, sprints, scrum – these terms have really become the norm at the team level in the 1st, 2nd and 3rd decades of the 21st century. Unlike high-level managers, modern teams don’t like to focus on dates and the timeline – rather they plan work on program boards or agile boards, or simply: boards.
1 PMI’s Pulse of the Profession 2017®. Project Management Institute, Newtown Square, PA, U.S.A.
Hybrid projects in plain Jira
(with no project management app added on top)
Plain Jira does have – somewhat limited – agile boards2, but it completely omits the waterfall Gantt charts.
The bottom line: it’s hardly feasible to do agile and waterfall – mixed project management in plain Jira Software, let alone Jira Core.
However, Jira + some project management app on top will do the job. When browsing Atlassian Marketplace look for a Jira app that has both the Gantt charts and agile boards (with teams). What’s more, the two tools have to absolutely keep in sync. One such app is BigPicture.
2 boards in Jira Software cover iterations but they don’t support teams and long-range planning, such as SAFe’s Program Increments (four iterations ≈ program increment).
Waterfall + agile, mixed projects in Jira + BigPicture
Now, let’s go step by step through the workflow in a hybrid project:
1. Initiate a project WATERFALL
First, you import tasks from Jira and this happens automatically when you create a program in BigPicture. Obviously, you can import a subset of tasks and not all of them. Later on, BigPicture will keep the imported tasks in sync with Jira.
Alternatively, use the BigPicture’s Scope module to start from scratch and break the project into phases, large tasks, and milestones (see top-down planning in Jira). Instead of the Scope module, you can use the Gantt chart’s left pane, the work breakdown structure, for that. How rough should the planning be at this stage? Say, you are a construction company; building a section of a motorway might constitute a phase of the project.
2. Develop the mid-level of the work breakdown structure WATERFALL
We’re still on the Scope module/Gantt chart. Add the mid-level of tasks. For instance, ‘building of an overpass’ task. You’re still working on dates in this step, say, your task starts on the 1st of March and ends on the 15th of August.
3. Add milestones to the Gantt chart WATERFALL
What is the milestone? Milestones are one-day long tasks that represent crucial dates. Milestones represent things accrued from contracts, such as ‘commissioning a part of the highway’. Why even have milestones on the Gantt chart? Because these ‘unusual’, diamond-shaped tasks attract the attention of everyone from a team member to a project manager, motivating people to respect deadlines.
See you in:
- Glasgow on Atlassian in Scotland by New Verve Consulting, March 18
- Tel Aviv on Methoda Atlassian Day, March 28
- Tallinn on Atlassian in Baltics by Trinidad Wiseman, March 28
- Las Vegas on Atlassian Summit 2019, April 9-11 – more
- The Hague during European SAFe Summit 2019, May 7-10
BigPicture / BigGantt are Jira 8 compatible. More
We’ve moved into a brand new office. Check photos on Facebook
The entirely new Program Board 2.0 is coming soon. It has both program increment- and sprint-level planning. We’ve just begun the tests of BigPicture 7.2. More
4. Now it’s teams’ turn. We’re submerging to the team-level and switching from the Gantt chart to Program board AGILE
and planning iterations in an agile manner. Before that, decide on how long your iterations (sprints) will last. Typically they are of a 2-, 3- or 4-week-long cadence.
Now, during the planning sessions that prepend each sprint/iteration teams add tasks to the upcoming one or two iterations. When doing the agile planning teams, and Product Owners, should consult the Gantt chart and observe those high-level, ‘general’ tasks, as well as milestones, that had been set by the project manager.
5. Align the agile, short-term planning with the high-level, waterfall plan AGILE WATERFALL
Back to the Gantt chart. Enable the cadences on the chart’s timeline:
Menu View > Show > Cadences
Something similar to the below picture should emerge – the waterfall Gantt chart overlaid by the agile iterations represented by those vertical green and violet bars. This is where hybrid project management happens.
Example: PRINCE2 and hybrid projects
PRINCE2 is a classic waterfall methodology, so PRINCE2 projects should utilize Gantt charts to plan work, shouldn’t they? Well, waterfall and agile, mixed projects are applicable here as well. Aren’t there those ‘work packages’ that PRINCE2 project managers pass responsibility for to teams? Why not slice these ‘work packages’ into iterations in an agile manner on a Program board?
Now, let’s see how ‘agile’ meets ‘waterfall’. Consider a couple of scenarios:
- a team failed to deliver a task in the current 2-week iteration and put that task off for the next iteration using their beloved agile Program board. The delay should be noticed by the project manager observing the Gantt chart, as the Program Board keeps in-sync with the Gantt chart. This 2-week delay could hit the whole high-level plan.
- the project manager is doing budgeting. Very typically, teams are hired and paid per iteration, so with iterations evident on the Gantt chart it’s easy to do budget forecasting.
Tip: how do tasks get transferred from the Program board onto the Gantt chart?
When you follow the above five-step tutorial and step 5 in particular, you’ll immediately face a dilemma: the low-level tasks sourced from the Board sometimes don’t look good on the Gantt chart. This is because the tasks don’t really have dates, as long as we look on the Board. In other words, the start and end dates of a task don’t really matter at this stage. Once we get back to the timeline of the Gantt chart, however, and this happens in step 5 discussed above, it may turn out that the bars of those iteration-level tasks look to ‘tiny’ or ‘short’. Or, quite contrary, a bar turns out much longer than an iteration itself. This is why we added the following two options to the Program board configuration in BigPicture:
Program configuration (cog icon) > Board > Task period synchronization > Precise alignment or Smart adjustment
What do they do?
Precise alignment – ‘no matter what’ sort of strategy. Once a task has been attached to an iteration on the Program board, this task aligns with the start and end dates of the iteration. Example: once attached to an Iteration 1, task X ‘takes over’ the iteration’s dates, i.e. now it starts on the first day of the iteration and ends on the last day of the iteration. So now, the task lasts as long as the iteration. This is an appropriate setup for very agile teams, who don’t face deadlines. See more in docs.
Smart adjustment – once a task has been assigned to an iteration, BigPicture tries to keep its original start and end dates – those set in Jira or on the Gantt chart – as much as it can. Sure, the task period has to be trimmed oftentimes, but Smart adjustment strategy will never stretch a one-day errand to align it with a two-week iteration. Rather it will move the tasks on the timeline so that the task is contained within the iteration, but the Smart adjustment will keep the one-day duration of the task. See more examples in docs.
- The ‘Waterfall vs. agile’ dilemma is no longer valid. You can have a single Jira project and utilize both waterfall and agile project management at the same time.
- Many enterprises think project managers need their MS Project and users need Jira. So the organizations keep both applications alive. Yet all they actually need to work both waterfall- and agile-style is Jira with BigPicture ‘extension’. Check the MS Project vs. Jira + BigPicture comparison.