Microsoft Project?
Discussion
crb said:
What kind of project are you going to be managing with ms project? If it isn't complex and doesn't involve lots of people, then there are simpler alternatives. Some of the web based ones, basecamp (paid) and projectpier (free, but you'll need to host it) are pretty good.
I can't use anything else I'm afraid 
t84 said:
crb said:
What kind of project are you going to be managing with ms project? If it isn't complex and doesn't involve lots of people, then there are simpler alternatives. Some of the web based ones, basecamp (paid) and projectpier (free, but you'll need to host it) are pretty good.
I can't use anything else I'm afraid 
Nothing helpful to add I'm afraid. Just that I prefer to use either TaskJuggler or GNOME Planner.
Microsoft Project.
Started out a tinpot little tool no-one would take seriously. Ended up the de-facto standard Project Management software for the world.
It is very, properly powerful - and therefore somewhat complex.
Before it's worth buying a Microsoft Press book (which is what I'd recommend) have you had critical path analysis training? If not - go get some or read a book on that first. Else Microsoft Project will be useless as you'll try and use it to do "the wrong thing"!
Started out a tinpot little tool no-one would take seriously. Ended up the de-facto standard Project Management software for the world.
It is very, properly powerful - and therefore somewhat complex.
Before it's worth buying a Microsoft Press book (which is what I'd recommend) have you had critical path analysis training? If not - go get some or read a book on that first. Else Microsoft Project will be useless as you'll try and use it to do "the wrong thing"!
I used to run Microsoft Project training for large corporations.
The tool itself is familiar to anyone who has used Office - that's not the problem. The problem is learning to make project management predictions using a powerful critical path analysis and resource smoothing engine - and then turning that into management information to allow non-technical managers to make good decisions.
The software is nothing. Its the wetware that matters.
The tool itself is familiar to anyone who has used Office - that's not the problem. The problem is learning to make project management predictions using a powerful critical path analysis and resource smoothing engine - and then turning that into management information to allow non-technical managers to make good decisions.
The software is nothing. Its the wetware that matters.
Alex said:
MS Project isn't naturally suited to use with Scrum.
Why do say that?I've used no end of fashionable project management methods and they all boil down to maintaining a communication hierarchy that tells you what is going on. Loads of different takes on doing that.
But MSP does Critical Path. Used for examining the outcome of slips, different resourcing options and so on. Why would that not work OK with Scrum?
(Genuinely interested, BTW. I worked for Metier (Artemis) and as a PM Consultant running Software Projects for years prior to setting up my firm and getting into other things...)
Size Nine Elm said:
Alex said:
MS Project isn't naturally suited to use with Scrum.
I would agree - you just want a simple burn down chart for each sprint.And keep each sprint chart for calibrating future ones in terms of estimates vs actuals.
Depends on the scale of the project...
Hmmm. I am always slightly suspicious of "lightweight", "agile", "rapid" methods that don't seem to allow close project management - with predicted outcomes and so on.
Spend millions on preparing highly accurate technical specifications of what the software must do....and then don't bother to specify how you are going to build it!
You absolutely but positively can know. Only a few R&D projects are genuinely "new"..everything else is a runner or a repeater.
Maybe I'm just the sort of b
d dinosaur that loves to pin people down.
Spend millions on preparing highly accurate technical specifications of what the software must do....and then don't bother to specify how you are going to build it!
You absolutely but positively can know. Only a few R&D projects are genuinely "new"..everything else is a runner or a repeater.
Maybe I'm just the sort of b
d dinosaur that loves to pin people down. Don said:
...project management predictions using a powerful critical path analysis and resource smoothing engine ...
Shame its crap at that then! We only use it for small projects (max line items 500 and simple network relationships). Any bigger and we'll create separate sub projects. We don't use it for analysis of CP, only identification nor use it for resource smoothing. It also can't do schedule risk analysis - useful to model predicted outcomes for a client delivery commitment. In essence its OK, treat it like a cross between Excel and powerpoint(!). Start off with establishing an activity network drawn on paper before committing to MSP you'll find it easier, quicker to create and change, less confusing and more visual than MSP. Then use the tool. Sometimes paper is the best place to start!
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff