Scott Berkun was at our Newark campus today giving a talk "Schedules and other lies: the myths of making good software on time." So I'm at Menlo Park, which is across the bay. And my truck is in the shop. No sweat. Hop on the free campus shuttle and head over to Newark for a free talk. To top it off Scott is handing out free copies of his book "The Art of Project Management." Schaweet
.
So Scott worked at Microsoft for ten years - which made me raise my eyebrow. Why does a person that worked at Microsoft come to Sun to pitch a book? *shrug* What was more important is that he was a program manager for ten years working on Internet Explorer - a major piece of software. So that meant he had experience, and probably something meaningful to say about the art of project management.
Well, he did. It was a good talk. He was energetic and made some good points. One that struck me in particular was this: look at the diagram, y axis being effort, x axis being time. As the project progresses along in time (x), then effort should decrease accordingly. So there's diagonal line indicating this relationship. But in reality the line (in red) will actually deviate outwards as the level of effort continues to grow. So we spend our time chopping out features to get that line to come back down. So his point was that if we have the ability to do that, then we have the ability to actually keep the project below that line (in blue), and cut features when we approach the boundary, instead of exceeding it and spending effort trying to get the project back in line. We constantly try to do too much.
There's a number of resources at Scott's website: forums, essays and a PM clinic. The forums are just starting out, so there's not much traffic there. The PM clinic looks promising. If you scroll down the signup page, you'll see an archive of previous discussion topics.




Posted by Umang on May 11, 2005 at 07:39 AM PDT #
Posted by tony : frosty on May 11, 2005 at 07:52 AM PDT #
Trying to build something that will be everything to everybody is not only silly, but I would wager it's the primary cause of the 'red line'...which decreases ROI and increases cost/complexity, and in the end probably doesn't add the expected value of the add'l functionality because everyone is busy holding the complexity together.
The second part to driving the use of common functionality is turning off the ability for people to go off and build their own thing. Tough love? Maybe, but it's the right thing to do in my opinion.
Stepping off soap box now...:-)
Posted by skrocki on May 11, 2005 at 03:39 PM PDT #