• 0 Vote(s) - 0 Average
  • 5
  • 4
  • 3
  • 2
  • 1
Thread Modes

Change Requests
#1
Hello,

In my company, we need to register requests that are considered as pre-projects. That means that they will be subject of analysis. Depending on various factors (budgets, resources, etc.) they can be aproved or refused. If approved, they will be converted in a project with tasks and resources.

I was thinking in using change requests to this purpose, rather than service requests. If a project is created, then we can associate the change request to the project.

Do you think it's the best solution?

Thank you!
pms23, proud to be a member of EV CONNECT FORUM since Apr 2017.

#2
(12-18-2018, 12:39 PM)pms23 Wrote: Hello,

In my company, we need to register requests that are considered as pre-projects. That means that they will be subject of analysis. Depending on various factors (budgets, resources, etc.) they can be aproved or refused. If approved, they will be converted in a project with tasks and resources.

I was thinking in using change requests to this purpose, rather than service requests. If a project is created, then we can associate the change request to the project.

Do you think it's the best solution?

Thank you!

From a process perspective, I'd stick with a Service Request being the initiator for the Project, rather than the Change Request. I see Service Requests as being the input whereas a Change Request would would be an output. This way, the Service Request shows who is the business driver of the project and the Change Requests show any and all Changes that are made to the infrastructure/architecture as part of a project roll-out.
cmiller, proud to be a member of EV CONNECT FORUM since Oct 2015.

#3
(12-18-2018, 04:31 PM)cmiller Wrote:
(12-18-2018, 12:39 PM)pms23 Wrote: Hello,

In my company, we need to register requests that are considered as pre-projects. That means that they will be subject of analysis. Depending on various factors (budgets, resources, etc.) they can be aproved or refused. If approved, they will be converted in a project with tasks and resources.

I was thinking in using change requests to this purpose, rather than service requests. If a project is created, then we can associate the change request to the project.

Do you think it's the best solution?

Thank you!

From a process perspective, I'd stick with a Service Request being the initiator for the Project, rather than the Change Request. I see Service Requests as being the input whereas a Change Request would would be an output. This way, the Service Request shows who is the business driver of the project and the Change Requests show any and all Changes that are made to the infrastructure/architecture as part of a project roll-out.

Thank you for your feedback!
pms23, proud to be a member of EV CONNECT FORUM since Apr 2017.






Users browsing this thread: 1 Guest(s)