Milestones are important, and they are a pivotal part of managing projects. Milestones are a way to communicate project progress to your team and boost confidence from your management. In this video, Bob McGannon explores ways to help you make your milestones effective including frequency, placement, naming of your milestones and incorporation into your schedule.
- I have a good friend who does not like tunnels.…Once he enters one, he looks for any markers…or the familiar glow of daylight so he knows…when he'll see the sky once again.…In other words, when in a tunnel,…he's looking for milestones.…Milestones are important, and they're very useful…in projects as well.…Milestones are a way to communicate project progress…to your team and management.…And a good set of milestones will ensure…you're communicating the right message to all your…stakeholders at the right time.…
However, technology projects often have milestones…that aren't understood or timed well.…There are a few things that help make milestones effective.…The first is frequency.…I recommend having a milestone about every six weeks.…If you have milestones too often, you could be putting…unnecessary scheduling pressure on your team.…If you have milestones that are too far apart,…the project can actually lose momentum…and team members lose focus.…
With agile projects, the milestone cycle…should align with your sprints so each sprint completion…
- Identify three characteristics of the ideal To Be process map.
- Summarize the steps to manage organizational change.
- Recognize three details to consider when evaluating a cloud solution.
- Recall the consequence of failing to address functionality gaps in a technical solution.
- Determine which facts to collect before discussing resource availability with sponsors.
- Identify the questions to ask when asking team members for feedback on milestone development.