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.
