<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Scrum Team on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</link>
		<description>Recent content in Scrum Team 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.hinshelwood.com/tags/scrum-team/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership.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.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>Professional Scrum teams build software that works</title>
				<link>https://engineering-leadership.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.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.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.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.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.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>Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</link>
				<pubDate>Tue, 27 Jun 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</guid>
				<description>In the first 90 days, a Scrum team can move from limited delivery to continuous delivery by focusing on frequent releases, clarifying business value, integrating user feedback, and empowering team members to take ownership. Success depends on organisational support and team readiness. Managers should prioritise building a delivery culture and enabling the team to sustain progress independently.</description>
			</item>
			<item>
				<title>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership.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.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>Free Workshop 04: Introduction to Sprint Reviews [Review &amp; Retrospective]</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/</link>
				<pubDate>Sat, 18 Sep 2021 13:32:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/</guid>
				<description>The workshop introduced key concepts of Sprint Reviews using interactive tools and received very positive participant feedback, despite technical audio issues during the live stream. The main learning was to check both music and voice before sessions to avoid similar problems, and future events will use a new community platform for easier access. Development managers should ensure thorough technical checks before virtual workshops and consider leveraging interactive formats for better engagement.</description>
			</item>
			<item>
				<title>The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success</title>
				<link>https://engineering-leadership.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.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>Hiring a Professional Scrum Master</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-scrum-master/</link>
				<pubDate>Mon, 15 Mar 2021 14:11:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Are technical skills required to be a Scrum Master?</title>
				<link>https://engineering-leadership.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.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>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership.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.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>Redefining the Scrum Master: From Boss to Empowering Facilitator</title>
				<link>https://engineering-leadership.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.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>The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</link>
				<pubDate>Tue, 22 Oct 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</guid>
				<description>Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success</title>
				<link>https://engineering-leadership.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.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>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership.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.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.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.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>Mastering Scrum: Essential Insights for New Teams from a Scrum Master&#39;s Journey</title>
				<link>https://engineering-leadership.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.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>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership.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.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>If your backlog is not refined then you are doing it wrong</title>
				<link>https://engineering-leadership.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.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>Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/</link>
				<pubDate>Fri, 10 Apr 2020 18:30:42 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/</guid>
				<description>Remote work requires strong communication, the right tools, and a focus on delivering value, even when teams are not co-located. Improving feedback loops, observing team dynamics through activities like games, and integrating UX early in Agile processes all help teams collaborate better and build the right products. Development managers should prioritize open communication, continuous process improvement, and shared accountability for user experience to help their teams thrive in a digital environment.</description>
			</item>
			<item>
				<title>let-us be blunt</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership.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>Professional Scrum Developer (.NET) Training in London</title>
				<link>https://engineering-leadership.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.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>Decoding Scrum Team Work: Balancing Sprint and Refinement Work</title>
				<link>https://engineering-leadership.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.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>How does a Scrum team decide on a Sprint goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</guid>
				<description>A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable.</description>
			</item>
			<item>
				<title>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership.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.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 Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>How does a Scrum Master or Agile coach motivate a Scrum Team?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</link>
				<pubDate>Mon, 11 Sep 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</guid>
				<description>Scrum Masters and Agile coaches play a key role in keeping teams motivated by aligning goals with stakeholder value, celebrating achievements, and fostering open communication. Teams lose motivation when goals are misaligned or stakeholder engagement is lacking, so it is important to set achievable objectives, involve stakeholders, and encourage autonomy and continuous learning. Regularly review team morale, connect work to its broader impact, and create feedback loops to maintain a resilient and high-performing team.</description>
			</item>
			<item>
				<title>What would you advise a scrum team to do in their first 4 weeks?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</link>
				<pubDate>Thu, 16 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</guid>
				<description>In the first four weeks, a scrum team should focus on practicing scrum correctly, learning both what works and what does not, and experimenting to find the best fit for their context. Teams should document obstacles and improvements, address one key change per sprint, and use retrospectives to drive continuous improvement. This approach builds a strong foundation and helps make organizational issues visible for future action.</description>
			</item>
			<item>
				<title>What is the hardest part of working with a brand-new scrum team?</title>
				<link>https://engineering-leadership.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.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>Sprint Review #1</title>
				<link>https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Redefining the Scrum Master: From Misconceptions to Empowering Leadership</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/signals/teams-are-self-managing/</link>
				<pubDate>Fri, 21 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership.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>Should the Scrum Master always remove impediments?</title>
				<link>https://engineering-leadership.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.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>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership.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.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>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership.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.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.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.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.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.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.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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.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.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>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership.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.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.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.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>What will you learn on the professional scrum master course?</title>
				<link>https://engineering-leadership.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.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>Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations</title>
				<link>https://engineering-leadership.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-leadership.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>Nexus Guide</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</link>
				<pubDate>Fri, 27 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</guid>
				<description>Ineffective Product Owners, whether due to lack of skills or organisational constraints, can hinder team performance and product success. Development managers should support Product Owners through relationship-building, organisational education, and open dialogue, while ensuring the team continues to deliver quality work. Take action by fostering collaboration and advocating for clear role expectations to help Product Owners and teams succeed.</description>
			</item>
			<item>
				<title>Is Your Scrum Master Struggling? Discover When to Choose an Agile Process Simulation Workshop</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</link>
				<pubDate>Wed, 05 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</guid>
				<description>If your Scrum Master is struggling with the team, first assess whether the issue is with their approach or deeper team dynamics. An Agile Process Simulation workshop can help by engaging the team in open dialogue and tailored learning, empowering them to decide if Scrum fits their needs. Prioritize collaboration and self-discovery over imposing solutions to achieve better team outcomes.</description>
			</item>
			<item>
				<title>Navigating Team Conflict: From Healthy Disagreement to Agile Harmony</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/</link>
				<pubDate>Tue, 07 Nov 2023 11:30:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/</guid>
				<description>Team conflict is normal and can drive innovation, but if disagreements escalate unchecked, they can harm team dynamics and project outcomes. Managers should watch for signs of unhealthy conflict and use open communication, objective discussions, mediation, and clear team norms to de-escalate issues early. Addressing conflict directly helps maintain productivity and keeps teams focused on delivering value together.</description>
			</item>
			<item>
				<title>Navigating Team Conflict: How Scrum Masters Can Prevent &#39;War&#39; in Agile Projects</title>
				<link>https://engineering-leadership.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-leadership.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>Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework</title>
				<link>https://engineering-leadership.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.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.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.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>Unlocking Trust in Scrum: The Power of Openness and Transparency</title>
				<link>https://engineering-leadership.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.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>Delivering Live Virtual Classes in Microsoft Teams and Mural</title>
				<link>https://engineering-leadership.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.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>My first Scrum team in the wild</title>
				<link>https://engineering-leadership.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.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>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering-leadership.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.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>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership.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.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>Searching for self-organisation</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/searching-for-self-organisation/</link>
				<pubDate>Wed, 31 Jul 2013 09:38:34 +0000</pubDate>
				<guid>https://engineering-leadership.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>How much of an impact can a strong, skilled product owner have?</title>
				<link>https://engineering-leadership.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.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>5 tools that Scrum Masters love. Part 1</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</link>
				<pubDate>Thu, 14 Sep 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</guid>
				<description>Liberating structures are a set of frameworks that help Scrum Masters run more engaging and effective meetings by matching specific techniques to clear objectives. Using these tools can boost team participation, break down communication barriers, and drive better outcomes. Consider adopting liberating structures to turn routine meetings into productive sessions that support team growth and innovation.</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.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.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>Product Owners are not a myth</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/product-owners-are-not-a-myth/</link>
				<pubDate>Tue, 18 Oct 2011 01:56:06 +0000</pubDate>
				<guid>https://engineering-leadership.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>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership.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.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>Sprint Planning Recipe</title>
				<link>https://engineering-leadership.hinshelwood.com/recipes/sprint-planning-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership.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.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>How does a Scrum team create a sprint goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</link>
				<pubDate>Thu, 01 Jun 2023 11:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</guid>
				<description>A Scrum team creates a sprint goal by combining the product’s strategic direction, the product owner’s tactical priorities, and current engineering challenges to identify the most valuable next step. The team then selects backlog items that best align with this goal to deliver clear value to stakeholders. Encourage your teams to invest time in understanding context before setting sprint goals for better alignment and outcomes.</description>
			</item>
			<item>
				<title>How critical is a Product Owner in developing a great Product Backlog?</title>
				<link>https://engineering-leadership.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.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>Adventures in Scrum: Lesson 2 - For the record</title>
				<link>https://engineering-leadership.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-leadership.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>Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/scrum/</link>
				<pubDate>Tue, 04 Mar 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Scrum Team</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>
	</channel>
</rss>
