Tag Archives: Manifesto

Agile Manifesto – Working Software Over Comprehensive Documentation

Do you sometimes feel like your team spends more time documenting your system than building it?  One of the biggest hindrances to progress in a software project is documentation.  The Agile Manifesto prescribes that teams should value working software over comprehensive documentation.  It doesn’t mean that you should not create documentation; it means you should create documentation that provides value and at the same time does not hinder the team’s progress.

Continue reading

Agile Manifesto – Value individuals and interactions over processes and tools

David Morgan and Cecil Williams, March 25, 2013

One of the biggest hindrances to progress in software projects is bureaucracy.  Rigorous processes that must be followed unswervingly, deliverables changing hands between independent groups and required approvals – hand-offs, sign-offs, and stand-offs – all get in the way of software projects making valuable progress.  So how would you change that? Continue reading

Manifesto for Agile Software Development

David Morgan and Cecil Williams, February 25, 2013

How many times have you been presented with a phone book-sized printout of ambiguous yet carefully crafted requirements?  How many times have you, swamped with remaining work and short of time, camped in your cubical to meet a looming deadline?  Or seen your customers paralyzed by an approval process out of fear that they will not think of everything up front?  Or witnessed an organization trying to contain costs “next time” by more strictly observing the same process as last thinking it wasn’t the process that led them astray but their lack of discipline?

If you’re answering yes to some or all of these questions, you’ve felt the pain that can happen during Waterfall (or defined process control) managed projects.  Continue reading