The Regenerate Web

facilitating the regeneration of software teams

User login

Syndicate

Syndicate content

Services


Add to Technorati Favorites

Project

- 1My campus life
- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
 - PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)

Management

- Boss (1)
- consensus (1)
- influence (1)
- leader (5)
- meetings (1)
- Motivation (1)
- process (1)
- Time Span (1)

Browse archives

« February 2007 »
Su Mo Tu We Th Fr Sa
        1 2 3
5 6 7 8 9 10
11 12 13 14 15 16
18 19 20 21 22 23 24
25 26 27 28      

Analysis

- abstraction (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)

Who's online

There are currently 0 users and 1 guest online.

archives

Critical difference between software development and construction...

|
Glen Alleman from the Herding Cats blog offers this post on the subject.  I want to agree with him.  I merely need to remind him that there is one key difference in the two industries:

Estimation - my experience with software development, and construction projects (church, home) though small, informs me of a key difference.  In construction projects, Once the required work is known, it can be estimated with some reasonable accuracy, because the vast majority of construction tasks have been done exactly the same way by the people who are doing them.  The tool set doesn't change every 2-5 years.  Carpenters still use nails to fasten wood together.  Wood still has the same physical properties that it did in 1965.  In software, there is a programming language every 6 weeks, and every 10-20 years the nature of raw materials change - assembler to procedural to functional to 4gl to object oriented, etc.  The new raw materials and tools require estimation to be redone from scratch.  The other factor in estimation is the difference in productivity between master, journeyman, and apprentice practitioners.  In construction the difference between resources can be a factor of 2 or 3, but years of stable estimates for building 40 linear feet of stud wall, provide a rational basis for scheduling.  In the software industry, only the practitioner who is doing the work can estimate his or her rate of completion, and the difference between practitioners can be a factor of 10 or 20.  

Meeting Effectiveness


The boys or grrls over at Trizzle.com had this thin post about stand-up meetings.  I wasn't impressed but it started me thinking.  I commented on their blog...


My comment on their post...

While standing up gets people to realize is a meeting pace. Meeting pace takes many things into consideration. Scrum uses several things to manage meeting pace. The most important is having everyone who attends be prepared to contribute.