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.
Jim and Michele McCarthy discuss the Core Protocols that make a common platform for an organization’s culture design.
Terry Yin explains different programming exercises, outlining the difference in their effectiveness.
Olivier Gourment explains, step by step, how any team or organization can adopt Agile code reviews which are known to reduce the costs of defect fixing by half.
Nikola Karpisek tells the story of decorating his house using an agile approach: a small board and convincing the contractors to use yellow post-it’s.
Dana Caulder discusses how to improve team communication and delivery, aligning processes and tooling for iterative improvement, processes to mitigate team member turnover and speed-up onboarding.
Janet Gregory discusses changing a tester’s mindset from “How can I break the software?” to “How can I help deliver excellent software?”, using examples and advising how to apply it on agile projects.
Allan Kelly introduces Xanpan, a mixture of Kanban, XP, Lean and economics, focusing on teams not projects, allowing for planned and unplanned work within iterations and levels flow.
Nick Zhu & Sharan Karanth introduce a thought framework, based on Anti-Fragility, that can be used to describe, explain, and tune Agile, Lean as well as Continuous Delivery practices.
Steve Arnold introduces Flow, an Agile method combining concepts from DevOps, Lean and Kanban, based on the idea that a requirement is worked on at each point of the software delivery pipeline.
Craig Strong and Daryn Holmes discuss applying the Theory of Constraints to software development, providing simulations and experience-based evidence to support the technique.
Ellen Grove presents a model for conflict recognition and resolution using practical games that teams can use to help clarify differing viewpoints and seek resolution.