<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Professional Scrum on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/</link>
		<description>Recent content in Professional Scrum on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</link>
				<pubDate>Mon, 22 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</guid>
				<description>Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control.</description>
			</item>
			<item>
				<title>The Definition of Done is a Commitment to Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</link>
				<pubDate>Wed, 07 May 2025 11:46:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</guid>
				<description>Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact.</description>
			</item>
			<item>
				<title>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</link>
				<pubDate>Wed, 21 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</guid>
				<description>Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence.</description>
			</item>
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</guid>
				<description>The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications.</description>
			</item>
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>Scrum Teams don’t set the bar for quality, they meet it</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/</link>
				<pubDate>Thu, 03 Apr 2025 15:30:01 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/</guid>
				<description>Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict, non-negotiable measure of what is releasable. Weakening or fluctuating the DoD increases risk and technical debt, undermining quality and predictability. Development managers should ensure their teams consistently strengthen the DoD over time rather than lowering it to deliver more features.</description>
			</item>
			<item>
				<title>Definition of Done - Objective vs Subjective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</link>
				<pubDate>Wed, 16 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</guid>
				<description>Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage.</description>
			</item>
			<item>
				<title>Delivery is the only Measure of Progress in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</link>
				<pubDate>Mon, 03 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</guid>
				<description>Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</link>
				<pubDate>Wed, 18 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</guid>
				<description>A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility.</description>
			</item>
			<item>
				<title>Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</link>
				<pubDate>Wed, 09 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</guid>
				<description>Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success.</description>
			</item>
			<item>
				<title>How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</link>
				<pubDate>Wed, 25 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</guid>
				<description>You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready.</description>
			</item>
			<item>
				<title>Scrum doesn’t stop you from optimising flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it.</description>
			</item>
			<item>
				<title>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</link>
				<pubDate>Thu, 05 Sep 2024 11:14:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</guid>
				<description>Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness.</description>
			</item>
			<item>
				<title>Professional Scrum teams build software that works</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</guid>
				<description>Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization&amp;rsquo;s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training.</description>
			</item>
			<item>
				<title>The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</link>
				<pubDate>Thu, 01 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</guid>
				<description>Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change.</description>
			</item>
			<item>
				<title>Can the Definition of Done change per Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</link>
				<pubDate>Mon, 14 Oct 2019 13:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</guid>
				<description>The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint.</description>
			</item>
			<item>
				<title>The Scrum Master is accountable for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>Toyota &#34;andon&#34; cord lets any worker stop production to fix defects</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</link>
				<pubDate>Mon, 12 May 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</guid>
				<description>Giving teams tools like Scrum events or defect reporting only works if you also create a culture where people feel safe to speak up and address problems. Without psychological safety and genuine empowerment, process changes alone will not lead to real improvement. Development managers should focus on building trust and openness so teams feel comfortable raising issues.</description>
			</item>
			<item>
				<title>I do continuous deliver, why should I Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</guid>
				<description>Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible.</description>
			</item>
			<item>
				<title>Executives want predictability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</link>
				<pubDate>Mon, 31 Mar 2025 15:30:08 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</guid>
				<description>If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating &amp;ldquo;Done&amp;rdquo; as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments.</description>
			</item>
			<item>
				<title>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</link>
				<pubDate>Wed, 16 Oct 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</guid>
				<description>There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone.</description>
			</item>
			<item>
				<title>The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</link>
				<pubDate>Mon, 21 Oct 2024 05:32:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</guid>
				<description>Scrum Masters need deep knowledge of both agile practices and the technical work of their teams to drive real improvement in product delivery. Without this competence, teams stagnate and fail to deliver business value, while skilled Scrum Masters elevate team capabilities and outcomes. Development managers should ensure their Scrum Masters have practical expertise, not just facilitation skills, to maximize team impact.</description>
			</item>
			<item>
				<title>Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</link>
				<pubDate>Wed, 23 Apr 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</guid>
				<description>When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement.</description>
			</item>
			<item>
				<title>A changing Definition of Done undermines quality and predictability in teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/</link>
				<pubDate>Fri, 04 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/</guid>
				<description>Frequently changing the Definition of Done makes it hard for teams to deliver predictable results and maintain quality. The Definition of Done should only evolve to raise standards, not lower them. To improve predictability and quality, keep your Definition of Done consistent and ensure it is followed.</description>
			</item>
			<item>
				<title>Hiring a Professional Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</link>
				<pubDate>Mon, 15 Mar 2021 14:11:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</guid>
				<description>Hiring a Scrum Master is challenging and requires someone who can lead, coach, and support both the team and organization to improve effectiveness and adopt Scrum practices. Key requirements include strong leadership, facilitation, and communication skills, a servant leadership mindset, and relevant certifications, with technical or business domain knowledge as a plus. Focus on candidates who can foster a safe, collaborative environment and drive continuous improvement for reliable product delivery.</description>
			</item>
			<item>
				<title>If every release feels high-risk, you lack a true Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</link>
				<pubDate>Sat, 05 Apr 2025 15:30:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</guid>
				<description>If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team&amp;rsquo;s process to make releases predictable and low-stress.</description>
			</item>
			<item>
				<title>Why compromising on software quality is a leadership decision</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/</link>
				<pubDate>Tue, 01 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/</guid>
				<description>Compromising on software quality is a leadership decision, not a team one, and lowering standards to meet deadlines carries business risks that should be explicitly approved by leadership. A clear Definition of Done helps maintain consistent quality, and any decision to reduce it should be transparent and deliberate. Development managers should ensure quality expectations are set and upheld at the leadership level, not left to teams under delivery pressure.</description>
			</item>
			<item>
				<title>Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</link>
				<pubDate>Thu, 04 Jan 2024 12:14:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</guid>
				<description>Relying on special Sprints like Sprint Zero or bug fix Sprints undermines true Agile practices by encouraging risky behavior, diluting focus, and creating a false sense of security. Teams should instead prioritize delivering a usable product at the end of every Sprint, foster accountability, and integrate quality assurance into regular work. Development managers should avoid safety nets and focus on continuous improvement and value delivery each Sprint.</description>
			</item>
			<item>
				<title>Are technical skills required to be a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</link>
				<pubDate>Sun, 01 Sep 2019 15:37:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</guid>
				<description>Technical skills are not strictly required to be a Scrum Master, but having a solid understanding of technical, business, and organizational contexts makes a Scrum Master much more effective. Mastery in these areas helps Scrum Masters better support their teams, guide Product Owners, and drive meaningful organizational change. Development managers should ensure their Scrum Masters are equipped with broad contextual knowledge to maximize team and business value.</description>
			</item>
			<item>
				<title>The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 16:30:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</guid>
				<description>Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings.</description>
			</item>
			<item>
				<title>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</link>
				<pubDate>Tue, 13 Sep 2011 20:40:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</guid>
				<description>Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.</description>
			</item>
			<item>
				<title>Pragmatism crushes Dogma in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</link>
				<pubDate>Thu, 21 Mar 2024 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</guid>
				<description>Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Boss to Empowering Facilitator</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</guid>
				<description>The Scrum Master should not act as a boss or micromanager but as a facilitator who empowers the team to self-organise and take ownership of their work. Key points include avoiding micromanagement, focusing on support and facilitation rather than control, and promoting collaboration and continuous learning. Development managers should ensure Scrum Masters adopt a coaching mindset to help teams thrive and deliver better results.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</link>
				<pubDate>Mon, 22 May 2023 14:00:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</guid>
				<description>A Scrum Master is essential for team effectiveness because they guide teams by understanding business needs, technical practices like DevOps, and organisational change. Without this role, teams often struggle to deliver value quickly and improve continuously. Development managers should ensure their teams have access to a skilled Scrum Master or equivalent expertise to maximize productivity and quality.</description>
			</item>
			<item>
				<title>Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</link>
				<pubDate>Thu, 04 Jun 2020 05:33:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</guid>
				<description>Focus on team productivity rather than just feature count, and ensure everyone understands the difference between Definition of Done, which sets quality standards, and acceptance criteria, which specify requirements for each item. Use backlog refinement to address unknowns instead of relying on spikes, and plan sprint capacity to accommodate some ad hoc work while maintaining transparency and continuous improvement. Review your team’s approach to these areas to improve delivery and reduce disruptions.</description>
			</item>
			<item>
				<title>Big Scrum: All you need and not enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</link>
				<pubDate>Wed, 01 Jul 2015 16:33:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</guid>
				<description>Scaling Scrum requires truly professional teams who embody agile values and strong engineering practices, not just following processes superficially. Off-the-shelf frameworks do not fit every organization, so adapting Scrum to your unique context is essential. Focus on building skilled teams, fostering effective communication, and adopting only the practices that support your specific scaling needs.</description>
			</item>
			<item>
				<title>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</link>
				<pubDate>Fri, 09 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</guid>
				<description>Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction.</description>
			</item>
			<item>
				<title>Getting started with a Definition of Done (DoD)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</link>
				<pubDate>Mon, 14 Dec 2020 13:03:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</guid>
				<description>A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what &amp;ldquo;done&amp;rdquo; means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product.</description>
			</item>
			<item>
				<title>A two-day Scrum Master certification doesn’t make you a Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</link>
				<pubDate>Thu, 27 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</guid>
				<description>A two-day Scrum Master certification alone is not enough to prepare someone for the real challenges of leading Scrum Teams and delivering value. Effective Scrum Masters have hands-on experience, understand code quality and DevOps, and have navigated real-world obstacles. Companies should prioritize hiring or developing Scrum Masters with proven experience rather than relying solely on certifications.</description>
			</item>
			<item>
				<title>Mastering Scrum: Essential Insights for New Teams from a Scrum Master&#39;s Journey</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</link>
				<pubDate>Tue, 28 Nov 2023 11:00:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</guid>
				<description>New Scrum teams succeed when they deeply understand Scrum principles, empiricism, and core values, which the Scrum Master should actively teach and reinforce. Practical workshops, real-world examples, and a focus on continuous learning help teams build trust, adapt to change, and improve over time. Development managers should ensure their teams have ongoing support and a safe environment to foster growth and agility.</description>
			</item>
			<item>
				<title>Big Scrum: Are you doing mechanical Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</link>
				<pubDate>Wed, 24 Jun 2015 13:43:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</guid>
				<description>Many organizations adopt Scrum hoping for rapid productivity gains but are disappointed when they only follow the motions without embracing its core values and technical excellence. True effectiveness and faster delivery come from practicing Professional Scrum, which means living the principles and focusing on quality, not just the framework. Development managers should ensure their teams go beyond mechanical Scrum and invest in building a professional culture to achieve real results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</link>
				<pubDate>Fri, 25 Oct 2024 07:02:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</guid>
				<description>Many Scrum Masters misunderstand their true responsibilities, focusing on tools and rituals instead of the core principles and accountabilities defined by Scrum. Effective Scrum Masters balance support for the team, Product Owner, and organisation, acting as coaches and mentors rather than process enforcers. Development managers should ensure Scrum Masters are competent in Scrum’s philosophies and adapt practices to fit their context, not just follow common routines.</description>
			</item>
			<item>
				<title>Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</link>
				<pubDate>Fri, 28 Apr 2023 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</guid>
				<description>Focusing on Scrum rituals instead of its core principles, empiricism, transparency, and delivering value, can hinder true agile success. Overemphasis on mechanics leads to misplaced priorities, reduced creativity, and lower team engagement. Development managers should encourage open dialogue, support experimentation, and regularly assess whether practices are truly delivering value, adapting or discarding those that do not.</description>
			</item>
			<item>
				<title>If your backlog is not refined then you are doing it wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</link>
				<pubDate>Thu, 17 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</guid>
				<description>If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints.</description>
			</item>
			<item>
				<title>Too many Scrum Masters believe they don’t need technical skills</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/</link>
				<pubDate>Mon, 24 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/</guid>
				<description>Scrum Masters need relevant technical and domain knowledge to effectively support their teams, not just certifications. Without understanding the specific challenges and practices of their team&amp;rsquo;s work, they cannot truly enable success. Development managers should ensure Scrum Masters have or develop the necessary expertise to make a meaningful impact.</description>
			</item>
			<item>
				<title>Scrum Masters and Product Owners are held accountable for results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</link>
				<pubDate>Mon, 17 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</guid>
				<description>Scrum Masters and Product Owners are often held accountable for results without having the authority needed to influence outcomes. This mismatch leads to empty expectations and limits team effectiveness. To achieve better results, organisations should empower Scrum Masters with real authority, not just expect them to coach from the sidelines.</description>
			</item>
			<item>
				<title>let-us be blunt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</guid>
				<description>Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability.</description>
			</item>
			<item>
				<title>Here the dirty secret behind many agile transformations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</link>
				<pubDate>Fri, 02 May 2025 15:30:32 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</guid>
				<description>Many agile transformations fail because organizations maintain tight control over how work is done while claiming to empower teams. True agility requires leadership to set clear goals and priorities but let teams decide how to achieve them. To foster commitment and improvement, review where your processes still dictate the how and shift toward real team autonomy.</description>
			</item>
			<item>
				<title>How effectively does an APS prepare a team to do a solid, professional Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</link>
				<pubDate>Sat, 12 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</guid>
				<description>The Applied Professional Scrum (APS) course helps teams focus on delivering a working product every iteration and sheds unhelpful habits that slow progress. Through practical exercises like the &amp;ldquo;Barnacle Exercise,&amp;rdquo; teams identify and remove outdated practices, leading to more effective Scrum adoption. Development managers should consider APS to build teams that consistently deliver value and embody true Scrum principles.</description>
			</item>
			<item>
				<title>Professional Scrum Developer (.NET) Training in London</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</link>
				<pubDate>Fri, 18 Jun 2010 15:53:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</guid>
				<description>Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies.</description>
			</item>
			<item>
				<title>Fear is the real enemy of agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/</link>
				<pubDate>Wed, 07 May 2025 15:30:42 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/</guid>
				<description>Fear blocks true agility and leads to stagnation, regardless of how many Agile practices you follow. The main job of leaders is to remove fear so teams can learn, adapt, and deliver value. Focus on creating an environment where people feel safe to speak up and take risks.</description>
			</item>
			<item>
				<title>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</link>
				<pubDate>Wed, 05 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</guid>
				<description>Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</link>
				<pubDate>Fri, 13 Sep 2024 07:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</guid>
				<description>Evidence-based management in Scrum focuses on four key value areas, current value, unrealized value, ability to innovate, and time to market, to guide data-driven decisions and balance innovation with stability. Tracking metrics in these areas helps teams improve customer satisfaction, identify growth opportunities, manage technical debt, and speed up delivery. Development managers should start measuring these areas to align teams with evidence-based management and drive sustainable product success.</description>
			</item>
			<item>
				<title>Decoding Scrum Team Work: Balancing Sprint and Refinement Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</link>
				<pubDate>Thu, 14 Sep 2023 14:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</guid>
				<description>Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes.</description>
			</item>
			<item>
				<title>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</link>
				<pubDate>Thu, 08 May 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</guid>
				<description>Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives.</description>
			</item>
			<item>
				<title>Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</link>
				<pubDate>Mon, 13 Nov 2023 06:56:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</guid>
				<description>A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk.</description>
			</item>
			<item>
				<title>Stop treating the end of the Sprint like a finish line</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</link>
				<pubDate>Thu, 05 Jun 2025 15:30:54 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</guid>
				<description>The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation.</description>
			</item>
			<item>
				<title>Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</link>
				<pubDate>Tue, 23 Aug 2022 16:53:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</guid>
				<description>The Scaled Professional Scrum course helps teams address common challenges in scaling Scrum, such as managing cross-team dependencies, maintaining self-management, and ensuring transparency. Through hands-on, interactive sessions, participants gain practical techniques and tools to structure and manage large agile projects effectively. Development managers looking to scale Scrum without unnecessary overhead should consider this course to equip their teams with proven practices and ongoing support.</description>
			</item>
			<item>
				<title>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</guid>
				<description>Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback.</description>
			</item>
			<item>
				<title>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>The Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</guid>
				<description>A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems.</description>
			</item>
			<item>
				<title>Why Every Scrum Master Needs an Immersive Training Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</link>
				<pubDate>Tue, 21 Nov 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</guid>
				<description>Immersive training is essential for Scrum Masters who already have hands-on experience, as it deepens practical skills, sharpens leadership abilities, and drives better team outcomes. Unlike standard courses, immersive classes focus on real-world challenges, immediate feedback, and peer learning, helping Scrum Masters maximize team value and effectiveness. Development managers should encourage experienced Scrum Masters to pursue immersive training to foster continuous improvement and stronger team leadership.</description>
			</item>
			<item>
				<title>Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</link>
				<pubDate>Mon, 06 Mar 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</guid>
				<description>Many Scrum Masters focus too much on administrative tasks like Jira management instead of empowering their teams and supporting the Product Owner and organization. The Advanced PSM course highlights the importance of enabling team accountability, facilitating value delivery, and addressing organizational barriers. Development managers should encourage Scrum Masters to move beyond admin work and focus on building team capability and organizational agility.</description>
			</item>
			<item>
				<title>What is the hardest part of working with a brand-new scrum team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</link>
				<pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</guid>
				<description>The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement.</description>
			</item>
			<item>
				<title>Professional Scrum is for everyone in your organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</link>
				<pubDate>Tue, 16 Jan 2018 13:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</guid>
				<description>Scrum works best when everyone in the organisation is involved, not just the development teams, as this breaks down old management habits and empowers people at all levels to contribute to value delivery. Training all staff together surfaces misconceptions, encourages open discussion, and creates a shared understanding that drives real change. To maximise the benefits, managers should ensure broad participation in Scrum training and use the resulting organisational change backlog to remove barriers to effective software delivery.</description>
			</item>
			<item>
				<title>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>Challenging Misconceptions About Behaviour in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</link>
				<pubDate>Thu, 13 Feb 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</guid>
				<description>Agile is often misused to justify poor planning and lack of accountability, but true agility demands more discipline, professionalism, and clear alignment with the product vision. Teams that fail to deliver usable increments or start work without sufficient understanding are not practicing real Agile. Development managers should ensure their teams uphold high standards and address unprofessional behavior rather than excusing it as Agile.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</link>
				<pubDate>Tue, 24 Oct 2023 06:50:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</guid>
				<description>Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars.</description>
			</item>
			<item>
				<title>How does the APS course help people apply scrum effectively?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</link>
				<pubDate>Wed, 18 Jan 2023 08:57:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</guid>
				<description>The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption.</description>
			</item>
			<item>
				<title>Story Points &amp; Velocity are a sign of an unsuccessful team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</link>
				<pubDate>Mon, 04 Jan 2021 14:20:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</guid>
				<description>Story points and velocity are not required by Scrum and relying on them long-term signals a team&amp;rsquo;s lack of maturity and adaptability. While they can help new teams start conversations and build shared understanding, they do not provide real predictability or confidence in delivery. Development managers should focus on transparency, concrete data, and metrics like cycle time to build true confidence and improve predictability for stakeholders.</description>
			</item>
			<item>
				<title>How Top Scrum Masters Are Selected by Their Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/</link>
				<pubDate>Wed, 19 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/</guid>
				<description>The most effective Scrum Masters are chosen by their teams based on trust, experience, and proven leadership, not assigned from outside. Teams naturally follow those who have already guided them through challenges and earned their respect. To ensure real impact and avoid resistance, let the team identify who they trust to lead as Scrum Master.</description>
			</item>
			<item>
				<title>Sprint Review #1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>Great Scrum Masters and Product Owners don’t micromanage</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</link>
				<pubDate>Sun, 23 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</guid>
				<description>Effective Scrum Masters and Product Owners avoid micromanaging by providing clear direction, supporting team autonomy, and ensuring accountability. Teams perform best when they understand the vision and operate within a structured framework that balances freedom with alignment. Leaders should focus on removing obstacles and maintaining this balance to enable true agility; consider how your organization supports both autonomy and structure.</description>
			</item>
			<item>
				<title>Hiring a Scrum Master is hard</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</link>
				<pubDate>Sun, 16 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</guid>
				<description>Hiring a Scrum Master is challenging because many organizations misunderstand the role and focus on the wrong qualifications. A strong Scrum Master needs deep knowledge of Scrum, the ability to drive team effectiveness, and enough technical understanding to support your teams and foster change. Look for candidates who demonstrate commitment, challenge assumptions, and coach teams to deliver real value, not just those with certifications or project management backgrounds.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Misconceptions to Empowering Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</link>
				<pubDate>Fri, 12 May 2023 14:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</guid>
				<description>The Scrum Master role is often misunderstood as tool administration or problem-solving, but its true value lies in empowering teams to self-organize and operate independently. Key insights include fostering team autonomy, guiding rather than controlling, and committing to continuous learning. Development managers should support Scrum Masters in becoming facilitators who enable teams to thrive without constant oversight.</description>
			</item>
			<item>
				<title>“Teams are self-managing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</link>
				<pubDate>Fri, 21 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</guid>
				<description>Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance.</description>
			</item>
			<item>
				<title>Balance of Leadership and Control in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</link>
				<pubDate>Mon, 17 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</guid>
				<description>Scrum Masters and Product Owners are expected to deliver results, so they need both influence and enough authority to remove obstacles, enforce alignment, and ensure accountability. Too much control stifles team autonomy, but too little makes teams ineffective; the right balance depends on the organisation and situation. Development managers should empower these roles with the authority needed to drive change while maintaining team ownership and continuous improvement.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management in Agile: Inform, Don’t Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</link>
				<pubDate>Wed, 11 Sep 2024 13:36:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</guid>
				<description>Evidence-Based Management helps you use data to guide decisions and understand team behaviors, but it should inform rather than control actions. Define clear outcomes, choose metrics that align with those goals, and use data as a conversation starter to uncover challenges and drive improvement. Regularly review metrics with your teams to stay aligned and focus on delivering real value, not just hitting targets.</description>
			</item>
			<item>
				<title>Should the Scrum Master always remove impediments?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/should-the-scrum-master-always-remove-impediments/</link>
				<pubDate>Mon, 23 Sep 2019 18:49:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/should-the-scrum-master-always-remove-impediments/</guid>
				<description>The Scrum Master is responsible for removing impediments, but should only step in when the team cannot resolve the issue themselves. Their focus should be on enabling the team to handle similar problems independently in the future, building self-sufficiency. Development managers should encourage Scrum Masters to coach teams rather than always solving problems for them.</description>
			</item>
			<item>
				<title>Professional Scrum Training for the Ghana Police Service</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</link>
				<pubDate>Mon, 30 Oct 2017 19:26:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</guid>
				<description>The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>Everyone loves the idea of self-managing teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</link>
				<pubDate>Tue, 18 Mar 2025 09:51:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</guid>
				<description>Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability.</description>
			</item>
			<item>
				<title>My journey into Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</link>
				<pubDate>Wed, 04 Feb 2015 10:53:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</guid>
				<description>Professional Scrum has been key to my success in software development and consulting, showing that most team challenges are cultural rather than technical. Building professional, adaptable individuals and teams leads to greater business agility and consistent delivery of valuable software. Avoid one-size-fits-all approaches to scaling Scrum; instead, tailor frameworks and practices to your organisation’s unique culture and needs.</description>
			</item>
			<item>
				<title>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>No one questions a Product Owner authority</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</link>
				<pubDate>Wed, 19 Mar 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</guid>
				<description>Product Owners are trusted with authority to make decisions that drive product success, but Scrum Masters often lack similar authority despite being responsible for team effectiveness and removing obstacles. Relying only on persuasion limits their impact; Scrum Masters need the power to enforce good practices and address issues directly. Development managers should ensure Scrum Masters have the authority needed to fulfill their role and support team agility.</description>
			</item>
			<item>
				<title>Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</link>
				<pubDate>Mon, 06 May 2024 14:12:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</guid>
				<description>Many common beliefs about Scrum, such as it being just meetings, requiring story points, encouraging micromanagement, lacking planning, or having no governance, are misconceptions that hinder its effectiveness. Scrum events are purposeful, story points are optional, teams should self-organise, planning is integral, and governance is flexible to business needs. Development managers should challenge these myths to help teams fully benefit from Agile and deliver greater value.</description>
			</item>
			<item>
				<title>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</link>
				<pubDate>Fri, 26 May 2023 14:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</guid>
				<description>Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes.</description>
			</item>
			<item>
				<title>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</guid>
				<description>A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>Why the Scrum Master’s True Power Lies in Influence, Not Authority</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/</link>
				<pubDate>Fri, 15 Sep 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/</guid>
				<description>The Scrum Master’s effectiveness comes from their ability to influence and build trust within the team, not from formal authority. By consistently providing value and fostering a collaborative environment, they help teams thrive and drive continuous improvement. Development managers should focus on supporting Scrum Masters in developing their leadership and relationship-building skills rather than granting them traditional authority.</description>
			</item>
			<item>
				<title>Daily Scrum Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</guid>
				<description>Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals.</description>
			</item>
			<item>
				<title>Understanding the True Role of a Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</link>
				<pubDate>Tue, 28 Nov 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</guid>
				<description>The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement.</description>
			</item>
			<item>
				<title>Scrum isn’t limited to building features</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</link>
				<pubDate>Fri, 30 May 2025 15:30:41 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</guid>
				<description>Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Unlocking the Scrum Master&#39;s Potential: Embracing Broader Responsibilities for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</guid>
				<description>Scrum Masters have a broader responsibility beyond supporting their teams; they also need to engage with the Product Owner and the wider organisation to remove obstacles and drive agility. Encouraging Scrum Masters to question outdated processes and model collaborative behaviours can lead to meaningful organisational change. Development managers should empower Scrum Masters to challenge the status quo and support their growth in these expanded roles.</description>
			</item>
			<item>
				<title>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</link>
				<pubDate>Mon, 11 Jan 2021 14:36:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</guid>
				<description>The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.</description>
			</item>
			<item>
				<title>Design Sprints in Scrum: Common Questions and Practical Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</link>
				<pubDate>Wed, 04 Jun 2025 15:31:05 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</guid>
				<description>There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.</description>
			</item>
			<item>
				<title>Scrum Myth Debunked: Unfinished Work is Allowed in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</link>
				<pubDate>Sat, 24 May 2025 15:30:17 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</guid>
				<description>Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries.</description>
			</item>
			<item>
				<title>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</link>
				<pubDate>Wed, 26 Mar 2025 16:30:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</guid>
				<description>Product Owners should be empowered as strategic leaders who drive product vision and business value, not just manage backlogs. Scrum Masters play a key role in coaching Product Owners to use customer insights and data for better decisions. Development managers should ensure Product Owners have the authority and support to lead effectively, rather than treating them as task managers.</description>
			</item>
			<item>
				<title>What will you learn on the professional scrum master course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</link>
				<pubDate>Thu, 19 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</guid>
				<description>The Professional Scrum Master course teaches the theory and practical skills needed to be an effective scrum master, focusing on serving developers, product owners, and the organization to maximize team value. Participants learn through real-world examples, discussions, and case studies about empiricism, delivering working increments each sprint, and overcoming common challenges. Development managers should consider this course to strengthen their teams&amp;rsquo; ability to deliver value and navigate complexity.</description>
			</item>
			<item>
				<title>If you could teach just one thing about Scrum, what would it be?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</link>
				<pubDate>Mon, 27 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</guid>
				<description>The most important thing to teach about Scrum is the principle of empiricism, which means making work transparent, inspecting progress frequently, and adapting based on what is learned. This approach helps teams navigate complex, uncertain environments where traditional project management falls short. Focus on building your team&amp;rsquo;s ability to learn and adapt quickly, as Scrum reveals problems but does not solve them for you.</description>
			</item>
			<item>
				<title>Unlocking Your Potential: Transformative Training for Aspiring Scrum Masters</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-your-potential-transformative-training-for-aspiring-scrum-masters/</link>
				<pubDate>Wed, 27 Jul 2022 18:45:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-your-potential-transformative-training-for-aspiring-scrum-masters/</guid>
				<description>Effective Scrum Master training combines interactive workshops, supplementary learning, and ongoing community support to build deep understanding and practical skills. Participants benefit from hands-on activities, access to assessments, and regular engagement with peers and trainers, which helps them apply Scrum principles in real-world settings. Investing in such training empowers Scrum Masters to foster collaboration and continuous improvement, so consider supporting your team’s development through similar opportunities.</description>
			</item>
			<item>
				<title>Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 06:00:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</guid>
				<description>Unrealised value, or the features your users need but you have not built or identified yet, is often overlooked but crucial for product success. To unlock this value, focus on understanding your users, validate assumptions with small experiments before full development, and increase deployment frequency to speed up feedback and learning. Make it a priority to continuously learn from your market and adapt your product strategy to stay relevant and maximise impact.</description>
			</item>
			<item>
				<title>Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</link>
				<pubDate>Tue, 18 Oct 2022 16:13:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</guid>
				<description>Scrum is a flexible framework that helps teams deliver value through transparency, clear roles, and structured events, all grounded in trust and five core values. Key elements include defined accountabilities, essential artifacts for decision-making, and regular events to inspect and adapt work. To get the most from Scrum, focus on building trust, maintaining transparency, and continuously improving team processes.</description>
			</item>
			<item>
				<title>Nexus Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</link>
				<pubDate>Fri, 31 Mar 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</guid>
				<description>The difference between a new and professional Scrum Master is less about labels and more about embracing accountability and a mindset focused on team effectiveness and value creation. Regardless of experience, a Scrum Master should guide the team, remove obstacles, and drive continuous improvement rather than micromanage. Development managers should support Scrum Masters in adopting a professional approach that prioritises team impact and organisational value.</description>
			</item>
			<item>
				<title>Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</link>
				<pubDate>Mon, 09 Jan 2023 12:36:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</guid>
				<description>Teaching Scrum through hands-on experience, including using Minecraft, helps participants move from initial chaos to a clear understanding of Scrum’s value. Students first experience confusion similar to real project starts, then learn to apply Scrum principles, leading to practical insights and improved teamwork. Development managers should consider experiential learning to help teams internalise agile practices and appreciate their real-world benefits.</description>
			</item>
			<item>
				<title>Maximising Value from Applying Professional Scrum Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</link>
				<pubDate>Mon, 09 Jun 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</guid>
				<description>The main benefit of Professional Scrum training is not just learning Scrum, but creating a clear list of organisational obstacles that slow delivery. When teams are empowered to identify these issues and leadership commits to addressing them, real transformation can begin. Development managers should ensure their teams have a change backlog and actively work with leadership to remove barriers.</description>
			</item>
			<item>
				<title>Scrum Masters: Why Influence Alone May Not Be Enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</link>
				<pubDate>Thu, 20 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</guid>
				<description>Relying only on influence limits a Scrum Master&amp;rsquo;s ability to drive real change, especially when teams or leaders resist Agile practices. Sustainable agility needs Scrum Masters who can enforce the framework, remove obstacles, and hold teams accountable, not just suggest improvements. Development managers should ensure Scrum Masters have enough authority to lead effectively, not just influence.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Essential Skills for Product Owners</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</link>
				<pubDate>Mon, 18 Dec 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</guid>
				<description>Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently.</description>
			</item>
			<item>
				<title>Say-Do Metrics: Avoiding Agile Banditry in Your Organization</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</link>
				<pubDate>Fri, 05 Jan 2024 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</guid>
				<description>Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change.</description>
			</item>
			<item>
				<title>Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</link>
				<pubDate>Wed, 18 Nov 2020 16:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</guid>
				<description>The 2020 update to the Scrum Guide simplifies language and reduces prescriptive rules, emphasizing that Scrum Teams are self-managing and collectively accountable for delivering value each Sprint. Key changes include clear commitments for Product Goal, Sprint Goal, and Definition of Done, as well as a focus on cross-functional teams and improved Sprint Planning. Development managers should review the new guide to align their teams with these streamlined practices.</description>
			</item>
			<item>
				<title>How do you handle conflict in a Scrum Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</link>
				<pubDate>Mon, 07 Oct 2019 16:32:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</guid>
				<description>When conflict arises in a Scrum Team, first encourage the team to resolve it themselves and use facilitation techniques that ensure everyone is heard, such as structured group discussions. The Scrum Master should coach team members and escalate only if necessary, involving HR or considering team changes as a last resort. Focus on building conflict resolution skills within the team and iteratively adapt your approach to find the best solution.</description>
			</item>
			<item>
				<title>What should be top of mind when a Scrum team prepare for a Sprint review?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</link>
				<pubDate>Mon, 04 Sep 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</guid>
				<description>To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency.</description>
			</item>
			<item>
				<title>Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/</link>
				<pubDate>Mon, 20 Nov 2023 07:51:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/</guid>
				<description>Immersive Professional Scrum Master training enables deeper learning by encouraging participants to question existing practices, apply new strategies, and collaborate with peers from diverse backgrounds. This approach helps Scrum Masters tackle real-world challenges, uncover organisational barriers, and continuously improve their methods. Consider enrolling in immersive training to foster a culture of reflection and shared problem-solving within your teams.</description>
			</item>
			<item>
				<title>One critical skill for a Scrum Master and why?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/one-critical-skill-for-a-scrum-master-and-why/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/one-critical-skill-for-a-scrum-master-and-why/</guid>
				<description>The most important skill for a Scrum Master is effective teaching, especially helping teams understand the reasons behind Agile practices rather than just the mechanics. When Scrum Masters focus on teaching the &amp;lsquo;why,&amp;rsquo; teams become more engaged, motivated, and open to change. Development managers should encourage Scrum Masters to develop strong teaching abilities to drive successful Agile transformation.</description>
			</item>
			<item>
				<title>David thought he already knew Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</link>
				<pubDate>Mon, 26 May 2025 15:30:28 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</guid>
				<description>Even experienced teams often fall into old habits and misunderstand Scrum, leading to ineffective practices that only look agile on the surface. Regularly revisiting the fundamentals and purpose of Scrum helps prevent complacency and ensures real improvement. Consider challenging your team&amp;rsquo;s understanding of Scrum to maintain true agility and drive meaningful change.</description>
			</item>
			<item>
				<title>What is Sprint Planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</link>
				<pubDate>Wed, 24 May 2023 14:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</guid>
				<description>Sprint planning is a team meeting to align on what will be accomplished in the next sprint, ensuring everyone understands the goals and priorities, including new features, technical debt, and unexpected work. It provides clarity, flexibility, and a shared sense of direction, whether you use Scrum or Kanban. Make sure your team uses sprint planning to regularly evaluate priorities and maintain alignment for better outcomes.</description>
			</item>
			<item>
				<title>Is a PSM II certification validation of your skills, or does it develop your skill and capability as a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</link>
				<pubDate>Mon, 17 Apr 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</guid>
				<description>The PSM II course is designed to develop your skills and capabilities as a Scrum Master, not just validate what you already know. The class focuses on advanced facilitation techniques and deepens your understanding of Scrum Master accountability to the team, Product Owner, and organization. If you want to grow as a Scrum Master and apply practical tools with your teams, attending the course is recommended over just taking the assessment.</description>
			</item>
			<item>
				<title>The Myth of Knowing Everything Upfront in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</link>
				<pubDate>Mon, 16 Jun 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</guid>
				<description>You cannot know everything upfront in software development, so focus on continuous discovery and adapt as you learn. Scrum supports this by encouraging just enough planning and design to move forward, then delivering and learning from real use. Prioritise delivery and feedback over excessive upfront design to create more value.</description>
			</item>
			<item>
				<title>Agile and Scrum are often misunderstood</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</link>
				<pubDate>Sun, 04 May 2025 15:30:30 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</guid>
				<description>Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team&amp;rsquo;s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance.</description>
			</item>
			<item>
				<title>Unlocking Trust in Scrum: The Power of Openness and Transparency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</guid>
				<description>Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early.</description>
			</item>
			<item>
				<title>How will a PSM II course challenge your assumptions the most?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-will-a-psm-ii-course-challenge-your-assumptions-the-most/</link>
				<pubDate>Mon, 03 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-will-a-psm-ii-course-challenge-your-assumptions-the-most/</guid>
				<description>The PSM II course challenges common misconceptions about the Scrum Master role, showing that it is much more than being a Jira admin or a problem solver; instead, it focuses on empowering teams to be self-sufficient and highlights the value of subtle, behind-the-scenes leadership. The course helps Scrum Masters evolve from basic task facilitators to advanced guides who foster team autonomy and sustainable practices. Development managers should consider this course to deepen their understanding of effective Scrum leadership and drive stronger team performance.</description>
			</item>
			<item>
				<title>Why Copying Scaled Agile Frameworks Fails in Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>Delivering Live Virtual Classes in Microsoft Teams and Mural</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/</link>
				<pubDate>Sun, 21 Jun 2020 21:40:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/</guid>
				<description>Delivering live virtual classes using Microsoft Teams and Mural offers strong security, flexibility, and features that support self-organising teams and foster a safe, collaborative learning environment. Running a tech check before classes saves time and sets expectations, while Teams enables students to manage their own breakout sessions and resources, promoting autonomy and engagement. For best results, set up Teams in advance and use Mural to create structured, interactive exercises that mirror in-person collaboration.</description>
			</item>
			<item>
				<title>Are you doing Scrum? Really?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</link>
				<pubDate>Sat, 19 Nov 2011 16:41:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</guid>
				<description>Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if they are truly following Scrum.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>Why Most Transformations Fail Without Honest Conversations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/</link>
				<pubDate>Thu, 19 Jun 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/</guid>
				<description>Most transformation efforts fail because teams avoid honest conversations about real issues. Creating space for open dialogue leads to genuine improvement and transparency, which are essential for true agility. Development managers should ensure their teams regularly discuss tough topics to drive meaningful change.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations in Alameda, California</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</link>
				<pubDate>Fri, 26 Oct 2012 16:30:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</guid>
				<description>Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles in the development process.</description>
			</item>
			<item>
				<title>What&#39;s in a burndown?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</link>
				<pubDate>Wed, 28 Mar 2012 03:52:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</guid>
				<description>Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.</description>
			</item>
			<item>
				<title>My first Scrum team in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</link>
				<pubDate>Sun, 03 Apr 2011 21:44:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</guid>
				<description>A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.</description>
			</item>
			<item>
				<title>Scrum is not an engineering process</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</link>
				<pubDate>Wed, 21 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</guid>
				<description>Scrum is a framework for fostering collaboration across the whole organisation, not just an engineering process for developers. True agility happens when everyone, regardless of role, understands and participates in Scrum, which helps break down silos and exposes issues that slow delivery. To achieve real change, ensure your entire team is aligned and involved in the conversation about how value is delivered.</description>
			</item>
			<item>
				<title>Most Common Thing You Hear in a PSM 1 Course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/most-common-thing-you-hear-in-a-psm-1-course/</link>
				<pubDate>Wed, 28 Jun 2023 11:00:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/most-common-thing-you-hear-in-a-psm-1-course/</guid>
				<description>Many PSM 1 students justify compromising transparency with clients by citing &amp;ldquo;real world&amp;rdquo; pressures, especially around upfront estimates. The course stresses that maintaining honesty and moral integrity with customers is essential, even when it feels difficult. Development managers should prioritize truth and transparency over convenience to build lasting trust and avoid misleading clients.</description>
			</item>
			<item>
				<title>What is the most common mistake in sprint planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</link>
				<pubDate>Thu, 25 May 2023 14:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</guid>
				<description>The most common mistake in sprint planning is failing to define a clear and tangible sprint goal, which is essential for guiding the team&amp;rsquo;s immediate work and connecting it to the broader product vision. A well-defined sprint goal provides focus, enables actionable stakeholder feedback, and helps the team understand and meet expectations. Development managers should ensure every sprint has a concrete goal that can be evaluated at the sprint review to drive progress and alignment.</description>
			</item>
			<item>
				<title>Quotes: Don&#39;t scale Scrum! Pragmatic or defeatist?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</link>
				<pubDate>Mon, 09 Oct 2023 14:30:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</guid>
				<description>The idea that Scrum cannot be scaled is a misconception; frameworks like Nexus show that Scrum can be effectively scaled to deliver greater value. Key recommendations include understanding Nexus, starting with a single team, and scaling thoughtfully while adapting as you go. Development managers should explore scaling options rather than dismissing them, as successful scaling is both possible and beneficial.</description>
			</item>
			<item>
				<title>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</guid>
				<description>Hiring a professional Product Owner is increasingly valued, with companies seeking external candidates who bring fresh perspectives and strong business understanding. The Product Owner is accountable for maximizing product value by setting vision, managing stakeholders, collaborating with teams, making key decisions, and using evidence-based approaches to drive outcomes. Ensure candidates have both certification and practical experience, but remember that while responsibilities can be delegated, ultimate accountability always remains with the Product Owner.</description>
			</item>
			<item>
				<title>Navigating the Future with a Fine-Tuned Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</link>
				<pubDate>Thu, 10 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</guid>
				<description>A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery.</description>
			</item>
			<item>
				<title>What is the most common Aha moment people have in a scrum course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</link>
				<pubDate>Fri, 03 Mar 2023 07:15:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</guid>
				<description>The most common realization in scrum courses is understanding the deep purpose behind each element of the scrum framework, especially its foundation in empiricism, rather than just following procedures. Many experienced practitioners discover they have been missing the true value of scrum by not connecting its events and artefacts to their intended outcomes. To unlock high performance, teams should focus on mastering the fundamentals and intentionally applying scrum’s principles, not just its mechanics.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</link>
				<pubDate>Wed, 30 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</guid>
				<description>Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs.</description>
			</item>
			<item>
				<title>Can organisations run an Applying Professional Scrum workshop? How would that help them?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</link>
				<pubDate>Wed, 29 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>Most companies still get Product Ownership wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</link>
				<pubDate>Thu, 17 Apr 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</guid>
				<description>Many companies misunderstand the Product Owner role, treating it as simple backlog management or assigning it to any business analyst, which leads to weak products and misaligned teams. Effective Product Owners are strategic leaders who own the vision, make tough decisions, and use evidence to guide development. Development managers should ensure they are hiring or empowering true Product Owners with the right skills and authority, not just filling a position.</description>
			</item>
			<item>
				<title>In Scrum, we don’t do UX separately</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</link>
				<pubDate>Thu, 12 Jun 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</guid>
				<description>UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed.</description>
			</item>
			<item>
				<title>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</link>
				<pubDate>Mon, 24 Feb 2025 07:26:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</guid>
				<description>The idea of a &amp;ldquo;junior Scrum Master&amp;rdquo; is misleading because the role demands significant experience, technical knowledge, and the ability to navigate complex team and organisational dynamics. Assigning this responsibility to inexperienced team members undermines both individual growth and team effectiveness. Development managers should ensure that Scrum Masters are chosen based on proven competence and relevant experience, not as entry-level positions.</description>
			</item>
			<item>
				<title>The Definition of Done: Ensuring Quality without Compromising Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</link>
				<pubDate>Wed, 27 Sep 2023 09:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</guid>
				<description>The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team&amp;rsquo;s delivery.</description>
			</item>
			<item>
				<title>The Sprint Goal is a commitment for the Sprint Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</link>
				<pubDate>Fri, 27 Nov 2020 13:09:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</guid>
				<description>The Sprint Goal is a clear, single objective for each Sprint that guides the team’s focus and aligns their work toward the Product Goal. It is set during Sprint Planning, helps teams adapt their work as needed without losing sight of the main purpose, and should be specific to your business context. Ensure your Product Owner proposes a meaningful Sprint Goal for each Sprint to keep the team aligned and working toward valuable outcomes.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</link>
				<pubDate>Thu, 01 Aug 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</guid>
				<description>Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive.</description>
			</item>
			<item>
				<title>#1 tip for a new Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</link>
				<pubDate>Wed, 17 May 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</guid>
				<description>New Scrum Masters should start by thoroughly reading and understanding the Scrum Guide to grasp the fundamentals of Scrum, including its roles, events, and principles. This foundational knowledge is essential for effectively leading teams, coaching others, and running Agile projects successfully. Make it a priority to master the basics before moving on to more advanced concepts.</description>
			</item>
			<item>
				<title>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</link>
				<pubDate>Wed, 03 Apr 2024 17:21:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</guid>
				<description>Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team&amp;rsquo;s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team&amp;rsquo;s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</link>
				<pubDate>Wed, 21 Jun 2023 11:00:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</guid>
				<description>The Scrum Master is not a manager or authority figure but a servant leader who facilitates team processes, removes obstacles, and encourages autonomy. Misconceptions like expecting status updates or report writing from the Scrum Master undermine team ownership and collaboration. Development managers should empower Scrum Masters to support teams rather than control them, fostering a culture of trust and shared responsibility.</description>
			</item>
			<item>
				<title>How much of an impact can a strong, skilled product owner have?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-much-of-an-impact-can-a-strong-skilled-product-owner-have/</link>
				<pubDate>Mon, 30 Jan 2023 07:30:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-much-of-an-impact-can-a-strong-skilled-product-owner-have/</guid>
				<description>A strong, skilled product owner is critical for turning engineering output into valuable solutions that solve real customer problems and drive business impact. Great product owners look ahead, anticipate market and customer needs, and enable teams to deliver the right features at the right time, avoiding the trap of just building more features. To maximize effectiveness, empower your product owner to focus on strategic value and proactive discovery, not just backlog management.</description>
			</item>
			<item>
				<title>In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</link>
				<pubDate>Mon, 30 Sep 2019 18:35:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</guid>
				<description>When managing multiple Scrum teams in a Nexus, the Product Owner should focus on high-level vision and attend only the Nexus Sprint Planning, delegating detailed planning to designated Team Owners or Area Owners for each team. This approach reduces overload, maintains alignment with the product vision, and relies on strong communication and autonomy within teams. To implement this, assign a representative for each team to handle their Sprint Planning and ensure ongoing coordination with the Product Owner.</description>
			</item>
			<item>
				<title>What is a product owner?    Why are they essential?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-owner-why-are-they-essential/</link>
				<pubDate>Tue, 23 May 2023 14:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-owner-why-are-they-essential/</guid>
				<description>A product owner is essential because they are accountable for maximizing the value delivered by the Scrum team, not just managing the backlog. They ensure alignment between stakeholders, customers, and developers by setting a clear vision and strategy based on market and user insights. To succeed, make sure your product owner is empowered to lead, deeply understands your market, and keeps everyone focused on shared goals.</description>
			</item>
			<item>
				<title>Product Owners are not a myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/product-owners-are-not-a-myth/</link>
				<pubDate>Tue, 18 Oct 2011 01:56:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/product-owners-are-not-a-myth/</guid>
				<description>Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large product backlogs effectively.</description>
			</item>
			<item>
				<title>Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</link>
				<pubDate>Thu, 25 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</guid>
				<description>Evidence-based management helps leaders make better decisions by focusing on meaningful metrics that drive real business value, such as current and unrealised value, time to market, and ability to innovate. Regularly reviewing and tailoring these metrics to your organisation enables data-driven strategies and a clear competitive advantage. Consider adopting this approach to move beyond gut feelings and ensure your team delivers measurable results.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Hiring a Product Owner? Avoid copying job specs from the internet</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/</link>
				<pubDate>Tue, 15 Apr 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/</guid>
				<description>When hiring a Product Owner, do not rely on generic job descriptions; a true Product Owner drives product success by setting vision, prioritizing value, collaborating closely with teams, making data-driven decisions, and maintaining accountability. Delegation is necessary, but the PO must remain responsible for outcomes, not just manage tasks. Review your job specs to ensure they focus on leadership and product impact, not just administrative duties.</description>
			</item>
			<item>
				<title>Sprint Planning Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</guid>
				<description>Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders.</description>
			</item>
			<item>
				<title>A great Product Owner drives product strategy, not just manages the backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/</link>
				<pubDate>Tue, 08 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/</guid>
				<description>A great Product Owner shapes product strategy by owning the vision, understanding customers and the market, making tough decisions, aligning stakeholders, and adapting based on evidence. Focusing only on backlog management limits their impact; empowered POs drive real value and influence roadmaps. Ensure your Product Owners have the authority and support to make strategic decisions, not just administrative tasks.</description>
			</item>
			<item>
				<title>Can you really commit to delivering work?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</link>
				<pubDate>Sat, 26 Nov 2011 20:24:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</guid>
				<description>Explores why Scrum shifted from &amp;ldquo;commitment&amp;rdquo; to &amp;ldquo;forecasting&amp;rdquo; work delivery, highlighting the risks of overpromising and the benefits of transparency in Agile teams.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</link>
				<pubDate>Mon, 15 Mar 2010 13:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</guid>
				<description>Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.</description>
			</item>
			<item>
				<title>What is a Sprint Backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</link>
				<pubDate>Mon, 29 May 2023 12:01:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</guid>
				<description>The Sprint Backlog is a combination of the Sprint Goal, selected tasks, and a clear plan for achieving them, providing transparency on current work and progress. It should balance goal-driven work with essential tasks like bug fixes, remain flexible to adapt to new needs during the Sprint, and set teams up for achievable success. Development managers should ensure Sprint Goals are realistic and use the Sprint Backlog to maintain focus while staying adaptable.</description>
			</item>
			<item>
				<title>Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-the-professional-scrum-product-owner-course-transforms-your-agile-journey/</link>
				<pubDate>Tue, 23 Aug 2022 17:22:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-the-professional-scrum-product-owner-course-transforms-your-agile-journey/</guid>
				<description>The Professional Scrum Product Owner course provides practical, hands-on training that helps product owners maximise product value, make effective decisions, and adopt modern agile practices. Participants benefit from interactive sessions, ongoing support, and access to a peer community, ensuring skills are applied and developed beyond the classroom. Development managers should consider this course to strengthen product leadership and drive better outcomes in their teams.</description>
			</item>
			<item>
				<title>How critical is a Product Owner in developing a great Product Backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</link>
				<pubDate>Wed, 31 May 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</guid>
				<description>A strong product owner is essential for creating and maintaining a focused, valuable product backlog that aligns with strategy and avoids becoming an unmanageable list of requests. The product owner is fully responsible for prioritizing and communicating the backlog, using discernment to filter out items that do not support the product vision. Development managers should ensure their product owners are empowered and proactive to keep teams focused on delivering real value.</description>
			</item>
			<item>
				<title>Coffee Talk: Introduction to Scrum - webcast event this Friday!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</link>
				<pubDate>Tue, 16 Aug 2011 02:57:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</guid>
				<description>Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking to improve team performance.</description>
			</item>
			<item>
				<title>The Product Goal is a commitment for the Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</link>
				<pubDate>Mon, 23 Nov 2020 14:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</guid>
				<description>The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency.</description>
			</item>
			<item>
				<title>The Importance of Evaluating Direction: Are You Heading the Right Way?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</link>
				<pubDate>Sat, 20 Jan 2024 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</guid>
				<description>Regularly evaluating your direction at every level, developer, product owner, and organization, is essential to avoid wasted effort and ensure you are building the right things for your users. Key insights include aligning work with the product vision, listening to feedback, and being willing to pivot based on data rather than sticking to outdated plans. Make time for honest retrospectives and be ready to change course when needed to achieve better outcomes.</description>
			</item>
			<item>
				<title>Sprint Review</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</link>
				<pubDate>Sun, 11 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</guid>
				<description>The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product&amp;rsquo;s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product&amp;rsquo;s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation.</description>
			</item>
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>Current Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</guid>
				<description>Current Value is a vital metric within Evidence-Based Management that quantifies the real-time value a product or service provides to its users. It includes various indicators such as customer satisfaction, revenue impact, and performance feedback, which together offer insights into the value being realised at any moment. This concept is crucial for teams striving to deliver value in a predictable and sustainable manner, as it facilitates continuous assessment and adjustment based on actual performance rather than assumptions. By tracking Current Value, organisations can make data-driven decisions that improve their offerings and better align them with customer needs. This ongoing evaluation promotes a culture of responsiveness and adaptability, allowing teams to swiftly adjust to feedback and shifting market conditions. Unlike static measures, Current Value is dynamic and systemic, reflecting the changing landscape of customer expectations and business environments. It empowers teams to concentrate on delivering meaningful outcomes, ensuring that their efforts lead to long-term success and customer loyalty. This emphasis on real-time value delivery distinguishes Current Value from other concepts such as Value Stream Management or Customer Satisfaction, which may not fully capture the immediacy and comprehensive nature of the value being generated.</description>
			</item>
			<item>
				<title>Unrealised Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/unrealised-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:19:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/unrealised-value/</guid>
				<description>Unrealised Value refers to the potential value that an organisation has yet to capture, highlighting opportunities for improvement and innovation. It encompasses various indicators that assess untapped possibilities, such as latent market demand or areas ripe for enhancement. By focusing on Unrealised Value, teams can identify opportunities to optimise processes, innovate products, or better meet customer needs, ultimately leading to increased competitiveness and sustainability. This concept is crucial for enabling teams to deliver value predictably and sustainably, as it promotes a proactive approach to recognising and addressing gaps in performance and capability. Systematically measuring and analysing Unrealised Value fosters a culture of continuous improvement, motivating teams to explore new ideas and solutions. This long-term focus not only enhances current operations but also positions organisations to adapt to changing market conditions and customer expectations. Understanding Unrealised Value empowers teams to make informed decisions about resource allocation, ensuring they are strategically planning for future growth and success rather than merely reacting to immediate challenges. This perspective shifts the focus from delivering current value to actively seeking and realising potential value, which is essential for thriving in today’s dynamic business landscape.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</link>
				<pubDate>Fri, 21 Mar 2025 14:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</guid>
				<description>Common Goals are a foundational principle for effective delivery within organisations, serving to align strategy with execution and ensuring that every decision, Sprint, and line of code contributes to a shared purpose. These goals are not mere aspirational statements; they represent the strategic objectives that unify efforts and connect individual contributions to meaningful outcomes. In the context of agile, DevOps, and product development, understanding and committing to common goals fosters ownership, clarity, and accountability among team members, enabling distributed decision-making and reducing friction in prioritisation. This alignment is crucial for creating adaptive and high-performing systems, as it allows teams to surface misalignments early and make informed trade-offs without waiting for permission. Furthermore, the integration of tactical commitments, such as Product Goals and Sprint Goals, ensures that strategic intent is operationalised at every level of delivery. By maintaining a focus on measurable outcomes and desired impacts, organisations can avoid the pitfalls of busywork and ensure that their efforts are directed towards achieving significant results. Ultimately, common goals provide the necessary framework for teams to understand their role in the larger organisational context, making it imperative for leaders to establish and communicate these objectives clearly.</description>
			</item>
			<item>
				<title>Evidence Based Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-management/</link>
				<pubDate>Fri, 21 Mar 2025 14:44:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-management/</guid>
				<description>Evidence-Based Management (EBM) is a strategic approach designed to enhance organisational agility by providing a framework for assessing and improving value delivery. Unlike traditional frameworks or methodologies, EBM focuses on empirical data to inform decision-making, enabling organisations to move beyond superficial metrics and truly understand their performance. It centres on four critical areas: Current Value, which evaluates immediate value delivery; Time to Market, which measures responsiveness and speed; Ability to Innovate, which assesses the capacity for creating new value amidst existing challenges; and Unrealised Value, which identifies potential opportunities for growth. By utilising these metrics, leaders can make informed decisions about resource allocation and prioritisation, ultimately fostering a culture of continuous improvement. EBM is particularly valuable in the contexts of agile, DevOps, and product development, as it encourages a shift from output-focused practices to outcome-driven strategies. This empirical approach not only clarifies organisational goals but also provides the necessary feedback to adapt and evolve, ensuring that efforts are aligned with delivering real value rather than merely maintaining the status quo. In a landscape where many organisations struggle with agility, EBM offers a practical solution for those seeking to enhance their effectiveness and responsiveness in a complex and dynamic environment.</description>
			</item>
			<item>
				<title>Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</link>
				<pubDate>Tue, 04 Mar 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</guid>
				<description>Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum&amp;rsquo;s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum&amp;rsquo;s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment.</description>
			</item>
			<item>
				<title>Daily Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
			<item>
				<title>Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/product-management/</guid>
				<description>Product Management is a strategic discipline focused on aligning customer needs, business objectives, and technical feasibility to maximise value delivery in product development. Originating from Agile methodologies, particularly within the Scrum framework, the role of the Product Owner is central to this discipline, emphasising accountability for value rather than mere output. This approach is crucial in ensuring that product teams prioritise impactful features over an extensive list of functionalities, thereby avoiding the pitfalls of feature bloat. Effective Product Management operates within a social system, requiring collaboration with stakeholders, executives, and developers while continuously engaging with users to maintain a compelling product vision. The use of evidence-based management is vital, as it allows Product Managers to make informed decisions based on measurable metrics rather than vanity metrics. Customer feedback is treated as a strategic asset, necessitating discernment in its application to avoid misalignment with product goals. Additionally, technical empathy is essential for understanding the feasibility and risks associated with product strategies, ensuring that desirability, viability, and feasibility are balanced. Clear boundaries of authority and accountability are necessary for effective collaboration, with Product Managers defining the &amp;lsquo;what&amp;rsquo; and &amp;lsquo;why&amp;rsquo;, while developers focus on the &amp;lsquo;how&amp;rsquo;. Ultimately, Product Management is about optimising value through informed decision-making, fostering a culture of learning, and prioritising outcomes over outputs, making it a critical function in Agile and DevOps environments.</description>
			</item>
			<item>
				<title>Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</guid>
				<description>The Product Owner is a key accountability within the Scrum framework, tasked with maximising the value of the product produced by the Scrum Team. This role encompasses more than just managing the product backlog; it involves making strategic decisions that align the product vision with customer needs and business objectives. The importance of the Product Owner lies in their responsibility for outcomes rather than merely tasks, as they prioritise features that balance immediate requirements with long-term goals. By optimising the product backlog and adapting to stakeholder feedback and market changes, the Product Owner significantly influences the product&amp;rsquo;s success and the team&amp;rsquo;s effectiveness. They foster collaboration between stakeholders and the development team, ensuring transparency and alignment across the organisation, which enhances decision-making and workflow efficiency. This accountability is crucial for a value-driven approach to product development, as the Product Owner must navigate competing priorities and ensure the product delivers measurable business value. Their strategic decision-making role is distinct from that of the Scrum Master or Development Team, as they continuously assess the product&amp;rsquo;s value and make evidence-based decisions to guide its evolution. By embedding this accountability within the organisational culture, the Product Owner helps maintain alignment with broader strategic goals, ultimately contributing to the consistency of value delivery and the successful completion of product iterations.</description>
			</item>
			<item>
				<title>Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/</guid>
				<description>Professional Scrum is a disciplined approach to the Scrum framework that emphasises empiricism, technical excellence, and the continuous delivery of value. Originating from the principles of Scrum, it prioritises the intentional and accountable ways in which individuals, teams, and organisations operate, rather than merely adhering to prescribed rituals or frameworks. This methodology underscores the importance of transparency, the definition of &amp;lsquo;Done&amp;rsquo;, and the necessity of empirical practices, positioning Product Owners as strategic leaders, Scrum Masters as catalysts for change, and Developers as skilled engineers. By embracing complexity as a dynamic to respond to rather than a challenge to control, Professional Scrum encourages rapid learning, frequent delivery, and ongoing improvement. Its significance lies in its ability to infuse professionalism, responsibility, and rigor into the process of complex product delivery, making it a valuable framework for organisations seeking to enhance their agility, foster collaboration, and achieve sustainable success in product development.</description>
			</item>
			<item>
				<title>Scrum Values</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</guid>
				<description>The Scrum Values are fundamental principles that form the backbone of the Scrum framework, consisting of commitment, courage, focus, openness, and respect. Originating from the need to create a structured yet flexible approach to project management, these values are essential for fostering a collaborative and high-performing team environment. Their importance lies in their ability to enhance a team&amp;rsquo;s capacity to deliver value consistently and sustainably, as they promote a culture of trust and accountability. Commitment drives team members to pursue their goals diligently, while courage encourages them to take risks and express concerns. Focus helps streamline efforts towards critical tasks, boosting productivity and efficiency. Openness facilitates transparent communication and collaboration, leading to effective problem-solving, and respect nurtures a supportive environment that values diverse perspectives, fostering innovation. The long-term benefits of integrating Scrum Values into daily practices are significant, enabling teams to effectively navigate complexities and adapt to evolving circumstances. By embedding these values within their organisational culture, companies can cultivate resilience, prioritise continuous improvement, and align their activities with overarching goals, ensuring that value delivery remains central to their product development and delivery processes.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</guid>
				<description>Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.</description>
			</item>
	</channel>
</rss>
