Professional Scrum: Elevating Agility Through Empiricism and Technical Excellence

Getting Started with the Definition of Done (DoD). Every team should define what is required, what criteria must be met, for a product increment to be …

The Scrum Master is an accountability in Scrum, responsible for enabling the effectiveness of the Scrum Team and fostering continuous improvement …

Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, ritualistic Agile …

Discover why “done” means live in production—not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes that …

A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex …

Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, Product …

Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint produces a …

Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …

NKD Agility helped the Ghana Police Service drive organisational change using Scrum, enabling continuous improvement, transparency, and local …

Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and continuously …

Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be earned …

Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over rigid sprint …

Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by completing …

Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria ensure …

Accountability in Scrum requires real agency; without the power to act, roles like Product Owner and Scrum Master become ineffective and …

Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and …

Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, and …

Explains how self-managing teams in Scrum need structure and leadership, clarifying the Scrum Master's role in maintaining clarity, alignment, and …

Explains Scrum’s core values, roles, artifacts, and events, highlighting how they support teamwork, transparency, and adaptability in managing complex …

Explores and corrects common misconceptions about Scrum, clarifying its true principles, events, planning, and governance to help teams adopt Agile …

Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage …

Scrum Teams uphold, not lower, quality by strictly following and evolving the Definition of Done, ensuring predictable releases and reducing technical …

Scrum Teams must consistently meet a clear, non-negotiable Definition of Done to ensure quality, manage risk, and prevent technical debt in every …

The end of a Sprint is a checkpoint for review and adaptation, not a deadline. Focus on flow, learning, and continuous improvement over strict task …

Explains how a Scrum Master drives team improvement, removes obstacles, and leads organisational change, going far beyond basic facilitation or …

Scrum can drive organisational change, not just product features, by using backlogs, teams, and feedback to enable real, evidence-based agility across …

Evidence-Based Management (EBM) is a strategy for improving an organisation’s ability to deliver value by making decisions based on evidence, not …

Explores how fear hinders true agility in teams, emphasising the need to foster courage and trust for effective Agile, Scrum, and DevOps practices and …

Discover why experienced Scrum practitioners often misunderstand core principles, and how revisiting Scrum fundamentals restores clarity, agility, and …

Explains why consistent delivery of usable increments is essential in Scrum, highlighting the Scrum Master's accountability for ensuring transparency, …

Combined Scrum Master and Product Owner training covering Agile mindset, Scrum framework, value delivery, backlog management, and certification exam …

Explains how true self-management in Scrum requires active, disciplined effort from Product Owners, Scrum Masters, and Developers, not chaos or lack …

Explains how Scrum reveals team dysfunctions by clarifying roles and accountability, highlighting its purpose to expose issues that hinder value …

Answers common questions about integrating design and UX work into Scrum Sprints, clarifying why dedicated Design Sprints aren’t needed and how to …

Explores why Scrum Masters need authority, not just influence, to enforce Agile practices, remove blockers, and ensure teams follow Scrum for true …

Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in your team.

Explains how true quality improvement needs both tools and a culture of safety, using Toyota’s andon cord as a lesson for Agile and Scrum adoption in …

Explains how effective Scrum Masters empower teams through facilitation, support, and coaching, moving away from authority and micromanagement to …

Highlights the importance of technical knowledge for Scrum Masters, arguing that understanding team-specific skills is essential to effectively …

Many agile transformations restrict team autonomy, leading to control and compliance instead of true ownership, adaptability, and meaningful …

Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, compliance, …

Unlock your team's true potential—discover why a powerful definition of done drives real business impact, customer value, and lasting competitive …

Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, defect-free, and …

The Definition of Done can evolve to improve quality but should not be weakened or vary per backlog item. Consistency ensures transparency and …

Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and predictability in …

Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum Masters better …

Many Scrum Masters lack essential skills and experience, leading to poor agile outcomes. True competence requires deep knowledge, practical …

Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum …

Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent delivery of …

Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in complex …

Explores how focusing on Scrum’s core principles—empiricism, transparency, and value delivery—leads to true agile success, beyond just following …

Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure effective …

Learn practical strategies for overcoming common challenges in scaling Scrum, based on hands-on insights from the Scaled Professional Scrum course and …

Discover how the Advanced PSM course helps Scrum Masters shift from admin tasks to empowering teams, supporting Product Owners, and tackling …

Explores key qualities of an effective Scrum Master, focusing on team empowerment, backlog management, collaboration, and removing organisational …

Explores common misconceptions about the Scrum Master role, highlighting the shift from tool admin to empowering leader who fosters team autonomy, …

Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective self-management, …

Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges of …

Learn essential principles for effective Sprint planning in Agile, including understanding the product backlog, setting clear goals, and fostering …

Explains how involving everyone in Professional Scrum training fosters organisational agility, breaks down silos, and empowers teams to drive …