Agile Software Development has been officially around for almost two decades now, yet surprisingly many organizations still face challenges with embracing its ways. As simply as the idea(l)s in the Manifesto have been laid out, a successful implementation of Agile principles require solid engineering practices, a collaborative culture, supportive management, strong sponsorship, and proper guidance. To top it off, many crucial practices seem counter-intuitive at first – pair programming is “a waste”, WIP limits are “inefficient”, TDD is “backwards”, developers doing QA is “blasphemous”, and staff liquidity is “just plain stupid”. Those who haven’t experienced true agility may be tempted to think “this won’t work for us” or even “this can’t possibly work”, and those who have can never go back to their old ways.
If you would like to see how these superbly beneficial, yet often misunderstood practices improve the agility of a team, then come join us in a game of Lego® to find out. Some of the concepts we’ll explore include pair programming, concurrent development, deep (I-shaped) vs. broad (T-shaped) skillsets, developer testing, automated testing, technical debt, cycle time, feedback loops, staff liquidity, WIP limits, and metrics. There will be no computers in sight, and not a line of code will be written – just a ton of Lego® bricks and a lot of fun. This is a full day workshop.