8

Here's one source: https://project-management-knowledge.com/definitions/e/external-dependency/ Simply research "external dependencies in project scheduling." Your schedule will simply be incomplete if you do not have identified in your schedule the dependencies upon which your schedule is based. Your best argument is the word, "dependency.&...


5

You're not communicating well with your client ...and possibly also using your schedule incorrectly. You're asking about milestones as though they were a pure schedule artifact. However, every example from your question and from your follow-on comments shows that "milestones" are something that your client provides. That is undesirable for at least ...


5

Think "Communications," Not Collections The nature of your budgetary obligations is obviously dependent on the definition of the Project Manager role within your particular organization. However, in my experience "chasing money" isn't the proper role of a project management professional. For example, you are probably not an enforcer working for a loan-...


4

Milestones don't directly affect resource allocation. They are just another element in your schedule (tasks, summary tasks, and milestones). Milestones are scheduled the same way tasks are except they have no duration. It is likely that the milestone you are referring to was being used as an anchor to prevent an overlap of resources. As an anchor, I mean ...


3

Two things you haven't mentioned that will have a bearing on this: What kind of project? What is the purpose of the document you are sharing with the client? The fact that you have mentioned advanced payment suggests you are defining some form of contract. If it's a software development project then many customers may prefer to avoid phase-based milestones ...


3

Milestones: Terminal Nodes of Major Project Activities Think of milestones as major markers along your path to project completion. Much like mile markers along the side of the road, a project milestone tells you where you are in your overall project journey. It may be easiest to think of a milestone as a measure of progress or important inflection point ...


3

CodeGnome provided an outstanding answer. To add to it slightly: I have observed in my experience that backwards planning is done nearly exclusively. Deadlines are typically driven by some business or legal need; thus, the project has no alternative but to work backwards from there. The problem with this method is that the resulting plan may have no basis ...


3

Mikado Method On a technical basis, this sort of "reverse planning" can be done using the Mikado Method. The best in-depth treatment of this method can be found in The Mikado Method, Ellnestam and Brolund, 2014. While not optimized for project management, parts of the method (e.g. visualizing the dependency tree) may be useful in scoping a project, ...


3

The PM is accountable for all aspects of the project, including satisfaction of money owed to all vendors, including his/her own organization. So, the involvement needs to be consistent with accountability. Delegate tasks as you see fit, but accountability for task completion and success is not transferable. EDIT: If you are a seller of services, you ...


3

Although I am not familiar with Project Libre, my reading of that article is that the author refers to "Driving Milestones" to mean externally imposed milestones- the things that drive the project. Personally I don't see any practical difference between what he calls "Driving Milestones" and "Buoys", where Buoys are the "marker" milestones that surface from ...


2

We faced the similar need. The solution was: Jira for each project detailed tracking (releases, sprints, stories, tasks, bugs etc) Gannt chart for high level cross project tracking (features, releases) The idea is that Gannt chart does not contain more than 10-12 entries per project. It's very high level and is not synced with Jira tasks, but updated ...


2

Having been a Kerzner Award winner and Project Manager for over 20 years I have some experience in this area. There are other issues that you have not listed here that need to be considered: Is work at the corporate offices and/or vendor locations weighted? In other words, does a vendor have critical path work while another office does not? How will you ...


2

Why do you need to share the milestones with the client? You could keep the milestones for yourself and present whatever plan you have to the client without them.


2

My technique to tackle this is fairly straight forward. I add an agenda item "Meeting summary and actions" When meeting summary is talked about, I also type up a few bullet points and actions and send it out before closing the meeting. Once meeting finishes, usually another meeting starts or get pulled into tasks. So doing this during the meeting could be ...


1

The major project Milestones should reflect what is documented in the Contract. Do not even start work without an executed Contract. Look for Contract items like: When does your client want to kick off? Does your Contract specify 10% payment up front Are there any client reviews, meetings, progress updates, risks, contingencies, acceptance tests etc ...


1

Of course, you post a question and then you immediately find the answer. I tried some new word combinations and found this that solved my problem: If you have costs by task and resource in your project, here's how to see them by month. Switch to the Task usage view (Utilisaton des Tâches") Right-Click on the timescale, select Timescale As Middle Tier, ...


1

"It is all relative to the project size" is the first sort of unspoken thing to understand-whether a 1-day, 1-month, or 1-year project. But, one basic way, no matter which tool or process you are using, is to force rank every task that needs to be completed under a milestone. If there are sub-tasks, then force rank them too under their respective tasks. ...


1

TL;DR There's nothing wrong with building in inspect-and-adapt phase gates into a project management process, even a traditional waterfall model. In fact, it's a very sensible approach to ensure that you have completed a work package (or set of packages) before moving onto the next phase of the project. Make Phase-Gating Activities Explicit Personally, I ...


1

The problem looks to be that you are scheduling the very first task from "today"... If you link them nose-to-tail the entire project will schedule from "today" and the milestone must move to accommodate that. If you set the start date of the first task sufficiently far in the past that there is enough time to fit all the first tasks in before the milestone ...


Only top voted, non community-wiki answers of a minimum length are eligible