Agile trip 1

The Agile manifesto - for someone in my age - is nothing but a collection of common sense. It is addressing issues what were issues before I was cloned... oh well lot before I started to work in this industry. I have never met anyone who thinks processes and tools can tell us how to do our jobs. I have never met with a product owner who wanted to see and read the documentation and ignored the software, or ever said: "The feature is awesome, straightforward, but unfortunately not every button is documented....". And even if the customer collaboration was far from perfect, no one ever followed the contract line by line, even if sometimes we should have done it for our own good. But I still often see we do not want to adapt to change. As testers we love to create plans (I don't) and follow them, and ask for detailed requirements what already contains everything so we do not need to use our brains anymore during our job, only if we want to for some reason. And as developers who are so into the details implementation or under the spell of a cool/new/rare/fancy tool/library so they want to use it for sure even if it is just does not make sense anymore. Or doing technology migrations, re-factoring/optimization/etc  for their own fun without adding any value to anyone, and keep doing that even if the whole world change meanwhile. Change is somewhat against our default mindset. We love change, but only planned ones. We love change but only those ones what we start. We hate continuously changing focus, re-planning our tasks, dropping things we love in favor of things we do not know. It seems we forget we are not raising children here.... we create software what can maybe live for weeks even if that piece of code is the best thing we created in our life. We are creating short living phantoms; not statues for eternity.  It is like a shoemaker who either working on one shoe during his life, or does not want to sell any of his creations...