Practice

A practice is a commonly used technique, habit, or routine that helps teams consistently achieve goals, improve performance, and enhance collaboration within Agile, DevOps, and Lean environments.

Practice refers to consistent, repeatable techniques or habits that teams use to enhance their effectiveness, collaboration, and delivery of value. Unlike methods, which are structured approaches with defined steps, practices focus on habits that can be incorporated into a team’s regular workflow.

In Agile, Lean, and DevOps environments, practices like Pair Programming, Continuous Deployment, and Retrospectives are foundational. They are not one-time actions but ongoing, systematic routines that enable teams to work together efficiently and continually improve.

For example, Pair Programming is a practice where two developers collaborate closely to write code. This not only improves code quality but also facilitates knowledge sharing and team collaboration. Similarly, Retrospectives are a practice where teams reflect on their work processes to identify opportunities for improvement, making them a key tool for continuous improvement.

While tools may facilitate practices, they are not the practice itself. For example, a Kanban board is a tool used to support the practice of visualising work and managing flow, but the practice itself is in how the team manages their workflow using the board. Similarly, a method like Test-Driven Development (TDD) provides a structured process, while TDD practices are the consistent habits or routines (e.g., writing tests before code) that support its execution.

The long-term value of practices lies in their ability to embed behaviours that lead to predictable, sustainable outcomes. For instance, the practice of Continuous Deployment enables teams to release software frequently and reliably, thus enhancing responsiveness to customer needs and increasing feedback cycles.

What sets practices apart is that they are adaptable and evolve with the team. As teams grow and their environment changes, their practices adapt to new challenges and improve over time. This adaptability is essential in the fast-paced, ever-changing environments where Agile, Lean, and DevOps thrive.

In summary, practices are the backbone of effective teamwork. They are the daily actions, routines, and habits that shape how teams collaborate, improve, and deliver value. By cultivating strong practices, organisations can enhance team performance, drive continuous improvement, and remain responsive to both internal and external demands.

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

Article Product Development Leadership

Telling People What to Do Is Not Leadership. It’s a Failure of System Design

Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …

Read article
Article Engineering Excellence Product Development

Don’t Manage Dependencies, Remove Them

Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …

Read article
Article Engineering Excellence Product Development

Stop Hiding Behind Complexity and Start Delivering Continuously

Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …

Read article
Video DevOps Engineering Excellence

From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation

Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …

Watch video
Video Engineering Excellence DevOps

Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success

Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …

Watch video
Article Product Development Engineering Excellence

Resilience is Part of the Product, Not an Afterthought

Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …

Read article
Article Engineering Excellence Technical Leadership

Stop Promoting Branches

Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …

Read article
Article Lean Kanban

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …

Read article
Video DevOps Engineering Excellence

Stop Testing Quality In: How Shifting Left Builds Better Software, Faster

Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …

Watch video