How to keep the Stakeholders informed about the Project Deliverables: The Secret of the Milestones

In this podcast, Ricardo gives tips on how to create your WBS to better communicate key project deliverables to the project stakeholders.

Download (3 MB)

Episode transcript

The transcript is generated automatically by Podscribe, Sonix, Otter and other electronic transcription services.

Hello everybody welcome to the, for five minutes BM Podcast Today. I like to discuss how we can keep informant the core team or the main stakeholders about the Deliverables of our projects. I received this question many times saying, Oh, look, I did the Microsoft project scaffolding with 700 tests, 500 tasks. And how do I report this? Should I print 500 lines and how to explain it's too complex. And I really agree. It's really complex to have this kind of information if you want to display as a communication tool.

So let me explain how do I organize the information related to deadlines in my Project the first thing I decompose my project using the WBS technique into Deliverables it's very, very important. So let's suppose that my project is building a house. I have the roof, I have the walls, I have hydraulical systems. So I create these groups. And for me,

Speaker 1 (1m 1s): Each group, I create

Speaker 0 (1m 3s): At least one milestone. Maybe I create more than one, but for example, a painting concluded roof installed. So I try to put this remembering that all the Milestones have zero duration. And then what I do let's suppose that you are using Microsoft process to do that. So immediately when you put the duration, zero, Microsoft project will recognize that it's a milestone. So Microsoft has a lot of custom fields called flags.

Flags is a yes or no field. So I use some of this fields based on the group of Stakeholders. For example, I put Project board in one PFLAG. The second one, I can create a second column suppliers or a specific supplier core team organization in general, for example, to communicate to the remaining part of the organization. And for every single milestone I put the yes or no. If I put the Yasmin's, I want that, that milestone be display it in a communication.

When I talk about the deadlines. No it's because that Milestones is not relevant for that group of stakeholders. So for example, when I have a Project of a thousand tasks, for example, usually I have 50, 60 Milestones to control the Project and then I say, Oh, look for that kind of supplier. I should use 10 Milestones for that. Or the one is more relevant deal or a 10. So I put these yes or no. So it's very simple. I just filter and I put the milestone with the baseline date and the forecast.

So with that, it's very, very simple and easy for me to track on that topic. What is going on on the project and keep better inform it, my stakeholder and not, I think I do when I want just like explore on will not cover her on this podcast. I am planning to record out her podcast to talk about it. Its the MTA or Milestones trend analysis. It's a chart like a triangle. Where do you track your Milestones overtime? It's a very, very good tool. I use it all the time and it's very good because in a visual format you can track and understand better.

What is about your project, if it's go and find or not. But all the reason I do that, its to make sure that I am compiling on the right information to the right people and to do that, there is nothing better than the Milestones. There is nothing better. For example, even if you are using critical chain, for example, you show the buffer it and some critical Milestones in the middle. So it's very powerful and simple too, to keep your Stakeholders informative. I hope you like this tip or this advice and to see you next week with another five minutes BM Podcast.

Menu

Resources & Insights

Products & Services

More Resources & Insights

Ricardo Vargas

Podcasts

How to keep the Stakeholders informed about the Project Deliverables: The Secret of the Milestones

Search in Podcasts

Latest podcast episodes

Book recommendations