Managing Workstreams as Individual Projects - Feedback Requested
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 07:50 AM
We have recently implemented SPM in my organization to replace a sharepoint and excel tool solution. The improvements in productivity and communication on portfolio status and financials has been a massive improvement. Our business team inputs demands as capability ideas - ideally those are converted to projects when the demand is ready to be worked as a project. One trend folks have stated is when they receive the demand, if it impacts multiple IT teams instead of collaborating in a single project, they want to spawn off multiple demands - hence projects to ensure that other folks have "tickets" to manage their work. Otherwise they feel the work gets lost. If feels like they are resorting to this to only worry about their work and let others worry about their and the timeline - this will likely lead to poor reporting to the business team and a misalignment on dates. The true need here is to ensure that when there are multiple development teams needed to complete a project, that they have line of sight into the project. How have you all solved for this? I have proposed tagging as a potential solution - tag the projects that you as a manager are not point on to deliver but have deliverables so that you can easily tag and query for the tag and see the projects that you don't manage but your team is working on. Anyone else solved for this? Looking for all ideas, thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2024 02:32 AM
Hi Mer, might be worth looking at sub-projects functionality. You can have a main project which got created from a demand being converted and then additional projects which can be added as sub projects to the main project. This should provide that overview of the entire work and how projects are being progressed (dates, dependencies, etc.)
Alternatively, if the teams are looking for "tickets" type to manage work, I guess if the project is not complex to justify having sub-projects, maybe explore using the Project Tasks and the Assignment group and Assgigned to fields, to designate the team and responsible owner for the said task.
Hope this will help as starting point 🙂
