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.
As a consultant I try to read and know as much as possible about the subjects I’m considered to be an expert in. Apart from blogs and Microsoft TechNet there is a whole universe of project (management) literature out there to suite just that need. This is why I started doing book reviews!
Continue reading Book reviews on Project management and MS Project (server)
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
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
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 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)
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.