Agile methodologies and frameworks
Basecamp's alternative to Scrum and Kanban. Instead of sprints, use six-week cycles with two-week cooldowns. Shape work before building: define the appetite (time budget), narrow the problem, and design at the right level of abstraction. Small batch vs. big batch projects. Gives teams full autonomy within fixed time constraints. Influential in startup and product circles.
How organizations like Amazon, Spotify, and Bosch have scaled agile methods from a few teams to hundreds. Covers common pitfalls (imposing agile on everything, trying to scale too fast), and successful patterns (start with leadership teams, sequence rollout by capability). By Jeff Sutherland, co-creator of Scrum.
Google's Project Aristotle found psychological safety to be the single most important factor distinguishing high-performing teams from average ones, more important than team composition, structure, or resources. Psychological safety means team members feel safe to take interpersonal risks including admitting mistakes, asking questions, and offering dissenting opinions without fear of punishment or humiliation. The article provides six specific practices for building psychological safety including framing work as learning problems, acknowledging fallibility, and modeling curiosity.
Comprehensive guide to adopting agile methods. Agile started in software but now applies to manufacturing, marketing, HR, and C-suite strategy. Covers the conditions where agile works best (complex problems, uncertain requirements, creative solutions), how to start (begin with a pilot), and six practices of agile: lean staffing, small empowered teams, short cycles, active involvement, daily standups, rapid iteration.
Knapp outlines the five-day design sprint process developed at Google Ventures for rapidly prototyping and testing new product ideas. The methodology compresses months of debate into a structured week of mapping, sketching, deciding, prototyping, and user testing to validate concepts before committing resources.
Surveys estimation techniques used in software projects, from planning poker and story points to probabilistic methods like Monte Carlo simulation. Fowler argues that the goal of estimation is not precision but enabling better decisions about scope, schedule, and resource allocation.
Captain Marquet transformed USS Santa Fe from the worst to the best-performing submarine by replacing the leader-follower model with leader-leader. Instead of giving orders, he pushed decision-making authority to the people with the information. Key mechanism: replace 'permission to' with 'I intend to' language. Widely used in agile and leadership training.
Research showing that of all the things that can boost emotions, motivation, and perceptions during a workday, the single most important is making progress in meaningful work. The 'progress principle': even small wins boost inner work life tremendously, while small losses have an outsized negative effect. Managers should remove barriers and catalyze progress. Links to Kanban visualization of work flow.
The MVP is the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
Why a flat product backlog doesn't work and how user story mapping gives teams a shared understanding of the big picture while still breaking work into small deliverable pieces.