.svg){kind=small}
.svg){kind=small}
Our team of experts have checked various Jira PlugIns with a WBS (Work-Breakdown-Structure) for necessary key functions that are needed. We would like to present the results of this evaluation in this blog post.
Introduction
For our customer transformation program we have the following Jira plug-ins, which allow the creation of a WBS (work breakdown structure or work breakdown structure)with more than 3500 planning work packages (detailed work packages will be refined later) enable, tested in detail.
Big Gantt (as part of Big Picture):
WBS Gantt Chart:
https://marketplace.atlassian.com/apps/1211768/wbs-gantt-chart-for-jira?hosting=cloud&tab=overview
Structure Gantt:
https://marketplace.atlassian.com/apps/1217809/structure-gantt-planning-at-scale?hosting=datacenter&tab=overview
Based on the feedback on more than 30 project managers we identified several key capabilities we need in our customer context. We assigned the coverage grade of every tool to the capability to find out the tool we will use for our whole IT project portfolio: WBS Gantt Chart.
In the next section we show the result of our evaluation (it must be noted that the evaluation was already two years ago and therefore some data is not up to date. We are already working on a more up-to-date evaluation):
Result of the evaluation
Create and Maintain a WBS/Project Plan including all Elements: WBS Levels, Work packages, Activities
Allow Users to convert a task to a milestone (Visualised as milestone) and to flag a task as inbound/outbound deliverable
Create and maintain a hierarchical relationship in the WBS without Level limitation
Allow a full collaborative work wise for all wbs tasks and for different user access rights (Write / Read)
Allow a full collaborative work wise for all wbs tasks and for different user access rights (Write / Read)
Allow sub-stream related WBS plans and a master view referencing to sub-stream Plans. This Setup should be changeable. This setup should be changeable.
Technically possible. The Vendor recommends to edit a wbs task only in one gantt board (sub-stream Board). Therefore the master board should be only for reading and could have several root elements. The provider recommends to edit a wbs task only in a Gantt board (sub-stream board). Therefore, the master board should be read-only and could have multiple root elements.
Visualise the Plan in List View with full customisable Columns
Sorting of several plug-In standard columns cannot be changed
Visualise the WBS Plan in Gantt View with customisable Date Ranges
Editing in Gantt AND List are possible and lead to the same data result.
Gantt changes don’t lead always to the expected data change result.
Implementing and Visualizing a Dependency Type: From End to Start
Implement and Visualise dependency type: FF, SF, SS
Allow multiple dependencies between WBS Plan elements
100% Automatic recalculation of the date due to changes in dependencies.
Selective automatic date re-calculation based on changes of dependencies
Tasks can be selectively configured to recalculate automatically or manually.
Some tasks can be frozen for every normal users i.e. program key mile stones. In this case, linked WBS elements cannot force a recalculation/shift on those.
Selective automatic date Re-calculation based on Day Lags (e.g. FS + xx Days)
Lock plan elements / milestones against changing
WBS list view allows quick inline editing in, without opening jira edit forms
Summary is editable.
100% planned in the product roadmap
Allow baseline: 1…n
GANTT View allows grouping the dates of child elements and showing the aggregated duration, earliest and latest Date
Start/end date and duration of subordinate WBS elements should be aggregated bottom-up
Child Elements can influence directly start and end dates of upper elements, if upper elements are not locked.
If upper elemens are locked for recalculation, then changes at child elements will be limited within the range of upper elements.
Calculation implemented by an own implemented jira script, running every 60 MIN.
Changes of start / end dates und duration should be calculated top-down to child wbs elements
simple reschedules of parent elements work as expected
Expand / Reduce Plan List View to different Levels
Add Jira Filters to WBS View allowing Sub-Set Views and Editing for Sub-Teams
The Plan and all relationsships must be technically readable to allow QA Dashboards, Reporting and EVA Calculation
The Plan and all relationsships must be technically readable to allow QA Dashboards, Reporting and EVA Calculation
Better as structure gantt, but missing inline editing feature and the prompt changes in jira issues types lead to a slower workflow as wbs gantt chart.
Best Performance: After fast initial load, all changes are done in memory until the “Save” button is pressed.
Work with our plan (3500 wbs tasks in 10 levels) was no more reliable. we have stopped working with the structure gantt.
Allow Instruments to “Control” the Progress of WBS/Plan: Status, Grade of Completion, Estimated End Date, Efforts…
Ressource Planning: 1..n Resources with different Loads (Planned Efforts vs Duration)
Team assignment ist possible.
A team consists of x receivers with independent capacity pattern, a team can be assigned a task. Task may have specific skill requirements defined in the team definition.
Only 1:1 assignment
