Method

A method is a structured procedure or technique employed to achieve specific goals, often involving a series of defined steps or actions to solve problems or implement solutions.

Method refers to a structured, step-by-step approach used to achieve specific goals within a system. Unlike frameworks, which offer broader structures and guidelines, methods are focused on detailed procedures and actions that enable teams to implement solutions or solve problems.

In Agile, Lean, and DevOps environments, methods play a crucial role in guiding teams through systematic steps that support collaborative work, value delivery, and continuous improvement. Methods are often employed to optimise workflows, manage iterative development, and measure progress.

For instance, in the Scrum method, teams follow a set sequence of events, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, to manage work in short, repeatable cycles, continuously adapting to changing requirements. Similarly, the Kanban method helps teams visualise their workflow, limit work in progress, and ensure that work is completed efficiently.

Methods are essential for ensuring consistency and predictability in outcomes. They break down complex processes into manageable tasks, allowing teams to execute with precision and adapt in real-time to feedback.

In Lean, the method of identifying and eliminating waste ensures teams focus on delivering the most value with the least amount of effort, enabling continuous improvement. In DevOps, methods like Continuous Integration and Continuous Delivery enable teams to release high-quality software rapidly and reliably.

It is important to distinguish methods from frameworks and practices:

  • Frameworks like Scrum or Kanban provide the structural foundation for teams, outlining roles and events, but they do not prescribe specific methods for every action.
  • Practices, such as Pair Programming or Test-Driven Development (TDD), are individual techniques that are part of the broader methods teams adopt.

By following structured methods, teams can increase efficiency, ensure alignment, and consistently deliver value to customers. These methods empower teams to be proactive, iterative, and adaptable in their approach to problem-solving, ultimately leading to improved performance and outcomes.

A method is not rigid; it can be tailored to fit the unique context of a team or project, allowing teams to continuously refine their approach while maintaining a clear, systematic path toward achieving their goals.

The strongest work on Method — ranked by substance, not recency. How this is ranked

Video Engineering Excellence

The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower

Explores the financial, productivity, and reputational impacts of poor-quality code, and offers practical steps to turn code quality into a …

Watch video
Article Engineering Excellence DevOps

Testing in Production Maximises Quality and Value

Explains how audience-based deployment and testing in production enable faster feedback, safer rollouts, and higher software quality by …

Read article
Video Product Development Product Management

Maximising Product Value: The Power of Hypothesis-Driven Engineering

Explores how hypothesis-driven engineering helps teams maximise product value by testing ideas, measuring outcomes, and learning from …

Watch video
Video Product Development

Transforming Technical Debt: Unlocking Innovation and Value Through Quality Product Delivery

Explores how managing technical debt enables faster delivery, higher product quality, and greater innovation, highlighting strategies for …

Watch video
Video Product Development

Understanding the Power of Kanban in Scrum

Explains how integrating Kanban with Scrum boosts transparency, limits work in progress, and improves workflow, helping teams identify …

Watch video
Article Product Development Engineering Excellence

You are doing it wrong if you are not using test first

Explains how adopting test-first practices in software development improves quality, reduces bugs, and enables confident continuous delivery …

Read article
Article Scrum Product Development

In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?

Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and …

Read article
Article Product Development Scrum

Work can flow across the Sprint boundary

Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …

Read article
Article Kanban Product Development

Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)

Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …

Read article