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.
Mike Mallete discusses the why performance appraisals fail and what can be done instead.
Peter Stevens teaches the basics of Scrum starting from its principles, explaining why it works and how team can use it to be effective.
Sergejus Barinovas discusses the challenges, failures and actual steps required to move an organization to continuous delivery and as follows - continuous happiness.
Christian Legnitto offers insight in some of the tools and processes used by Facebook for pushing new updates to their mobile apps.
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.