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.
Hey there,
Here is the second addition to my series on incorrect use of Microsoft Project stand alone version. It started as a list with 5 most common mistakes people use during there scheduling experiences, however some people have suggested additional flaws, this flaw was also hinted by Swagato Bandyopadhyay, thanks again, and hope you like this post as well. Continue reading What’s your status? Forgetting to set a status date (flaw 7)
Hi there,
In a recent post I mentioned incorrect use, or no use at all of the baseline functionality in Ms Project. In this post I would like to dive deeper into baselines from an application perspective. Continue reading About baselines
Hey People,
Let me start by thanking you for some of the great responses I got on my serries on incorrect way’s to use Microsoft Project stand alone version. Most people agreed on the flaws I noted in the series of blogs, and some had additions to the flaws.
I have picked a number of additional flaws, that I believe need to be discussed. Today I’ll post my thoughts on linking summary tasks. This flaw was suggested by Swagato Bandyopadhyay, thank you, I hope you like what I did with your suggestion. Continue reading Using predecessors in Summary tasks (flaw 6)
This is a post to vent some frustration, it will not give you new insights on MS Project or Project Server. However, if you are Dutch like me, it might make you smile. If you’re here to learn something try my series on incorrect use of the product.
— Update August 2017 —
I’m happy to say that I now am part of the “Microsoft Office Language Quality” A Linked In group created with the help of Microsoft to support better language support trough out the world.
Continue reading Lost in translation – a Microsoft horror story
Hi there,
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)
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)
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)