Adrian Howard introduces a Lean Startup practice that could be complementary to stories: making hypothesis and creating experiments meant to validate or invalidate those hypothesis.
Jeff Gothelf explains how to create better product definitions with Design Thinking and Lean UX.
Steve Ross-Talbot discusses the what, why and how of describing things, in particular requirements, along with a set of tools serving that purpose and called Zero Deviation Lifecyle.
David Czarnecki discusses several Redis data structures and their associated libraries used in real cases for building leaderboards, relationships and activity feeds.
Mike Williams outlines some of the main characteristics that make developers and teams perform better than the average.
Robert Godfrey discusses the requirements set at AMQP’s foundation: Applicability, Reliability, Fidelity, Interoperability, Manageability, Ubiquity, explaining how AMQP was designed for the future.
Barry emphasizes the need to continue thinking critically about the processes and practices we embrace, accounting for the context in which they exist, and the importance of reflection and refinement at both the organizational and personal levels.
Joel Semeniuk discusses ways of making better project estimates excluding guessing as much as possible.
James Kovacs explains how to use TDD and BDD to focus the architectural efforts on the high-value areas of the code in order to obtain just-in-time software architecture.
Mario Cardinal explains how to use agile practices to incrementally introduce non-functional requirements into the architecture in order to reduce the complexity of the solution.
Simon Ogle, Alexander Kikhtenko, and Peter Thomas present a case study of a development team transitioning from a waterfall approach to 15 offshore Agile teams over a period of 5 years.
Jamie Wright provides advice on project management based on 37 signals’ software development methodology for those involved in consulting.