2History of Agile Egg v1.0• Agile Egg v1.0 developed by an ETS working group lead by Tony Stansfield based on experience of pilot projects that used an eXtreme Programming (XP) approach in 2002.• The name Agile Egg reflected the understanding that a pure XP approach was not appropriate for many Egg projects and that approach should always be adapted to context. Some projects would have constraints such that a Waterfall life-cycle might be selected.• Following a down-sizing of IT and relocation to Derby, Agile Egg was rolled out in ETS (July 2003) . In late 2003 ETS rolled out the Agile Egg approach to teams distributed across Egg and partner sites (Lostwax and Keane)• ETS teams were given the freedom to pick and choose agile practices to suit their project: – projects on the existing mixed technology stack employed XP Planning practices using XP Story Studio to support cross-site working (2 week iterations were the norm).– Test Driven Development was only implemented on .Net and Flash projects– no formal governance so teams have inconsistent work practices (can cause problems people who work across development teams such as QA/Security)– some ad-hoc coaching provided by ThoughtWorks, eXoftware and author of this report
< Page 2 | Page 4 >