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
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 …
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 …
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 …
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 …
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 …
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, …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
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 …
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 …
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 …
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 …
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 …
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 …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Stop Writing Business Logic in Stored Procedures
Explains why business logic should not be written in stored procedures, highlighting testability, maintainability, scalability, and …
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, …
Fragile by Design: The Cost of Pretending to Be Resilient
Explores how poor engineering, shallow product thinking, and organisational denial lead to fragile systems, stressing that true resilience …
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 …
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 …
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 …
Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)
Still deploying manually? Discover why automation isn’t optional, protect your business, avoid disaster, and deliver value with modern …
Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win
Unlock your team's true potential, discover why a powerful definition of done drives real business impact, customer value, and lasting …
Legacy Systems Aren’t the Enemy, Friction Is: How to Unblock Innovation and Accelerate Agile Delivery
Is legacy tech slowing your team? Discover how removing friction unlocks agility, innovation, and faster delivery in your organisation.
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation
Stop firefighting late-stage bugs, discover how shifting left saves time, money, and reputation by building quality in from the start. Learn …
120 resources, newest first
Before You Call Yourself an Agile Coach: The Importance of Real Experience
Real-world experience with teams is essential for Agile coaches, providing credibility, empathy, and practical insight needed to effectively …
Navigating Team Conflict: From Healthy Disagreement to Agile Harmony
Explores recognising and managing team conflict in Agile, outlining stages from healthy disagreement to destructive "war" and offering …
How to Set and Achieve Effective Sprint Goals
Learn how to define, craft, and achieve effective Sprint Goals in Scrum, using frameworks like SMART and OKR to align teams, deliver value, …
How does a Scrum Master or Agile coach motivate a Scrum Team?
Explains how Scrum Masters and Agile coaches boost team motivation by setting clear goals, fostering engagement, recognising achievements, …
Mastering Product Ownership: Unlocking the Secrets to Effective Product Management in Agile Teams
Explores the vital role of product ownership in agile teams, highlighting key skills, challenges, and strategies for effective product …
Unlocking Agile Mastery: How the Minecraft Case Study Transforms Training and Team Dynamics
Discover how using a Minecraft-based case study enhances Agile training by boosting engagement, illustrating complexity, and improving team …
Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support
Learn how practical training, real-world application, and community support help you build confidence and skills to succeed as a Scrum …
Reasons to do a PSM II Course in 60 seconds
Discover how the PSM II course deepens Scrum Master skills, boosts team performance, supports product owners, and advances agile careers …
July 2023 NKDAgility: Introducing NKD Agility's Next Generation of Agile Practitioners: Transforming Work, Building Success, and Achieving Greatness in the 21st Century!
NKD Agility offers immersive, multi-week agile training to build practical skills in Scrum, leadership, and continuous improvement for …
In WIP, less is more. Why?
Limiting work in progress boosts productivity by reducing multitasking, context switching, and bottlenecks, helping teams focus, finish …
Why Many Scrum Masters Stall at PSM1: The Crucial Role of Passion in Professional Growth
Many Scrum Masters stop at PSM1 due to lack of passion. Ongoing learning, genuine interest, and active engagement are key to advancing and …
Can organisations run an Applying Professional Scrum workshop? How would that help them?
Running an Applying Professional Scrum workshop helps organisations build agile skills, improve teamwork, and adopt Scrum practices through …
March 2023 NKDAgility: The magic of immersive classes
Immersion programmes extend learning beyond the classroom, combining real-world practice, retrospectives, and expert guidance for deeper, …
What would you advise a scrum team to do in their first 4 weeks?
Guidance for new scrum teams on establishing effective practices, learning from experience, experimenting, and improving during their first …
Free Workshop 04: Introduction to Sprint Reviews [Review & Retrospective]
Covers key concepts of Sprint Reviews, interactive workshop delivery using Teams and Mural, technical challenges faced, participant …
Training Schedule 2021 Q4/2022 Q1
Overview of live virtual training methods, free workshop recordings, schedule updates, and new coaching and retraining programmes for Q4 …
A better way than staggered iterations for delivery
Explains why staggered iterations harm software delivery, increasing technical debt, and recommends cross-functional teams, test-first, and …
Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture
Explore proven strategies from Azure DevOps for building resilient, reliable software systems, covering transparency, automation, telemetry, …
Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World
Practical strategies for remote Agile teams, covering communication, tool selection, value delivery, team dynamics, gamification, and …
No Estimates and is it advisable for a Scrum Team to adopt it?
Explores whether Scrum Teams should adopt No Estimates, comparing estimation methods, team maturity, and metrics like cycle time, …