Karen Siers outlines the difficulties encountered by a developer switching from a waterfall or cowboy coding environment to a collaborative Agile style.
Tim Lister presents the advantages—and the dangers—of practicing risk management in an adult-like fashion, offering a process for tailoring an organization and discussing how an organization can grow up.
Emma Langman explores the usefulness of some of the Quality tools that have been around since the 50s for gathering requirements, tackling repeat problems, or innovating more efficiently as a team.
Barb Spurway, Tracy Bowman discuss Voice of the Customer (VoC), a Total Quality Management/ Lean Manufacturing concept helping teams build quality products from the customers’ perspective.
Giovanni Asproni suggests that teams should not blindly embrace a methodology but rather create their own suiting their specific needs by using an approach based on patterns and pattern languages.
Rob Keefer outlines 7 practices that managers and other project stakeholders can use to influence an Agile team in a positive way.
Dror Helper shares from his experience implementing Agile practices in his team, outlining the do and don'ts that can make all the difference. He addresses teams working in a non-agile environment.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
Michael Sahota discusses top 10 Agile gotchas: when release is ready, sprint meetings take too long, no retrospectives, people aren’t working together, getting new stories, stand-ups are boring, etc.
Steffan Surdek introduces key Tribal Leadership models for Scrum Masters, Project Managers, Development managers or anyone else interested in a better understanding the teams they are working with.
Stefan Fochler shares best practices on using Ember.js to master the needs of real-world web applications, discussing what worked well and what didn't.
Zach Holman discusses the various stumbling blocks GitHub encountered as the company grew over the years.