The core content of the TPC blog, Microsoft Project related articles. I started this blog way back in 2014 with a series of articles to spot incorrect use of Microsoft Project. It took storm and I continued to write about the tool that Microsoft created for Project tracking and scheduling. The posts that you will find in this category are all linked to usage of the desktop application. Examples are the Backwards scheduling vs deadlines post and Never delete a task.
But there is much more content, please explore and I hope you find the content that you are looking for. If not, you can always reach out by adding a comment on a post.
This is my last post in my series about incorrect way’s to use Microsoft Project stand alone version. In it I have discussed some of the common flaws people run into when using the Project application. This post will be about the baseline functionality, it is often forgotten or ignored by project managers. I will be talking about why you should want to have a baseline in your project. Again this is a very theoretical subject and you should always check with your company if there are any policies regarding baselining a project. Continue reading Not using the baseline functionality (flaw 5)
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)
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)
This is post number 2 in my series about incorrect use of Microsoft Project stand alone version. I started this series to get the most commonplace examples out in the world and help people understand Microsoft Project a little better. Once again, the images in these posts are build using the Microsoft Project 2013 Pro edition, but this series can be useful for all versions of the product. Continue reading Capacity as Activity (flaw 2)
In my last post I announced 5 flaws that are common in using the stand alone version of Microsoft Project. Today I’m taking a closer look at “date related planning”.
So what is this flaw? Take a close look at this Gantt table, and more specifically the Indicators column (the blue i icon left to task mode):
I started a YouTube channel in 2018. And on the channel I thought I’d add the incorrect ways of using Microsoft Project articles. It’s a new way of sharing the information that’s in this post and I hope you’ll enjoy:
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.
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.