Agile Manifesto

When people ask me if I know and practice "Agile" development. That answer is a resounding yes. But most of the people who ask me this are not programmers, and do not actually know what they are asking.

The fact is, is that I have been following agile development principals since I first started programming. Even though I didn't associate what I considered logical, humble, and ethical behavior as "agile" development.

Manifesto for Agile Software Development See

We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on

the right, we value the items on the left more.

Regarding the project manager version of agile development, I have found the DevOps methologies to be the most productive. Though I do not believe it solves every problem or holds the best practices for all scenarios or projects.

But in general, I do not believe in using strict agile methologies on a global basis. Each project is unique and different, and has its own unique requirements.

Programmers need to be smart, humble, and proactive enough to properly evaluate the needs of a project to make the best decisions on how to complete it to the best of their ability. And managers need to trust their programmers to do their job properly without feeling the need to second guess every decision they make.

Continue to My Projects
View Erik Gassler's LinkedIn profile I am a codementor