One of the important parts of tracking project progress is defining milestones. \u00a0These are points during the project where the required tasks and the goals for time meet. \u00a0It only makes sense that the definition of milestones and how they are treated are an important part of project success.<\/p>\n
Although these steps in the definition process are necessary, that does not mean they have to be complex. \u00a0Every project is different, but I have found these guidelines useful. \u00a0In fact, I use them every time we need to craft milestones.<\/p>\n
Defining a deliverable for a milestone is rarely a problem. \u00a0However, I have seen vague descriptions like “complete the application UI” as the total of the objective. \u00a0This\u00a0description is a start, but not truly definable. \u00a0Nor is there a deliverable mentioned. \u00a0We have to be able to say a milestone is complete (or not) without ambiguity. \u00a0This example\u00a0is\u00a0improved by including a UI demo to be delivered as part of the objective.<\/p>\n
This point is often an issue during a project. \u00a0There will be a step that includes securing the site or building a backend database. \u00a0Unfortunately, the implementation does not have a visible result. That is not okay. \u00a0Find a way to craft the deliverable so that the customer can see that progress has been made. \u00a0The progress may be a login screen tied to an ACL or the result of some select statements to show default data in a database. \u00a0When in doubt, modify the milestones, so the “invisible” work is part of visible steps.<\/p>\n
Milestones are more than just getting work done. \u00a0They are also an opportunity to gather customer feedback. \u00a0Use the milestone deliverables as a way to verify the implementation is still on track with the vision and goals of the client. \u00a0This option helps deliver a successful project instead of just delivering a project.<\/p>\n
We have already alluded to milestones being about more than progress. \u00a0They can also be designed to improve the chances of a successful project. \u00a0As mentioned earlier, the first step is to ensure that customer feedback is part of delivering any milestone. \u00a0This goal can be achieved through regular demos and review sessions that coincide with milestone deliverables. \u00a0I find that presenting milestone deliverables in some way is useful for drawing out feedback as well as a sort of test of the deliverables. \u00a0That extra look over the deliverable can be a sanity check well also revealing gaps.<\/p>\n
Scheduling the milestones in a way to reduce risk is recommended. \u00a0When the milestones that have the most risk are tackled early in a project, it allows for the less risky steps to be used to make up time. \u00a0Of course, that is not always possible. \u00a0In most cases, the work on challenging items early in a project is a way to bring up estimation issues and slippage sooner.<\/p>\n
We are not always a part of the project definition. \u00a0Thus, we run into those projects that are ill-defined and yet, we want to be successful. \u00a0In these cases, I find it is best to break the work you control (or are assigned) into milestones. \u00a0Your position in the team may not allow for customer feedback as part of milestone delivery. \u00a0However, you can usually find someone to which the deliverable can be presented. \u00a0Every little bit helps.<\/p>\n
Even the largest projects can be broken down into smaller “sub-projects.” \u00a0This\u00a0step is where milestones come into play. \u00a0Thus, an over-whelming or “impossible” task becomes more manageable. \u00a0Since there are so many ways projects can go wrong we need to use tools like milestones to improve our chances for success wherever possible.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the important parts of tracking project progress is defining milestones. \u00a0These are points during the project where the required tasks and the goals for time meet. \u00a0It only makes sense that the definition of milestones and how they are treated are an important part of project success. Defining Milestones Simplified Although these steps […]<\/p>\n","protected":false},"author":1,"featured_media":293,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[20],"tags":[14,9],"class_list":["post-289","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-building-software","tag-design","tag-projects"],"yoast_head":"\n