Essentials of PM 1

[remi12]

What are the first things (steps) of note to someone just getting his foot in the door of Project management

How do I cope with several requirements - what software applications will help - How do I incorporate PM issues into my proposals - and business plans (I am starting a small business soon)

 

[BNPMike]

If you are fresh to this, then read a good book. Don't go on a course. Most courses are just a structure for someone to rip you off on the pretext of some methodology or other.

Above all remember project management is primarily management - making people make something good happen. No software can solve this problem. The principle tools are Outlook, Word, Excel, Powerpoint and Access. Add in Microsoft Project and I think that's about all you'll ever need.

 

[BernardErtl]

Hopefully project management tools/methodologies assist a manager in promoting:

Visibility - All team members can see the plan
Objectivity - Progress reporting is objective (as measured against the plan)
Analysis - Identifying critical work flows or constraints


Bernard Ertl
www.interplansystems.com - eTaskMaker project planning tool

 

[MSGJack]

I believe in the CMMI process. I do several projects a year and nothing else comes close. Read it and understand the principles. I'm not to crazy about the certifications. If the requirements are not fully defined, baselined and the customer is willing to sign the bottom line, make requirements definition a part of the proposal. The last five years I've written several proposals in two parts. First: define and baseline the requirements/design, second: negotiate the work required to produce the product. PM is a part of the proposal, state it clearly in the cost and schedule. I've used several tools for requirements tracking, mostly DOORS. You can accomplish everything as BNPMike stated with a simple suite of tools. Don't go overboard on high dollar software. Management is management, if there was a magic tool they wouldn't need us would they. Good luck on your business.

 

[dianne001]

I found a book that has been very helpful to me.
"Project Planning Scheduling and Control" by James P. Lewis.
I also like using the UML process with Rational Rose products.
Thanks,
Dianne

 

[mbuell]

Another resource is Project Management Institute - or PMI. There may be a chapter meeting near you, and their meetings are open to the public. Can be a source for networking.



Mark
<O>
_|_

 

[bas007]

If you don't want to buy anything and want a fast and
fun start on (software) project management, you can also
visit my free project management course.

Ok, ok, I wrote it, so it's a shameless plug, but non-
commercial, just see for yourself, hope it helps.

Cheers
Bas

 

[guestgulkan]

I think a lot of 'people skills are also required in real life project management - simply put if you can't get people to work for you then you're sunk!

 

[RAGP]

Learn to say no, can't, not possible, maybe this is better - most overlooked essential of project management

Robert Andrew G. Pangilinan
Business Analyst/IT Consultant
Philam Systems, Inc.
AIG Group of Companies

 

[johnherman]

It also helps to think of yourself as a resource manager. A project is usually limited by one of three resources. Money/budget, time/due date, quality threshholds/standards.

Quite simply:
Cheap + quick <> quality
Cheap + quality <> quick
Quality + quick <> cheap

A note from experience:
After the project is approved, make a record of EVERY change to the project scope or requirements, no matter how small it appears to be. Then estimate (over estimate) the time it takes to add this feature and ask the steering committee for the project for approval, denial, or deferral to the next stage.

Sometimes the grass is greener on the other side because there is more manure there - original.

 

[remi12]

I appreciate all these winderful suggestions - I sure gonna get cranking.

Thanks a lot for all your help.

 

[stormcloudgathering]

I agree with RAGP
I've managed projects now for over 12 years. In all those years the skills I've needed most were diplomacy, communication (honest, open and frank), realism - the plan will ALWAYS get changed, and a very thick skin - you end being hated by seemingly everyone!

Being able to use the software has been the least needed skill I've used!

 

[BNPMike]

The world is dominated by formal, bureaucratic methodologies. These usually are 'waterfall' - define a solution and then proceed to build it in an ordered fashion. Preferably, delegate in as many presciptive formats to as many sub-teams, most of whom don't have a clue about what the business need is, or even what the business is. Then have a load of testers and other innocents who are just floating in never-never land. Eventually your project will work (sort of) but in the meantime you will have blown away enough cash to save half the population of some drought-ridden African region. Sadly however, they die.

Alternatively, think in terms of dynamic (if unfashionable) alternatives like RAD, Timeboxing, Extreme Project Management etc etc. At least you'll feel there are few mortals out there that are sentient beings like you.

It's a distorted in which we live, but it's helpful if you can sit in that meeting thinking "I know you all think I'm daft, but actually it's you that are deluding yourselves..."

 

[wojtekszala]

Try Cristal Clear small team software development technology. It is really worth looking at. I have found it and I may clearly suggest it.

Wojtek

 

[johnherman]

I'd also like to recommend a good text (even for experienced PM's). It's called Software Project Survival Guide by Steve McConnell. Although the book is published by Microsoft Press, there is no Microsoft bias.

-------------------------
The trouble with doing something right the first time is that noboby appreciates how difficult it was.
- Steven Wright