A principle is a fundamental, actionable belief or guiding rule that shapes decision-making and behaviour within an organisation. It serves as a framework for action, ensuring that teams know how to approach their work in alignment with the organisation’s broader goals and values.
Principles provide clarity in dynamic environments. They are not abstract ideals but actionable guides that teams rely on to navigate complexity and uncertainty. For example, the principle of Empiricism encourages teams to make decisions based on evidence and experience, helping to ensure that choices are grounded in real-world data rather than assumptions. Similarly, the principle of Self-Management enables teams to organise themselves, take ownership of their work, and make decisions autonomously, which fosters empowerment and accountability.
Unlike values, which express what an organisation stands for, principles are actionable and directly influence behaviour. For example, the Continuous Improvement principle emphasises the need for teams to reflect on their processes and outcomes, striving to enhance their performance over time. This action-oriented focus ensures that principles don’t just shape what teams care about but also how they execute.
Principles also differ from tenets in that they are not specific doctrines or philosophies; they are guidelines that teams can actively apply to improve their processes. For instance, the principle of Adaptability encourages teams to respond to changing environments, ensuring they remain flexible and resilient.
The long-term value of principles lies in their systemic nature. They provide a stable foundation for decision-making across all levels of the organisation. Whether it’s delivering value to customers, fostering a culture of learning and collaboration, or driving innovation, principles provide a consistent and coherent framework for achieving goals.
In summary, principles are the guiding beliefs that inform decision-making and influence how teams approach their work. They ensure alignment, drive continuous improvement, and enable teams to navigate challenges with confidence. By embedding these principles in the organisation’s culture, teams can adapt to change while staying focused on delivering sustainable value.
The strongest work on Principle — ranked by substance, not recency. How this is ranked
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency
Explains how managing technical debt and distinguishing it from poor quality can boost product efficiency, reduce costs, and support …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, 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, …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership
Explores how adopting naked agility boosts engineering excellence, quality, and leadership by addressing technical debt, shifting left, and …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, 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, …
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, …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management
Compares Agile’s risk mitigation through incremental, usable products with traditional project management’s reliance on documentation, …
Story Points & Velocity are a sign of an unsuccessful team
Explains why relying on story points and velocity signals team immaturity in Scrum, and highlights better ways to build confidence and …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency
Explains how managing technical debt and distinguishing it from poor quality can boost product efficiency, reduce costs, and support …
Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership
Explores how adopting naked agility boosts engineering excellence, quality, and leadership by addressing technical debt, shifting left, and …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation
Learn how to automate legacy systems by shifting organisational mindset, adopting DevOps practices, and making incremental improvements to …
Unlocking Sustainable Growth: Why Leadership is the Key to Successful Scaling
Effective scaling depends on strong leadership, empowering teams, removing bottlenecks, and decentralising decisions to enable sustainable …
Why More Teams Won't Speed Up Delivery: The Truth About Scaling Effectively
Adding more teams doesn’t guarantee faster delivery; effective scaling requires reducing dependencies, aligning goals, and minimising …
Unlocking Product Value: Why Real User Feedback is Your Best Asset
Real user feedback is essential in product development to validate assumptions, guide improvements, and ensure your product delivers real …
Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments
Explores how Azure DevOps shifted from slow, two-year releases to rapid, continuous delivery, highlighting the benefits of fast feedback, …
Kendall Guide - A System of Work for AI Adoption
Manifesto for Agile Software Development
Evidence-Based Portfolio Management
199 resources, newest first
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Maximising Value from Applying Professional Scrum Training
Learn how Professional Scrum training empowers teams to identify organisational blockers, create actionable change backlogs, and drive real …
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, …
Too many organisations hide behind excuses:"
Many organisations use excuses to avoid Agile, but even large, regulated bodies can adopt iterative delivery to reduce risk and deliver …
Stop treating the end of the Sprint like a finish line
The end of a Sprint is a checkpoint for review and adaptation, not a deadline. Focus on flow, learning, and continuous improvement over …
Design Sprints in Scrum: Common Questions and Practical Insights
Answers common questions about integrating design and UX work into Scrum Sprints, clarifying why dedicated Design Sprints aren’t needed and …
You can’t deliver change through memos
Change succeeds when everyone understands and engages with it. Broad Scrum training empowers all roles to identify blockers and drive real, …
Scrum isn’t limited to building features
Scrum can drive organisational change, not just product features, by using backlogs, teams, and feedback to enable real, evidence-based …
When you scale Scrum, the challenge isn’t just delivery, it coherence
Explains how scaling Scrum requires UX coherence through Communities of Practice, shared frameworks, and collaboration, not central control, …
David thought he already knew Scrum
Discover why experienced Scrum practitioners often misunderstand core principles, and how revisiting Scrum fundamentals restores clarity, …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
During a massive flood in London, nearly every datacentre went down."
A London flood shut down most datacentres, but Rackspace stayed online by regularly live-testing failures, proving true resilience comes …
We hear self-managing teams so often it become a cliché
Explains how true self-management in Scrum requires active, disciplined effort from Product Owners, Scrum Masters, and Developers, not chaos …
Fear is the real enemy of agility
Explores how fear hinders true agility in teams, emphasising the need to foster courage and trust for effective Agile, Scrum, and DevOps …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Most teams don’t fail because they lack frameworks
Teams struggle not from lacking frameworks, but from ignoring feedback. Success depends on acting on signals, fostering safety, and …
Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation
Learn how to automate legacy systems by shifting organisational mindset, adopting DevOps practices, and making incremental improvements to …
Agile without a usable working product is just expensive theatre
Highlights the importance of delivering a usable product each sprint in Agile, warning against focusing on process over outcomes and …
You don’t own your market
Explains why businesses must prioritise customer needs and agility to stay relevant, avoid missed opportunities, and remain competitive in a …
Why Most Companies Fail at Adopting Agility Beyond IT
Most companies struggle with agility due to rigid structures, outdated processes, and cultural barriers, not technical issues. True agility …
“Teams are self-managing
Explains how self-managing teams in Scrum need structure and leadership, clarifying the Scrum Master's role in maintaining clarity, …
Everyone loves the idea of self-managing teams
Explains how self-managing teams thrive with autonomy balanced by structure, highlighting the need for clear goals, accountability, and …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Why Slow Processes Impact Developer Productivity and Performance
Explores how inefficient processes, not individual shortcomings, hinder developer productivity and performance, highlighting the need for …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
Agile Is Not Easier Than Traditional Methods: Common Misconceptions
Explains why Agile methods are often more challenging than traditional ones, highlighting common misconceptions, required discipline, and …