| Create and Maintain a WBS/Project Plan including all Elements: WBS Levels, Work packages, Activities |
100% |
100% |
100% |
| Allow Users to convert a task to a milestone (Visualised as milestone) and to flag a task as inbound/outbound deliverable |
100% |
100% |
100% |
| Create and maintain a hierarchical relationship in the WBS without Level limitation |
100% |
100% |
0%Limited to 10, according to vendor. 3 levels recommended. |
| Allow a full collaborative work wise for all WBS tasks and for different user access rights (Write / Read) |
100% |
100% |
100% |
| Allow sub-stream related WBS plans and a master view referencing to sub-stream Plans. This setup should be changeable. |
0% |
80%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. |
100% |
| Visualise the Plan in List View with full customisable Columns |
100% |
80%Sorting of several plug-in standard columns cannot be changed. |
100% |
| Visualise the WBS Plan in Gantt View with customisable Date Ranges |
100% |
100% |
100% |
| Editing in Gantt AND List are possible and lead to the same data result |
100% |
100% |
50%Gantt changes don't lead always to the expected data change result. |
| Implementing and Visualizing a Dependency Type: From End to Start |
100% |
100% |
100% |
| Implement and Visualise dependency type: FF, SF, SS |
100% |
100% |
100% |
| Allow multiple dependencies between WBS Plan elements |
100% |
100% |
100% |
| 100% Automatic recalculation of the date due to changes in dependencies |
100% |
100% |
100% |
| Selective automatic date re-calculation based on changes of dependencies |
100%Tasks can be selectively configured to recalculate automatically or manually. Some tasks can be frozen for every normal users i.e. program key milestones. In this case, linked WBS elements cannot force a recalculation/shift on those. |
100% |
0% |
| Selective automatic date Re-calculation based on Day Lags (e.g. FS + xx Days) |
100% |
0% |
0% |
| Lock plan elements / milestones against changing |
100% |
100% |
0% |
| WBS list view allows quick inline editing in, without opening Jira edit forms |
10%Summary is editable. 100% planned in the product roadmap. |
100% |
100% |
| Allow baseline: 1…n |
50% |
50% |
0% |
| GANTT View allows grouping the dates of child elements and showing the aggregated duration, earliest and latest Date |
100% |
100% |
100% |
| Start/end date and duration of subordinate WBS elements should be aggregated bottom-up |
100%Child elements can influence directly start and end dates of upper elements, if upper elements are not locked. If upper elements are locked for recalculation, then changes at child elements will be limited within the range of upper elements. |
100% |
*Calculation implemented by an own implemented Jira script, running every 60 MIN. |
| Changes of start / end dates and duration should be calculated top-down to child WBS elements |
100% |
50%Simple reschedules of parent elements work as expected. |
0% |
| Expand / Reduce Plan List View to different Levels |
100% |
100% |
100% |
| Add Jira Filters to WBS View allowing Sub-Set Views and Editing for Sub-Teams |
100% |
0% |
100% |
| The Plan and all relationships must be technically readable to allow QA Dashboards, Reporting and EVA Calculation |
50%Better as Structure Gantt, but missing inline editing feature and the prompt changes in Jira issue types lead to a slower workflow as WBS Gantt Chart. |
100%Best Performance: After fast initial load, all changes are done in memory until the "Save" button is pressed. |
0%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… |
100% |
100% |
100% |
| Resource Planning: 1..n Resources with different Loads (Planned Efforts vs Duration) |
50%Team assignment is 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. |
25%Only 1:1 assignment. |
30% |
| Bulk shift of several WBS Elements directly in WBS Plan e.g. 3 Months later |
100% |
100% |
0% |
| Bulk Change of Attributes of selected WBS Elements |
–No bar shown |
100% |
0% |
| Bulk Copy of a WBS Sub-Tree |
–No bar shown |
0% |
100% |
| Import MS Project Plans |
100% |
100% |
0% |
.svg)
.svg)
