Deliverable

Exclusive forum for iZenBirdge PMP® clients
salman_2005
Participant
Participant
Posts: 58
Joined: Wed Sep 26, 2018 8:15 pm

Deliverable

Postby salman_2005 Thu Oct 25, 2018 6:45 pm

Hi Manish,
In D&M project work, it says that change control should be applied once the first version of a deliverable has been completed?

What does it mean?

Thank you.
manishpn
Expert
Expert
Posts: 2588
Joined: Sat Jan 04, 2014 3:55 pm

Re: Deliverable

Postby manishpn Thu Oct 25, 2018 6:53 pm

salman_2005 wrote:Hi Manish,
In D&M project work, it says that change control should be applied once the first version of a deliverable has been completed?

What does it mean?
[u]
Lets say you are delivering a website for an ecom company,
there is a deliverable in terms of module for delivering payment interface to the website, the change control should be applied to the first version of the payment interface when its delivered, without the first version of the deliverable how will we apply change control on that deliverable?
change control can be of course applied to the schedule/cost etc while producing the deliverable but not on the deliverable itself
[/u]


Thank you.
Last edited by manishpn on Fri Nov 16, 2018 11:06 am, edited 1 time in total.
Br,
Manish P
PMP, PMI - ACP, SAFe Agilist
http://www.izenbridge.com/blog/7-effect ... ification/
salman_2005
Participant
Participant
Posts: 58
Joined: Wed Sep 26, 2018 8:15 pm

Re: Deliverable

Postby salman_2005 Fri Oct 26, 2018 6:26 pm

Unable to understand. So, after the first version, change control can be applied on the deliverables like scope, schedule etc but not on the deliverable itself as the product deliverable is still in the making? Is it what you are saying?

My thought was that once the first version of the deliverable, let's say payment module's beta version is (or a project artifacts related to payment module) developed, then the change control should apply in order to ensure that the payment module (or any other deliverable) is in line with the requirements and client is satisfied, if not then change request can be raised.

Please correct me.

Thank you.
manishpn
Expert
Expert
Posts: 2588
Joined: Sat Jan 04, 2014 3:55 pm

Re: Deliverable

Postby manishpn Mon Oct 29, 2018 12:28 pm

salman_2005 wrote:Unable to understand. So, after the first version, change control can be applied on the deliverables like scope, schedule etc
schedule is not a deliverable
Deliverable is a tangible product or part of it or a service.
You can apply change control to overall scope, at any time.


but not on the deliverable itself as the product deliverable is still in the making? Is it what you are saying?

My thought was that once the first version of the deliverable, let's say payment module's beta version is (or a project artifacts related to payment module) developed, then the change control should apply in order to ensure that the payment module (or any other deliverable) is in line with the requirements and client is satisfied, if not then change request can be raised.


Please correct me.

Thank you.
Br,
Manish P
PMP, PMI - ACP, SAFe Agilist
http://www.izenbridge.com/blog/7-effect ... ification/

Return to “PMP® Queries and Tips”

Who is online

Users browsing this forum: No registered users and 4 guests