Implementation of SPM Question

Damian Martinez
Mega Sage

Hello Community,

I have been given a road map with sprints for the implementation of SPM.

In sprint 1 I have the core configuration, in sprint 2 I have portfolio and Program Management.
In sprint 3 Demand Management, sprint 4 Project Management and sprint 5 Resource Management.
My question do I have to follow this order or can I start setting up for example Project Management first?
Is there any dependencies between them?
We want to start with Project Management and Resource Management but we are not sure if we need to follow the exact order because there are dependencies or we can start with those with no issues.

Thanks!

5 REPLIES 5

Mark Manders
Mega Patron

Yes, there are dependencies, but I know enough companies that only use project management. Or companies just using resource management. You can implement them independently and tie them together once the other module comes around, although the roadmap sounds like a good order if you are going to use it all.

One question though: you 'were given' the roadmap with the sprints. Who gave it to you? If your client is allocating resources based on the provided roadmap, you have project managers ready for testing in sprint 4, while delivering it in sprint 2?  Someone gave you the roadmap, including the sprints, so that someone really is the one to tell you why it has been defined like this. 


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Damian Martinez
Mega Sage

Hello Mark! Thanks for your fast response!

My Manager got this road map directly from ServiceNow but our highest priority is project and resource management.
So I am starting with sprint 1, core configuration then project and resource management.
Sorry I don't understand this question:
If your client is allocating resources based on the provided roadmap, you have project managers ready for testing in sprint 4, while delivering it in sprint 2?
We are the customers, I'm working on the implementation.
Regards.

In that case, your good. My question was more like: if you were a partner implementing it and got the roadmap from your client that already made arrangements, you could run into issues. Since you are the client, you're safe. I missed the info of your role.

 

And indeed: start with what brings the most value and has the highest priority, but don't forget about the rest if you are set out to use it all. You can use project mgt and resource mgt without portfolio and program. Do think about Demand though. Of course you can add it later, but more often than not, it is the source for projects. If that's also the case with your company, you are missing the step to create projects from demands, while you start using projects. But: it's all depending on how you are currently used to working. You can easily create projects without demands and start with that later.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Nil C
Tera Contributor

Hi Damian,

as Mark already pointed out, please follow that guideline. but i have just one additional point to add: most companies start from a demand/ideation, which is in all cases a pre-project and that is probably the domain specific best practice, irrespective of the tool itself (i.e. SN SPM or any other comparable tools). But this might be also based on the current situation of the company in question and their maturity level with the process part, so if they are already doing Project/Portfolio/Program mgmt. and that is why they might have a specific order requested. The requirement and the best practice guideline should dictate the order, so it might be worthwhile to check this requirement with the client before starting the implementation.

 

If my answer helped you in any way, please then mark it as helpful or correct.

Mit freundlichen Grüßen

Nil C

Please let me know if this helps! You can mark this answer as "Correct" if it resolves your issue, and "Helpful" if you find it valuable.

mit freundlichen Grüßen/Thanks and regards,

Nil

Solution Architect
Germany