The Agile Manifesto for Software Development

The Agile Manifesto for Software Development


Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

The four values from the agile manifesto for software development were published in 2001 and set in motion a revolutionary change for more than just software development.  They highlighted the organisational values that we had put in place to control how teams work, and addressed the balance with a set of values emphasising trust in teams.  

Here at JTPM, we provide agile consultancy services that align wholly with the agile values and principles.  Our experience extends to before the agile manifesto, and stems from software development, business analysis and project management on projects and services with many blue chip organisations.  We’ve been deep within project teams where PRINCE2 project management was layered on top of waterfall (often SSADM) software development teams (often with a filling of change management sandwiched in-between).  We were on that journey from waterfall, through a raft of RAD-type methodologies, onto a plethora of iterative frameworks in the mid-90’s, through to agile and onto where we are today – our mindset is agile by default, always challenging, always looking to improve, and always focusing on delivering value now.

All of our services are designed to share the knowledge and experiences we’ve gained and that we continue to gain as we continue our journey of discovering  better ways people can work together to achieve great things.  Our goal is not to just teach agile, our goal is to create agile cultures.