Re: MS Project Server
- From: "Bob Dawson" <bdawson@xxxxxxxxxx>
- Date: Mon, 6 Feb 2006 09:20:27 -0600
"DJSox" wrote
Wow! Project is a tool, not a substitute for proper program planning.track
And after the planning is done, you still must have a way to actually
the progress, so one way or another you will end up using a project like
tool at some point.
There has to be some tracking/traceability/accountability, but whether the
tool for that should look like Project, I have my doubts. Don't know Borland
Tempo--can't comment on that one.
Big issue here is where exactly the breakdown is between the real nature of
software development management and, say, construction project
management--something that I'd expect Project to handle well.
There are two historic religious wars on this terrain: the software
engineering folks vs. the agile folks (heavy process vs light process), and
the software engineering folks vs. the software-as-art/craft folks. But of
course the really interesting points here are not the top-level posturing
but the details: If software development isn't a fit to classical
engineering approaches (and it currently isn't), then exactly why not, and
what, if anything, can we do either to fix that, or to redesign the
management approach and tools to be more appropriate?
Management likes project because with just one or two charts
you can capture the status a project.
Or hideously misrepresent it, depending on the skill, talent, insight,
incentives, and integrity of the person behind it. Like KPI's and PowerPoint
slides, Project takes a lot of abuse because it's most commonly used as a
substitute for deep understanding. That is, Project is used not as a tool
for planning by the manager who needs it, but as a way to produce briefing
material for higher authorities: a recognized 'evidence of diligence' that a
middle manager can use to fend off higher interest.
In my case I'm usually allotted
15 minutes for my briefing,
And that's partly what's wrong with it: it can produce, in 15 minutes, the
illusion of understanding. By creating a falsely concrete sense of what's
'done', and what's actually known about what remains to do, it enables
managers to make decisions who may or may not realize that they're
responding to the images on Socrates' cave wall
(http://www.historyguide.org/intellect/allegory.html).
and you can bet your bottom dollar, I don't want to
exceed this limit without good reason.
....or you risk inviting an enquiry/decision-point you'd rather not be
elevated out of your own control?
So that's my two cents worth, Project is a just tool, not a substitute
for proper planning.
With that understanding, I doubt I'd have as many doubts about your using
it, as about its use in general.
bobD
.
- References:
- MS Project Server
- From: Richard Grossman
- Re: MS Project Server
- From: Jim Cooper
- Re: MS Project Server
- From: Kevin
- Re: MS Project Server
- From: Jim Cooper
- Re: MS Project Server
- From: Kevin
- Re: MS Project Server
- From: Bob Dawson
- Re: MS Project Server
- From: DJSox
- Re: MS Project Server
- From: Bob Dawson
- Re: MS Project Server
- From: DJSox
- MS Project Server
- Prev by Date: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Next by Date: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Previous by thread: Re: MS Project Server
- Next by thread: Re: MS Project Server
- Index(es):
Relevant Pages
|