Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Application/Web Development
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 
Computerworld 2007Subscribe to Computerworld
40 years of the most authoritative source of news and information for IT leaders.

What's Wrong With Wednesdays?

 

Sign up to receive Security Resource Alerts

January 17, 2003 (Computerworld) -- Many of the project schedules I review contain milestone completions on Fridays and new task or phase beginnings on Mondays. With a Friday or Monday milestone, what you're really saying is that people can work overtime all week and all weekend to make the Friday milestone, so they won't be late for the Monday start.
Why? Why do we do this to ourselves and to our project teams?
It's convenient to think about project milestones ending on Fridays and new things starting on Mondays. But just because it's more convenient from a calendar perspective, should we use Fridays and Mondays to end and begin project segments?
I say no. Down with Fridays and Mondays. Let's end and begin project segments on Wednesdays. Wednesday is a perfectly good day, and one that is possibly underutilized in project planning. Tuesdays and Thursdays are also good, and in my experience, underutilized. Here are the effects we might see if we choose a Wednesday to end a project phase or start a new phase.


  1. Improve schedule precision. We would know that our schedule estimations are wrong, and we might know more about how we estimate incorrectly. When we hide the actual milestone complete dates behind massive overtime, we encourage our project staff to inaccurately predict the next schedule, leading to even more overtime. Here's why: When we schedule project phases to complete on Fridays, we allow ourselves to take the weekend to complete the pieces not quite done on Friday. Completing a phase on Friday really means the phase is complete by the time people get to work on Monday morning. If we don't complete the work by Monday morning, then we're honest-to-goodness late. But, if we completed the work on Sunday morning, are we truly late? In reality, yes! We have underestimated the work, and we need to know about that underestimation to improve our estimation the next time. Otherwise, we can continue to underestimate projects by however much we are underestimating them now.

  2. DevTalk
    Johanna Rothman
    Johanna Rothman consults on managing high technology product development, focusing on project management, risk management and people management.

  3. Adjust for schedule risk sooner. We would know earlier in the project that the project has a higher risk than we earlier believed of not meeting its release date. The earlier in the project you know that the project is in trouble, the more options you have. At the beginning of the project, you can still add more staff, change tools, drop features, modify your life cycle, change how you work to reduce defects, or choose to allow more defects. In the middle of the project, you may be able to add more staff, drop features, change how you work to reduce defects or choose to allow more defects. At the end of the project, you can drop features or choose to allow more defects. As a project manager, I want to have more options rather than fewer when I'm faced with schedule-related bad news.

  4. Avoid hidden overtime. We would have less self-induced project overtime. When we're in the last couple of weeks of the project, it may make sense to ask people to work overtime. Many people can manage a week or two of overtime and still think carefully and make good decisions. However, allowing overtime for more than a couple of consecutive weeks is a poor management decision. People who work overtime for more than a couple of weeks stop thinking clearly because they're too tired. Or they don't have any new ideas because their brains are stuck on the same old ideas. Or they stop paying attention to themselves and their self-care, so they get sick and then pass the disease to everyone else, causing the entire project team to work at less than full strength. When we schedule for midweek milestones, the amount of overtime needed is much more obvious, and we can make conscious choices about how much overtime to use on the project. If you have numerous two-to-three-week minor milestones, and people are constantly working overtime to meet the milestones, you have an entire project of overtime. Constant overtime generally leads to staff burnout and software technical debt.


So if you'd like to see just how close your schedule estimates are, create schedules with milestones ending in the middle of the week. Track how closely you meet each milestone. At the end of the project, look at how much extra time you needed and see if you could have planned your project or estimated the tasks differently to have developed a more accurate schedule at the beginning. Make your project schedules honest and help yourself see the reality of the schedule sooner, say, on a Wednesday.
Johanna Rothman consults on managing high-technology product development, focusing on project management, risk management and people management. You can reach her at jr@jrothman.com or by visiting www.jrothman.com.

Previous column by Johanna Rothman:

What's Your Fault Feedback Ratio?



Print this Story Send Us Feedback E-mail this Story Digg! Digg this Story Slashdot this Story
Hire People, Not Tools
11 Steps to Successful Outsourcing: A Contrarian's View
When do you say 'No, that's not my job any longer'?
Use All Three Parts of Project Estimation
Steering vs. Repeatable
What's Wrong With Wednesdays?
""Somebody messes with me, I'm gonna mess with him," says Robert De Niro, playing gangster Al Capone in one of..." Read more...
"This pilot fish is fresh out of college with a psychology degree, but he gets a job in IT anyway..." Read more...
Read more Development posts or See all Blogs
HP confirms XP SP3 endless reboot snafu, promises patch
Microsoft pulls Windows Home Server backup feature
Yahoo tells Icahn that its own board knows best
More top stories...
Tools circulate that crack Debian, Ubuntu keys
Elgan: Hyperconnectivity: Friend or foe?
Former Microsoft manager offers free fix for XP SP3 'endless reboot'
Specialists have retrieved about 99% of the data on a disk drive on board the crashed space shuttle Columbia. Don't miss the photographs of the recovered drive.
These big ideas were supposed to revolutionize technology, but they never actually appeared. In a few cases, you'll be glad they didn't.
Nearly 20 years after the first Internet worm, Steven J. Vaughan-Nichols takes stock of the malware/anti-malware landscape and spotlights how the two sides are approaching the battle.
Though some thought it was released too soon, Mac OS X 10.5 has matured into a solid operating system, says reviewer Michael DeAgonia.
Reviews, analyses, how-tos, visual tours, hot issues and predictions about Microsoft's new OS.
Four years from now, the IT field will be a vastly different place. Will you be ready?
All Zones
Application Performance Zone
Enterprise-Class Security Zone
Enterprise Solutions Zone
The File Data Management Zone
Grid Computing on Windows Zone
Security Management Zone
ITIL Best Practices Zone
The SAS Zone
Storage Virtualization Zone
The Data Center Management Zone

Ads by TechWords

See your link here
Computerworld Report : Smart Storage
Download this Computerworld report, free for a limited time, compliments of HP.
(Source: Computerworld) Faced with growing demands, immature tools and a confusing array of technologies, IT decision-makers have to make some strategic choices. Learn how to avoid the pitfalls in this Computerworld report, a $49.95 value, available free for a limited time, compliments of HP.
Download this executive briefing download
Transformational Analytics: Virtualizing IT Environments
Download this white paper, free, compliments of CiRBA.
(Source: CiRBA) The overwhelming complexity of the modern data center compounds the problem of how to safely virtualize IT environments. This paper provides an in-depth guide to analyzing complex environments for virtualization opportunities, particularly within production environments where stability, service levels and performance are of the upmost performance.
Download this white paper go
Rapid, Widespread Adoption of CMMI at Lockheed Martin with Application Lifecycle Management
Rapid, Widespread Adoption of CMMI at Lockheed Martin with Application Lifecycle Management
Get this webcast now
Go to the webcast 
White Papers
Read up on the latest ideas and technologies from companies that sell hardware, software and services.
Discover the Secret to Secure Remote Access: GoToMyPC Corporate Security White Paper
Spam Spikes: A Real Risk to Your Business
Six Support Issues That Keep Execs Awake at Night
View more whitepapers