The Department of Defense (DoD) and the Defense Information Systems Agency (DISA) have historically operated on 18-36 months release cycles for major IT projects. DISA is now stri...
This is a story of how one project succeeded in delighting their customer, despite being put into the most difficult of all situations for an agile team – a fixed price contract...
A complex Enterprise Relationship Planning (ERP) data migration was in trouble: low quality, poor performance, instability, and an overworked team threatened project success. Faci...
As academic institutions become more reliant on Information Technology for everyday work and learning, Harvard Business School needed to find a better way to meet the ever-increas...
Susan Borges, Jennifer Gilmore, Sarah Edrie Olivei...
Agile processes rely on feedback and communication to work and they often work best with co-located teams for this reason. Sometimes agile makes sense because of project requireme...
The Agile Manifesto emphasizes customer collaboration over contract negotiation. No Extreme Programming practice embodies this more than onsite customer. This paper describes our ...
Michelle Williams, Jay Packlick, Rajeev Bellubbi, ...
Using Bruce Tuckman’s [1] “Forming – Storming – Norming – Performing” model of team development we review the effects of change on our team through each stage. We go o...
What would your Analyst team do when torn between meeting Customer versus Developer demands? When their needs conflict with one another, how do you appease them both? The report o...
BT, as part of its Agile transformation, has widened its Agile footprint into the demand-side of its business. This is being achieved by using Agile techniques in a forum called a...
Alan Armitage, Peter Wisniewski, Alan de-Ste-Croix