Thanks to our writers, we have a new publication for you. In their own words:-
It can sometimes be a challenge for new users to find their way through Project 2007 on their way to becoming project managers. The Project team has just produced another tool that will help you understand Project 2007 —The Project Management Quick Reference Guide. You can download and print this template for ease of use. Now you have another tool to help your organization achieve your project goals.
Once again, MS has led with its chin.
I followed your link and then followed the instructions at the link. Guess what? Yeah, you guessed it: I couldn't download it.
What's the first thing that happens when I visit the MS site? You guessed it: my machine (behind all sorts of corporate firewalls) has to be validated by MS to see if it is "genuine" software. And, of course, it can't be validated so I get the "The MS Office Genuine Validation ActiveX Control has failed to install". Whoopee-sh*t ... I could have predicted that with my eyes closed and sound asleep.
What options do I get? "Retry" (how useless is that?) and "Continue". Continue? Oh, that sounds good. Let's try that. How useless could it be after the "retry" option?
How useless? As it turns out: a lot. "You can download this template from within the Microsoft Office program it was designed for."
"Start the MS Office 2007 program that is required to open the template".
Oh, there's a good idea. No, wait, it isn't: our multinational corp is still using the previous version of Office and there's no equivalent set of download instructions provided. Let's see if we can come up with the same thing.
File -> New -> Templates -> On my web sites. No joy there.
Ok, let's see what other "help" MS has on offer.
Oh! Here's a good one: Add the site to the list of trusted site. Pardon me while I ROFL! I'm in a large corp and our machines are *severely* locked down. How locked down? Enough that I can easily get every task I need to do done but also locked down so much that I can't load a new ActiveX (the major virus vector) on to my machine.
Ever the optimist, I follow MS's instructions about changing the list of trusted site. Remember how I mentioned that our machines are locked down? Guess what! (You got it in one: there's a policy that prevents the addition of sites to the Trusted Zone.)
Way to go MS: for those of us who want to promote a migration from P2003 to P2007 you've made it sufficiently difficult that I don't see any purpose in doing anything to help you earn revenue since, in other to do that, I have go through corporate process justifying the need to get my machine "image" set up as a "different from everybody else around the world" image.
Great. I have such a document but it was not as Rich as this. Thanks guys,
Glad you liked it Jerry - and sorry Len that it didn't work for you. It would appear that between Microsoft trying to protect our IP, and your corporation trying to protect their systems we have stopped you getting something useful. If you want to use the contact option on the blog we can see how we might correct this - but for now if you are looking for details of Project 2007 to promote a migration then take a look at:-
What’s New in client:
What’s New in Enterpriese:
Project RoadMap, which is useful for overview and evaluation:
The additional links (in your reply) worked and certainly provide some good supporting documentation -- though not, I suspect, as rich as the document you originally linked to.
I suspect you are not the one making the decisions about what can be released and in what format documentation is released so my earlier vitriol should probably have been directed to others but, perhaps, you might know the names of those who do make those decisions and you can use my impassioned remarks to convince them that the decision should be reviewed.
You are also not the person responsible for the roundly -- and deservedly so -- rebuked "WGA" process. I won't revisit the arguments here but would like to point out that Project (particularly Server) is so unlikely to be pirated that imposing WGA requirements on some P2007 documentation is a seriously ill-considered decision. I suspect that many Project users (and an even greater percentage of Server users) are behind firewalls and corporate policies that prevent XP/Vista environments from being updated by ActiveX controls (a Microsoft-recognized issue as demonstrated by the existence of a policy setting that will enable/disable that activity) so imposing WGA validation for a mere piece of documentation seems, well, absolutely foolhardy.
As I said at the beginning of my first message: MS has led with its chin. You can substitute "ready, fire, aim", "shot itself in the foot", "penny-wise, pound-foolish" but the impact is the same: MS is mugging their products' supporters.
Len, I’m one of the principal Project folks who decides what gets published and not, and in what format. We are constantly evolving our policy decisions about the how and when for publication in this fast evolving, Internet-based documentation cycle. I have passed your comments on to two separate teams within Microsoft. The response I got back was: “This is important feedback for us.” So we listen, and grow, and much more quickly than the rest of the world is ready to admit. Also, if you want the most robust treatment of project management from the perspective of Microsoft Project, you really do need to be using the RoadMap at http://office.microsoft.com/en-us/project/HA102143771033.aspx?pid=CH102202741033, which you don’t have to download.
I sense -- just a little <g> -- a certain defensiveness about MS's responsiveness to feedback. I think the existence of blogs, like Brian's, shows the desire to engage in dialog even if the implementation road is a bit bumpy. (The IE8 team's recent response -- including a statement that they have ACID2 compliance -- shows how responsive MS can be because, at the time, they were being criticised about a variety of things including lack of response and lack of progress updates whereupon MS came back with some significant progress updates.)
Incidentally, the url you provided was also in Brian's message and I'm still trying to find the time to read it. Too many hours of work; too few hours in a day!
Have a wonderful Christmas and I hope Santa is good to you, your family, and the MS Project team.
(Apologies if this is a dup posting ... the internet seems to have had a hiccup.)
This is a great document for project managers to use as a reference. The only flaw that I see is in Section 5 - Update Progress. There is an activity missing from your list. Once the actual hours and remaining hours are captured, the remaining work needs to be moved from the past to the present. The status date should be updated, task type should be either fixed work or fixed units and then the Update As Scheduled or Reschedule Work button needs to be used. It is imperative that remaining work move from the past to the present/future and the schedule updated accordingly. Without performing these activities your schedule may not reflect the current reality.
Thanks and I hope this helps others - the failure to perforn this part of the update led to problems with resource scheduling and estimated completion date.
Thanks for the feedback Bert. I can't imagine a project that ever has work that wasn't completed in the allocated time and needs moving forward :) - but just in case others have better imaginations than me I will bring this to the authoer's attention.