This book, a whopping 1040 pages thick, is a must have for anyone that needs to implement or administer Microsoft Project Server 2013 (what’s in a name right?). The guys at msProjectExperts are well known in the community, Gary Chefetz, Bill Raymond and Dale Howard are great at providing knowledge trough the book medium. And if you ever get the chance to visit a seminar or reading by them do not hesitate! It will surely be an enjoyable experience. Continue reading Book review: Implementing and Administering Microsoft Project Server 2013
I’m sad to say the book is currently only available in Dutch and I don’t know if there is an English translation on the way. However: If you are an international project manager and need to manage a project in The Netherlands, please read this book. This little book is a real gem. It’s to the point and a nice introduction in the subtle sabotaging ways of Dutch project members. And a great way to learn the Dutch language. Continue reading Book review: De Projectsaboteur (The Project saboteur)
I got a respons on one of my earlier posts.
I have a task with a start date in the past, completion is 0% and the “i” column doesn’t show that calendars.
The “i” column or indicator column doesn’t show the information described in the comment. Here is the complete list of the indicators it does show. Any new indicators you need to build yourself using custom fields and graphical indicators. I’ll build the custom field and indicator using the new MS Project professional 2013 but it will work on just about any other version. Continue reading Building a visual custom field for late progress in MS Project professional
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.
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
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)