If you ask of any company these days whether or not they consider themselves to be "agile", the vast majority will answer in the affirmative, and proudly point you to the many "agile processes" they follow, and "agile tools" they use.

And yet ... in spite of all this "agility", as our meticulously-planned "sprints" take longer to execute, as our backlogs fill-up with overhead having nothing to do with core business value, as it gets exponentially difficult to predict just *what* is going to be delivered and _*when*_, it feels like just about every software project we end-up working on, doesn't quite deliver on this feeling of overabundant "agility".

We will explore various challenges that we software engineers face, and offer practical approaches to overcome them, while making software engineering fun again, as we evolve toward True Agility.


Comments are closed.

Dion Snoeijen at 09:03 on 9 Jun 2018

Well, this was about TDD, but nevertheless, I found it very useful and it inspired me to try that road more often in the future.

Dennis C. at 10:47 on 9 Jun 2018

When talking about TDD for 30 minutes of a 45 minute talk, please make sure it says so on the summary so your audience can make an informed decision on if this talk is for them. Maybe reduce the self promotion of your social media presence.

Kaz van Wel at 20:48 on 9 Jun 2018

Chris sounds like a naturally good speaker, and the talk was inspirational and fun. Unexpectedly the talks main message was: do TDD. I don't do TDD, and I know I should. This talk and his arguments finally got me serious about writing tests. So Chris, good job!

Nice talk. However it should cover more the other points and not focus so much on TDD

Arnout Boks at 19:12 on 14 Jun 2018

I found this talk pretty disappointing. I did not expect a talk about just TDD and patterns, as neither of these terms are mentioned in the abstract. Based on the abstract I would have expected more content about agile processes/way of thinking and getting feedback early.

Also the concepts that were treated, I think the amount of useful content was a bit low. Apart from 'do TDD' there were little takeaways or lessons. Telling that a friend has built an e-commerce system using TDD (without going deeper into the challenges, struggles and choices) does not add much value in my opnion.