Peter Stevens teaches the basics of Scrum starting from its principles, explaining why it works and how team can use it to be effective.
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.
Seb Rose explores the choices a team needs to make when considering which Agile test practices to adopt, urging teams to practice, practice, practice until they are happy with the way they code.
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.
David Tanzer takes a look at the current status of software development and suggests what a team can do to stay competitive, and what a developer can do so his/her employers still need him over time.
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.
Oliver Szymanski reviews the pros and cons of several frameworks and tools when one attempts to use them in an Agile environment.
Sue Johnston advises on communicating with different types of personalities starting from known psychological principles with the aim to improve relationships at work and in daily life.
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.
Scott Ambler explains the pros/cons of daily just-in-time architectural modeling and a TDD approach to design level, advising through examples on integrating these techniques into development.
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.