Chronicles Of Testing

10 things I learned from being agile. I do not have to worry about knowing everything about the product/feature right at the beginning. I can take my time to learn the product feature by feature and I get to learn together with the team and from many minds. Being agile is almost like studying the self, what works for me and what doesn’t. And to learn dynamically to make necessary changes when needed. Learn on the GO what technique/ method/approach works for that context and discard the rest. Switch to the right sources of knowledge. It's about also being a pendulum when needed, shift left/right to deliver. To not invest in the unnecessary, but to question and learn rather than mere adherence. To g o figure out who can help, to have my own point of contacts of who can help and network with the learned. This means - To be DRIVEN. Agile - Is not the ultimate rule book of do’s and don’ts. Quick and dynamic is what it makes me in how I begin to do things (requirement gatheri...

Day 1 - Agile Leadership Vishu Hegde from PM Power Consulting hacked the agile leadership arena and striked the cord with the audience. He spoke about the major loophole in the transformation from the industrial era to the knowledge era. And the loophole is that many of us have not transitioned from the industrial era to the knowledge era. Key points: The answer to the problems of this era lies with an understanding and the paradigm shift towards the knowledge era and beyond. Vishu suggests that we question the norms and learn the skill/art of questioning. My take away: Continue to question and encourage questioning. Day 2 - Agile Team Culture Kalpesh Shah @agilebrightspot and Ellen Grove @eegrove stole the limelight on Day 2. True agility was demonstrated by Kalpesh - context based solutions were ideated and illustrated. As @pragmaticandy conveyed at the Better Software Conference keynote in 2015 -  don’t just follow agile but do what fits and s...