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
Debunking the Scrum Myth: Why "Twice the Work in Half the Time" is a Misleading Promise
Explores why Scrum's "twice the work in half the time" claim is misleading, emphasising value over output and the importance of realistic …
Why does Agile focus on values and principles rather than a prescribed set of steps?
Agile emphasises values and principles to guide teams through complex, uncertain work, enabling adaptation and improvement where fixed steps …
What will you learn on the professional scrum master course?
Gain practical skills and deep understanding of the scrum master role, scrum theory, empiricism, team dynamics, and delivering value in …
How is agile product development different to waterfall project management?
Compares agile product development and waterfall project management, highlighting differences in decision-making, delivery, customer …
Unlocking Agile Success: How Empirical Models Transform Project Outcomes
Explains how empirical Agile models improve project outcomes by increasing visibility, enabling change, reducing risk, and delivering value …
Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development
Explains how agile practices help teams manage complexity, adapt to change, and deliver value faster in modern product development, compared …
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 …
There is no place like production
Validating product value requires releasing features to real users in production, gathering feedback, and measuring usage, satisfaction, and …
Evidence-Based Portfolio Management
Online is the new co-located
Explores how advances in technology have redefined co-location, emphasising the importance of video presence for effective online …
Luddites have no place in the modern organisation
Explores how resistance to change and outdated mindsets hinder organisational agility, stressing the need for adaptable, forward-thinking …
Transforming Enterprises: How DevOps Drives Collaboration and Continuous Improvement
Explores how DevOps enhances enterprise collaboration, continuous improvement, automation, and customer focus to drive cultural and …
Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective
Explores the limitations of story points, optimal team sizes, and the benefits of emergent architecture for improving agile practices and …
Transforming Management into Agile Leadership: The Power of Virtual Training
Explores how virtual training supports the shift from traditional management to agile leadership, highlighting benefits like flexibility, …
Empowering Development Teams: Cultivating an Agile Mindset for Lasting Quality
Explores how leaders can foster an agile mindset in development teams by promoting autonomy, mastery, purpose, and a culture of quality and …
Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape
Explores how to balance engineering excellence and effective Agile processes, highlighting the need for technical skills, continuous …
What is your perspective on collocation?
Explores the benefits and challenges of collocation in Scrum teams, comparing face-to-face collaboration with remote work, and offering …
Are technical skills required to be a Scrum Master?
Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum …
Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm
Explores how practical, real-world Scrum training at Great Calm improved team collaboration, alignment, and continuous improvement across …