The Use Case For Using Jira or NOT on a Multiple Project Program with Shared IT Resources......
As a Program / Project Manager I need to manage 10 projects in parallel with :
- Shared IT Resources - SA, BA, Devs and Testers
- Telephony Vendor implementing a new Telephony system
- A digital Agency Vendor developing the website - Who use Asana and refuse to integrate/sync to Jira
- Payments Vendor developing the Payments Solution for the Website (already using their own Jira)
- Another software Vendor to make changes to that cloud app
- Only some of the projects are appropriate for Scrum or Kanban - the others need to be managed in a much more waterfall fashion
- All of the vendors need tasks from the Shared IT Resources
- Some projects are mandatory / MVP - whereas others can slip till after launch
- All external vendors need the Shared IT Resources to action stories/tasks for them
I have found in the past that Jira and the use of Sprints are very BAD at managing shared resourcing i.e. only work well when you have full time resources dedicated to the one project. However other tools like Monday.com and Asana seem equally bad at this....
Does anyone have any recommendations on how to set this up so each of the 10 projects can be planned and managed separately BUT the Shared IT Resources can be shared and NOT overcommitted across the 10 projects i.e. have resource availability / levelling / sharing /overallocation clearly visible ?