Mastering

Agile Practice


An onsite course at your location, over either two or three days, run by

@JonJagger and @KevlinHenney

How do you develop expertise?
Peter Norvig writes:

The key is deliberative practice: not just doing it again and again, but challenging yourself with a task that is just beyond your current ability, trying it, analyzing your performance while and after doing it, and correcting any mistakes. Then repeat. And repeat again.

Mary Poppendieck writes:

It takes elite performers a minimum of 10,000 hours of deliberate focused practice to become experts.

For a developer, deliberate practice means trying new things, trying old things with a view to making them fresh and trying to move from accidental practice to intentional discipline. Deliberate practice improves technical agility through increased self-awareness. This includes how you approach existing code, new code, testing, working with colleagues and customers, and other aspects of software craftsmanship.

Agile Development is more than simply a revival of iterative and incremental development. Organisations, teams and individuals often fail to achieve the promise of agility. The subtlety of Agile Development is based on adaptability, team work and attention to technical excellence, not tools or project management techniques.

We will explore this subtlety through practice. Join us.

Contact Us

jon@jaggersoft.com, kevlin@curbralan.com

Feedback

It helped me understand what I need to do to improve my performance and to understand some of the difficulties of working in a team and developing software. A couple of weeks after attending the session, I arranged a similar practice session at work and we used the CyberDojo to practice TDD and pair programming.
John Moss, Software Developer, Cascade, UK
The key message of taking deliberate practices (continuous change) as part of my everyday work practices was effective. I think it also worked very well having two speakers. I think you "synch" very well together, and the pace of the day never got boring nor stagnant. Talking about the self image and maintaining of it was good.
Lauri Mikkola, Ericsson R&D Finland.
I took away from it a new view on the value of pair programming and on the test first development process. I can see it as quite valuable for breaking down the stigma of code review practice and fostering best practice and style within a team with the "ownership" issues getting in the way. It was fun and informative.
Neil Horlock, Director Information Technology, Credit Suisse, UK
You have so many insights and share them in a clear and thought-provoking way. I particularly liked the discussion around "velocity" in agile development. An eye-opener was the historical reflection around the branding of "Agile" and the alternative name "Adaptive". The CyberDojo was brilliant. I love the concept. It's an excellent learning tool that I actually pushed out internally at our company.
Adam Peterson, LearningWell, Sweden
The presentations were interesting but I think the real learning happened during the dojo sessions. In the software world there is a constant urgency to stay updated to keep your skills and practices relevant. Deliberate Practice is a fun and motivating way to follow a course of self-development.
Mike Long, Senior Software Engineer, Schlumberger, Norway
It affected me a lot, and in a good way. It reinforced my enthusiasm to learn: both software stuff and non-software stuff. I enjoyed it a lot! I haven't seen a presentation with two presenters before, and it worked out brilliantly.
Csaba Hoch, Scrum Master, Ericsson
I had a fantastic time. I couldn't fault the course and I thought the practical demonstrations of self organisation worked really well. It showed that getting it right was more about doing than knowing.
Mark Booth, Software Engineer, Diamond Light Source, UK