Re: OOP - a question about database access

Phlip wrote:
> Some managers cut everything up into features, sort them by
> priority, and track how long each one takes to finish. Then
> they use this velocity metric to estimate how many features
> would be finished by a given time. This allows them to,
> eventually, put the most important 5 pounds of shit into the
> bag.

It seems to me that these managers have confused features with tasks. Using the analogy of a building: these managers think they can schedule construction by rooms, thereby ignoring tasks such as pouring the foundation, laying down the pipes and ducts and pulling the wires.

Translating featuers to tasks is often non-trivial. Most managers lack the necessary skillset and that is often why they become managers instead of architects or independent consultants.

Tak

--
----------------------------------------------------------------------
Tak To                                            takto_at_alum.mit.eduxx
--------------------------------------------------------------------^^
  [taode takto ~{LU5B~}]      NB: trim the xx to get my real email addr