<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Accountability on Engineering as a Leadership System</title>
		<link>https://engineering.hinshelwood.com/concepts/accountability/</link>
		<description>Recent content in Accountability on Engineering as a Leadership System</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering.hinshelwood.com/concepts/accountability/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering.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.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>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering.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.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.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering.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 Scrum Master is accountable for Delivery</title>
				<link>https://engineering.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering.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>The Insufficiency of Scrum is a fallacy</title>
				<link>https://engineering.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</link>
				<pubDate>Sat, 23 Mar 2013 17:37:31 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</guid>
				<description>Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes.</description>
			</item>
			<item>
				<title>Hiring a Professional Scrum Master</title>
				<link>https://engineering.hinshelwood.com/articles/hiring-a-professional-scrum-master/</link>
				<pubDate>Mon, 15 Mar 2021 14:11:00 +0000</pubDate>
				<guid>https://engineering.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>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering.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.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>Scrum Masters and Product Owners are held accountable for results</title>
				<link>https://engineering.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.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.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering.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>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering.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.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>The fallacy of the rejected backlog item</title>
				<link>https://engineering.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering.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.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.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>Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course</title>
				<link>https://engineering.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.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>Challenging Misconceptions About Behaviour in Agile Teams</title>
				<link>https://engineering.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</link>
				<pubDate>Thu, 13 Feb 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering.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>Who broke the build?</title>
				<link>https://engineering.hinshelwood.com/articles/who-broke-the-build/</link>
				<pubDate>Mon, 29 Mar 2010 18:47:08 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/who-broke-the-build/</guid>
				<description>Explains the importance of passing builds, common causes of build failures, how to identify issues and responsible users, and best practices for build ownership.</description>
			</item>
			<item>
				<title>let-us be blunt, if a Scrum Team isn’t delivering, is it effective</title>
				<link>https://engineering.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</link>
				<pubDate>Fri, 07 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</guid>
				<description>A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness.</description>
			</item>
			<item>
				<title>Great Scrum Masters and Product Owners don’t micromanage</title>
				<link>https://engineering.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.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.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</link>
				<pubDate>Sun, 16 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering.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>Balance of Leadership and Control in Scrum</title>
				<link>https://engineering.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</link>
				<pubDate>Mon, 17 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering.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>Cultivating Patience: The Secret Ingredient for Thriving Agile Teams</title>
				<link>https://engineering.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/</link>
				<pubDate>Fri, 08 Dec 2023 11:00:09 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/</guid>
				<description>Patience is essential for agile teams to build trust, avoid blame, and support growth, leading to better collaboration and outcomes. Leaders should set realistic expectations, encourage open communication, and model patient behavior to foster a healthy team environment. Take time to invest in team development and celebrate progress to enable long-term success.</description>
			</item>
			<item>
				<title>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering.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.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.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</link>
				<pubDate>Wed, 19 Mar 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering.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>What Does an Ineffective Scrum Master&#39;s Day Look Like?</title>
				<link>https://engineering.hinshelwood.com/videos/what-does-an-ineffective-scrum-master&#39;s-day-look-like/</link>
				<pubDate>Tue, 20 Jun 2023 12:00:28 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/what-does-an-ineffective-scrum-master&#39;s-day-look-like/</guid>
				<description>An ineffective Scrum Master spends too much time on reports instead of supporting the team, treats daily meetings as status checks rather than collaboration opportunities, and blocks communication between developers and the business. These behaviors hinder progress and team growth. Recognizing and addressing these habits is crucial for improving team effectiveness.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering.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.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.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.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>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</link>
				<pubDate>Mon, 23 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</guid>
				<description>Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Wrath</title>
				<link>https://engineering.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/</link>
				<pubDate>Mon, 16 Oct 2023 11:00:31 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/</guid>
				<description>Wrath in Agile teams shows up as blame and fear of mistakes, which stifles innovation and learning. Shifting from blame to shared accountability creates a safer environment for risk-taking and continuous improvement. Development managers should encourage open discussion of mistakes and support a culture where learning from errors is valued over perfection.</description>
			</item>
			<item>
				<title>Avoid the Bug as Task anti-pattern in Azure DevOps</title>
				<link>https://engineering.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</link>
				<pubDate>Wed, 06 Aug 2014 14:46:41 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</guid>
				<description>Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers guidance for agile teams to avoid it.</description>
			</item>
			<item>
				<title>Unlocking the Scrum Master&#39;s Potential: Embracing Broader Responsibilities for Agile Success</title>
				<link>https://engineering.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.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>Scrum Master Effectiveness Begins with Consistent Delivery</title>
				<link>https://engineering.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</link>
				<pubDate>Thu, 06 Mar 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</guid>
				<description>Scrum Master effectiveness depends on ensuring teams deliver something every sprint, as delivery enables feedback and improvement. Without delivery, there is no basis for learning or adding value. Development managers should prioritize consistent delivery as the foundation for team effectiveness and continuous improvement.</description>
			</item>
			<item>
				<title>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering.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.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>Worst Contribution from a Product Owner that You Know Of</title>
				<link>https://engineering.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</link>
				<pubDate>Tue, 06 Jun 2023 11:00:34 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</guid>
				<description>A product owner publicly blamed the development team during a sprint review instead of supporting them when stakeholders questioned product decisions, undermining trust and collaboration. Product owners should balance accountability to stakeholders with support for their teams, especially under pressure. Development managers should ensure product owners are prepared to defend team decisions and foster a collaborative environment.</description>
			</item>
			<item>
				<title>Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations</title>
				<link>https://engineering.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</link>
				<pubDate>Mon, 13 Mar 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</guid>
				<description>A great Scrum Master is defined by their fit with the team and their ability to build trust, which is best achieved when teams help select their own Scrum Master. Beyond supporting the team, the most effective Scrum Masters build relationships across the organisation to identify and address broader obstacles, empowering others to drive change. Development managers should involve teams in Scrum Master selection and support their efforts to connect with stakeholders for greater organisational impact.</description>
			</item>
			<item>
				<title>The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap</title>
				<link>https://engineering.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.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>Scrum Masters: Why Influence Alone May Not Be Enough</title>
				<link>https://engineering.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.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>Navigating Team Conflict: How Scrum Masters Can Prevent &#39;War&#39; in Agile Projects</title>
				<link>https://engineering.hinshelwood.com/videos/navigating-team-conflict-how-scrum-masters-can-prevent-&#39;war&#39;-in-agile-projects/</link>
				<pubDate>Mon, 30 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/navigating-team-conflict-how-scrum-masters-can-prevent-&#39;war&#39;-in-agile-projects/</guid>
				<description>Team conflict can quickly escalate from healthy debate to destructive arguments that harm collaboration and project outcomes. Scrum Masters play a key role in preventing this by fostering open communication, keeping discussions focused on issues rather than individuals, and de-escalating tensions early. Development managers should watch for early signs of conflict and support Scrum Masters in maintaining a productive team environment.</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.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.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>Lack of Authority Blocks Progress on Critical Projects</title>
				<link>https://engineering.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</link>
				<pubDate>Sun, 16 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</guid>
				<description>Scrum Masters need real authority to remove obstacles and drive project success, but many are blocked by bureaucracy and lack of support. Without empowerment, they cannot be held accountable for outcomes and become ineffective. Development managers should ensure Scrum Masters have the authority to act if they expect meaningful results.</description>
			</item>
			<item>
				<title>Most influential people in Agile: Simon Reindl</title>
				<link>https://engineering.hinshelwood.com/videos/most-influential-people-in-agile-simon-reindl/</link>
				<pubDate>Thu, 06 Jul 2023 14:33:51 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/most-influential-people-in-agile-simon-reindl/</guid>
				<description>Many Product Owners feel they lack control over key decisions like backlog order and product goals, often being excluded from strategic discussions. Recognizing this gap is the first step toward gaining more influence and accountability. Product Owners should proactively seek involvement in important meetings and build relationships to elevate their role within the organization.</description>
			</item>
			<item>
				<title>Most companies still get Product Ownership wrong</title>
				<link>https://engineering.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</link>
				<pubDate>Thu, 17 Apr 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering.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>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering.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.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>Vision, Value, and Validation: The Keys to Successful Product Management</title>
				<link>https://engineering.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</link>
				<pubDate>Thu, 14 Dec 2023 06:45:02 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</guid>
				<description>When moving from project management to product management, it is essential for Product Owners to fill the gap left by traditional planning tools by focusing on vision, value, and validation. Clearly define and communicate the product vision, ensure all work aligns with delivering real value, and continuously validate progress through feedback and measurement. Prioritize these pillars to keep teams aligned and maximize product impact; consider seeking support if challenges arise.</description>
			</item>
			<item>
				<title>Part 2: Common Mistakes that Scrum Masters Make</title>
				<link>https://engineering.hinshelwood.com/videos/part-2-common-mistakes-that-scrum-masters-make/</link>
				<pubDate>Fri, 07 Jul 2023 14:00:33 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/part-2-common-mistakes-that-scrum-masters-make/</guid>
				<description>Scrum Masters often fall into the trap of handling administrative tasks for their teams, which distracts from their real role of improving team effectiveness. Taking on these duties can undermine both the Scrum Master’s impact and the team’s growth. Focus on enabling the team rather than doing their work for them, and avoid becoming the team’s secretary.</description>
			</item>
			<item>
				<title>What are the barriers that prevent developers from fully accepting a Product Owner as the final decision maker?</title>
				<link>https://engineering.hinshelwood.com/videos/what-are-the-barriers-that-prevent-developers-from-fully-accepting-a-product-owner-as-the-final-decision-maker/</link>
				<pubDate>Tue, 03 Oct 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/what-are-the-barriers-that-prevent-developers-from-fully-accepting-a-product-owner-as-the-final-decision-maker/</guid>
				<description>Developers may not fully accept the Product Owner as the final decision maker when stakeholders undermine the Product Owner’s authority, send mixed messages, or fail to consistently support their decisions. This leads to confusion, lack of trust, and developers second-guessing decisions. To address this, ensure stakeholders back the Product Owner publicly, document agreements, and foster open communication to build trust and accountability.</description>
			</item>
			<item>
				<title>From Product Owner to Systemic Leader: Embracing the Evolution in Agile Leadership</title>
				<link>https://engineering.hinshelwood.com/videos/from-product-owner-to-systemic-leader-embracing-the-evolution-in-agile-leadership/</link>
				<pubDate>Fri, 28 Jul 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/from-product-owner-to-systemic-leader-embracing-the-evolution-in-agile-leadership/</guid>
				<description>Experienced Product Owners often grow into broader leadership roles, taking on more accountability and influencing organisational culture and systems. This transition requires a shift from managing backlogs to creating environments that empower teams and foster innovation. Development managers should support Product Owners in developing leadership skills and consider training like Agile Leadership Essentials to help them drive positive change across the organisation.</description>
			</item>
			<item>
				<title>Searching for self-organisation</title>
				<link>https://engineering.hinshelwood.com/articles/searching-for-self-organisation/</link>
				<pubDate>Wed, 31 Jul 2013 09:38:34 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/searching-for-self-organisation/</guid>
				<description>Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and consistency for effective collaboration.</description>
			</item>
			<item>
				<title>Mastering Prioritisation: How Product Owners Can Drive Value and Accountability</title>
				<link>https://engineering.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</link>
				<pubDate>Mon, 27 Nov 2023 11:00:56 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</guid>
				<description>Product Owners play a crucial role in ensuring resources are spent wisely by prioritising the most valuable work, aligning development with business goals, and maintaining stakeholder trust through clear communication. Effective prioritisation maximises value delivery, keeps teams focused, and adapts to changing needs. Development managers should support Product Owners in understanding users, collaborating closely, and staying flexible to drive successful outcomes.</description>
			</item>
			<item>
				<title>Signs You&#39;re Failing as a Product Owner: How to Take Control and Deliver Real Value</title>
				<link>https://engineering.hinshelwood.com/videos/signs-you&#39;re-failing-as-a-product-owner-how-to-take-control-and-deliver-real-value/</link>
				<pubDate>Fri, 22 Sep 2023 07:00:32 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/signs-you&#39;re-failing-as-a-product-owner-how-to-take-control-and-deliver-real-value/</guid>
				<description>A failing product owner is marked by poor product quality, inconsistent delivery, lack of vision, and not taking true ownership of the product. To deliver real value, product owners must make decisions, communicate a clear vision, and focus on actual outcomes rather than vanity metrics. Development managers should ensure their product owners are empowered to lead, make tough calls, and stay aligned with user and business needs.</description>
			</item>
			<item>
				<title>Unlocking Growth: The Transformative Power of Poly Immersive Learning Experiences</title>
				<link>https://engineering.hinshelwood.com/videos/unlocking-growth-the-transformative-power-of-poly-immersive-learning-experiences/</link>
				<pubDate>Thu, 13 Jul 2023 12:20:07 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/unlocking-growth-the-transformative-power-of-poly-immersive-learning-experiences/</guid>
				<description>Poly immersive learning experiences help teams adapt to complexity by encouraging learning from real-world feedback, fostering collaboration, and providing time for reflection. They reinforce knowledge through structured assignments and practical experiments, which build habits of continuous improvement. Development managers should integrate these approaches to drive ongoing learning and accountability within their teams.</description>
			</item>
			<item>
				<title>Why is becoming a Scrum Master a great career option?</title>
				<link>https://engineering.hinshelwood.com/videos/why-is-becoming-a-scrum-master-a-great-career-option/</link>
				<pubDate>Thu, 30 Mar 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/why-is-becoming-a-scrum-master-a-great-career-option/</guid>
				<description>Becoming a Scrum Master is a strong first step for team members aiming for leadership roles, as it allows you to demonstrate leadership by improving team effectiveness and taking on new responsibilities. The role is widely recognized and respected as a starting point on the leadership ladder, regardless of your current specialty. Consider pursuing Scrum Master training to build these skills and advance your career in software development leadership.</description>
			</item>
			<item>
				<title>Product Owners are not a myth</title>
				<link>https://engineering.hinshelwood.com/articles/product-owners-are-not-a-myth/</link>
				<pubDate>Tue, 18 Oct 2011 01:56:06 +0000</pubDate>
				<guid>https://engineering.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>The Real Scope of a Product Owner: Beyond the Backlog</title>
				<link>https://engineering.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</link>
				<pubDate>Mon, 27 Nov 2023 06:46:47 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</guid>
				<description>The Product Owner role goes far beyond managing the backlog, requiring strategic decision-making, budget accountability, and proactive leadership to maximize product value and stay ahead of the market. Success depends on strong relationships, deep market understanding, and continuous learning, not just training. Development managers should ensure Product Owners have the authority, information, and support needed to drive product direction and deliver real business impact.</description>
			</item>
			<item>
				<title>Why Validate Your Advanced Product Ownership Skills with a PSPO-A</title>
				<link>https://engineering.hinshelwood.com/videos/why-validate-your-advanced-product-ownership-skills-with-a-pspo-a/</link>
				<pubDate>Thu, 08 Jun 2023 11:00:05 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/why-validate-your-advanced-product-ownership-skills-with-a-pspo-a/</guid>
				<description>Validating your skills with a PSPO-A demonstrates advanced product ownership abilities that go beyond the basics, positioning you as a visionary leader who can bridge departments and drive product success. Advanced Product Owners act like mini-CEOs, integrating business, strategy, and Agile leadership to deliver greater value. Consider pursuing the PSPO-A to elevate your impact and lead innovation within your organization.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering.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.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>1 thing that sinks a consulting engagement before it starts gaining traction?</title>
				<link>https://engineering.hinshelwood.com/videos/1-thing-that-sinks-a-consulting-engagement-before-it-starts-gaining-traction/</link>
				<pubDate>Sat, 19 Aug 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/1-thing-that-sinks-a-consulting-engagement-before-it-starts-gaining-traction/</guid>
				<description>Overly detailed contracts that specify exact deliverables, timelines, and costs can undermine consulting engagements because they do not account for the unpredictable nature of software development. Focusing on outcomes and the value delivered, rather than rigid outputs, leads to better results. Development managers should prioritize flexibility in contracts to adapt to changing requirements and ensure project success.</description>
			</item>
			<item>
				<title>Hiring a Product Owner? Avoid copying job specs from the internet</title>
				<link>https://engineering.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.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>Most Common Thing You Hear in a PSPO Course?</title>
				<link>https://engineering.hinshelwood.com/videos/most-common-thing-you-hear-in-a-pspo-course/</link>
				<pubDate>Thu, 29 Jun 2023 11:00:18 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/videos/most-common-thing-you-hear-in-a-pspo-course/</guid>
				<description>Many Product Owners feel they lack control over key aspects like backlog order, product goals, and strategic discussions, which limits their impact. Recognizing this gap is the first step toward greater empowerment and influence. Product Owners should proactively seek involvement in important meetings, build relationships, and demonstrate competence to earn more accountability and elevate their role.</description>
			</item>
			<item>
				<title>Does your organisation have both Project Mangers as well as Product Owners?</title>
				<link>https://engineering.hinshelwood.com/articles/does-your-organisation-have-both-project-mangers-as-well-as-product-owners/</link>
				<pubDate>Thu, 10 Apr 2014 15:33:01 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/does-your-organisation-have-both-project-mangers-as-well-as-product-owners/</guid>
				<description>Explores the challenges of having both Project Managers and Product Owners in teams, highlighting conflicts, reporting issues, and impacts on agile delivery and team focus.</description>
			</item>
			<item>
				<title>Can you really commit to delivering work?</title>
				<link>https://engineering.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</link>
				<pubDate>Sat, 26 Nov 2011 20:24:42 +0000</pubDate>
				<guid>https://engineering.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.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.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>Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey</title>
				<link>https://engineering.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.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>Even Scrum should have detailed Task descriptions</title>
				<link>https://engineering.hinshelwood.com/articles/even-scrum-should-have-detailed-task-descriptions/</link>
				<pubDate>Wed, 28 Apr 2010 19:25:57 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/even-scrum-should-have-detailed-task-descriptions/</guid>
				<description>Scrum tasks should include detailed descriptions so anyone can complete them, ensuring project continuity if team members are unavailable or leave unexpectedly.</description>
			</item>
			<item>
				<title>Do you have a contract between the Product Owner and the Team?</title>
				<link>https://engineering.hinshelwood.com/articles/do-you-have-a-contract-between-the-product-owner-and-the-team/</link>
				<pubDate>Wed, 14 Apr 2010 15:46:09 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/do-you-have-a-contract-between-the-product-owner-and-the-team/</guid>
				<description>Explains the benefits of a Sprint Contract in Scrum, clarifying roles and agreements between Product Owner and Team to improve collaboration and manage scope during each Sprint.</description>
			</item>
			<item>
				<title>Do you know that every user story should have an owner?</title>
				<link>https://engineering.hinshelwood.com/articles/do-you-know-that-every-user-story-should-have-an-owner/</link>
				<pubDate>Wed, 17 Mar 2010 14:34:08 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/do-you-know-that-every-user-story-should-have-an-owner/</guid>
				<description>Assigning an owner to each user story in Scrum ensures clear responsibility, better communication, and accountability throughout the sprint for both teams and stakeholders.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 2 - For the record</title>
				<link>https://engineering.hinshelwood.com/articles/adventures-in-scrum-lesson-2-for-the-record/</link>
				<pubDate>Mon, 15 Mar 2010 16:28:01 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/articles/adventures-in-scrum-lesson-2-for-the-record/</guid>
				<description>Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, especially with proxy Product Owners.</description>
			</item>
			<item>
				<title>Accountability</title>
				<link>https://engineering.hinshelwood.com/concepts/accountability/</link>
				<pubDate>Thu, 10 Apr 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering.hinshelwood.com/concepts/accountability/</guid>
				<description>Accountability is a structural concept that delineates who is answerable for outcomes within a work system, distinguishing it from task-level responsibility and decision-making authority. In the context of Scrum, accountability is embodied by three roles: the Product Owner, the Scrum Master, and the Developers, each clarifying their responsibility for value, the work system, and the delivery of completed increments. This framework is crucial in Agile, Scrum, and DevOps environments, where self-management, decentralised control, and transparency are vital for success. Without clear accountability, organisations risk falling into patterns of unclear ownership, blame diffusion, and command-and-control management. It is important to note that accountability is distinct from responsibility, which pertains to task execution, and authority, which involves decision-making power; individuals can possess authority without accountability or responsibility without ownership of outcomes. By establishing clear accountabilities, organisations can facilitate inspection and adaptation, enabling data-driven decision-making, identifying delivery bottlenecks, and enhancing overall flow and value delivery. Ultimately, accountability serves as a defined structural mechanism that fosters clarity, alignment, and effective delivery in complex work systems.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering.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>Product Owner</title>
				<link>https://engineering.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering.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>Scrum Team</title>
				<link>https://engineering.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/tags/scrum-team/</guid>
				<description>A Scrum Team is a fundamental component of the Scrum framework, tasked with delivering value through iterative and incremental work. Comprising a Scrum Master, Product Owner, and Developers, the team operates collaboratively towards a unified Product Goal. Characterised by its self-managing and cross-functional nature, the Scrum Team eschews sub-teams and hierarchies, holding collective accountability for producing a usable Increment at the end of each Sprint. While individual members may have specific roles, the team&amp;rsquo;s shared responsibility encompasses all facets of product delivery, including stakeholder engagement, development, validation, and release. This structure empowers the Scrum Team to autonomously manage its work, making it a vital element in agile methodologies, DevOps practices, and effective organisational design. Understanding the dynamics and responsibilities of the Scrum Team is crucial for navigating complex and adaptive environments, as it highlights the importance of collaboration and accountability in achieving successful product outcomes.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering.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>
