<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Agile Product Management on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/agile-product-management/</link>
		<description>Recent content in Agile Product Management on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/agile-product-management/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Telling People What to Do Is Not Leadership. It’s a Failure of System Design</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</link>
				<pubDate>Mon, 04 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</guid>
				<description>Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work.</description>
			</item>
			<item>
				<title>Release planning and predictable delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.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>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership.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.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</link>
				<pubDate>Wed, 16 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</guid>
				<description>Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage.</description>
			</item>
			<item>
				<title>Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster</title>
				<link>https://engineering-leadership.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.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>Delivery is the only Measure of Progress in Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</link>
				<pubDate>Mon, 03 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</guid>
				<description>Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</link>
				<pubDate>Wed, 18 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</guid>
				<description>A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility.</description>
			</item>
			<item>
				<title>A better way than staggered iterations for delivery</title>
				<link>https://engineering-leadership.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.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>The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</link>
				<pubDate>Thu, 01 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</guid>
				<description>Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change.</description>
			</item>
			<item>
				<title>Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</link>
				<pubDate>Tue, 27 Jun 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</guid>
				<description>In the first 90 days, a Scrum team can move from limited delivery to continuous delivery by focusing on frequent releases, clarifying business value, integrating user feedback, and empowering team members to take ownership. Success depends on organisational support and team readiness. Managers should prioritise building a delivery culture and enabling the team to sustain progress independently.</description>
			</item>
			<item>
				<title>I do continuous deliver, why should I Sprint?</title>
				<link>https://engineering-leadership.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.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>let-us do the maths</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/</link>
				<pubDate>Wed, 30 Apr 2025 15:30:52 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/</guid>
				<description>Slow release cycles mean customer needs go unmet and competitors gain an edge. Microsoft’s shift from a two-year delivery cycle to three-week sprints allowed them to deliver features in days, improving customer satisfaction and competitiveness. Accelerate your delivery process to stay relevant and meet customer demands faster.</description>
			</item>
			<item>
				<title>Why Most Companies Operating Models Fail in Dynamic Markets</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-most-companies-operating-models-fail-in-dynamic-markets/</link>
				<pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-most-companies-operating-models-fail-in-dynamic-markets/</guid>
				<description>Most organisations still use a Predictive Operating Model built for stable, predictable markets, which now creates massive waste, slow decisions, and disengaged teams in today&amp;rsquo;s dynamic environment. An Adaptive Operating Model, built on empiricism, rapid learning, decentralised decision-making, and persistent cross-functional teams, is a better fit because it focuses on outcomes, adaptability, and continuous alignment with customers. The real work is redesigning structures, measures, and leadership, not just adopting new processes.</description>
			</item>
			<item>
				<title>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</link>
				<pubDate>Tue, 13 Sep 2011 20:40:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</guid>
				<description>Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.</description>
			</item>
			<item>
				<title>Pragmatism crushes Dogma in the wild</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</link>
				<pubDate>Thu, 21 Mar 2024 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.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.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.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 Power of Sprint Planning: Transform Your Agile Approach for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/</link>
				<pubDate>Thu, 29 Jun 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/</guid>
				<description>Effective Sprint planning can transform your team&amp;rsquo;s Agile approach by building shared understanding, enabling hands-on practice with real-time coaching, and fostering continuous improvement through feedback. As teams gain confidence, they should adapt Sprint planning to fit their unique needs and culture. Consider structured workshops with flexible delivery to empower your team to run impactful Sprint planning sessions independently.</description>
			</item>
			<item>
				<title>Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</guid>
				<description>The Scrum Master should not act as a boss or micromanager but as a facilitator who empowers the team to self-organise and take ownership of their work. Key points include avoiding micromanagement, focusing on support and facilitation rather than control, and promoting collaboration and continuous learning. Development managers should ensure Scrum Masters adopt a coaching mindset to help teams thrive and deliver better results.</description>
			</item>
			<item>
				<title>Unmasking Agile: How to Spot Genuine Practices Amidst the Myths</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unmasking-agile-how-to-spot-genuine-practices-amidst-the-myths/</link>
				<pubDate>Wed, 18 Mar 2020 13:56:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unmasking-agile-how-to-spot-genuine-practices-amidst-the-myths/</guid>
				<description>Most organizations claim to be agile, but few actually follow core practices like short iterations, ordered backlogs, and regular retrospectives, which limits their ability to deliver value and improve. Cultural resistance and outdated management styles are major barriers to genuine agility. Development managers should honestly assess their teams against key agile principles and take action to remove obstacles, empower teams, and focus on rapid feedback and continuous improvement.</description>
			</item>
			<item>
				<title>The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</link>
				<pubDate>Tue, 22 Oct 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</guid>
				<description>Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress.</description>
			</item>
			<item>
				<title>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</link>
				<pubDate>Fri, 09 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</guid>
				<description>Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction.</description>
			</item>
			<item>
				<title>The Pitfalls of Routine Agile Questions: Avoiding the Ghosts of Agile Past</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</link>
				<pubDate>Wed, 03 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</guid>
				<description>Focusing daily meetings on routine status questions leads to disengagement and distracts from delivering real value. Instead, teams should use these meetings to track progress toward sprint goals, manage aging tasks before they become bottlenecks, and adapt ceremonies to support value delivery and continuous improvement. Review your Agile practices and shift the focus from individual updates to team outcomes for better results.</description>
			</item>
			<item>
				<title>Getting started with a Definition of Done (DoD)</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</link>
				<pubDate>Mon, 14 Dec 2020 13:03:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</guid>
				<description>A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what &amp;ldquo;done&amp;rdquo; means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product.</description>
			</item>
			<item>
				<title>Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</link>
				<pubDate>Thu, 27 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</guid>
				<description>If teams do not deliver a usable product at the end of each iteration, trust with stakeholders erodes, technical debt grows, adaptability slows, and expectations become misaligned. This also leads to lower team morale and a lack of feedback, making it hard to improve or stay on track. To avoid these issues, ensure every iteration results in a usable product so you maintain trust, alignment, and the ability to adapt quickly.</description>
			</item>
			<item>
				<title>Maximising Product Value: The Power of Hypothesis-Driven Engineering</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</link>
				<pubDate>Wed, 11 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</guid>
				<description>Focusing on hypothesis-driven engineering helps teams maximise product value by testing ideas with small experiments, measuring outcomes, and quickly adapting based on real customer feedback. The Azure DevOps team’s experience showed that even costly initiatives can provide critical learning, allowing resources to be redirected before larger losses occur. Development managers should encourage rapid experimentation and validation at all levels to ensure investments deliver real value and support agility.</description>
			</item>
			<item>
				<title>Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</link>
				<pubDate>Thu, 17 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</guid>
				<description>If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints.</description>
			</item>
			<item>
				<title>Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/</link>
				<pubDate>Fri, 10 Apr 2020 18:30:42 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/</guid>
				<description>Remote work requires strong communication, the right tools, and a focus on delivering value, even when teams are not co-located. Improving feedback loops, observing team dynamics through activities like games, and integrating UX early in Agile processes all help teams collaborate better and build the right products. Development managers should prioritize open communication, continuous process improvement, and shared accountability for user experience to help their teams thrive in a digital environment.</description>
			</item>
			<item>
				<title>let-us be blunt</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt/</guid>
				<description>Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability.</description>
			</item>
			<item>
				<title>Most teams don’t fail because they lack frameworks</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</link>
				<pubDate>Mon, 05 May 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</guid>
				<description>Teams usually fail not because they lack frameworks like Agile or Scrum, but because they ignore the feedback these frameworks reveal. The real challenge is creating a culture where teams feel safe and empowered to act on what they learn. Development managers should focus on listening to feedback and enabling teams to address issues, which leads to better performance and competitive advantage.</description>
			</item>
			<item>
				<title>You can not implement Agile or Scrum successfully by decree</title>
				<link>https://engineering-leadership.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.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>Too much refinement wastes time</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/too-much-refinement-wastes-time/</link>
				<pubDate>Tue, 29 Apr 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/too-much-refinement-wastes-time/</guid>
				<description>Too much backlog refinement wastes time, while too little causes confusion and delays. Aim for just enough detail so developers can start work confidently without needing constant clarification. If Sprint Planning is about making commitments rather than figuring things out, your refinement process is working well.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</link>
				<pubDate>Fri, 13 Sep 2024 07:00:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</guid>
				<description>Evidence-based management in Scrum focuses on four key value areas, current value, unrealized value, ability to innovate, and time to market, to guide data-driven decisions and balance innovation with stability. Tracking metrics in these areas helps teams improve customer satisfaction, identify growth opportunities, manage technical debt, and speed up delivery. Development managers should start measuring these areas to align teams with evidence-based management and drive sustainable product success.</description>
			</item>
			<item>
				<title>Decoding Scrum Team Work: Balancing Sprint and Refinement Work</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</link>
				<pubDate>Thu, 14 Sep 2023 14:25:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</guid>
				<description>Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes.</description>
			</item>
			<item>
				<title>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</link>
				<pubDate>Thu, 08 May 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</guid>
				<description>Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives.</description>
			</item>
			<item>
				<title>Agile is Not New: A Journey Back to the Basics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/</link>
				<pubDate>Thu, 10 Oct 2024 15:48:56 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/</guid>
				<description>Agile is rooted in centuries-old practices focused on human connection and adaptability, but mass production and Taylorism shifted work toward efficiency at the cost of empathy and craftsmanship. The Agile movement aimed to restore these values, yet many organizations now face a competence gap, hiring for Agile roles without ensuring the necessary skills, which leads to disappointing results. Development managers should prioritize building real competence and continuous learning in their teams to realize Agile’s true benefits and prepare for a coming reset that emphasizes value, empathy, and adaptability over rigid processes.</description>
			</item>
			<item>
				<title>Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery</title>
				<link>https://engineering-leadership.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.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>Mastering Evidence-Based Management for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/</link>
				<pubDate>Wed, 02 Oct 2024 13:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/</guid>
				<description>Evidence-Based Management helps Agile teams make better decisions by using data from four key areas: current value, unrealized value, ability to innovate, and time to market. By collecting and analyzing relevant metrics, teams can prioritize improvements, boost innovation, and deliver more value to customers. Start by tracking a few key metrics with simple tools, then use those insights to guide your team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Stop Starting and Start Finishing: The Key to Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</link>
				<pubDate>Wed, 31 Jan 2024 14:26:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</guid>
				<description>Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact.</description>
			</item>
			<item>
				<title>Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</link>
				<pubDate>Fri, 20 Oct 2023 16:01:48 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</guid>
				<description>Many teams claim to be Agile but stall due to issues like not delivering working software each Sprint, lacking clear goals, ignoring user feedback, slow deployments, rigid requirements, and resistance to process change. These signs indicate a lack of true agility and hinder progress. Development managers should honestly assess their teams for these problems and take action to empower teams, streamline feedback and deployment, and adapt processes as needed.</description>
			</item>
			<item>
				<title>Quotes: Less is More. True or False?</title>
				<link>https://engineering-leadership.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.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>How Usable Working Products Are Your Ultimate Weapon Against Risks</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</link>
				<pubDate>Thu, 20 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</guid>
				<description>Continuously delivering a usable working product is the most effective way to reduce risk in Agile development. Focus on releasing functional increments, fixing bugs quickly, automating tests, and keeping documentation lean to stay responsive to market needs. Prioritise regular feedback from users and stakeholders to ensure you are building what truly adds value.</description>
			</item>
			<item>
				<title>Evidence-based Management: Gathering the metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</link>
				<pubDate>Wed, 30 Dec 2020 14:02:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</guid>
				<description>Evidence-based Management helps software organizations focus on delivering real value by tracking metrics in three areas: current value, time to market, and ability to innovate. Traditional measures like on-time and on-budget delivery miss customer value, so organizations should gather and regularly review these agile-focused metrics to guide improvement. Start collecting baseline data now and reassess quarterly to track progress and demonstrate the impact of agile investments.</description>
			</item>
			<item>
				<title>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</guid>
				<description>Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback.</description>
			</item>
			<item>
				<title>Harnessing Your Entrepreneurial Spirit: Key Strategies for Product Owners to Drive Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harnessing-your-entrepreneurial-spirit-key-strategies-for-product-owners-to-drive-team-success/</link>
				<pubDate>Wed, 20 Sep 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harnessing-your-entrepreneurial-spirit-key-strategies-for-product-owners-to-drive-team-success/</guid>
				<description>Product owners should connect their teams to the value they create by clearly communicating vision and goals, and foster evidence-based decision-making using data and user feedback rather than intuition. Focusing on metrics like time to market and balancing innovation with maintenance helps teams deliver better results faster. Encourage regular dialogue and rapid prototyping to keep teams engaged and responsive to user needs.</description>
			</item>
			<item>
				<title>The Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/scrum-guide/</guid>
				<description>A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems.</description>
			</item>
			<item>
				<title>Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility</title>
				<link>https://engineering-leadership.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.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>Professional Scrum is for everyone in your organisation</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</link>
				<pubDate>Tue, 16 Jan 2018 13:25:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</guid>
				<description>Scrum works best when everyone in the organisation is involved, not just the development teams, as this breaks down old management habits and empowers people at all levels to contribute to value delivery. Training all staff together surfaces misconceptions, encourages open discussion, and creates a shared understanding that drives real change. To maximise the benefits, managers should ensure broad participation in Scrum training and use the resulting organisational change backlog to remove barriers to effective software delivery.</description>
			</item>
			<item>
				<title>Not all surprises in product development are true unknowns</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/</link>
				<pubDate>Mon, 28 Apr 2025 15:30:55 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/</guid>
				<description>Many surprises in product development are due to poor backlog management rather than true unknowns. Regularly reviewing and categorizing past surprises helps teams improve their backlog and anticipate issues. Development managers should ensure their teams use backlog refinement to build foresight and reduce avoidable disruptions.</description>
			</item>
			<item>
				<title>Sprint Review #1</title>
				<link>https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>Great Scrum Masters and Product Owners don’t micromanage</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</link>
				<pubDate>Sun, 23 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</guid>
				<description>Effective Scrum Masters and Product Owners avoid micromanaging by providing clear direction, supporting team autonomy, and ensuring accountability. Teams perform best when they understand the vision and operate within a structured framework that balances freedom with alignment. Leaders should focus on removing obstacles and maintaining this balance to enable true agility; consider how your organization supports both autonomy and structure.</description>
			</item>
			<item>
				<title>Agile without a usable working product is just expensive theatre</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/</link>
				<pubDate>Sun, 20 Apr 2025 15:30:27 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/</guid>
				<description>Agile only delivers value if each sprint results in a usable working product; focusing on rituals, documentation, or velocity without real output wastes time and resources. The key measure of success is having something shippable at the end of every sprint, which enables feedback and reduces risk. Development managers should ensure their teams are consistently delivering usable products rather than just going through the motions.</description>
			</item>
			<item>
				<title>Combatting the Agile Apocalypse: How to Overcome the Famine of Feedback and Engagement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</link>
				<pubDate>Wed, 08 Nov 2023 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</guid>
				<description>A lack of feedback and engagement from stakeholders, especially the product owner, leads to disengaged teams, poor product alignment, and increased risk of failure. Regular feedback sessions, open communication, and early stakeholder involvement are essential to keep teams motivated and ensure products meet business needs. Development managers should prioritise active stakeholder participation to maintain team morale and deliver better outcomes.</description>
			</item>
			<item>
				<title>7 Deadly Sins of Agile: Greed</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</link>
				<pubDate>Wed, 11 Oct 2023 12:00:36 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</guid>
				<description>Focusing on resource utilisation over value in Agile leads to busywork, burnout, and reduced innovation, undermining true productivity. Teams should prioritise delivering customer value, balance workloads, and foster open communication and trust to enable creativity and continuous improvement. Development managers should shift from maximising activity to nurturing a value-driven, healthy Agile culture that supports learning and adaptation.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>DOD has made it illegal to do waterfall</title>
				<link>https://engineering-leadership.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.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>Overcoming Project Blockers and Challenging Organisational Inertia</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/</link>
				<pubDate>Sat, 22 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/</guid>
				<description>Teams are often held responsible for project outcomes without having the authority to remove blockers or challenge ineffective practices, which leads to frustration and failure. True accountability requires giving teams both autonomy and the power to influence their environment. Development managers should ensure teams have the authority needed to address obstacles and drive results, not just the responsibility.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Critical Role of User Feedback in Requirement Changes</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/</link>
				<pubDate>Fri, 19 Jul 2024 06:45:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/</guid>
				<description>Empowering teams to change requirements based on real user feedback is essential for true agility, yet many organizations are held back by rigid contracts, complex change processes, and lack of team autonomy. Teams must be able to quickly adapt, discard outdated features, and act on feedback to keep products relevant and valuable. Development managers should streamline change processes, build flexibility into contracts, and foster a culture of trust so teams can respond rapidly to evolving business needs.</description>
			</item>
			<item>
				<title>Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation</title>
				<link>https://engineering-leadership.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.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>Redefining Agile’s Core: Beyond Rituals and Procedures</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</link>
				<pubDate>Mon, 22 Jan 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</guid>
				<description>Agile is not about following rituals or procedures but about delivering value and adapting to change to maximize business outcomes. Teams that focus only on rituals risk losing sight of continuous improvement and ownership, while over-automation can miss the need for human judgment in complex situations. Development managers should prioritize outcomes, encourage critical thinking about processes, and adapt Agile practices to their unique context rather than just checking boxes.</description>
			</item>
			<item>
				<title>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership.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.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>The Importance of Evidence-Based Management in Agile Environments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</link>
				<pubDate>Mon, 22 Jan 2024 11:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</guid>
				<description>Evidence-based management helps Agile teams make smarter decisions by tracking key metrics like value delivered, time to market, and ability to innovate, ensuring changes actually lead to improvement. Without data, teams risk wasting time and resources on ineffective changes, but with regular measurement and analysis, they can adapt quickly and foster continuous improvement. Start by identifying and tracking a few important metrics, involve your team, and use the insights to guide your next steps.</description>
			</item>
			<item>
				<title>Mastering Scrum: Effective Planning and Prioritisation for Agile Success</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/recipes/daily-scrum-recipe/</guid>
				<description>Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering-leadership.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.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>What should you do if your Sprint Review delivers harsh, scathing feedback?</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Transforming Sprint Reviews: How to Engage Stakeholders and Secure Meaningful Feedback</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</link>
				<pubDate>Fri, 15 Dec 2023 11:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</guid>
				<description>Sprint reviews often fail to engage stakeholders or generate useful feedback because stakeholders do not see the value or feel emotionally connected to the work. To address this, communicate the benefits of participation early, use visuals, create a safe space for feedback, engage stakeholders before reviews, and tailor your approach to their interests. Development managers should focus on making Sprint reviews relevant and personal to stakeholders to drive better engagement and product outcomes.</description>
			</item>
			<item>
				<title>Debunking the Scrum Myth: Why &#34;Twice the Work in Half the Time&#34; is a Misleading Promise</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/debunking-the-scrum-myth-why-twice-the-work-in-half-the-time-is-a-misleading-promise/</link>
				<pubDate>Thu, 02 Feb 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/debunking-the-scrum-myth-why-twice-the-work-in-half-the-time-is-a-misleading-promise/</guid>
				<description>The idea that Scrum enables teams to do twice the work in half the time is misleading and sets unrealistic expectations; Scrum is about delivering greater value to customers, not just increasing output. Focusing on outcomes rather than the number of features helps teams avoid burnout and frustration, and practices should be adapted to each team&amp;rsquo;s context rather than following so-called best practices. Development managers should prioritize value delivery and continuous improvement over chasing productivity slogans.</description>
			</item>
			<item>
				<title>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership.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.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>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering-leadership.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.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>There is no place like production</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/there-is-no-place-like-production/</link>
				<pubDate>Mon, 28 Dec 2020 14:12:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/there-is-no-place-like-production/</guid>
				<description>To deliver real value and reduce risk, teams must release features to production quickly so real users can provide feedback, since assumptions and testing environments cannot replace actual usage. Key measures like customer satisfaction, product usage, and employee satisfaction help validate value, and releasing early also offers financial benefits through capital expenditure write-downs. Prioritize getting small increments into production to maximize learning, value, and organizational savings.</description>
			</item>
			<item>
				<title>If you could teach just one thing about Scrum, what would it be?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</link>
				<pubDate>Mon, 27 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</guid>
				<description>The most important thing to teach about Scrum is the principle of empiricism, which means making work transparent, inspecting progress frequently, and adapting based on what is learned. This approach helps teams navigate complex, uncertain environments where traditional project management falls short. Focus on building your team&amp;rsquo;s ability to learn and adapt quickly, as Scrum reveals problems but does not solve them for you.</description>
			</item>
			<item>
				<title>Worst Contribution from a Product Owner that You Know Of</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</link>
				<pubDate>Tue, 06 Jun 2023 11:00:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</guid>
				<description>A product owner publicly blamed the development team during a sprint review instead of supporting them when stakeholders questioned product decisions, undermining trust and collaboration. Product owners should balance accountability to stakeholders with support for their teams, especially under pressure. Development managers should ensure product owners are prepared to defend team decisions and foster a collaborative environment.</description>
			</item>
			<item>
				<title>Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 06:00:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</guid>
				<description>Unrealised value, or the features your users need but you have not built or identified yet, is often overlooked but crucial for product success. To unlock this value, focus on understanding your users, validate assumptions with small experiments before full development, and increase deployment frequency to speed up feedback and learning. Make it a priority to continuously learn from your market and adapt your product strategy to stay relevant and maximise impact.</description>
			</item>
			<item>
				<title>Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events</title>
				<link>https://engineering-leadership.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.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>How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</link>
				<pubDate>Fri, 27 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</guid>
				<description>Ineffective Product Owners, whether due to lack of skills or organisational constraints, can hinder team performance and product success. Development managers should support Product Owners through relationship-building, organisational education, and open dialogue, while ensuring the team continues to deliver quality work. Take action by fostering collaboration and advocating for clear role expectations to help Product Owners and teams succeed.</description>
			</item>
			<item>
				<title>The Synergy Between Product Management and Product Development in Agile Environments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</link>
				<pubDate>Thu, 25 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</guid>
				<description>Product Management and Product Development must work closely together in agile environments to deliver products that meet current and future market needs. Product Management sets the vision and strategy, while Product Development brings these ideas to life through innovation, quality, and fast delivery, with both functions relying on continuous feedback and improvement. Development managers should ensure strong collaboration and feedback loops between these teams to maximize product value and long-term success.</description>
			</item>
			<item>
				<title>Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/</link>
				<pubDate>Thu, 24 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/</guid>
				<description>Keep your product backlog minimal but sufficient, ensuring it is clear and transparent for all stakeholders while also considering future needs to avoid surprises. Regularly review and reflect on completed work and unexpected issues to refine your backlog and adapt to changing circumstances. Aim for a balance that supports both current priorities and readiness for what lies ahead.</description>
			</item>
			<item>
				<title>How Do You Know How Long It Takes to Deliver Value?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</link>
				<pubDate>Fri, 26 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</guid>
				<description>Measuring and improving Time to Market is essential for delivering value quickly and staying competitive. Key metrics like lead time, cycle time, time to pivot, time to learn, and time to fix help teams identify bottlenecks and make better decisions. Focus on streamlining processes, automating tasks, gathering fast feedback, and building cross-functional teams to reduce delivery times and ensure you are delivering what customers need most.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Essential Skills for Product Owners</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</link>
				<pubDate>Mon, 18 Dec 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</guid>
				<description>Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Gluttony</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/</link>
				<pubDate>Wed, 11 Oct 2023 11:35:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/</guid>
				<description>Excessive backlog items, overambitious sprint plans, and unnecessary product features can slow teams down and reduce focus. Regularly prioritise and trim the backlog, set realistic sprint goals, and remove unused features to keep the team agile and deliver real value. Focus on quality and relevance rather than quantity to improve productivity and morale.</description>
			</item>
			<item>
				<title>What&#39;s the best way to work around multiple PO?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/what&#39;s-the-best-way-to-work-around-multiple-po/</link>
				<pubDate>Mon, 16 Sep 2019 17:57:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/what&#39;s-the-best-way-to-work-around-multiple-po/</guid>
				<description>If multiple people are acting as Product Owners but are not providing clear direction or attending key meetings, your team lacks true ownership of the product backlog and value delivery. This leads to wasted effort on features that may not matter, with industry data showing up to 65 percent of time spent on the wrong work. Raise this issue with management and ensure someone is clearly accountable for prioritizing and validating work, even if it means temporarily assigning the role until a suitable Product Owner is found.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</link>
				<pubDate>Mon, 29 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</guid>
				<description>Evidence-Based Management (EBM) helps product owners make better decisions by tracking key metrics like current value, unrealized value, ability to innovate, and time to market, ensuring teams focus on delivering the right value efficiently. Using EBM enables you to identify when to pivot, align stakeholders, and engage your team in the product’s success. Consider adopting EBM practices or training, such as the PAL-EBM course, to maximize value delivery and team effectiveness.</description>
			</item>
			<item>
				<title>Combatting Famine in Agile: How to Foster Stakeholder Engagement and Boost Team Morale</title>
				<link>https://engineering-leadership.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.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.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.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>Companies often say &#34;we-are going Agile!&#34; as if declaring it makes it so</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/companies-often-say-we-are-going-agile-as-if-declaring-it-makes-it-so/</link>
				<pubDate>Fri, 25 Apr 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/companies-often-say-we-are-going-agile-as-if-declaring-it-makes-it-so/</guid>
				<description>Simply declaring an Agile transformation does not make a company truly agile; real agility is about quickly responding to market changes, not just adopting frameworks like SAFe or Scrum@Scale. Successful organisations tailor their ways of working to their unique needs rather than copying others. Development managers should focus on building agility that fits their own business instead of relying on off-the-shelf solutions.</description>
			</item>
			<item>
				<title>What is Sprint Planning?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-sprint-planning/</link>
				<pubDate>Wed, 24 May 2023 14:00:36 +0000</pubDate>
				<guid>https://engineering-leadership.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>How do you know if you&#39;ve got a great Sprint Goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-if-you&#39;ve-got-a-great-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 11:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-if-you&#39;ve-got-a-great-sprint-goal/</guid>
				<description>A great sprint goal excites and energizes both the team and stakeholders, sparking curiosity and engagement. If your team feels genuinely enthusiastic and eager to start, your sprint goal is likely effective. Aim to craft sprint goals that inspire interest and conversation, not just list tasks.</description>
			</item>
			<item>
				<title>The Myth of Knowing Everything Upfront in Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</link>
				<pubDate>Mon, 16 Jun 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</guid>
				<description>You cannot know everything upfront in software development, so focus on continuous discovery and adapt as you learn. Scrum supports this by encouraging just enough planning and design to move forward, then delivering and learning from real use. Prioritise delivery and feedback over excessive upfront design to create more value.</description>
			</item>
			<item>
				<title>What is a sprint goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-goal/</link>
				<pubDate>Wed, 31 May 2023 11:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-goal/</guid>
				<description>A sprint goal is a clear, tactical objective that guides the Scrum team’s work during each sprint, connecting daily efforts to the broader product vision. It provides a concrete focus for the team, enables actionable stakeholder feedback at sprint reviews, and helps maintain alignment and motivation. Development managers should ensure each sprint has a well-defined, tangible goal to drive progress and gather meaningful feedback.</description>
			</item>
			<item>
				<title>Transforming Scope Creep into Success: Embrace Agility and Deliver Value in a Changing Market</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</link>
				<pubDate>Wed, 04 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</guid>
				<description>Scope creep is often a sign that traditional fixed-scope approaches are failing in today’s fast-changing market. Focusing on delivering customer value, embracing flexible planning, and actively seeking feedback helps teams adapt and succeed. Development managers should shift from rigid scope management to Agile practices that prioritize value and responsiveness to change.</description>
			</item>
			<item>
				<title>Unlocking Success: The Essential Role of Product Ownership in Lean Product Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-the-essential-role-of-product-ownership-in-lean-product-delivery/</link>
				<pubDate>Thu, 28 Sep 2023 09:01:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-the-essential-role-of-product-ownership-in-lean-product-delivery/</guid>
				<description>Strong product ownership is essential for aligning product vision with business goals, fostering team collaboration, and enabling quick adaptation to change. Lean product delivery helps teams focus on delivering customer value, encourages continuous improvement, and empowers teams to take ownership of their work. Development managers should invest in training, promote experimentation, and establish feedback loops to enhance product ownership and stay competitive.</description>
			</item>
			<item>
				<title>Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum</title>
				<link>https://engineering-leadership.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.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>Rethinking Product Backlog: Navigating Through the Weeds of Complexity</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/</link>
				<pubDate>Thu, 17 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/</guid>
				<description>Relying on rigid hierarchies in the Product Backlog can hinder transparency and adaptability in complex product development. Instead, focus on a flat backlog that highlights valuable, deliverable items, supports team autonomy, and leverages emergent practices over fixed best practices. Empower your teams to structure the backlog in ways that foster learning, innovation, and resilience in changing environments.</description>
			</item>
			<item>
				<title>My first Scrum team in the wild</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</link>
				<pubDate>Sun, 03 Apr 2011 21:44:22 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</guid>
				<description>A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.</description>
			</item>
			<item>
				<title>The Evolution of Product Management in the Agile Era</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</link>
				<pubDate>Thu, 18 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</guid>
				<description>Agile product management replaces long release cycles with short, frequent delivery, enabling faster feedback, reduced risk, and more responsive adaptation to customer needs. Building quality in from the start and using practices like continuous integration and a clear definition of done minimizes defects and waste. Development managers should focus on shorter cycles, continuous feedback, and embedding quality throughout the process to stay competitive and maximize business value.</description>
			</item>
			<item>
				<title>Mastering Product Ownership: Unlocking the Secrets to Effective Product Management in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-ownership-unlocking-the-secrets-to-effective-product-management-in-agile-teams/</link>
				<pubDate>Tue, 05 Sep 2023 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-ownership-unlocking-the-secrets-to-effective-product-management-in-agile-teams/</guid>
				<description>Effective product management, especially through a strong product owner, is essential for agile teams to stay focused, align with goals, and deliver value. Key practices include providing clear vision, engaging stakeholders, prioritising work, fostering collaboration, and continuous learning. Development managers should prioritise investing in skilled product owners to drive team success and product quality.</description>
			</item>
			<item>
				<title>What is the most common mistake in sprint planning?</title>
				<link>https://engineering-leadership.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.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>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-product-owner/</guid>
				<description>Hiring a professional Product Owner is increasingly valued, with companies seeking external candidates who bring fresh perspectives and strong business understanding. The Product Owner is accountable for maximizing product value by setting vision, managing stakeholders, collaborating with teams, making key decisions, and using evidence-based approaches to drive outcomes. Ensure candidates have both certification and practical experience, but remember that while responsibilities can be delegated, ultimate accountability always remains with the Product Owner.</description>
			</item>
			<item>
				<title>Navigating the Future with a Fine-Tuned Product Backlog</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</link>
				<pubDate>Thu, 10 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</guid>
				<description>A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery.</description>
			</item>
			<item>
				<title>Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</link>
				<pubDate>Mon, 06 May 2024 13:29:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</guid>
				<description>Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership.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.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.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.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>Most companies still get Product Ownership wrong</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</link>
				<pubDate>Thu, 17 Apr 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</guid>
				<description>Many companies misunderstand the Product Owner role, treating it as simple backlog management or assigning it to any business analyst, which leads to weak products and misaligned teams. Effective Product Owners are strategic leaders who own the vision, make tough decisions, and use evidence to guide development. Development managers should ensure they are hiring or empowering true Product Owners with the right skills and authority, not just filling a position.</description>
			</item>
			<item>
				<title>Vision, Value, and Validation: The Keys to Successful Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</link>
				<pubDate>Thu, 14 Dec 2023 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</guid>
				<description>When moving from project management to product management, it is essential for Product Owners to fill the gap left by traditional planning tools by focusing on vision, value, and validation. Clearly define and communicate the product vision, ensure all work aligns with delivering real value, and continuously validate progress through feedback and measurement. Prioritize these pillars to keep teams aligned and maximize product impact; consider seeking support if challenges arise.</description>
			</item>
			<item>
				<title>Unlocking the Product Owner Potential: Bridging Theory and Practice in Agile Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-product-owner-potential-bridging-theory-and-practice-in-agile-leadership/</link>
				<pubDate>Fri, 09 Jun 2023 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-product-owner-potential-bridging-theory-and-practice-in-agile-leadership/</guid>
				<description>The Product Owner role requires moving beyond theory to practical leadership, taking on broader responsibilities like marketing, sales, and contract negotiation, and influencing key business areas. An immersive, collaborative learning approach helps product owners apply new strategies, share real-world experiences, and learn from peers to drive better outcomes. Development managers should support ongoing learning and cross-functional engagement for their product owners to maximize their impact.</description>
			</item>
			<item>
				<title>The Sprint Goal is a commitment for the Sprint Backlog</title>
				<link>https://engineering-leadership.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.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>The Power of Humility in Agile: A Core Virtue for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/</link>
				<pubDate>Tue, 12 Dec 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/</guid>
				<description>Humility is crucial for Agile teams because it enables better collaboration, trust, and openness to feedback, leading to stronger products and happier teams. Recognizing that not all ideas are right, listening to others, and being willing to change course based on data and feedback are key to success. Development managers should foster a culture where team members check their egos, seek diverse perspectives, and use data thoughtfully to continuously improve.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership.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.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>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</link>
				<pubDate>Wed, 03 Apr 2024 17:21:43 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</guid>
				<description>Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team&amp;rsquo;s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team&amp;rsquo;s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results.</description>
			</item>
			<item>
				<title>Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</link>
				<pubDate>Tue, 26 Mar 2024 10:56:26 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</guid>
				<description>Using a flat backlog instead of a hierarchical one makes it easier to prioritise work, adapt to changing needs, and focus on delivering value rather than just managing tasks. Flat structures avoid the inflexibility and complexity of parent-child relationships, allowing teams to use tags and flexible visualisations for context. Development managers should consider shifting to a flat backlog to improve agility and value delivery.</description>
			</item>
			<item>
				<title>From Product Owner to Systemic Leader: Embracing the Evolution in Agile Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/from-product-owner-to-systemic-leader-embracing-the-evolution-in-agile-leadership/</link>
				<pubDate>Fri, 28 Jul 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/from-product-owner-to-systemic-leader-embracing-the-evolution-in-agile-leadership/</guid>
				<description>Experienced Product Owners often grow into broader leadership roles, taking on more accountability and influencing organisational culture and systems. This transition requires a shift from managing backlogs to creating environments that empower teams and foster innovation. Development managers should support Product Owners in developing leadership skills and consider training like Agile Leadership Essentials to help them drive positive change across the organisation.</description>
			</item>
			<item>
				<title>How do you select the most valuable items for the sprint backlog?</title>
				<link>https://engineering-leadership.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.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>Mastering Prioritisation: How Product Owners Can Drive Value and Accountability</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</link>
				<pubDate>Mon, 27 Nov 2023 11:00:56 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</guid>
				<description>Product Owners play a crucial role in ensuring resources are spent wisely by prioritising the most valuable work, aligning development with business goals, and maintaining stakeholder trust through clear communication. Effective prioritisation maximises value delivery, keeps teams focused, and adapts to changing needs. Development managers should support Product Owners in understanding users, collaborating closely, and staying flexible to drive successful outcomes.</description>
			</item>
			<item>
				<title>Signs You&#39;re Failing as a Product Owner: How to Take Control and Deliver Real Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/signs-you&#39;re-failing-as-a-product-owner-how-to-take-control-and-deliver-real-value/</link>
				<pubDate>Fri, 22 Sep 2023 07:00:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/signs-you&#39;re-failing-as-a-product-owner-how-to-take-control-and-deliver-real-value/</guid>
				<description>A failing product owner is marked by poor product quality, inconsistent delivery, lack of vision, and not taking true ownership of the product. To deliver real value, product owners must make decisions, communicate a clear vision, and focus on actual outcomes rather than vanity metrics. Development managers should ensure their product owners are empowered to lead, make tough calls, and stay aligned with user and business needs.</description>
			</item>
			<item>
				<title>How much of an impact can a strong, skilled product owner have?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-a-strong-skilled-product-owner-have/</link>
				<pubDate>Mon, 30 Jan 2023 07:30:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-a-strong-skilled-product-owner-have/</guid>
				<description>A strong, skilled product owner is critical for turning engineering output into valuable solutions that solve real customer problems and drive business impact. Great product owners look ahead, anticipate market and customer needs, and enable teams to deliver the right features at the right time, avoiding the trap of just building more features. To maximize effectiveness, empower your product owner to focus on strategic value and proactive discovery, not just backlog management.</description>
			</item>
			<item>
				<title>A bloated backlog is not a sign of good product management</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/a-bloated-backlog-is-not-a-sign-of-good-product-management/</link>
				<pubDate>Thu, 10 Apr 2025 15:30:07 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/a-bloated-backlog-is-not-a-sign-of-good-product-management/</guid>
				<description>A backlog packed with every idea signals indecision, not good product management. Overloaded backlogs make it hard to prioritize, confuse stakeholders, and slow teams down. Keep your backlog focused on the most valuable upcoming work and regularly remove items your team cannot realistically address.</description>
			</item>
			<item>
				<title>In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</link>
				<pubDate>Mon, 30 Sep 2019 18:35:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</guid>
				<description>When managing multiple Scrum teams in a Nexus, the Product Owner should focus on high-level vision and attend only the Nexus Sprint Planning, delegating detailed planning to designated Team Owners or Area Owners for each team. This approach reduces overload, maintains alignment with the product vision, and relies on strong communication and autonomy within teams. To implement this, assign a representative for each team to handle their Sprint Planning and ensure ongoing coordination with the Product Owner.</description>
			</item>
			<item>
				<title>A great backlog isn’t just a list of tasks</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/a-great-backlog-isn-t-just-a-list-of-tasks/</link>
				<pubDate>Sun, 13 Apr 2025 15:30:17 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/a-great-backlog-isn-t-just-a-list-of-tasks/</guid>
				<description>A backlog should guide strategic decisions and reflect the product vision, not just list tasks. Filling it with unchecked requests leads to loss of focus and unclear priorities. Review your backlog to ensure it highlights what truly matters for delivering value and supports your product strategy.</description>
			</item>
			<item>
				<title>What is a product owner?    Why are they essential?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-owner-why-are-they-essential/</link>
				<pubDate>Tue, 23 May 2023 14:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-owner-why-are-they-essential/</guid>
				<description>A product owner is essential because they are accountable for maximizing the value delivered by the Scrum team, not just managing the backlog. They ensure alignment between stakeholders, customers, and developers by setting a clear vision and strategy based on market and user insights. To succeed, make sure your product owner is empowered to lead, deeply understands your market, and keeps everyone focused on shared goals.</description>
			</item>
			<item>
				<title>How to Overcome Agile Banditry: A Product Owner’s Journey</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/</link>
				<pubDate>Wed, 10 Jan 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/</guid>
				<description>Product Owners who micromanage and focus on rigid task planning undermine team engagement and product success. Shifting to a focus on vision, value, and outcomes while empowering teams leads to higher motivation, better collaboration, and improved results. Development managers should encourage Product Owners to let go of detailed control, trust their teams, and prioritize clear goals and customer value.</description>
			</item>
			<item>
				<title>Product Owners are not a myth</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/product-owners-are-not-a-myth/</link>
				<pubDate>Tue, 18 Oct 2011 01:56:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/product-owners-are-not-a-myth/</guid>
				<description>Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large product backlogs effectively.</description>
			</item>
			<item>
				<title>The Real Scope of a Product Owner: Beyond the Backlog</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</link>
				<pubDate>Mon, 27 Nov 2023 06:46:47 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</guid>
				<description>The Product Owner role goes far beyond managing the backlog, requiring strategic decision-making, budget accountability, and proactive leadership to maximize product value and stay ahead of the market. Success depends on strong relationships, deep market understanding, and continuous learning, not just training. Development managers should ensure Product Owners have the authority, information, and support needed to drive product direction and deliver real business impact.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Hiring a Product Owner? Avoid copying job specs from the internet</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/</link>
				<pubDate>Tue, 15 Apr 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/</guid>
				<description>When hiring a Product Owner, do not rely on generic job descriptions; a true Product Owner drives product success by setting vision, prioritizing value, collaborating closely with teams, making data-driven decisions, and maintaining accountability. Delegation is necessary, but the PO must remain responsible for outcomes, not just manage tasks. Review your job specs to ensure they focus on leadership and product impact, not just administrative duties.</description>
			</item>
			<item>
				<title>Sprint Planning Recipe</title>
				<link>https://engineering-leadership.hinshelwood.com/recipes/sprint-planning-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/recipes/sprint-planning-recipe/</guid>
				<description>Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders.</description>
			</item>
			<item>
				<title>What is a product goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-goal/</link>
				<pubDate>Tue, 30 May 2023 11:00:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-goal/</guid>
				<description>A sprint goal is a specific, tactical objective that guides a Scrum team’s work during each sprint, connecting daily efforts to the broader product goal and vision. It provides a clear, tangible focus for the team and enables actionable stakeholder feedback at sprint reviews. Development managers should ensure every sprint has a well-defined goal to drive alignment, motivation, and meaningful progress.</description>
			</item>
			<item>
				<title>A great Product Owner drives product strategy, not just manages the backlog</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/</link>
				<pubDate>Tue, 08 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/</guid>
				<description>A great Product Owner shapes product strategy by owning the vision, understanding customers and the market, making tough decisions, aligning stakeholders, and adapting based on evidence. Focusing only on backlog management limits their impact; empowered POs drive real value and influence roadmaps. Ensure your Product Owners have the authority and support to make strategic decisions, not just administrative tasks.</description>
			</item>
			<item>
				<title>What is the one thing a PSPO course forces you to focus on?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-a-pspo-course-forces-you-to-focus-on/</link>
				<pubDate>Mon, 15 May 2023 14:00:13 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-a-pspo-course-forces-you-to-focus-on/</guid>
				<description>The PSPO course centers on understanding and defining value, which goes beyond just financial outcomes and varies by organization. Product Owners are expected to lead in clarifying and championing what value means for their teams and stakeholders. Development managers should ensure their teams have a shared, well-communicated definition of value to guide decisions and priorities.</description>
			</item>
			<item>
				<title>Mastering the Art of Product Ownership: Balancing Innovation, Customer Needs, and Team Dynamics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-balancing-innovation-customer-needs-and-team-dynamics/</link>
				<pubDate>Mon, 08 May 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-balancing-innovation-customer-needs-and-team-dynamics/</guid>
				<description>Effective product ownership requires balancing innovation with customer needs and team well-being, not just chasing new features. The Advanced PSPO course highlights the importance of data-informed decisions, ongoing customer engagement, and strong team collaboration. Development managers should ensure product owners focus on both delivering value and maintaining healthy team dynamics.</description>
			</item>
			<item>
				<title>Unlocking Agile’s Core: Questioning to Create Value</title>
				<link>https://engineering-leadership.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.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>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</link>
				<pubDate>Mon, 15 Mar 2010 13:08:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</guid>
				<description>Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Insights from the New Scrum.org Course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/</link>
				<pubDate>Thu, 30 Nov 2023 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/</guid>
				<description>Scrum.org’s new Product Backlog Management course offers focused, practical training in backlog management, helping teams capture, prioritize, and break down work for better clarity and alignment. The compact 8-hour format teaches actionable techniques to minimize distractions, improve transparency, and ensure teams deliver high-value work that supports business goals. Development managers should consider this course to streamline their backlog processes and boost team efficiency.</description>
			</item>
			<item>
				<title>Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-the-professional-scrum-product-owner-course-transforms-your-agile-journey/</link>
				<pubDate>Tue, 23 Aug 2022 17:22:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-the-professional-scrum-product-owner-course-transforms-your-agile-journey/</guid>
				<description>The Professional Scrum Product Owner course provides practical, hands-on training that helps product owners maximise product value, make effective decisions, and adopt modern agile practices. Participants benefit from interactive sessions, ongoing support, and access to a peer community, ensuring skills are applied and developed beyond the classroom. Development managers should consider this course to strengthen product leadership and drive better outcomes in their teams.</description>
			</item>
			<item>
				<title>Understanding Product Discovery: Why It Matters More Than Ever</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/understanding-product-discovery-why-it-matters-more-than-ever/</link>
				<pubDate>Mon, 26 Aug 2024 07:44:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/understanding-product-discovery-why-it-matters-more-than-ever/</guid>
				<description>Product Discovery is a proactive process that helps teams identify what to build and why, ensuring alignment with business goals and user needs. It goes beyond backlog refinement by uncovering new opportunities, involving diverse perspectives, and driving strategic direction at both portfolio and team levels. To maximize product value and ROI, development managers should invest in deliberate discovery practices, involve their teams early, and continuously gather feedback to guide decisions.</description>
			</item>
			<item>
				<title>How does a Scrum team create a sprint goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</link>
				<pubDate>Thu, 01 Jun 2023 11:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</guid>
				<description>A Scrum team creates a sprint goal by combining the product’s strategic direction, the product owner’s tactical priorities, and current engineering challenges to identify the most valuable next step. The team then selects backlog items that best align with this goal to deliver clear value to stakeholders. Encourage your teams to invest time in understanding context before setting sprint goals for better alignment and outcomes.</description>
			</item>
			<item>
				<title>How critical is a Product Owner in developing a great Product Backlog?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</link>
				<pubDate>Wed, 31 May 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</guid>
				<description>A strong product owner is essential for creating and maintaining a focused, valuable product backlog that aligns with strategy and avoids becoming an unmanageable list of requests. The product owner is fully responsible for prioritizing and communicating the backlog, using discernment to filter out items that do not support the product vision. Development managers should ensure their product owners are empowered and proactive to keep teams focused on delivering real value.</description>
			</item>
			<item>
				<title>Unlocking Effective Product Development: How a Hypothesis-Driven Approach Transforms User Experience</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</link>
				<pubDate>Mon, 10 Apr 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</guid>
				<description>A hypothesis-driven approach to product development helps teams make better decisions by focusing on user needs, testing ideas with small experiments, and measuring outcomes before committing to full features. Collaboration between design and engineering is essential to align daily decisions with long-term goals, and integrating these practices into continuous delivery ensures ongoing improvement. Development managers should encourage experimentation, cross-team collaboration, and data-driven feedback loops to build products that truly meet user needs.</description>
			</item>
			<item>
				<title>The Product Goal is a commitment for the Product Backlog</title>
				<link>https://engineering-leadership.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.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>Customer Focus</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-focus/</link>
				<pubDate>Tue, 13 May 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/customer-focus/</guid>
				<description>Customer Focus is not a platitude. It&amp;rsquo;s the first principle of agile delivery and product development. It defines value, directs investment, and constrains decisions. If you&amp;rsquo;re not anchored in real customer outcomes, you&amp;rsquo;re optimising the wrong system. This principle demands more than empathy. It demands feedback, evidence, and relentless alignment to customer need.</description>
			</item>
			<item>
				<title>Sprint Review</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/sprint-review/</link>
				<pubDate>Sun, 11 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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.hinshelwood.com/tags/increment/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Product Backlog</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-backlog/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-backlog/</guid>
				<description>The Product Backlog is a dynamic and prioritised list of work items that acts as the definitive source for what needs to be accomplished in order to deliver a product. It includes features, enhancements, bug fixes, and technical tasks, providing teams with a clear understanding of their objectives. This concept is vital as it allows teams to deliver value in a predictable and sustainable manner by offering transparency regarding priorities and progress. Effective management of the backlog encourages collaboration among stakeholders and enables continuous refinement based on feedback and shifting market conditions. It empowers teams to make informed decisions about their next steps, aligning their work with strategic goals and customer needs. The Product Backlog is more than just a to-do list; it is a living artefact that captures the evolving understanding of the product and its context, promoting a culture of continuous improvement and adaptability. By maintaining a well-structured backlog, organisations can enhance agility, minimise waste, and optimise resource allocation, leading to more successful product outcomes. This systematic approach to backlog management supports long-term planning while remaining flexible enough to address new insights and challenges as they emerge. Ultimately, the Product Backlog is foundational to effective Agile practices, ensuring that teams focus on delivering high-quality, valuable products that meet user expectations and contribute to business success.</description>
			</item>
			<item>
				<title>Current Value</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/current-value/</guid>
				<description>Current Value is a vital metric within Evidence-Based Management that quantifies the real-time value a product or service provides to its users. It includes various indicators such as customer satisfaction, revenue impact, and performance feedback, which together offer insights into the value being realised at any moment. This concept is crucial for teams striving to deliver value in a predictable and sustainable manner, as it facilitates continuous assessment and adjustment based on actual performance rather than assumptions. By tracking Current Value, organisations can make data-driven decisions that improve their offerings and better align them with customer needs. This ongoing evaluation promotes a culture of responsiveness and adaptability, allowing teams to swiftly adjust to feedback and shifting market conditions. Unlike static measures, Current Value is dynamic and systemic, reflecting the changing landscape of customer expectations and business environments. It empowers teams to concentrate on delivering meaningful outcomes, ensuring that their efforts lead to long-term success and customer loyalty. This emphasis on real-time value delivery distinguishes Current Value from other concepts such as Value Stream Management or Customer Satisfaction, which may not fully capture the immediacy and comprehensive nature of the value being generated.</description>
			</item>
			<item>
				<title>Time to Market</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/time-to-market/</link>
				<pubDate>Thu, 10 Apr 2025 14:20:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/time-to-market/</guid>
				<description>Time to Market is a critical metric that evaluates how quickly an organisation can transform ideas into market-ready products or features, incorporating various measures such as lead time and cycle time to provide a comprehensive understanding of product development efficiency. This concept is essential for organisations striving to deliver value in a predictable and sustainable manner, as a shorter Time to Market allows teams to swiftly address customer needs and adapt to market fluctuations. By prioritising Time to Market, organisations can gain a competitive advantage, ensuring that their innovations reach customers ahead of competitors. This focus on agility promotes a culture of continuous improvement, encouraging teams to refine processes and eliminate inefficiencies. The systemic nature of Time to Market impacts not only individual projects but also the overall organisational capacity for innovation and adaptability. It aligns with Lean and Agile methodologies, fostering a mindset that prioritises speed while maintaining quality. Ultimately, a strong commitment to Time to Market nurtures an environment where delivering value becomes a core organisational principle, contributing to long-term success and resilience in an ever-evolving marketplace.</description>
			</item>
			<item>
				<title>Product Development</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/product-development/</link>
				<pubDate>Wed, 09 Apr 2025 14:47:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/product-development/</guid>
				<description>Product Development is a structured approach to creating valuable and usable products through iterative learning, customer feedback, and continuous improvement. Originating from methodologies such as Agile, Lean, and DevOps, it aligns strategy, discovery, and delivery to enhance outcomes while reducing risks. This process is vital as it enables teams to swiftly adapt to shifting market demands and customer preferences, fostering an innovative environment. By promoting collaboration and transparency among cross-functional teams, Product Development ensures that customer feedback informs product iterations, leading to enhancements that not only meet but exceed user expectations. Its systemic nature underscores that Product Development is not just about launching a product but establishing a sustainable framework for ongoing value delivery. This approach encourages experimentation and learning, resulting in greater efficiency and effectiveness in product delivery. By prioritising continuous improvement and adaptability, organisations can build resilience and maintain a competitive advantage in a dynamic landscape. Ultimately, the focus on value delivery ensures that all efforts align with the organisation&amp;rsquo;s strategic objectives, highlighting the critical role of a well-defined Product Development process in achieving long-term success.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/common-goals/</link>
				<pubDate>Fri, 21 Mar 2025 14:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/common-goals/</guid>
				<description>Common Goals are a foundational principle for effective delivery within organisations, serving to align strategy with execution and ensuring that every decision, Sprint, and line of code contributes to a shared purpose. These goals are not mere aspirational statements; they represent the strategic objectives that unify efforts and connect individual contributions to meaningful outcomes. In the context of agile, DevOps, and product development, understanding and committing to common goals fosters ownership, clarity, and accountability among team members, enabling distributed decision-making and reducing friction in prioritisation. This alignment is crucial for creating adaptive and high-performing systems, as it allows teams to surface misalignments early and make informed trade-offs without waiting for permission. Furthermore, the integration of tactical commitments, such as Product Goals and Sprint Goals, ensures that strategic intent is operationalised at every level of delivery. By maintaining a focus on measurable outcomes and desired impacts, organisations can avoid the pitfalls of busywork and ensure that their efforts are directed towards achieving significant results. Ultimately, common goals provide the necessary framework for teams to understand their role in the larger organisational context, making it imperative for leaders to establish and communicate these objectives clearly.</description>
			</item>
			<item>
				<title>Agile Product Operating Model</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-product-operating-model/</link>
				<pubDate>Fri, 21 Mar 2025 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-product-operating-model/</guid>
				<description>The Agile Product Operating Model (APOM) is an operating model that integrates agile methodologies with contemporary product management principles, enabling organisations to consistently deliver value through a product-centric approach. As a specialization of the Adaptive Operating Model, APOM addresses the specific need to shift away from traditional project-based approaches, which often emphasise rigid timelines and budgets, toward continuous value delivery and responsiveness to customer feedback. This model is crucial in the context of agile, DevOps, and product development as it aligns organisational efforts around well-defined outcomes, ensuring that every product has clear boundaries, stakeholders, and measurable value. By integrating elements such as business and technology roadmaps, operational stability, and governance, APOM allows organisations to adapt swiftly to market changes while maintaining a clear connection to their strategic goals. Furthermore, it emphasises evidence-based decision-making, fostering transparency and collaboration across teams, which enhances the ability to manage and optimise product value effectively. While non-agile product operating models are possible, APOM provides the recommended approach that empowers organisations to shape their unique operating models, driving sustainable value creation in a dynamic environment.</description>
			</item>
			<item>
				<title>Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/scrum/</link>
				<pubDate>Tue, 04 Mar 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/scrum/</guid>
				<description>Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum&amp;rsquo;s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum&amp;rsquo;s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment.</description>
			</item>
			<item>
				<title>Backlog Refinement</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/</guid>
				<description>Backlog Refinement is a fundamental practice within Agile methodologies that focuses on ensuring the product backlog is clearly defined, prioritised, and prepared for execution. Originating from the need for effective collaboration between product owners and development teams, this ongoing process involves clarifying requirements, estimating effort, and adjusting priorities based on evolving insights and stakeholder feedback. The importance of Backlog Refinement lies in its ability to enhance focus and alignment on delivering value, thereby enabling teams to deliver outcomes predictably and sustainably. By regularly refining the backlog, teams can reduce risks associated with ambiguity and miscommunication, facilitating smoother sprint planning and execution. This practice promotes a culture of continuous improvement, allowing teams to adapt to changing circumstances and customer needs while maintaining momentum. Additionally, it supports long-term planning by prioritising the most valuable items, optimising resource allocation, and enhancing overall productivity. By integrating Backlog Refinement into their workflows, organisations can foster a more responsive and agile environment, leading to improved product outcomes and greater stakeholder satisfaction. This systemic approach not only streamlines the development process but also encourages a proactive mindset among team members, empowering them to take ownership of their work and align with the organisation&amp;rsquo;s strategic objectives.</description>
			</item>
			<item>
				<title>Customer Feedback Loops</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-feedback-loops/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/customer-feedback-loops/</guid>
				<description>Customer feedback loops are critical processes that enable the integration of user insights into product development, ensuring that offerings are closely aligned with actual user needs and preferences. Originating from agile methodologies, these loops involve the systematic collection and analysis of customer feedback, fostering a culture of responsiveness and adaptability within teams. Their importance lies in the ability to drive predictable and sustainable value delivery, allowing teams to make informed decisions based on real user experiences rather than assumptions. This reduces the risk of misalignment between product features and market demands, supporting a long-term vision where learning from customer interactions is central to the development cycle. Additionally, customer feedback loops enhance the understanding of user behaviour, informing strategic planning and prioritisation. By embedding these mechanisms into the organisational structure, teams promote continuous learning and improvement, leading to increased customer satisfaction and loyalty. This proactive approach not only mitigates potential failures but also positions organisations to capitalise on new opportunities, ensuring competitiveness in a rapidly changing market environment.</description>
			</item>
			<item>
				<title>Definition of Ready</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/definition-of-ready/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/definition-of-ready/</guid>
				<description>Definition of Ready (DoR) is a concept within the Scrum framework that outlines the criteria necessary for a Backlog Item to be considered ready for implementation by the development team. It emerges from the collaborative understanding among Developers, the Product Owner, and Stakeholders regarding what is required to proceed with a Backlog Item. The importance of DoR lies in its potential to enhance clarity and alignment within agile teams, yet it also presents challenges, such as creating a false sense of readiness, neglecting the need for ongoing refinement, and leading to misconceptions about its equivalence with the Definition of Done (DoD). Unlike the DoD, which is an absolute measure of completion, the subjective nature of DoR can result in partial implementation, risking the integrity of the development process. To mitigate these issues, it is suggested that teams adopt a more nuanced approach to defining readiness, ensuring that each Backlog Item meets specific criteria, such as having a clear outcome, hypothesis, and telemetry for evaluation. The INVEST criteria further guide the formulation of Product Backlog Items, emphasising their independence, negotiability, value, estimability, size, and testability. Ultimately, a well-defined DoR fosters effective communication and understanding within agile teams, contributing to successful product development and organisational design.</description>
			</item>
			<item>
				<title>Estimation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/estimation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/estimation/</guid>
				<description>Estimation is a fundamental practice within Agile and Scrum methodologies that allows teams to predict the effort and time necessary to complete tasks or deliver features. Originating from the need to manage uncertainty in project management, estimation employs empirical data and collaborative techniques to align stakeholder expectations and foster a shared understanding of project scope and timelines. This practice transcends mere numerical assignment; it involves engaging the entire team in discussions that utilise collective knowledge and experience, thereby enhancing both accuracy and team buy-in. Effective estimation is crucial as it enables teams to deliver value in a predictable and sustainable manner, facilitating improved planning and resource allocation. It also supports continuous improvement through a feedback loop that compares past estimates with actual outcomes, refining future forecasting. This iterative process promotes a culture of transparency and accountability, which is vital for high-performing teams. Unlike broader concepts such as Agile Planning or Backlog Refinement, estimation focuses on the tactical execution of tasks, serving as a foundational element for successful Agile practices. By incorporating estimation into their workflows, organisations can improve their agility and responsiveness in a rapidly changing market, ultimately leading to better outcomes for customers and stakeholders.</description>
			</item>
			<item>
				<title>Forecasting</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/forecasting/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/forecasting/</guid>
				<description>Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation.</description>
			</item>
			<item>
				<title>Hypothesis Driven Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/hypothesis-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/hypothesis-driven-development/</guid>
				<description>Hypothesis Driven Development is a structured methodology that utilises experimentation and validated learning to guide product decisions. Originating from the need to make informed choices based on user needs and behaviours, this approach enables teams to formulate hypotheses and design experiments that test these assumptions in real-world contexts. Its importance lies in enhancing predictability and sustainability in delivering value, as it allows organisations to gather actionable data and insights that inform product development, thereby reducing reliance on intuition. By continuously testing and iterating on ideas, teams can swiftly adapt to evolving market conditions and user feedback, minimising the risk of developing products that fail to meet customer expectations. This methodology fosters a culture of learning and experimentation, encouraging teams to embrace uncertainty and view setbacks as opportunities for growth. In contrast to traditional development methods that often depend on extensive upfront planning, Hypothesis Driven Development promotes an agile mindset where learning and adaptation are central to the process. This long-term, systemic approach not only leads to improved product outcomes but also empowers teams to innovate and effectively tackle emerging challenges, ultimately contributing to organisational success through a more profound understanding of customer value and market dynamics.</description>
			</item>
			<item>
				<title>Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/product-management/</guid>
				<description>Product Management is a strategic discipline focused on aligning customer needs, business objectives, and technical feasibility to maximise value delivery in product development. Originating from Agile methodologies, particularly within the Scrum framework, the role of the Product Owner is central to this discipline, emphasising accountability for value rather than mere output. This approach is crucial in ensuring that product teams prioritise impactful features over an extensive list of functionalities, thereby avoiding the pitfalls of feature bloat. Effective Product Management operates within a social system, requiring collaboration with stakeholders, executives, and developers while continuously engaging with users to maintain a compelling product vision. The use of evidence-based management is vital, as it allows Product Managers to make informed decisions based on measurable metrics rather than vanity metrics. Customer feedback is treated as a strategic asset, necessitating discernment in its application to avoid misalignment with product goals. Additionally, technical empathy is essential for understanding the feasibility and risks associated with product strategies, ensuring that desirability, viability, and feasibility are balanced. Clear boundaries of authority and accountability are necessary for effective collaboration, with Product Managers defining the &amp;lsquo;what&amp;rsquo; and &amp;lsquo;why&amp;rsquo;, while developers focus on the &amp;lsquo;how&amp;rsquo;. Ultimately, Product Management is about optimising value through informed decision-making, fostering a culture of learning, and prioritising outcomes over outputs, making it a critical function in Agile and DevOps environments.</description>
			</item>
			<item>
				<title>Product Owner</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Product Validation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-validation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-validation/</guid>
				<description>Product validation is the process of testing product ideas with actual users to confirm that they meet market demands and provide real customer value. This practice is essential for organisations seeking to develop products that connect with their target audience, as it reduces the risk of investing in features or solutions that do not meet user expectations. By involving users early and frequently, teams can collect feedback that informs design and functionality, facilitating iterative enhancements that improve product-market fit. The importance of product validation lies in its capacity to enable teams to deliver value in a predictable and sustainable manner, fostering a culture of experimentation and learning where assumptions are validated through real-world data rather than theoretical models. This not only speeds up the development process but also increases the likelihood of product success in a competitive environment. Additionally, product validation is a long-term, systemic practice that aligns well with agile methodologies, lean principles, and DevOps practices. It promotes cross-functional collaboration and empowers teams to make informed decisions based on user insights, ultimately driving continuous improvement and innovation. By prioritising validation, organisations can establish a strong feedback loop that enhances their adaptability and resilience in a constantly changing market.</description>
			</item>
			<item>
				<title>Agile Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-product-management/</guid>
				<description>Agile Product Management is a methodology that prioritises maximising product value by aligning organisational strategy with customer needs through iterative and incremental delivery processes. Originating from Agile principles, this approach allows teams to swiftly adapt to changing market demands while ensuring that product development is informed by real user feedback. Unlike Agile Project Management, which focuses on project execution within Agile frameworks, Agile Product Management encompasses the entire product lifecycle, from discovery to delivery, fostering a culture of collaboration among cross-functional teams. This systemic approach to value delivery emphasises not only immediate outputs but also the long-term evolution of products to meet shifting user requirements. By enabling organisations to maintain a competitive edge and adapt to disruptions, Agile Product Management is essential for driving sustained growth and innovation. It enhances organisational agility and resilience, empowering teams to thrive in dynamic environments and ultimately leading to improved customer satisfaction and retention.</description>
			</item>
			<item>
				<title>Value Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/value-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/value-delivery/</guid>
				<description>Value Delivery is a systematic approach aimed at providing consistent and meaningful outcomes to customers through iterative and incremental processes. Originating from methodologies such as Lean and Agile, it is used in product development to ensure that efforts are aligned with customer needs, allowing for every release to contribute tangible benefits. This concept is vital as it enables teams to deliver value predictably and sustainably, fostering a culture of continuous improvement and responsiveness to change. By prioritising value delivery, organisations can significantly enhance customer satisfaction and loyalty, as products are more likely to meet expectations. It promotes cross-functional collaboration, encouraging teams to work together to identify and eliminate waste, optimise workflows, and streamline processes. Value Delivery encompasses the entire lifecycle of product development, from initial discovery to delivery and beyond, ensuring that teams can adapt to evolving market demands and customer feedback. This long-term focus ultimately leads to sustained organisational success and resilience in a competitive landscape, as embedding value delivery into the organisational culture creates a robust framework that supports innovation and drives continuous value creation for customers and stakeholders alike.</description>
			</item>
	</channel>
</rss>
