Agile Manifesto: Responding to Change

Posted on by
Traditional project management methodologies have always tried to control the amount of change within a project. Change management procedures, meticulously scripted legal contracts and rigorous budget policies are designed to fend change off as long as possible and keep change within a project to a bare minimum. This has often led to “successfully” completed projects
read more
Posted in

Agile Manifesto: Customer Collaboration

Posted on by
Traditional project management methodologies do a very good job in keeping the customer away. In fact, customer involvement in what was deemed completely successful projects amounts to merely two instances: once at the beginning and again at the end of a project. In slightly less successful project environments you may also have customer involvement when
read more
Posted in

4 simple ways to make your Drupal project (more) agile

Posted on by
Agile project management methodologies have been around for almost a decade but it’s not until the last few years that it’s gained critical mass amongst the software development community. The web develpment community, though, has so far somewhat defied this trend and keeps resisting what many developers simply call “common sense practice”. I have often
read more
Posted in