The Miser Project  
privacy 
 
 
 

Collaborative articulation of how abstraction and language is employed in the computational manifestation of numbers -- including analysis of the role of syntax, semantics, and meaning in the specification and use of software interfaces.



Click for Blog Feed
Blog Feed

Recent Items
 
All that's needed isn't written down; how much mor...
 
Abstract or concrete? Maybe both.
 
A mesh of agreements, I am, I am
 
Service interface experiences
 
Compiling Num.java 0.1x
 
Deja Double Vu
 
Blog Restored
 
Unorganized set of references: to be evaluated
 
Document-centric integration; perils of API's
 
Libraries and Platform Independence

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


visits to Miser Project 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 that the operational-level, week-by-week planning for eXtreme Programming (and Agile methods that have followed) support containment of scope creep.   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.

 
I also have no clue how I managed to post this here rather than on Professor von Clueless where it belongs. I shan't move it, but I will also "cross-post."
 

 
Construction Structure (Hard Hat Area) You are navigating The Miser Project.

template created 2004-05-31-22:34 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 21:00 $
$$Revision: 22 $