Tim Bryce is a writer and management consultant located in Palm Harbor, Florida.
http://www.phmainstreet.com/timbryce.htm
He can be contacted at: timb001@phmainstreet.com
Copyright © 2008 Tim Bryce. All rights reserved.
"Remember, it's Ready, Aim, Fire; any other sequence is counterproductive."
- Bryce's Law
Having been involved with the systems methodologies field for over 30 years I have been occasionally asked what percentage of time in a project should typically be devoted to a specific phase of work, for example a Phase 1 Feasibility Study, Phase 2 Systems Design, etc. Basically, the reason the person wants to know this is to use it as a means for estimating the remainder of the project. For example, if I were to say Phase 1 represents 10% of the overall project, they would simply multiply the amount of time spent in Phase 1 by ten. This is an unreliable approach for estimating which is why I usually balk at giving out such figures.
Systems development projects vary in size from large to small and although statistics should certainly be maintained, I still consider this an erroneous approach to estimating. Instead, I recommend basing an estimate on a rough design of the product to be built (the system), including all of its pieces and parts, such as inputs, outputs, files, records, data elements, etc. Some of these components may be reused from other systems, some may require modification, and some may be entirely new. This is called estimating based on the system's "Bill of Materials," a simple concept derived from engineering and manufacturing. Even if a project only involves a single program (as opposed to a major system), I would still examine the types and number of components affected by the assignment.
Having said all of this, let me give you my spin on the proportion of work in the typical systems development project. I have seen many companies skip through the early phases in order to get to the programming phases which is considered the important work. Under this scenario, programming represents 85% of the project. Instead I advocate more time spent in the early phases for better clarity of requirements definition and for producing better specifications for the programmers and DBA's to follow. Under this scenario, I see as much as 60% in the early phases involving systems analysis and design, 15% in programming, and 25% in implementation and review. You heard right, 15% in programming. Why the disparity? Simply because programmers have long suffered from the lack of decent specifications and end up spinning their wheels over and over again trying to deliver what is needed. But if you concentrate on better specifications upfront, the guesswork is eliminated for the programmer.
Some people consider the upfront work to be somewhat frivolous, that the "real work" is down in programming. I don't know why this is, perhaps programming is more tangible since screens and reports can be visibly shown to people. But I do not subscribe to this notion, and believe the vital work to be in the early phases, but then again, I am considered a dinosaur by the "Agile" methodology people. Regardless, if you have to build anything of substance, be it a bridge, a skyscraper, an automobile, or a system or a single program, you have to do your homework first, otherwise you find yourself constantly tearing things down and rebuilding them over and over again. If we built bridges the same way we build systems in this country, this would be a nation run by ferryboats.
One last word on applying percentages to project estimates, the danger here is that you might calculate you are 90% complete; inevitably you will discover the last 10% will take forever. So, my recommendation is to avoid the percentage trap and consider the Bill of Materials you are going to work on instead.
If you would like to discuss this with me in more depth, please do not hesitate to send me an e-mail.
- Related Videos
- Related Articles
- Ask / Related Q&A
- Bryce Management Analysis Service Introduced
- The Bryce Is Right! The Lost Chapter
- Bryce's Crash Course in Management
- Bryce's Pet Peeves of the Week
- Craftsmanship: Its Cultural and Managerial Implications
- The Cost of Technology
- A Short History of Systems Development
- Methodologies versus Techniques and Tools




Eight Enterprise Performance Management Best Practices - Defining Phase
By: Victor Holman | 07/11/2009The defining phase is where preliminary management processes are performed. These preliminary processes are those outside of traditional performance management, but which are critical to the success of your performance management initiative. Defining phase best practices are the executive processes that don't necessarily include participation from all levels within the organization.
10 Best Reasons for Document Scanning
By: Steven Hastert | 06/11/2009More and more businesses are moving to electronic records. Learn the ten biggest reasons why document scanning can help save time, save money and increase security.
Eligibility criteria for the PMP exam
By: Bogdan Gorka | 06/11/2009The PMP credential is probably different to most tests. If you take a language test as an example, you can sit even the proficiency test in Chinese and nobody will ask you for any prerequisites. As long as you pay the exam fee, you can sit this exam (and fail of course). In order to sit for the PMP exam you must meet certain educational and professional experience requirements. Only meeting these will open the door to the exam.
Code For Sustainable Homes (CSH) - The Role of the Pre-Assessment
By: Paul Giesberg | 03/11/2009The Code for Sustainable Homes (CSH) is the benchmark for measuring the sustainability of new houses in the United Kingdom. A CSH pre-assessment is not a formal part of the Code for Sustainable Homes assessment process, but it is a valuable tool nevertheless. This article describes why.
How to find the right office fit out contractor
By: Adil | 02/11/2009Taking the hassle out of finding the right office fit out company for your business.
Succession and Inheritance Issues
By: michaelrussell | 02/11/2009When it comes to estate planning the prospective client has a couple of options open to him. Either they could prepare the plan on their own with the help of an expert or leave the process for Government to finalize. Succession and inheritance occupies the prime spot among the issues to be determined.
Avoiding Government Intervention
By: michaelrussell | 02/11/2009Few people realize that estate planning is such a process that if not carried out in private, Government would intervene and carry it out. Downside of it would be that Government planning would be expensive.
Helping Avoid the Hazards of Probate
By: michaelrussell | 02/11/2009Avoiding the nightmarish administrative hurdles of probate is the objective of many people resorting to estate planning. Good and efficient probate attorney can achieve the feat for their clients.
Why Project Management Fails
By: Tim Bryce | 21/10/2009 | ManagementFour reasons why project management breaks down.
The Problem with "Man Hours"
By: Tim Bryce | 16/09/2009 | Project ManagementI've never been comfortable with the concept of "Man Hours," not that it's a gender issue, but rather it implies ignorance of how time is used in the work place and fumbles away some simple management concepts needed to run any business, namely accountability and commitment. Actually, I thought the "Man Hour" concept disappeared with the passing of the 20th century, but it appears to be making a comeback.
Humor in the Work Place
By: Tim Bryce | 31/08/2009 | ManagementWhen and how humor should be injected in the work place.
Software Versions and Releases
By: Tim Bryce | 31/08/2009 | SoftwareAre the words synonymous? Can they be used interchangeably?
Challenging the Status Quo
By: Tim Bryce | 28/08/2009 | ManagementStagnation is not an option.
Information Systems Theory 101
By: Tim Bryce | 13/08/2009 | ProgrammingProvides a conceptual foundation for all Information Systems work.
Remembering Names
By: Tim Bryce | 27/07/2009 | Customer ServiceThe importance of remembering names. It's just good business.
Credit Scores
By: Tim Bryce | 27/07/2009 | CreditWhether we like it or not, our lives are greatly impacted by our financial credit scores. If you have a good credit rating, lending institutions are more than happy to loan you the money to buy a house, a boat, a car, help you start a business venture, or whatever. If you have a bad rating, you're basically stuck in Nowheresville.