The Miser Project status 
 
privacy 
 
contact 

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.

 
Comments:
 
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."
 
Post a Comment
 
Construction Zone (Hard Hat Area) You are navigating the Miser Project

template created 2004-05-31-22:34 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 06-02-04 21:17 $
$$Revision: 1 $