What is a Work Breakdown Structure? – Guest post

Hi readers,

It has been a while since I asked someone to do a  guest post on The Project Corner, but here we go again. I asked my twitter buddy Michael Belfry (@MichaelBelfry) to write a post about the WBS. The WBS, or Work Breakdown Structure, has been mentioned before on the blog in my 5 incorrect way’s to use MS Project series. But I believe it could go with an upgrade and some more information for you, the readers. Continue reading What is a Work Breakdown Structure? – Guest post

Book review: Dynamic Scheduling with MS Project 2010

The Dynamic Scheduling books (2003, 2007 and 2013 also available) are a great way to get to know Microsoft Project and learn some of the key features that help you build a schedule that last the whole project life cycle. As far as I know there isn’t a 2013 version yet.

In my work as a consultant I have seen a lot of people use date related planning, the Dynamic Scheduling method helps define a better way to building a project plan. The book is nicely arranged and has some good best practices from building Work Breakdown Structures (WBS) to Earned Value (EV) calculations.

The book comes with a nice set of Web Added Value (WAV) downloads and will be a great way to learn for Microsoft certification Exam 70-178: Microsoft Project 2010, Managing Projects. Grab your own copy of the book by going to this link.

I would give this book a score of 4 out of 5 stars.

Too much detail in the schedule (flaw 4)

Hi there,

This is the fourth post in my series on incorrect use of Microsoft Project stand alone version. In my last post I talked about the lack of a Work Breakdown Structure, and this post will continue on that path. Please feel free to give your own insight on the subject because it is highly theoretical. Here goes!
Continue reading Too much detail in the schedule (flaw 4)

Lack of structure (Work Breakdown Structure) (flaw 3)

Hi there,

This is the third post in my series on incorrect use of Microsoft Project stand alone version. I hope you can relate to the situations I described so far and I hope you have learned some nice insights on the workings of MS Project. This post will be about structuring your project to an agreeable level. This structure is called a Work Breakdown Structure or WBS for short. Continue reading Lack of structure (Work Breakdown Structure) (flaw 3)

Five incorrect way’s to use Microsoft Project stand alone version

Hi there,

As a consultant you come across a lot of different projects/companies/people. I’ve been doing this for 5+ years and there are some flaws that keep popping up, regardless of the company, project or person.

In this post I would like to announce 5 of these flaws, the next couple of blogs will be dedicated to explaining and subsequently solving the situation.

Here we go:

Flaw 1: Date related planning

Flaw 2: Capacity as activity

Flaw 3:Lack of structure (Work Breakdown Structure)

Flaw 4: To much detail in the schedule

Flaw 5: No way back! Not using the baseline functionality

Edit: 12 November 2013

I got some really great responses on the flaws mentioned above. And some people have suggested new flaws. I will post about these flaws as well and ad the links to this post to give you a complete overview.

Flaw 6: using predecessors in summary tasks

Flaw 7: What’s your status? Forgetting to set a status date

If you are done reading all the articles above here are two suggestions for more:

  • The TPC newsletter: a periodic newsletter with information about PPM and Project (management).
  • The TPC OneDrive: a place with valuable project content such as whitepapers and reports.