I prepared a schedule, and I'm happy with it
Thanks for the reminder. Time to update my schedule again
![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
I'm an engineer who works or manages (or occasionally both) many concurrent projects with many external dependencies on any given project.
In 2003, I created a basic project schedule for my RV-8A in MS Project, which I use at least weekly as part of my job. I built the schedule before I committed to beginning the kit, and I refer to it approximately twice a year.
I created the schedule with:
approximate build times (thank you Sam Buchanan)
equipment costs (thank you Vans and equipment vendors)
approximate shipping, tax, duty costs, (thank you Marc DeG.)
inspection fees (thank you MD-RA)
Why I created a schedule:
This is a major purchase for me.
I can't afford to build this airplane for $100K as a lump sum. I needed to understand the probably cash flow. This led me to believe that I could afford to get started. - even to build most of the airplane, before I had to send the wife back to work...
I can probably afford to build this airplane for the cash flow I established, USING THE SCHEDULE.
+Did I get the build durations right?
Not a chance. I'm slower, dumber, and more error-prone than average - my times are not going to be average. I'm also away a lot for work.
+Do I update the schedule?
Yes, first update took an hour after I got the empennage kit.
I haven't updated it since receiving the wing kit - I've got some time before I need it again.
+Are the costs accurate?
Yes, in $CDN, which means little at the moment, as the exchange rate when I started was 0.65 and is now 1.05 or so. (I'm thinking about quickbuild fuse and an engine ASAP before the US fixes their dollar. Holy 30% Discount Batman!)
I don't think that there is any point or joy in taking the detail of the schedule down to the "cleco here" level, as it becomes wasted effort tracking - as much effort as performing the work on the kit, and doesn't provide any feedback I need. It'd be interesting to see, though.
I won't spend much time arguing about project management at work - I've lived without it, and with it, and been it, over 18 years. I prefer life with it, and being it if necessary. Lots less surprises.
I used to sound like most of the posts about schedules and WBS here, and know others who did as well.
There is a point, (if you are still complaining, you haven't reached it yet -it was pretty clear when it arrived for me) at which you begin to get some personal value out of scheduling at work; yes, and out of the WBS as well.
Yes, basic scheduling can be done in your head. No, you are not going to accurately be able to judge whether or not a change has a significant impact on a complex project without a more formal schedule than your skull.
Scheduling is like any tool we use - there are good fits and bad, correct application and misapplication, and the tool holding the tool is a part of achieving the desired result.