Microsoft Enterprise Project Management

Comming soon

Is Microsoft Enterprise Project Management (EPM) really necessary for Malaysian users?

The answer is a big NO and a very small yes

What the Salesmen tells you
Big Organizations need EPM to control all their projects, to have a better control

What they DON'T tell you, is ...(The real FACTs they hide)

You need for your Project Management team to be very well trained in Microsoft Project BASIC or the Professional model FIRST before you can even fiddle around with EPM

Most of EPM "features" like multiple projects controls, can actually be done using the standard Microsoft Projects version

Most of these "salesmen/women" (forget what they say on their business cards ... they are just out for your money!) are NOT WELL VERSED in the MS Projects functions, some don't even use the software!

2 Major (Big Boys of GLC and Government status) feedback on EPM purchases express serious regrets. Their EPM purchases ends up as a white elephant!

MORE FACTS

You may use MS Project to
a) Manage more then one projects
b) You can share resources using the standard versions
c) The standard versions costs only 5% of the EPM version
d)Data storage & exchanges using MSP is easier the EPM

Ok now, for some good things about EPM

EPM gives the top management an access to preset reports from all their projects, this is necessary when the top management don't have the skills to operate MS Projects.

Since they are top management, they thus can have the power to buy expensive tools to serve their needs.

EPM too does Portfolio management

But really ... do Project Managers need portfolio management to THAT extent? Yes, you'll need to extract data from related features BUT you can do this with simple cheaper softwares like Microsoft's Access (TM) , which in turn can be linked to MS Project

Frankly, I wouldn't waste my money on EPM as I believe my Project Management needs will be easily satisfied using MS Project (or any other PM Softwares of that equivalent, e.g Primavera).

For added information, Primavera's equivalent of EPM, called ENTERPRISE, too is a BIG flop in Malaysia. Sold by its former ally,HSSI, Enterprise never made a hold in Malaysia because Primavera in itself is too specialize to be used by MOST Project Managers.

In general it is safe to say,

Just stick to the simple software solutions for now, until you can answer questions about Microsoft Project without having to switch on your PC, then and only then should you think about EPM

Microsoft Project 2007 (New is not necessary better)

FLAWS & SHORTFALLS

First we dissect up Microsoft Project 2007

There are a couple of problems importing data into Microsoft Project 2007.

The first one is that importing an Excel 2007 file (in the new .xlsx format) does not work. The import appears to get hung up on some of the header information and from there you are stuck. The work-around for this is simple. Save from Excel into Excel 2000-2003 format and open that file in Project.

The second relates to importing .MPX files from other applications. At least a couple versions back, Microsoft started walking away from the .mpx format in favor of using xml as a standard exchange format. However, there are still other tools using it to exchange data and Project 2007 can open but not write .mpx files. If there are some records specifying correct calendars in the file then it will crash. For an explanation of what is happening and how to fix it, the best source is the ever helpful Adrian Jenkins who writes:

What I've found that if the file you're importing doesn't have a record type 20 and if at least one of the record type 20's calendar name doesn't match what's in record type 30, then the crash happens. Here's an example of what you may find in your MPX file:

MPX,Integration Tool Name,4.0
11,3,0,3,9,45
30,Project Name,,,,,,,1/17/2007
41,40,49,1,2,3,42

Importing an MPX file where record type 20 is missing and where the project's calendar name isn't identified in record 30 will cause the crash.

With record type 20 added, it'll look like this:

MPX,Integration Tool Name,4.0
11,3,0,3,9,45
20,Standard
30,Project Name,,,,,,,1/17/2007
41,40,49,1,2,3,42

In addition to record type 20, record type 30 also needs to specify the project's base calendar name and it should match the name in at least one of the type 20 records. Therefore, the MPX with the addtional information in record type 30 will look like this:

MPX,Integration Tool Name,4.0
11,3,0,3,9,45
20,Standard
30,Project Name,,,Standard,,,,1/17/2007
41,40,49,1,2,3,42

If you add this information to your MPX file, it should stop the crash from happening. You *may* see an additional import error, but you can click No to prevent the error(s) from appearing and the file should open.

P.S. With such problems Analyse Timescale in Excel is going to be messy. That too if you can find the Analyse Timescale in Excel icon to begin with .... its missing from its original position

Suggestion

Keep to Microsoft Project 2003 or its Professional brother, with Microsoft it never pays to be the First to have it

Starting a Project Management Program

Well in all, when you want to start a Program in Microsoft Project, the quickie way is to do the following

Create a title .... Yup NAME THAT PROJECT OF YOURS
Open MSP
On the highest line (line 1), type in your Project Name
Then on line 2
Type in START, make the DURATION value a ZERO (thus changing the TASK to a MILESTONE)
Go to line 3
Type in your FIRST Activity .... put in the duration
REPEAT to all the ACTIVITIES you wish to put in ... of course on the next line and repeat
On your LAST activity type in FINISH, put in ZERO for the duration


NEXT

LINK the activities

Start with START, bring your mouse to the milestone icon (arrow will change to a 4-corner arrow), click and drag to the activity you want to RELATE that START to.

Repeat to ALL activities ... make sure somehow all will be linked to another or if can't be linked to anywhere else, link it to FINISH

THAT, is the Quickie way to your first Work Program!

Have fun ...