<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Agile Frameworks on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</link>
		<description>Recent content in Agile Frameworks on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Is Agile Really Just a Mindset?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</link>
				<pubDate>Mon, 11 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</guid>
				<description>Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change.</description>
			</item>
			<item>
				<title>The Definition of Done is a Commitment to Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Release planning and predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</guid>
				<description>The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications.</description>
			</item>
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>Definition of Done - Objective vs Subjective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</link>
				<pubDate>Wed, 02 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</guid>
				<description>Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality.</description>
			</item>
			<item>
				<title>Scrum doesn’t stop you from optimising flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it.</description>
			</item>
			<item>
				<title>A better way than staggered iterations for delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</link>
				<pubDate>Thu, 10 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</guid>
				<description>Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality.</description>
			</item>
			<item>
				<title>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</link>
				<pubDate>Thu, 05 Sep 2024 11:14:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</guid>
				<description>Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness.</description>
			</item>
			<item>
				<title>Professional Scrum teams build software that works</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</guid>
				<description>Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization&amp;rsquo;s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training.</description>
			</item>
			<item>
				<title>The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</link>
				<pubDate>Thu, 01 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</guid>
				<description>Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change.</description>
			</item>
			<item>
				<title>Can the Definition of Done change per Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</link>
				<pubDate>Mon, 14 Oct 2019 13:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</guid>
				<description>The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint.</description>
			</item>
			<item>
				<title>The Scrum Master is accountable for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>I do continuous deliver, why should I Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</guid>
				<description>Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible.</description>
			</item>
			<item>
				<title>The Insufficiency of Scrum is a fallacy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</link>
				<pubDate>Sat, 23 Mar 2013 17:37:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</link>
				<pubDate>Wed, 16 Oct 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</guid>
				<description>There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Hiring a Professional Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</link>
				<pubDate>Mon, 15 Mar 2021 14:11:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</guid>
				<description>Hiring a Scrum Master is challenging and requires someone who can lead, coach, and support both the team and organization to improve effectiveness and adopt Scrum practices. Key requirements include strong leadership, facilitation, and communication skills, a servant leadership mindset, and relevant certifications, with technical or business domain knowledge as a plus. Focus on candidates who can foster a safe, collaborative environment and drive continuous improvement for reliable product delivery.</description>
			</item>
			<item>
				<title>The Importance of Visualizing Your Work in a Kanban Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</link>
				<pubDate>Thu, 07 Mar 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</guid>
				<description>Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process.</description>
			</item>
			<item>
				<title>Are technical skills required to be a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</link>
				<pubDate>Sun, 01 Sep 2019 15:37:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</guid>
				<description>Technical skills are not strictly required to be a Scrum Master, but having a solid understanding of technical, business, and organizational contexts makes a Scrum Master much more effective. Mastery in these areas helps Scrum Masters better support their teams, guide Product Owners, and drive meaningful organizational change. Development managers should ensure their Scrum Masters are equipped with broad contextual knowledge to maximize team and business value.</description>
			</item>
			<item>
				<title>The Power of Kaizen: Continuous Improvement in Scrum and Beyond</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</link>
				<pubDate>Sun, 25 Aug 2024 22:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</guid>
				<description>Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum.</description>
			</item>
			<item>
				<title>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</link>
				<pubDate>Tue, 13 Sep 2011 20:40:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</guid>
				<description>Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.</description>
			</item>
			<item>
				<title>Pragmatism crushes Dogma in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</link>
				<pubDate>Thu, 21 Mar 2024 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</guid>
				<description>Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively.</description>
			</item>
			<item>
				<title>Mastering Agile: 3 Essential Strategies to Boost Your Team&#39;s Sprint Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</link>
				<pubDate>Thu, 16 Nov 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</guid>
				<description>To improve your team&amp;rsquo;s Sprint outcomes, clearly define what &amp;ldquo;done&amp;rdquo; means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place.</description>
			</item>
			<item>
				<title>Unlocking the True Potential of Scrum: Why Professionalism Matters in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</link>
				<pubDate>Thu, 20 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</guid>
				<description>Many software teams fall short of Scrum’s true potential because organizations prioritize speed over professionalism, leading to shortcuts and unprofessional practices. Achieving real value with Scrum requires a commitment to transparency, production-ready increments each iteration, and honest assessment of current capabilities, often revealing significant gaps. Development managers should focus on fostering a professional work ethic and closing these gaps to unlock Scrum’s full benefits.</description>
			</item>
			<item>
				<title>Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</link>
				<pubDate>Thu, 27 Jul 2017 18:16:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</guid>
				<description>Great Calm improved team alignment and agility by investing in Scrum training led by a trainer with real engineering experience, which fostered open dialogue and practical learning. The training is expected to enhance communication, align teams with business goals, and empower them to own their processes. Development managers should consider similar real-world-focused training to drive meaningful change and continuous improvement in their teams.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Boss to Empowering Facilitator</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</guid>
				<description>The Scrum Master should not act as a boss or micromanager but as a facilitator who empowers the team to self-organise and take ownership of their work. Key points include avoiding micromanagement, focusing on support and facilitation rather than control, and promoting collaboration and continuous learning. Development managers should ensure Scrum Masters adopt a coaching mindset to help teams thrive and deliver better results.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Transformative Power of Teaching the &#34;Why&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</guid>
				<description>Helping teams understand the reasons behind Agile practices is key to real engagement and lasting change. When team members grasp the value and purpose of what they do, they collaborate better, adapt more easily, and drive continuous improvement. Development managers should focus on explaining the &amp;ldquo;why&amp;rdquo; behind processes to empower teams and boost performance.</description>
			</item>
			<item>
				<title>Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</link>
				<pubDate>Thu, 04 Jun 2020 05:33:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</guid>
				<description>Focus on team productivity rather than just feature count, and ensure everyone understands the difference between Definition of Done, which sets quality standards, and acceptance criteria, which specify requirements for each item. Use backlog refinement to address unknowns instead of relying on spikes, and plan sprint capacity to accommodate some ad hoc work while maintaining transparency and continuous improvement. Review your team’s approach to these areas to improve delivery and reduce disruptions.</description>
			</item>
			<item>
				<title>Big Scrum: All you need and not enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</link>
				<pubDate>Wed, 01 Jul 2015 16:33:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</guid>
				<description>Scaling Scrum requires truly professional teams who embody agile values and strong engineering practices, not just following processes superficially. Off-the-shelf frameworks do not fit every organization, so adapting Scrum to your unique context is essential. Focus on building skilled teams, fostering effective communication, and adopting only the practices that support your specific scaling needs.</description>
			</item>
			<item>
				<title>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</link>
				<pubDate>Fri, 09 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</guid>
				<description>Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction.</description>
			</item>
			<item>
				<title>Getting started with a Definition of Done (DoD)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</link>
				<pubDate>Mon, 14 Dec 2020 13:03:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</guid>
				<description>A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what &amp;ldquo;done&amp;rdquo; means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product.</description>
			</item>
			<item>
				<title>Mastering Scrum: Essential Insights for New Teams from a Scrum Master&#39;s Journey</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</link>
				<pubDate>Tue, 28 Nov 2023 11:00:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</guid>
				<description>New Scrum teams succeed when they deeply understand Scrum principles, empiricism, and core values, which the Scrum Master should actively teach and reinforce. Practical workshops, real-world examples, and a focus on continuous learning help teams build trust, adapt to change, and improve over time. Development managers should ensure their teams have ongoing support and a safe environment to foster growth and agility.</description>
			</item>
			<item>
				<title>Big Scrum: Are you doing mechanical Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</link>
				<pubDate>Wed, 24 Jun 2015 13:43:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</guid>
				<description>Many organizations adopt Scrum hoping for rapid productivity gains but are disappointed when they only follow the motions without embracing its core values and technical excellence. True effectiveness and faster delivery come from practicing Professional Scrum, which means living the principles and focusing on quality, not just the framework. Development managers should ensure their teams go beyond mechanical Scrum and invest in building a professional culture to achieve real results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</link>
				<pubDate>Fri, 25 Oct 2024 07:02:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</guid>
				<description>Many Scrum Masters misunderstand their true responsibilities, focusing on tools and rituals instead of the core principles and accountabilities defined by Scrum. Effective Scrum Masters balance support for the team, Product Owner, and organisation, acting as coaches and mentors rather than process enforcers. Development managers should ensure Scrum Masters are competent in Scrum’s philosophies and adapt practices to fit their context, not just follow common routines.</description>
			</item>
			<item>
				<title>You can&#39;t stop the signal! But you can ignore it!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</link>
				<pubDate>Wed, 17 Apr 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</guid>
				<description>Agile and Scrum frameworks highlight problems in team processes, but many organizations ignore these signals due to cultural barriers like fear of repercussions and resistance to change. Simply adopting these frameworks is not enough; their effectiveness depends on a culture that encourages transparency, feedback, and continuous improvement. Development managers should focus on building an environment where raising and addressing issues is supported and valued to fully realize the benefits of Agile and Scrum.</description>
			</item>
			<item>
				<title>Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</link>
				<pubDate>Fri, 28 Apr 2023 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</guid>
				<description>Focusing on Scrum rituals instead of its core principles, empiricism, transparency, and delivering value, can hinder true agile success. Overemphasis on mechanics leads to misplaced priorities, reduced creativity, and lower team engagement. Development managers should encourage open dialogue, support experimentation, and regularly assess whether practices are truly delivering value, adapting or discarding those that do not.</description>
			</item>
			<item>
				<title>If your backlog is not refined then you are doing it wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</link>
				<pubDate>Thu, 17 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</guid>
				<description>If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints.</description>
			</item>
			<item>
				<title>Scrum Masters and Product Owners are held accountable for results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</link>
				<pubDate>Mon, 17 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</guid>
				<description>Scrum Masters and Product Owners are often held accountable for results without having the authority needed to influence outcomes. This mismatch leads to empty expectations and limits team effectiveness. To achieve better results, organisations should empower Scrum Masters with real authority, not just expect them to coach from the sidelines.</description>
			</item>
			<item>
				<title>let-us be blunt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</guid>
				<description>Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability.</description>
			</item>
			<item>
				<title>How effectively does an APS prepare a team to do a solid, professional Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</link>
				<pubDate>Sat, 12 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</guid>
				<description>The Applied Professional Scrum (APS) course helps teams focus on delivering a working product every iteration and sheds unhelpful habits that slow progress. Through practical exercises like the &amp;ldquo;Barnacle Exercise,&amp;rdquo; teams identify and remove outdated practices, leading to more effective Scrum adoption. Development managers should consider APS to build teams that consistently deliver value and embody true Scrum principles.</description>
			</item>
			<item>
				<title>Professional Scrum Developer (.NET) Training in London</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</link>
				<pubDate>Fri, 18 Jun 2010 15:53:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</guid>
				<description>Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies.</description>
			</item>
			<item>
				<title>You can not implement Agile or Scrum successfully by decree</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/</link>
				<pubDate>Tue, 13 May 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/</guid>
				<description>Agile and Scrum cannot be made effective just by issuing mandates or using tools; their success depends on a culture of trust, openness, and willingness to improve. If your team fears blame or resists change, process changes alone will not help. Focus on building a supportive culture before trying to improve processes.</description>
			</item>
			<item>
				<title>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</link>
				<pubDate>Wed, 05 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</guid>
				<description>Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence.</description>
			</item>
			<item>
				<title>Decoding Scrum Team Work: Balancing Sprint and Refinement Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</link>
				<pubDate>Thu, 14 Sep 2023 14:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</guid>
				<description>Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: How Empirical Models Transform Project Outcomes</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</link>
				<pubDate>Wed, 12 Oct 2022 17:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</guid>
				<description>Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>How to Be an Effective Agile Coach: Agnosticism in Practice</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</link>
				<pubDate>Tue, 14 Nov 2023 11:00:50 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</guid>
				<description>Effective Agile coaching means being flexible and not pushing one framework; instead, help teams understand core Agile, Lean, and Scrum principles so they can choose what works best for their context. Encourage experimentation, educate teams on different approaches, and support their decision-making process. Focus on enabling teams to own their process and continuously improve rather than prescribing solutions.</description>
			</item>
			<item>
				<title>Detecting Agile BS: Lessons from the US Department of Defense</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</link>
				<pubDate>Fri, 28 Jun 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</guid>
				<description>Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense&amp;rsquo;s &amp;ldquo;Detecting Agile BS&amp;rdquo; guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation.</description>
			</item>
			<item>
				<title>How long does it take to transition from project management to Kanban?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</link>
				<pubDate>Fri, 16 Feb 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</guid>
				<description>Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams.</description>
			</item>
			<item>
				<title>Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</link>
				<pubDate>Mon, 13 Nov 2023 06:56:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</guid>
				<description>A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk.</description>
			</item>
			<item>
				<title>Stop treating the end of the Sprint like a finish line</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</link>
				<pubDate>Thu, 05 Jun 2025 15:30:54 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</guid>
				<description>The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation.</description>
			</item>
			<item>
				<title>Quotes: Less is More. True or False?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</link>
				<pubDate>Sat, 14 Oct 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</guid>
				<description>Focusing on fewer, high-value tasks rather than trying to do everything leads to better productivity and higher quality in Agile teams. Regularly refining the backlog and planning sprints around essential work helps eliminate waste and ensures efforts align with project goals. Development managers should encourage teams to prioritize what matters most to maximize results.</description>
			</item>
			<item>
				<title>Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</link>
				<pubDate>Tue, 23 Aug 2022 16:53:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</guid>
				<description>The Scaled Professional Scrum course helps teams address common challenges in scaling Scrum, such as managing cross-team dependencies, maintaining self-management, and ensuring transparency. Through hands-on, interactive sessions, participants gain practical techniques and tools to structure and manage large agile projects effectively. Development managers looking to scale Scrum without unnecessary overhead should consider this course to equip their teams with proven practices and ongoing support.</description>
			</item>
			<item>
				<title>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</guid>
				<description>Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback.</description>
			</item>
			<item>
				<title>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>The Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</guid>
				<description>A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems.</description>
			</item>
			<item>
				<title>The Importance of Delivering Working Software Every Iteration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</link>
				<pubDate>Wed, 26 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</guid>
				<description>Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort.</description>
			</item>
			<item>
				<title>How does a Scrum Master or Agile coach motivate a Scrum Team?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</link>
				<pubDate>Sun, 14 Apr 2024 12:17:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</guid>
				<description>Achieving true agility requires more than adopting Agile practices; organisations often fall into seven common traps such as seeking quick fixes, overloading backlogs, focusing on resource utilisation over value, lacking accountability, fostering blame, copying others blindly, and letting pride block learning. These behaviours hinder innovation, value delivery, and team effectiveness. Development managers should regularly assess and address these pitfalls, tailor Agile to their context, and foster a culture of continuous improvement and honest reflection.</description>
			</item>
			<item>
				<title>Why Every Scrum Master Needs an Immersive Training Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</link>
				<pubDate>Tue, 21 Nov 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</guid>
				<description>Immersive training is essential for Scrum Masters who already have hands-on experience, as it deepens practical skills, sharpens leadership abilities, and drives better team outcomes. Unlike standard courses, immersive classes focus on real-world challenges, immediate feedback, and peer learning, helping Scrum Masters maximize team value and effectiveness. Development managers should encourage experienced Scrum Masters to pursue immersive training to foster continuous improvement and stronger team leadership.</description>
			</item>
			<item>
				<title>Quotes: &#34;I estimate that 75% of those organisations using Scrum will not succeed in getting the benefits that they hope for from it.&#34; - Ken Schwaber</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</link>
				<pubDate>Fri, 06 Oct 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</guid>
				<description>Most organisations using Scrum do not achieve the benefits they expect because they focus on team-level practices instead of making broader organisational changes. Success requires adopting an agile mindset across the whole company, securing management support, and continuously improving processes. Development managers should drive holistic transformation beyond just the development team to increase the chances of real Scrum success.</description>
			</item>
			<item>
				<title>What is the hardest part of working with a brand-new scrum team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</link>
				<pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</guid>
				<description>The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement.</description>
			</item>
			<item>
				<title>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>The Future of Scrum Training: Immersive Learning for Lasting Change</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</link>
				<pubDate>Thu, 23 Nov 2023 08:30:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</guid>
				<description>Immersive learning is more effective than traditional Scrum training because it provides ongoing support, real-time problem solving, and peer collaboration over several weeks, helping participants apply new skills in real situations. This approach leads to gradual, sustainable change and builds confidence through shared learning and continuous improvement. Development managers should consider immersive learning to achieve lasting transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</link>
				<pubDate>Tue, 24 Oct 2023 06:50:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</guid>
				<description>Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars.</description>
			</item>
			<item>
				<title>How does the APS course help people apply scrum effectively?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</link>
				<pubDate>Wed, 18 Jan 2023 08:57:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</guid>
				<description>The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption.</description>
			</item>
			<item>
				<title>Sprint Review #1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Misconceptions to Empowering Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</link>
				<pubDate>Fri, 12 May 2023 14:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</guid>
				<description>The Scrum Master role is often misunderstood as tool administration or problem-solving, but its true value lies in empowering teams to self-organize and operate independently. Key insights include fostering team autonomy, guiding rather than controlling, and committing to continuous learning. Development managers should support Scrum Masters in becoming facilitators who enable teams to thrive without constant oversight.</description>
			</item>
			<item>
				<title>“Teams are self-managing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</link>
				<pubDate>Fri, 21 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</guid>
				<description>Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance.</description>
			</item>
			<item>
				<title>Balance of Leadership and Control in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</link>
				<pubDate>Mon, 17 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</guid>
				<description>Scrum Masters and Product Owners are expected to deliver results, so they need both influence and enough authority to remove obstacles, enforce alignment, and ensure accountability. Too much control stifles team autonomy, but too little makes teams ineffective; the right balance depends on the organisation and situation. Development managers should empower these roles with the authority needed to drive change while maintaining team ownership and continuous improvement.</description>
			</item>
			<item>
				<title>Professional Scrum Training for the Ghana Police Service</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</link>
				<pubDate>Mon, 30 Oct 2017 19:26:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</guid>
				<description>The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>Scrum doesn&#39;t solve problems, it reveals them. How, and why is that valuable?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</link>
				<pubDate>Wed, 27 Sep 2023 07:00:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</guid>
				<description>Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation.</description>
			</item>
			<item>
				<title>DOD has made it illegal to do waterfall</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</link>
				<pubDate>Tue, 01 May 2018 01:02:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</guid>
				<description>The US Department of Defense has updated its procurement rules to require agile, iterative development instead of traditional waterfall methods, following high-profile failures like the FBI’s Sentinel project. Agile approaches have proven to deliver higher success rates, lower costs, and reduced risk, and these changes are now influencing government and vendor practices across the US and UK. Development managers working with government clients should adopt agile methods to align with new regulations and improve project outcomes.</description>
			</item>
			<item>
				<title>My journey into Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</link>
				<pubDate>Wed, 04 Feb 2015 10:53:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</guid>
				<description>Professional Scrum has been key to my success in software development and consulting, showing that most team challenges are cultural rather than technical. Building professional, adaptable individuals and teams leads to greater business agility and consistent delivery of valuable software. Avoid one-size-fits-all approaches to scaling Scrum; instead, tailor frameworks and practices to your organisation’s unique culture and needs.</description>
			</item>
			<item>
				<title>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>No one questions a Product Owner authority</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</link>
				<pubDate>Wed, 19 Mar 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</guid>
				<description>Product Owners are trusted with authority to make decisions that drive product success, but Scrum Masters often lack similar authority despite being responsible for team effectiveness and removing obstacles. Relying only on persuasion limits their impact; Scrum Masters need the power to enforce good practices and address issues directly. Development managers should ensure Scrum Masters have the authority needed to fulfill their role and support team agility.</description>
			</item>
			<item>
				<title>Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</link>
				<pubDate>Mon, 06 May 2024 14:12:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</guid>
				<description>Many common beliefs about Scrum, such as it being just meetings, requiring story points, encouraging micromanagement, lacking planning, or having no governance, are misconceptions that hinder its effectiveness. Scrum events are purposeful, story points are optional, teams should self-organise, planning is integral, and governance is flexible to business needs. Development managers should challenge these myths to help teams fully benefit from Agile and deliver greater value.</description>
			</item>
			<item>
				<title>The Pitfalls of Agile Burndowns: Stop Being Agile Bandits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</link>
				<pubDate>Tue, 09 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, false confidence, and wasted effort, as most plans quickly become outdated and only a fraction of features are actually used. Instead, focus on minimal, just-in-time planning and continuous flow to adapt quickly, reduce overhead, and deliver real value. Encourage your teams to plan only what is needed for the next day, adjust daily, and prioritize delivering value over maintaining detailed charts.</description>
			</item>
			<item>
				<title>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</link>
				<pubDate>Fri, 26 May 2023 14:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</guid>
				<description>Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes.</description>
			</item>
			<item>
				<title>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</guid>
				<description>A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>When is an APS course appropriate for a scrum team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</link>
				<pubDate>Thu, 12 Oct 2023 08:32:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</guid>
				<description>An APS course is valuable for Scrum teams that want to deepen their understanding of core Scrum principles and shed ineffective practices that may have accumulated over time. It helps teams focus on delivering a working product each iteration and provides practical exercises, like the Barnacle Exercise, to identify and remove process inefficiencies. Consider APS if your team needs to realign with authentic Scrum practices and drive meaningful agile transformation.</description>
			</item>
			<item>
				<title>Mastering Scrum: Effective Planning and Prioritisation for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/</link>
				<pubDate>Fri, 24 Mar 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/</guid>
				<description>Effective Scrum planning and prioritisation require aligning work with business goals, regularly communicating with stakeholders, and keeping the product backlog lean and focused on near-term priorities. Use a simple value, risk, and size formula to help order backlog items, and continuously adjust based on customer data and outcomes. Keep your backlog manageable and iterate often to ensure your team delivers meaningful results that support business objectives.</description>
			</item>
			<item>
				<title>Daily Scrum Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</guid>
				<description>Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals.</description>
			</item>
			<item>
				<title>Understanding the True Role of a Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</link>
				<pubDate>Tue, 28 Nov 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</guid>
				<description>The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</link>
				<pubDate>Mon, 23 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Scrum isn’t limited to building features</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</link>
				<pubDate>Fri, 30 May 2025 15:30:41 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</guid>
				<description>Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products.</description>
			</item>
			<item>
				<title>What should you do if your Sprint Review delivers harsh, scathing feedback?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</link>
				<pubDate>Fri, 08 Sep 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</guid>
				<description>Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Unlocking the Scrum Master&#39;s Potential: Embracing Broader Responsibilities for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</guid>
				<description>Scrum Masters have a broader responsibility beyond supporting their teams; they also need to engage with the Product Owner and the wider organisation to remove obstacles and drive agility. Encouraging Scrum Masters to question outdated processes and model collaborative behaviours can lead to meaningful organisational change. Development managers should empower Scrum Masters to challenge the status quo and support their growth in these expanded roles.</description>
			</item>
			<item>
				<title>Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</link>
				<pubDate>Wed, 17 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</guid>
				<description>Empowering teams to update or delete requirements based on user feedback is essential for true agility and delivering maximum value. Regularly engaging with the product team, keeping the backlog dynamic, and being willing to pivot or remove features ensures your product stays relevant and user-focused. Review your processes to make sure your teams have the authority and support to make these changes.</description>
			</item>
			<item>
				<title>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</link>
				<pubDate>Mon, 11 Jan 2021 14:36:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</guid>
				<description>The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.</description>
			</item>
			<item>
				<title>Scaling Agility: Navigating the Dragons of Change in the Future of Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/</link>
				<pubDate>Wed, 25 Mar 2020 16:17:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/</guid>
				<description>Scaling agility is about more than just expanding frameworks like Scrum or Nexus; it requires focusing on core practices, using meaningful metrics, and adapting to new ways of working such as virtual training. Key insights include the importance of revisiting Scrum fundamentals, tailoring metrics to your context, and leveraging technology for effective remote collaboration. Development managers should prioritize continuous learning, experiment with virtual tools, and stay open to sharing experiences to navigate the challenges of scaling in today’s changing work environment.</description>
			</item>
			<item>
				<title>Design Sprints in Scrum: Common Questions and Practical Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</link>
				<pubDate>Wed, 04 Jun 2025 15:31:05 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</guid>
				<description>There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.</description>
			</item>
			<item>
				<title>Scrum Myth Debunked: Unfinished Work is Allowed in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</link>
				<pubDate>Sat, 24 May 2025 15:30:17 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</guid>
				<description>Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries.</description>
			</item>
			<item>
				<title>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</link>
				<pubDate>Wed, 26 Mar 2025 16:30:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</guid>
				<description>Product Owners should be empowered as strategic leaders who drive product vision and business value, not just manage backlogs. Scrum Masters play a key role in coaching Product Owners to use customer insights and data for better decisions. Development managers should ensure Product Owners have the authority and support to lead effectively, rather than treating them as task managers.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: The Essential Knowledge Every Coach Needs</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</link>
				<pubDate>Wed, 15 Nov 2023 11:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</guid>
				<description>Effective Agile coaching relies on a deep understanding of both frameworks like Scrum, Kanban, and Lean, and the principles behind them, along with strong technical knowledge. Continuous learning, community engagement, and practical experimentation are key to improving coaching skills and supporting teams. Development managers should prioritize ongoing education and active involvement to help their teams succeed with Agile.</description>
			</item>
			<item>
				<title>What will you learn on the professional scrum master course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</link>
				<pubDate>Thu, 19 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</guid>
				<description>The Professional Scrum Master course teaches the theory and practical skills needed to be an effective scrum master, focusing on serving developers, product owners, and the organization to maximize team value. Participants learn through real-world examples, discussions, and case studies about empiricism, delivering working increments each sprint, and overcoming common challenges. Development managers should consider this course to strengthen their teams&amp;rsquo; ability to deliver value and navigate complexity.</description>
			</item>
			<item>
				<title>Maximizing Transparency and Improvement in Software Engineering with Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</link>
				<pubDate>Mon, 29 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</guid>
				<description>Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement.</description>
			</item>
			<item>
				<title>Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</link>
				<pubDate>Tue, 18 Oct 2022 16:13:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</guid>
				<description>Scrum is a flexible framework that helps teams deliver value through transparency, clear roles, and structured events, all grounded in trust and five core values. Key elements include defined accountabilities, essential artifacts for decision-making, and regular events to inspect and adapt work. To get the most from Scrum, focus on building trust, maintaining transparency, and continuously improving team processes.</description>
			</item>
			<item>
				<title>Nexus Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</link>
				<pubDate>Mon, 09 Jan 2023 12:36:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</guid>
				<description>Teaching Scrum through hands-on experience, including using Minecraft, helps participants move from initial chaos to a clear understanding of Scrum’s value. Students first experience confusion similar to real project starts, then learn to apply Scrum principles, leading to practical insights and improved teamwork. Development managers should consider experiential learning to help teams internalise agile practices and appreciate their real-world benefits.</description>
			</item>
			<item>
				<title>Scrum Masters: Why Influence Alone May Not Be Enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</link>
				<pubDate>Thu, 20 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</guid>
				<description>Relying only on influence limits a Scrum Master&amp;rsquo;s ability to drive real change, especially when teams or leaders resist Agile practices. Sustainable agility needs Scrum Masters who can enforce the framework, remove obstacles, and hold teams accountable, not just suggest improvements. Development managers should ensure Scrum Masters have enough authority to lead effectively, not just influence.</description>
			</item>
			<item>
				<title>Why is Scrum so easy to understand but incredibly hard to master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</link>
				<pubDate>Tue, 28 Feb 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</guid>
				<description>Scrum is challenging to master because true understanding and effective implementation require deep cultural change, transparency, and alignment with agile values, not just following the framework. Many teams struggle due to legacy mindsets, lack of comprehension, and misaligned organizational structures, leading to superficial adoption and missed opportunities for value creation. Development managers should focus on fostering a culture of transparency, learning, and value-driven collaboration to realize Scrum’s full benefits.</description>
			</item>
			<item>
				<title>Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</link>
				<pubDate>Fri, 07 Oct 2022 10:41:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</guid>
				<description>Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs.</description>
			</item>
			<item>
				<title>Overview of the &#39;scaling with portfolio Kanban&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-the-&#39;scaling-with-portfolio-kanban&#39;-course/</link>
				<pubDate>Thu, 22 Feb 2024 07:00:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-the-&#39;scaling-with-portfolio-kanban&#39;-course/</guid>
				<description>The &amp;ldquo;Scaling Portfolio Kanban&amp;rdquo; course helps development leaders move from team-level to organization-wide workflow management, enabling better visibility, predictability, and value delivery across multiple teams. Key outcomes include improved forecasting, data-driven decision-making, and optimized flow of high-value projects. If your current workflow lacks predictability or efficiency, consider applying these Kanban strategies to drive measurable improvement.</description>
			</item>
			<item>
				<title>How do you think Agile is evolving since its inception in 2001?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</link>
				<pubDate>Wed, 15 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</guid>
				<description>Agile has evolved since 2001, but many organizations still rely on top-down management rather than empowering teams to make decisions. The next major shift will be moving beyond just adopting frameworks like Scrum to building true agile capabilities across leadership, partners, and teams, focusing on adaptability and customer value. Development managers should revisit agile principles and work to remove barriers that prevent teams from responding quickly to change.</description>
			</item>
			<item>
				<title>Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</link>
				<pubDate>Wed, 18 Nov 2020 16:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</guid>
				<description>The 2020 update to the Scrum Guide simplifies language and reduces prescriptive rules, emphasizing that Scrum Teams are self-managing and collectively accountable for delivering value each Sprint. Key changes include clear commitments for Product Goal, Sprint Goal, and Definition of Done, as well as a focus on cross-functional teams and improved Sprint Planning. Development managers should review the new guide to align their teams with these streamlined practices.</description>
			</item>
			<item>
				<title>Combatting Famine in Agile: How to Foster Stakeholder Engagement and Boost Team Morale</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-famine-in-agile-how-to-foster-stakeholder-engagement-and-boost-team-morale/</link>
				<pubDate>Tue, 31 Oct 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-famine-in-agile-how-to-foster-stakeholder-engagement-and-boost-team-morale/</guid>
				<description>A lack of stakeholder feedback in Agile leads to disengagement, low team morale, and misalignment with business goals. Regular check-ins, fostering a feedback culture, involving the product owner, and visualizing progress help keep stakeholders engaged and teams motivated. Development managers should prioritize active stakeholder involvement to ensure team purpose and deliver better results.</description>
			</item>
			<item>
				<title>What should be top of mind when a Scrum team prepare for a Sprint review?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</link>
				<pubDate>Mon, 04 Sep 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</guid>
				<description>To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency.</description>
			</item>
			<item>
				<title>Best Scrum advice you ever received?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</link>
				<pubDate>Mon, 05 Jun 2023 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</guid>
				<description>The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team&amp;rsquo;s unique context. Flexibility and continuous improvement are more important than strict adherence to the framework, so use Scrum as a guide and modify it as needed to maximize value and innovation. Encourage your teams to experiment and iterate, focusing on what works best for your organization.</description>
			</item>
			<item>
				<title>Kanban Guide for Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</guid>
				<description>Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery.</description>
			</item>
			<item>
				<title>David thought he already knew Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</link>
				<pubDate>Mon, 26 May 2025 15:30:28 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</guid>
				<description>Even experienced teams often fall into old habits and misunderstand Scrum, leading to ineffective practices that only look agile on the surface. Regularly revisiting the fundamentals and purpose of Scrum helps prevent complacency and ensures real improvement. Consider challenging your team&amp;rsquo;s understanding of Scrum to maintain true agility and drive meaningful change.</description>
			</item>
			<item>
				<title>What is Sprint Planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</link>
				<pubDate>Wed, 24 May 2023 14:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</guid>
				<description>Sprint planning is a team meeting to align on what will be accomplished in the next sprint, ensuring everyone understands the goals and priorities, including new features, technical debt, and unexpected work. It provides clarity, flexibility, and a shared sense of direction, whether you use Scrum or Kanban. Make sure your team uses sprint planning to regularly evaluate priorities and maintain alignment for better outcomes.</description>
			</item>
			<item>
				<title>Is a PSM II certification validation of your skills, or does it develop your skill and capability as a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</link>
				<pubDate>Mon, 17 Apr 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</guid>
				<description>The PSM II course is designed to develop your skills and capabilities as a Scrum Master, not just validate what you already know. The class focuses on advanced facilitation techniques and deepens your understanding of Scrum Master accountability to the team, Product Owner, and organization. If you want to grow as a Scrum Master and apply practical tools with your teams, attending the course is recommended over just taking the assessment.</description>
			</item>
			<item>
				<title>Manifesto for Agile Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</guid>
				<description>Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement.</description>
			</item>
			<item>
				<title>Agile and Scrum are often misunderstood</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</link>
				<pubDate>Sun, 04 May 2025 15:30:30 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</guid>
				<description>Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team&amp;rsquo;s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance.</description>
			</item>
			<item>
				<title>Unlocking Trust in Scrum: The Power of Openness and Transparency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</guid>
				<description>Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early.</description>
			</item>
			<item>
				<title>Why Copying Scaled Agile Frameworks Fails in Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>My journey with Kanban and why I actively recommend it to clients</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/</link>
				<pubDate>Fri, 23 Feb 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/</guid>
				<description>Kanban is a practical strategy for improving workflow and predictability by making work processes more transparent and data-driven, which builds trust and enables better decision-making. Integrating Kanban with Scrum helps teams deliver more consistently and reduces stakeholder uncertainty. Development managers should consider adopting Kanban to optimize team performance and deliver greater value across any context.</description>
			</item>
			<item>
				<title>Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</link>
				<pubDate>Wed, 25 Oct 2023 13:30:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</guid>
				<description>Effective planning is essential for Agile and Scrum teams, not something to skip; key Scrum events like sprint planning, backlog refinement, and daily standups all revolve around planning. The goal is to find the right balance, plan enough to provide direction and coordination, especially in large teams, but avoid over-planning that wastes resources. Development managers should ensure their teams have clear goals, roadmaps, and themes to align efforts and adapt as needed.</description>
			</item>
			<item>
				<title>The FBI Sentinel project was textbook waterfall</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</link>
				<pubDate>Wed, 11 Jun 2025 15:30:44 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</guid>
				<description>The FBI&amp;rsquo;s Sentinel project failed after years and massive spending using a traditional waterfall approach, delivering nothing. Switching to a small, focused Agile team produced a working product in a year at a fraction of the cost. Consider adopting iterative methods to avoid wasted time and resources and deliver real value sooner.</description>
			</item>
			<item>
				<title>Are you doing Scrum? Really?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</link>
				<pubDate>Sat, 19 Nov 2011 16:41:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</guid>
				<description>Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if they are truly following Scrum.</description>
			</item>
			<item>
				<title>You can’t deliver change through memos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</link>
				<pubDate>Sat, 31 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</guid>
				<description>Change cannot be achieved through memos or top-down mandates; real progress happens when everyone is trained together and understands the reasons behind new approaches. Broad-based training helps people identify problems and suggest improvements, making change more effective and sustainable. To drive meaningful change, involve all stakeholders in learning and improvement, not just managers or specialists.</description>
			</item>
			<item>
				<title>Kanban Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</link>
				<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</guid>
				<description>Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>In high competition markets, how does scrum product development help acquire and retain customers?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</link>
				<pubDate>Mon, 13 Feb 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</guid>
				<description>Scrum does not directly acquire or retain customers, but it helps teams deliver value quickly and adapt based on customer feedback, which can lead to competitive advantage. Its main strengths are making problems and opportunities visible, enabling rapid execution, and supporting a culture of innovation, but leaders and teams must still identify what customers need and how to deliver it. To succeed, focus on building strong teams, understanding market value, and using Scrum to consistently deliver and validate valuable features.</description>
			</item>
			<item>
				<title>How do you incorporate a Design Sprint in Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</link>
				<pubDate>Fri, 16 Aug 2019 12:35:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</guid>
				<description>Design Sprints should not be treated as separate or special sprints in Scrum; instead, design and UX work should be integrated into regular sprints as part of the team&amp;rsquo;s ongoing activities or handled during backlog refinement for future work. All team members should collaborate on these tasks, leveraging individual skills without creating silos or specialist-only phases. Development managers should ensure design activities are visible, collaborative, and aligned with sprint goals, using communities of practice to share knowledge across teams.</description>
			</item>
			<item>
				<title>Professional Scrum in Immingham, UK</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-in-immingham-uk/</link>
				<pubDate>Wed, 11 Dec 2013 09:34:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-in-immingham-uk/</guid>
				<description>Summary of a multi-team Professional Scrum training at DFDS Seaways in Immingham, UK, highlighting co-located learning, cross-team collaboration, and agile best practices.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations in Alameda, California</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</link>
				<pubDate>Fri, 26 Oct 2012 16:30:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</guid>
				<description>Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles in the development process.</description>
			</item>
			<item>
				<title>What&#39;s in a burndown?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</link>
				<pubDate>Wed, 28 Mar 2012 03:52:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</guid>
				<description>Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.</description>
			</item>
			<item>
				<title>My first Scrum team in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</link>
				<pubDate>Sun, 03 Apr 2011 21:44:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</guid>
				<description>A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.</description>
			</item>
			<item>
				<title>Scrum is not an engineering process</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</link>
				<pubDate>Wed, 21 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</guid>
				<description>Scrum is a framework for fostering collaboration across the whole organisation, not just an engineering process for developers. True agility happens when everyone, regardless of role, understands and participates in Scrum, which helps break down silos and exposes issues that slow delivery. To achieve real change, ensure your entire team is aligned and involved in the conversation about how value is delivered.</description>
			</item>
			<item>
				<title>Would you recommend the APS course to a newbie scrum team, and Why?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/would-you-recommend-the-aps-course-to-a-newbie-scrum-team-and-why/</link>
				<pubDate>Thu, 23 Mar 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/would-you-recommend-the-aps-course-to-a-newbie-scrum-team-and-why/</guid>
				<description>The APS course is highly recommended for new Scrum teams because it simplifies Scrum concepts, helps teams identify and address necessary organizational changes, and empowers both team members and leaders to drive improvements. Key benefits include creating an actionable Organizational Change Backlog and fostering team engagement and alignment. Development managers should consider enrolling their teams to ensure a strong start with Scrum and ongoing alignment with agile principles.</description>
			</item>
			<item>
				<title>What is the most common mistake in sprint planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</link>
				<pubDate>Thu, 25 May 2023 14:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</guid>
				<description>The most common mistake in sprint planning is failing to define a clear and tangible sprint goal, which is essential for guiding the team&amp;rsquo;s immediate work and connecting it to the broader product vision. A well-defined sprint goal provides focus, enables actionable stakeholder feedback, and helps the team understand and meet expectations. Development managers should ensure every sprint has a concrete goal that can be evaluated at the sprint review to drive progress and alignment.</description>
			</item>
			<item>
				<title>Quotes: Don&#39;t scale Scrum! Pragmatic or defeatist?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</link>
				<pubDate>Mon, 09 Oct 2023 14:30:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</guid>
				<description>The idea that Scrum cannot be scaled is a misconception; frameworks like Nexus show that Scrum can be effectively scaled to deliver greater value. Key recommendations include understanding Nexus, starting with a single team, and scaling thoughtfully while adapting as you go. Development managers should explore scaling options rather than dismissing them, as successful scaling is both possible and beneficial.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Sweep problems under the rug</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/</link>
				<pubDate>Mon, 04 Mar 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/</guid>
				<description>Ignoring problems in your Kanban process leads to bigger issues, workflow blockages, and potential crises like project delays or cost overruns. Teams should regularly identify, visualize, and address problems, foster transparency, and take prompt action to prevent issues from escalating. Make it a priority to surface and resolve problems early to keep your workflow effective and avoid costly setbacks.</description>
			</item>
			<item>
				<title>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</link>
				<pubDate>Thu, 15 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</guid>
				<description>Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions.</description>
			</item>
			<item>
				<title>Introducing Kanban for Professional Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</link>
				<pubDate>Mon, 26 Feb 2018 15:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</guid>
				<description>A new Professional Scrum with Kanban class and guide now enable Scrum teams to integrate Kanban practices like workflow visualization, limiting work in progress, and flow-based metrics without changing Scrum itself. This approach helps teams focus on value delivery and can replace traditional metrics like velocity with more actionable measures such as throughput and cycle time. Development managers should consider reviewing the Kanban Guide for Scrum Teams and exploring the training to enhance their teams&amp;rsquo; effectiveness.</description>
			</item>
			<item>
				<title>What is the most common Aha moment people have in a scrum course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</link>
				<pubDate>Fri, 03 Mar 2023 07:15:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</guid>
				<description>The most common realization in scrum courses is understanding the deep purpose behind each element of the scrum framework, especially its foundation in empiricism, rather than just following procedures. Many experienced practitioners discover they have been missing the true value of scrum by not connecting its events and artefacts to their intended outcomes. To unlock high performance, teams should focus on mastering the fundamentals and intentionally applying scrum’s principles, not just its mechanics.</description>
			</item>
			<item>
				<title>Transforming Training: The Power of Immersive Learning in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</link>
				<pubDate>Wed, 08 May 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</guid>
				<description>Traditional two-day Scrum training is ineffective for lasting change because participants retain little and struggle to apply what they learn. Immersive learning, with shorter sessions spread over time, hands-on assignments, and ongoing feedback, leads to better retention, practical application, and continuous improvement. Development managers should consider adopting immersive training formats to drive real, sustainable transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>The Key to a Kanban Strategy: Understanding WIP Limits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</link>
				<pubDate>Wed, 06 Mar 2024 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</guid>
				<description>Setting work-in-progress (WIP) limits is essential for an effective Kanban strategy because it prevents overload, exposes bottlenecks, and improves workflow. The optimal WIP limit for each stage should be found through experimentation and regular adjustment, aiming for a balance that maximizes flow without causing idle time or bottlenecks. Start small, monitor results, and adjust limits as needed to boost team productivity and collaboration.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</link>
				<pubDate>Wed, 30 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</guid>
				<description>Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs.</description>
			</item>
			<item>
				<title>Can organisations run an Applying Professional Scrum workshop? How would that help them?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</link>
				<pubDate>Wed, 29 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>In Scrum, we don’t do UX separately</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</link>
				<pubDate>Thu, 12 Jun 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</guid>
				<description>UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed.</description>
			</item>
			<item>
				<title>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</link>
				<pubDate>Mon, 24 Feb 2025 07:26:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</guid>
				<description>The idea of a &amp;ldquo;junior Scrum Master&amp;rdquo; is misleading because the role demands significant experience, technical knowledge, and the ability to navigate complex team and organisational dynamics. Assigning this responsibility to inexperienced team members undermines both individual growth and team effectiveness. Development managers should ensure that Scrum Masters are chosen based on proven competence and relevant experience, not as entry-level positions.</description>
			</item>
			<item>
				<title>The false claim that Scrum is immutable</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/</link>
				<pubDate>Tue, 25 Jun 2024 11:37:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/</guid>
				<description>Scrum is meant to be flexible and adaptable, not rigid, despite some claims that it is &amp;ldquo;immutable.&amp;rdquo; The Scrum Guide&amp;rsquo;s reference to immutability applies to its definition, not to how teams must implement it, so teams can adapt Scrum as needed as long as they are transparent about changes. Development managers should focus on delivering value, getting feedback, adapting plans, and reflecting regularly rather than debating strict adherence to the Scrum Guide.</description>
			</item>
			<item>
				<title>The Sprint Goal is a commitment for the Sprint Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</link>
				<pubDate>Fri, 27 Nov 2020 13:09:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</guid>
				<description>The Sprint Goal is a clear, single objective for each Sprint that guides the team’s focus and aligns their work toward the Product Goal. It is set during Sprint Planning, helps teams adapt their work as needed without losing sight of the main purpose, and should be specific to your business context. Ensure your Product Owner proposes a meaningful Sprint Goal for each Sprint to keep the team aligned and working toward valuable outcomes.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</link>
				<pubDate>Thu, 01 Aug 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</guid>
				<description>Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive.</description>
			</item>
			<item>
				<title>What is Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-scrum/</link>
				<pubDate>Fri, 19 May 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-scrum/</guid>
				<description>Scrum is a framework that helps teams organize around shared goals and is especially effective for tackling complex, unpredictable work where you learn as you go. It is designed to help teams navigate tasks that are novel or constantly changing, making it ideal for software development environments. Consider exploring Scrum further to boost your team&amp;rsquo;s productivity and adaptability.</description>
			</item>
			<item>
				<title>#1 tip for a new Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</link>
				<pubDate>Wed, 17 May 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</guid>
				<description>New Scrum Masters should start by thoroughly reading and understanding the Scrum Guide to grasp the fundamentals of Scrum, including its roles, events, and principles. This foundational knowledge is essential for effectively leading teams, coaching others, and running Agile projects successfully. Make it a priority to master the basics before moving on to more advanced concepts.</description>
			</item>
			<item>
				<title>3 core practices of Kanban. Actively managing work items in a workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</link>
				<pubDate>Mon, 26 Feb 2024 14:06:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</guid>
				<description>Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow.</description>
			</item>
			<item>
				<title>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</link>
				<pubDate>Wed, 03 Apr 2024 17:21:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</guid>
				<description>Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team&amp;rsquo;s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team&amp;rsquo;s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</link>
				<pubDate>Wed, 21 Jun 2023 11:00:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</guid>
				<description>The Scrum Master is not a manager or authority figure but a servant leader who facilitates team processes, removes obstacles, and encourages autonomy. Misconceptions like expecting status updates or report writing from the Scrum Master undermine team ownership and collaboration. Development managers should empower Scrum Masters to support teams rather than control them, fostering a culture of trust and shared responsibility.</description>
			</item>
			<item>
				<title>How do you select the most valuable items for the sprint backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</link>
				<pubDate>Tue, 30 May 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</guid>
				<description>Selecting the most valuable items for the sprint backlog requires input from business, product, and engineering perspectives, not just following the product backlog order. It is a collaborative process where the team and stakeholders align on priorities to ensure each sprint delivers real value. Development managers should facilitate open discussions to balance strategic goals and technical needs when planning sprints.</description>
			</item>
			<item>
				<title>Scrum is hard to adopt and disruptive to your organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</link>
				<pubDate>Thu, 22 Sep 2011 01:17:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</guid>
				<description>Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful organisational change and Agile adoption.</description>
			</item>
			<item>
				<title>Choosing a Process Template for your Team Project</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</link>
				<pubDate>Tue, 16 May 2017 10:40:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</guid>
				<description>For agile software teams using TFS or VSTS, choose the Scrum process template to minimize friction and avoid legacy constraints found in the Agile and CMMI templates. The Scrum template is lightweight, flexible, and easier to customize for your team&amp;rsquo;s needs, while the other templates enforce outdated practices and create unnecessary barriers. Start with the Scrum template and tailor it as needed to support your workflow and adoption.</description>
			</item>
			<item>
				<title>3 Core Practices of Kanban: Improving a Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</link>
				<pubDate>Wed, 28 Feb 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</guid>
				<description>Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements.</description>
			</item>
			<item>
				<title>Why Immersive Learning Keeps Scrum Students Excited and Engaged</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</link>
				<pubDate>Thu, 01 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</guid>
				<description>Immersive learning keeps Scrum students engaged by making each session a hands-on journey of discovery, allowing them to apply new concepts in real time and reflect on their experiences. Spreading content over multiple sessions helps teams assimilate knowledge, experiment safely, and continuously improve through feedback. Development managers should break training into manageable pieces, encourage experimentation, and foster regular feedback to maintain excitement and drive ongoing growth.</description>
			</item>
			<item>
				<title>Temperance in Agile: Why Less is More</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</link>
				<pubDate>Tue, 05 Dec 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</guid>
				<description>Focusing on just enough work and keeping your backlog, planning, and team size lean helps your team deliver more value and avoid waste or burnout. Prioritize only high-impact tasks, limit work in progress, and avoid over-refining or over-planning. Say no to non-essential work, balance short-term wins with long-term goals, and seek coaching if you struggle to maintain this balance.</description>
			</item>
			<item>
				<title>The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</link>
				<pubDate>Thu, 03 Jul 2025 05:22:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</guid>
				<description>The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together.</description>
			</item>
			<item>
				<title>In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</link>
				<pubDate>Mon, 30 Sep 2019 18:35:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</guid>
				<description>When managing multiple Scrum teams in a Nexus, the Product Owner should focus on high-level vision and attend only the Nexus Sprint Planning, delegating detailed planning to designated Team Owners or Area Owners for each team. This approach reduces overload, maintains alignment with the product vision, and relies on strong communication and autonomy within teams. To implement this, assign a representative for each team to handle their Sprint Planning and ensure ongoing coordination with the Product Owner.</description>
			</item>
			<item>
				<title>Overview of Applying Professional Kanban course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</link>
				<pubDate>Wed, 21 Feb 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</guid>
				<description>The Applying Professional Kanban course teaches how to integrate Kanban into any workflow to improve efficiency, identify bottlenecks, and drive continuous improvement using data and visualizations. Key outcomes include better workflow management, data-driven decision-making, and increased value delivery to stakeholders. Development managers should consider this course to optimize their team&amp;rsquo;s processes and deliver more value quickly.</description>
			</item>
			<item>
				<title>Scrum-damentals Webcast on 17th February 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-damentals-webcast-on-17th-february-2012/</link>
				<pubDate>Thu, 16 Feb 2012 22:56:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-damentals-webcast-on-17th-february-2012/</guid>
				<description>Explore common challenges in Scrum adoption, practical strategies for overcoming them, and proven practices to help teams implement Scrum more effectively.</description>
			</item>
			<item>
				<title>Mastering Kanban: A Simple Guide to Its Core Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</link>
				<pubDate>Mon, 01 Jul 2024 07:00:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</guid>
				<description>Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency.</description>
			</item>
			<item>
				<title>Understanding the Power of Kanban in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</link>
				<pubDate>Mon, 05 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</guid>
				<description>Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery.</description>
			</item>
			<item>
				<title>Understanding Kanban: A Tool for Transparency and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</link>
				<pubDate>Mon, 24 Jun 2024 06:48:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</guid>
				<description>Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements.</description>
			</item>
			<item>
				<title>Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</link>
				<pubDate>Tue, 27 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</guid>
				<description>Defining and visualising your workflow in Kanban creates shared understanding, clarity, and alignment among team members, which leads to greater efficiency. Establishing clear rules for task selection, workflow stages, and work in progress is essential for a stable and productive system. Take time to document and visualise your process so everyone knows how work flows and can contribute effectively.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Sprint Planning Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</guid>
				<description>Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders.</description>
			</item>
			<item>
				<title>Why Limiting Work in Progress is Key to Success in Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</link>
				<pubDate>Mon, 22 Jul 2024 06:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</guid>
				<description>Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable.</description>
			</item>
			<item>
				<title>Unlocking Agile’s Core: Questioning to Create Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</link>
				<pubDate>Tue, 23 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</guid>
				<description>Agile success depends on fostering a culture where everyone questions existing processes, seeks continuous improvement, and adapts quickly to change. Scrum helps teams identify inefficiencies and encourages regular reflection, while leadership must empower all employees to challenge the status quo and act on feedback. To stay ahead of competitors, create open forums for discussion, reward initiative, and ensure that improvement is a shared, ongoing effort across the organization.</description>
			</item>
			<item>
				<title>Upcomming Scrum at Scale Workshop from Scrum.org</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upcomming-scrum-at-scale-workshop-from-scrum-org/</link>
				<pubDate>Wed, 22 Oct 2014 12:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upcomming-scrum-at-scale-workshop-from-scrum-org/</guid>
				<description>Scaling Scrum in large organizations is challenging mainly due to cultural resistance and lack of commitment to change. Scrum.org’s Scrum at Scale Workshop offers practical tools like the Agility Index and practices assessment to help you measure, guide, and sustain organizational change. Development managers leading agile transformation should consider this workshop to effectively drive and monitor enterprise-level agility.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</link>
				<pubDate>Mon, 15 Mar 2010 13:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</guid>
				<description>Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.</description>
			</item>
			<item>
				<title>What is a Sprint Backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</link>
				<pubDate>Mon, 29 May 2023 12:01:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</guid>
				<description>The Sprint Backlog is a combination of the Sprint Goal, selected tasks, and a clear plan for achieving them, providing transparency on current work and progress. It should balance goal-driven work with essential tasks like bug fixes, remain flexible to adapt to new needs during the Sprint, and set teams up for achievable success. Development managers should ensure Sprint Goals are realistic and use the Sprint Backlog to maintain focus while staying adaptable.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning in Agile: Overcoming Cognitive Bias</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</link>
				<pubDate>Mon, 05 Feb 2024 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</guid>
				<description>Immersive learning is essential for Agile teams because it exposes knowledge gaps and helps overcome overconfidence, leading to real skill growth. By focusing on hands-on practice, continuous feedback, and regular reflection, teams can drive ongoing improvement and avoid common pitfalls. Development managers should encourage immersive, practical learning environments to ensure their teams keep evolving and truly master Agile principles.</description>
			</item>
			<item>
				<title>What is the most valuable thing you have learned through training people?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</link>
				<pubDate>Tue, 07 Feb 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</guid>
				<description>The most valuable lesson from training people worldwide is that teams everywhere face the same core challenges when adopting agile and Scrum, regardless of culture or location. Shared experiences in training help participants realize their problems are not unique, which builds confidence and accelerates learning. Development managers should leverage global perspectives and proven Scrum practices to address common issues and drive improvement in their teams.</description>
			</item>
			<item>
				<title>Coffee Talk: Introduction to Scrum - webcast event this Friday!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</link>
				<pubDate>Tue, 16 Aug 2011 02:57:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</guid>
				<description>Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking to improve team performance.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 2 - For the record</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Product Goal is a commitment for the Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</link>
				<pubDate>Mon, 23 Nov 2020 14:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</guid>
				<description>The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency.</description>
			</item>
			<item>
				<title>Sprint Review</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</link>
				<pubDate>Sun, 11 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</guid>
				<description>The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product&amp;rsquo;s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product&amp;rsquo;s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation.</description>
			</item>
			<item>
				<title>Increment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</guid>
				<description>Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices.</description>
			</item>
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>Definition of Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</guid>
				<description>The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability.</description>
			</item>
			<item>
				<title>Agnostic Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:49:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</guid>
				<description>Agnostic Agile is a movement that advocates for a flexible and context-driven approach to agility, emphasising the importance of principles over rigid frameworks. Originating from the need for adaptability in various methodologies, it encourages teams to tailor their practices based on specific requirements rather than conforming to a single ideology. This pragmatic approach allows practitioners to integrate diverse methodologies such as Scrum, Kanban, Lean, and Extreme Programming, fostering an environment that values critical thinking and professionalism. By prioritising value delivery, Agnostic Agile equips teams to respond effectively to evolving circumstances, ensuring predictable and sustainable value generation. This adaptability is essential in today&amp;rsquo;s dynamic environments, where the capacity to pivot and innovate can significantly influence an organisation&amp;rsquo;s success. Furthermore, Agnostic Agile promotes ethical practices by avoiding brand loyalty to specific frameworks, thereby nurturing a culture of continuous improvement and learning. This mindset empowers teams to experiment and refine their processes, ultimately supporting a long-term, systemic approach to agility that enhances organisational resilience and effectiveness. As such, Agnostic Agile is a crucial concept in contemporary product development and delivery, providing valuable insights for teams striving to thrive in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>Artifact</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</link>
				<pubDate>Fri, 21 Mar 2025 13:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</guid>
				<description>An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change.</description>
			</item>
			<item>
				<title>Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</guid>
				<description>Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation&amp;rsquo;s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation&amp;rsquo;s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of &amp;ldquo;Kaizen,&amp;rdquo; which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value.</description>
			</item>
			<item>
				<title>Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</link>
				<pubDate>Tue, 04 Mar 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</guid>
				<description>Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum&amp;rsquo;s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum&amp;rsquo;s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment.</description>
			</item>
			<item>
				<title>Agile Frameworks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</guid>
				<description>Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape.</description>
			</item>
			<item>
				<title>Agile Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</guid>
				<description>Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development.</description>
			</item>
			<item>
				<title>Daily Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
			<item>
				<title>Large Scale Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/large-scale-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/large-scale-agility/</guid>
				<description>Large Scale Agility is the implementation of agile principles and practices throughout entire organisations, moving beyond individual teams to cultivate a culture of adaptability, collaboration, and continuous improvement. Originating from the need for enterprises to respond quickly to market dynamics and customer demands, this approach ensures that value delivery remains both predictable and sustainable. By adopting agile methodologies at scale, organisations can dismantle silos, improve cross-functional collaboration, and align strategic objectives with operational execution. This concept prioritises systemic change, focusing on the organisation as a cohesive unit rather than isolated teams, and encourages the use of frameworks like the Scaled Agile Framework (SAFe) or Large Scale Scrum (LeSS) to provide structured methods for scaling agile practices. The holistic perspective of Large Scale Agility enhances transparency, decision-making, and a shared understanding of goals across all organisational levels. The long-term advantages include increased capacity for innovation, improved employee engagement, and stronger alignment between business and technology. By creating an environment conducive to experimentation, learning, and adaptation, organisations can better navigate the complexities of a rapidly changing landscape, ultimately achieving sustained competitive advantage through agility at scale.</description>
			</item>
			<item>
				<title>Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</guid>
				<description>The Product Owner is a key accountability within the Scrum framework, tasked with maximising the value of the product produced by the Scrum Team. This role encompasses more than just managing the product backlog; it involves making strategic decisions that align the product vision with customer needs and business objectives. The importance of the Product Owner lies in their responsibility for outcomes rather than merely tasks, as they prioritise features that balance immediate requirements with long-term goals. By optimising the product backlog and adapting to stakeholder feedback and market changes, the Product Owner significantly influences the product&amp;rsquo;s success and the team&amp;rsquo;s effectiveness. They foster collaboration between stakeholders and the development team, ensuring transparency and alignment across the organisation, which enhances decision-making and workflow efficiency. This accountability is crucial for a value-driven approach to product development, as the Product Owner must navigate competing priorities and ensure the product delivers measurable business value. Their strategic decision-making role is distinct from that of the Scrum Master or Development Team, as they continuously assess the product&amp;rsquo;s value and make evidence-based decisions to guide its evolution. By embedding this accountability within the organisational culture, the Product Owner helps maintain alignment with broader strategic goals, ultimately contributing to the consistency of value delivery and the successful completion of product iterations.</description>
			</item>
			<item>
				<title>Scrum Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Scrum Values</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</guid>
				<description>The Scrum Values are fundamental principles that form the backbone of the Scrum framework, consisting of commitment, courage, focus, openness, and respect. Originating from the need to create a structured yet flexible approach to project management, these values are essential for fostering a collaborative and high-performing team environment. Their importance lies in their ability to enhance a team&amp;rsquo;s capacity to deliver value consistently and sustainably, as they promote a culture of trust and accountability. Commitment drives team members to pursue their goals diligently, while courage encourages them to take risks and express concerns. Focus helps streamline efforts towards critical tasks, boosting productivity and efficiency. Openness facilitates transparent communication and collaboration, leading to effective problem-solving, and respect nurtures a supportive environment that values diverse perspectives, fostering innovation. The long-term benefits of integrating Scrum Values into daily practices are significant, enabling teams to effectively navigate complexities and adapt to evolving circumstances. By embedding these values within their organisational culture, companies can cultivate resilience, prioritise continuous improvement, and align their activities with overarching goals, ensuring that value delivery remains central to their product development and delivery processes.</description>
			</item>
			<item>
				<title>Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/kanban/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/kanban/</guid>
				<description>Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments.</description>
			</item>
	</channel>
</rss>
