|
Posted by Louis Ohland on March 3, 2008, 6:21 pm
Please log in for more thread options
I need to document a process. Up until now, they used a simple
timeline, but that was when there was 18 months to make it work. Now 18
weeks is a luxury (closer to 30 days, minus)
Which book is worth getting?
The direct title match books are from the 60s and 70s.
Gantt, PERT, CPM
|
|
Posted by Ed Huntress on March 3, 2008, 6:35 pm
Please log in for more thread options
> I need to document a process. Up until now, they used a simple
> timeline, but that was when there was 18 months to make it work. Now 18
> weeks is a luxury (closer to 30 days, minus)
>
> Which book is worth getting?
>
> The direct title match books are from the 60s and 70s.
> Gantt, PERT, CPM
Gantt and PERT charts are so straightforward that I can't see why you'd need
a book. I did dozens of them with a freeware product called Gantt Project
(you'll find it on the Web), which is a slightly stripped down competitor
with Microsoft's Office Project.
There also are Excel templates available but I haven't tried them.
Is the project very complex, that you feel the need for a book, or are you
looking for the basics of Gantt and PERT? I've heard that the Microsoft
Project software comes with plenty of instruction, should you want to try
it. You can download a free trial version.
--
Ed Huntress
|
|
Posted by Tim Wescott on March 3, 2008, 7:24 pm
Please log in for more thread options Louis Ohland wrote:
> I need to document a process. Up until now, they used a simple
> timeline, but that was when there was 18 months to make it work. Now 18
> weeks is a luxury (closer to 30 days, minus)
>
> Which book is worth getting?
>
> The direct title match books are from the 60s and 70s.
> Gantt, PERT, CPM
I've worked on many projects that have severely missed their schedules,
and a few that came in within 10% of estimates.
The few had two factors in common:
1. They were tracked with Gantt charts.
2. _Everyone_, from the top of the management tree to the roots of the
worker-bee staff, respected the schedule. On the worker-bee end this
meant not overdoing your task and letting the project manager know when
things go awry. On the top-management end this means actually believing
that people whom you pay tons of money to be competent _are_ competent,
listening to what they say, and accepting that the impossible really
does take a bit of time. Of the two, the latter is more rare.
Gantt charts are close to intuitive, so those management books from the
60's and 70's are going to be perfectly good at filling in the gaps.
Management buy-in is rare.
You're talking about process, not projects, so the only thing I can add
is to draw a corollary to the "management buy-in" problem: don't
document the process times that _should_ exist; document the process
times that _do_ exist. If you start making it your business to shorten
up times, make plans based on the times that do exist while you're
expending effort on bringing the times in.
--
Tim Wescott
Wescott Design Services
http://www.wescottdesign.com
Do you need to implement control loops in software?
"Applied Control Theory for Embedded Systems" gives you just what it says.
See details at http://www.wescottdesign.com/actfes/actfes.html
|
|
Posted by Wayne Lundberg on March 3, 2008, 8:26 pm
Please log in for more thread options Brush up on some basic concepts and stick to a Gantt...
http://home.att.net/~Waynelund/projectmanagement.htm
> I need to document a process. Up until now, they used a simple
> timeline, but that was when there was 18 months to make it work. Now 18
> weeks is a luxury (closer to 30 days, minus)
>
> Which book is worth getting?
>
> The direct title match books are from the 60s and 70s.
> Gantt, PERT, CPM
|
|
Posted by Louis Ohland on March 3, 2008, 10:26 pm
Please log in for more thread options "Project management is the process which allows for disorder within an
orderly structure"
This is important, because the timeline gives no idea of what can slide,
and what's a critical dependency.
Wayne Lundberg wrote:
> Brush up on some basic concepts and stick to a Gantt...
>
> http://home.att.net/~Waynelund/projectmanagement.htm
>
>
>> I need to document a process. Up until now, they used a simple
>> timeline, but that was when there was 18 months to make it work. Now 18
>> weeks is a luxury (closer to 30 days, minus)
>>
>> Which book is worth getting?
>>
>> The direct title match books are from the 60s and 70s.
>> Gantt, PERT, CPM
>
>
|
| Similar Threads | Posted | | Good book on operating a mill | May 22, 2007, 10:24 am |
| Good book on paint selection? | October 30, 2007, 12:41 am |
| OT-Path to security | August 12, 2007, 5:45 am |
| you doubtfully ban up to likely critical darknesss | August 12, 2007, 9:24 pm |
| Critical Dimensions For Mixing Venturi? | December 14, 2006, 1:36 am |
| Project management and costing | October 11, 2006, 11:38 pm |
| Project time Management | April 20, 2006, 5:50 pm |
| project management australia | February 24, 2008, 7:47 am |
| [OT] Unbowed -- Joe Lieberman: "It is critical that we take advantage of this opportunity to win." | January 21, 2007, 11:05 am |
| otherwise the refugee in Pilar's european might owe some critical blacks | August 13, 2007, 12:26 am |
|
|
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap
> timeline, but that was when there was 18 months to make it work. Now 18
> weeks is a luxury (closer to 30 days, minus)
>
> Which book is worth getting?
>
> The direct title match books are from the 60s and 70s.
> Gantt, PERT, CPM