Methodology Design: the Way We Do Things Around Here

When people talk about “improving” software methodology, they rarely talk about tradeoffs. Requirements freeze, for example, runs the risk of delivering exactly what the customer asked for – and not what he needs. Concrete, detailed estimates take a considerable amount of time to create, and that’s time that could be spent writing code or executing tests. M. Heusser discusses the tradeoffs and choices you’ll have to make when the goal is improving (or even initially developing) your methodology.

One Response

  1. 2006-01-02 8:03 am