Jutta Eckstein provides insights in the latest scientific research on planning and shows how Beyond Budgeting and Agile principles can be combined so that even complex projects remain controllable.
Jane Street runs a large trading business on software written almost entirely in OCaml, a statically typed functional language. Yaron Minsky shows the reasons for choosing Ocaml and how it worked out.
Azat Mardan shares experiences using CoffeeScript in production, exploring its format, evaluating its design and showcasing some of the more useful and prominent projects that have adopted it.
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 it 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.