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)
This is a very specific post only useful for the lucky few. Answer the following questions with Yes and this post will be for you:
- Do you have a Project Server 2013 tennent running in your company?
- Do you use a Windows 8.1 tablet or desktop?
- Are you using Internet Explorer 11 (comes with Windows 8.1)? Continue reading Internet Explorer 11, Windows 8.1 and Project Server 2013.
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
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. Continue reading Lost in translation – a Microsoft horror story
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):
Continue reading Date related planning (flaw 1)