30 Days Of Agile Testing! Day Four.

Day four:
Read the agile manifesto and reflect on the implications for your role

The Agile Manifesto, courtesy of Agile Alliance:

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.

What I'm having to learn (re-learn!) at the moment is that very last statement - we value the items on the left more, but the items on the right still have value!

I'm suffering the consequence right now.

I have a software feature that works great - but I haven't kept my list of Jira tickets or confluence documentation up to scratch.
I'm now in a situation where I need to go back and ask myself "did I do that? What exactly did I do?". I'm not up to date with what I've done, meaning neither are my stakeholders. Yucko.

Lesson learned - embrace the items on the left wholeheartedly - but don't forget the things on the right!

- JE