Warning: include_once(/home/jennitta/jennittaandrea.com/wp-content/plugins/wordpress-support/wordpress-support.php): failed to open stream: Permission denied in /home/jennitta/jennittaandrea.com/wp-settings.php on line 222

Warning: include_once(): Failed opening '/home/jennitta/jennittaandrea.com/wp-content/plugins/wordpress-support/wordpress-support.php' for inclusion (include_path='.:/usr/local/lib/php:/usr/local/php5/lib/pear') in /home/jennitta/jennittaandrea.com/wp-settings.php on line 222
Process Adaptation | the andrea group
?>

Process Adaptation

  • foundations of agile software development (summary slides) Wondering what agile is all about? Skeptical that agile is the same old thing wrapped in new buzz words? Tried agile on a project with disappointing results? You need a solid foundation of what it really means to develop software using an agile approach. Regardless of the brand name, a successful agile project is easily recognized by its outcome: delivering valuable, running, tested features on a regular basis. During this full-day tutorial Jennitta Andrea explores each component of this definition in detail, looking at how specific practices and role collaboration work synergistically to achieve the goal. This foundation enables you to create a personal roadmap of agile topics to pursue during this conference—and beyond as you introduce agile to your organization. More importantly, your foundation is rock solid because you understand how project context influences decisions about selecting and adapting an agile process. 
  • The Blind Leading The Blind (BetterSoftware Nov 2007) This Management Chroniciles column highlights how the adoption of a new software development process affects each of the team roles differently.  Disappointing results are often experienced if the unique needs of each role are ignored. (Better Software, November 2007)
  • If The Shoe Doesn’t Fit (BetterSoftware, 2005)describes how to master agile requirements by tuning any requirements process to fit your unique set of project characteristics (Better Software, September 2005)
  • Agile Request For Proposal Process (Agile Development Conference, 2003) The Request For Proposal (RFP) process can be agile and efficient. At a high level, the key to achieving this is to specify requirements just in time and containing just enough detail. THe contributions of this paper to the agile community are two-fole: describing a practical application of XP concepts to a non-programming project; and making a use-case style requirements process more agile. (Agile Development Conference 2003, Experience Report) presentation slides
  • Framework XP (XP 2002) An experience report describing using XP to build frameworks, and how we had to modify XP to better suit this purpose.   We call this variant of XP Framework XP.  It builds on ideas first described in the XP books and augments them with concrete suggestions for dealing with the key issues such as how to derive framework stories from user stories.
  • Bootstrap Story (XP 2001)An ideal XP project is composed of stories defined by the customer that are of the right size and focus to plan and manage according to XP principles and practices. The reality of many XP projects is that the key story in the first release, the bootstrap story, is much larger than the rest of the stories. The bootstrap story represents the smallest deliverable kernel of the system that subsequent stories build upon incrementally. A number of strategies exist to mitigate the problems caused by the bootstrap story. (XP2001 Experience Report)