Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Sending Orcmid to (Code) Camp
 
Relaxing Patent Licenses for Open Documents
 
Navigating Data Models
 
Assessing Open Source for Corporate Usability
 
Safe Software: Getting Easier?
 
The End of the Historical Record?
 
Software Inspection's Lonely Adherents
 
Trustworthy Deployment: What's That?
 
Is Distributed Trustworthiness Soup Yet?
 
MDDi: Integrated Tool Chains for Software Developm...

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2005-10-13

 

Agile Scope-Creep and How to Detect It

Martin Fowler’s Bliki: FivePoundBag.  I had to laugh at this apt characterization of the danger of scope creep and how it is overcome by the operational-level, week-by-week planning at the heart of eXtreme Programming (and Agile methods that have followed).

First, I have seen that work on operational development (though in my case it was through preserving the weekly build and user-test schedule and not allowing last-minute changes to the code base).  Secondly, it reminds me that my M.Sc project dissertation approach was a definite failure at scope management, one that I needed to have recognized and addressed 4–5 months earlier instead of well-beyond the point of no return. 

I haven’t fully internalized that lesson.  I am currently operating week-to-week and it is still heavily randomizable activity.  Solo processes, in my case, are not trustworthy as committed efforts.  I am also girding up for a real development project and we’ll see if I can manage not to do it my habitual way, but with early scope management and reality-tracking.  Sounds good, right?  I have no clue.  Really.

Cross-posted from Numbering Peano. I don't know why I put it there [;<)

Update: I mangled the very first sentence and had to fix it.

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $