Heritage Techniques...Bike Shedding
Keith Pitty suggests the term "Heritage Techniques" for combination of the traditional software development documentation and the Agile Methods gaining notariety.
I like this term. It avoids the overused terms of "classic" or "legacy" while realizing that the audience, even in transition, may need an artifact that matches their expectation. In Scrum, when these artifacts are requested, they are listed as a feature* of the project and placed on the backlog.
*From what I understand any measurable/approvable/stick-a-fork-in-it completable 'task' can go in the backlog, but while I have yet to venture into practicing Scrum I'll stay in my idealistic happy-land considering everything definable as a feature, some with multiple requirements ;-), and let the implementers have the autonomy to determine and manage their own tasks.
For another other cool term see "Bike Shedding" (via Workbench, via RC3)
My linguistically inclined wife tells me we name things in order to have a sense of control over them. Makes sense. Another secondary feature (there are no primary) of this weblog's title is that it's easier for me to search for past content. (Ever noticed that the Google site search button doesn't include the "site:" phrase in the search history drop-down? grrr.)
So far I'm really enjoying the Squizlog. If ever there we get pompous enough to define our own blogger's bible, be sure to put this one near the front:
The longer I'm in this industry, the more important I think it is to constantly remind oneself of the people involved, whether they are fellow developers, managers, users or customers. We are all human beings with human failings.
10:47:29 PM  ,
|
