Project Management

Please login or join to subscribe to this thread

In a schedule, do you group project milestones at the end?

linkedin twitter facebook  
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain
Or do you prefer to embed them across the schedule? Discuss pros and cons of both approaches.
Sort By:
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
It's purely a matter of stylistic choice, in my opinion. I use Microsoft Project, and I embed milestones across my schedule. I can then filter the view to display only the milestones; this has the same effect as grouping milestones together at the end of the schedule.
If I used a spreadsheet to track my schedule I'd still embed the milestones within the schedule, but I'd also group them together on another worksheet for easy reference.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
I fully agree with Eric. More or Less, I do the same.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Eduard -

Milestones are supposed to be the culmination of multiple activities resulting in a significant accomplishment. As such, I prefer to have them at regular intervals over the life of my project to help keep team members motivated, drive client payments and so on. From an organization perspective, I prefer to keep them with the tasks that lead up to them so they would be embedded across the schedule.

Kiron
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Eduard,
When I put together a schedule, I'll place the milestone at the end of the related tasks. This way the schedule tells a story of progression through the cycle. Additionally, if need be I can sort by milestones, and of course, highlight them on my timeline.
avatar
Deepa Kalangi Manager, Program Management, Author, Trainer| CVS Health Charlotte, NC, United States
Mine is similar too, spread milestones across the plan as pertinent. But I have seen some PM's do them in the beginning, especially on a large project plan that is complex, they need them in the beginning to see every single morning. I have used those plans while executing as well.
avatar
Deepesh Rammoorthy ICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood Service Tarneit, Vic, Australia
Just like others have indicated, I find it easy to build a project schedule using MS Project and then specify key tasks as milestones as I go along. Helps with Management reporting and keep track of project timelines.
One advantage I have seen is , it helps me quickly understand resource dependencies and constraints and provides some direction on whether I should crash or fast track some activities to achieve or bring forward a particular milestone date. Having the milestone dates embedded as I go along also helps me do Rolling Wave Planning more effectively than if I had the milestone dates at the end.
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
I've done both, Eduard. It usually depends on my reporting needs. I really don't think of pros and cons with either approach.

Please login or join to reply

Content ID:
ADVERTISEMENTS

What's so great about a mom and pop store? Let me tell you something, if my mom and pop ran a store I wouldn't shop there.

- George Costanza

ADVERTISEMENT

Sponsors