Traditionally project managers have worked with a silo MS project plan, mapping their dependencies and detailed resource allocation in a single file.
This is used as a basis to run conference calls and status updates against the plan. The work breakdown structure (WBS) reflects the work needed to build or create deliverables, solution components, outputs, etc.
Our approach provides superior control because planing in Jira allows deliverables and milestones to be more directly manged in plans. Work is simply a lower level function of what is needed to get the deliverables complete.
We have all aspects of the project management process covered, fully aligned with PMI. Even better, as work is executed at the project level, it seamlessly rolls up to the portfolio level.
At the heart of project management is typically a WBS and project plan. Jira is often thought to be an Agile specific tool, SDLC, bug tracking or even just service desk related. That’s not the case. we’re rolling out Jira as a PPM to a very large telco who will be using it to both plan tactical projects and manage their multi-billion dollar portfolio.
Below we have an example plan in Jira which shows a flexible WBS (indent/outdent at ease), as tasks are actually completed and time is logged, the plan is automatically updated. MS Project plans can easily be imported. Resource management and allocation is fully integrated. Status lights can be linked to dynamically changing criteria for enhanced control. This all means greater effectiveness for the PM and an ability to cover more ground, more quickly. Potentially an end to long winded conference calls, rather a focus on where the smoke and the fire is.
In most organizations risk and financial control via strict gate management is a key element to managing projects and portfolios. We have a pre-designed gate management function with the ability for flexible configuration to meet your needs. Dashboard reporting, integration with project planning and roll up to the portfolio level all included.
For too long RAID logs have lived in spreadsheets, hidden in Sharepoint folders. We all know that this means that only the most important items are elevated to status reports. In our solution risks, issues , actions and Decisions are all available to all and are able to rolled up instantly so that management can spot any major risks and decision bottle necks across the enterprise.
In the example below we have the risk entity mapped out including composite risk index (automatically created). In an even better scenario the PM can assign risks and issues to individuals to create accountability for mitigation and management. RAID log items will also automatically form part of status reporting without the need to incorporate them manually.
Real time status reporting and benefits
By creating dashboard gadgets which reflect the status of deliverables and other items such as risks, the concept of a weekly report becomes less important. Context can still be provided by PMs of course – yet all the items under management are rolling up automatically into reports and other filtered views. This saves considerable administrative time.
Below is an example of a project status report – and you can also see that all elements such as this under management have associated workflows. This provides added governance in that all status reports can be tracked where management has accepted status.