Heymans.org » dependencies http://heymans.org I'm Bert Heymans, a project manager, moonlighting hobby photographer and an all-round tech adventurer. Mon, 30 Jan 2012 15:55:26 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Assumptions vs. Dependencies http://heymans.org/2009/01/assumptions-vs-dependencies/?utm_source=rss&utm_medium=rss&utm_campaign=assumptions-vs-dependencies http://heymans.org/2009/01/assumptions-vs-dependencies/#comments Wed, 21 Jan 2009 22:21:49 +0000 Bert http://heymans.org/?p=132 Words have the incredible power to set the trend in a business agreement, nothing new there, but at times differences can get subtle. That’s the case with using “assumptions” vs. using “dependencies”, they can mean the same thing but give a different message in the same context.

There will always be things that are unknown in a projects life cycle. Now, when do you use which word?

  • Filling in those particular blanks is critical for the success of the project? Then go for dependencies, reducing ambiguity on showstoppers is always good.
  • Need to make one choice over another to keep the story in the document intelligent, then you’re safe with assumptions.

Make the right choice, you don't have to guess

Assumptions tend to take care of the unknown but dependencies imply someone will need to take responsibility for them.

It’s a choice that keeps coming back in project charters, proposal texts and product case descriptions.

edit: The thing is that those terms get used as topic headlines a lot in standard PM templates, and sometimes when arguments arise it’s a lot easier to point to dependencies than to assumptions.

]]> http://heymans.org/2009/01/assumptions-vs-dependencies/feed/ 9