Deliverables and Milestones in Project Management

Рет қаралды 20,657

Күн бұрын

Пікірлер

@nomenetasaili8598 Жыл бұрын

Man in 5 minutes you explained in very clear detial examples the difference in these things that has been bugging me for ages. Thanks

@InfluentialPMO Жыл бұрын

Glad it helped! 👍

@rasheedaogburn123 10 ай бұрын

I am new to the project management world and this was super helpful. Thank you!

@growqueen 2 жыл бұрын

These videos really help me as a new project manager

@InfluentialPMO 2 жыл бұрын

Thank you - I’m really glad that they’re helpful. 😃👍 hope the new role is going well!

@faridyama97 Жыл бұрын

absolutely clear explanation of these concepts. Thank you very much!

@InfluentialPMO Жыл бұрын

Thank you - I'm delighted it helped

@OMERAAZIZ 8 ай бұрын

This is really simple and helpful, many thanks.

@xtalentng Жыл бұрын

Fun and simple explanation

@mikoakbednarczyk3250 2 жыл бұрын

I have just wanted to say that I started warching your videos today and I really adore how much knowledge ars in those, keep up good work pls

@InfluentialPMO 2 жыл бұрын

Thank you so much, it’s really nice to hear such feedback. I hope I can continue to inform and entertain you for many years to come.

@DodaGarcia Жыл бұрын

Glad to have found your channel, really useful! The way I had been intuitively thinking about it is that differently from deliverables, activities and tasks tend to be written prescriptively, so a good litmus test for me has been what would happen if I were to outsource the process of completing that deliverable. So if my project requires an image of a robot and I have in the plan an activity that says "Draw an image of a robot" just because that's the way I might personally go about it, I just created an unnecessary constraint: maybe the vendor would produce the image by using 3D software or photo compositing or AI generation, or maybe I could use a stock image. What my project really cares about is that the image of the robot exists in a way that satisfies the acceptance criteria. Of course this particular problem could be solved by just changing the wording to "Produce an image of a robot", but that's when the definition you mentioned kicks in: processes are a series of steps, so tracking the "process" of producing the image adds a lot more complexity than the binary question of "Does the image of the robot exist in a satisfying state or does it not?" By looking at the robot image as a deliverable, even if it's going to be produced internally with its own phases and tasks, that can be its own (smaller) project without its granularity polluting the main project.