<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Product Development on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/categories/product-development/</link>
		<description>Recent content in Product Development on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 24 Jun 2026 10:41:27 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/categories/product-development/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>Don’t Manage Dependencies, Remove Them</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</link>
				<pubDate>Mon, 29 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</guid>
				<description>Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy.</description>
			</item>
			<item>
				<title>Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</link>
				<pubDate>Mon, 15 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</guid>
				<description>The phrase “flow of value” is often misused in software development, as value is only confirmed when customers validate it, not just when work is completed. Teams should focus on validating outcomes quickly, breaking work into small, testable increments, and using data to cut features that do not deliver real value. To truly optimise value, ensure every item has a clear hypothesis, measure time to feedback, and prioritise learning over simply moving work through the system.</description>
			</item>
			<item>
				<title>Is Agile Really Just a Mindset?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/</link>
				<pubDate>Mon, 11 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/</guid>
				<description>Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change.</description>
			</item>
			<item>
				<title>Rethinking Capacity Planning</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/</link>
				<pubDate>Mon, 21 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/</guid>
				<description>Capacity planning should focus on optimising system flow and predictability, not tracking individual hours or task assignments. Shifting from micromanagement to managing work as a system at portfolio, category, and team levels helps prevent overload, improves value delivery, and enables reliable forecasting. Development managers should prioritise system-level metrics, enforce work-in-progress limits, and empower teams to pull well-prepared work, creating sustainable and predictable delivery.</description>
			</item>
			<item>
				<title>Why Topic Branches Drive High-Quality Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</link>
				<pubDate>Mon, 14 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</guid>
				<description>Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality.</description>
			</item>
			<item>
				<title>Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</link>
				<pubDate>Wed, 14 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</guid>
				<description>When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility.</description>
			</item>
			<item>
				<title>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</link>
				<pubDate>Mon, 22 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</guid>
				<description>Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control.</description>
			</item>
			<item>
				<title>The Definition of Done is a Commitment to Quality</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</link>
				<pubDate>Mon, 26 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</guid>
				<description>Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value.</description>
			</item>
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Velocity isn’t how many story points a team burns down</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</link>
				<pubDate>Mon, 10 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</guid>
				<description>Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness.</description>
			</item>
			<item>
				<title>Stop Hiding Behind Complexity and Start Delivering Continuously</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</link>
				<pubDate>Mon, 24 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</guid>
				<description>Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery.</description>
			</item>
			<item>
				<title>Should You Use One Project to Rule Them All in Azure DevOps?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</link>
				<pubDate>Mon, 25 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</guid>
				<description>Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and delivery.</description>
			</item>
			<item>
				<title>Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</link>
				<pubDate>Wed, 07 May 2025 11:46:58 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</guid>
				<description>Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact.</description>
			</item>
			<item>
				<title>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>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</link>
				<pubDate>Wed, 21 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</guid>
				<description>Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence.</description>
			</item>
			<item>
				<title>Testing in Production Maximises Quality and Value</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</link>
				<pubDate>Thu, 13 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</guid>
				<description>Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness.</description>
			</item>
			<item>
				<title>Definition of Done - Objective vs Subjective</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</link>
				<pubDate>Thu, 19 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</guid>
				<description>Technical debt is the cost of future rework from prioritising speed over good design, and it is distinct from poor quality, which often causes bigger productivity losses. Long release cycles and mislabeling poor quality as technical debt can lead to unsustainable practices and higher costs. Development managers should set clear quality standards, encourage regular refactoring, and adopt continuous improvement to reduce technical debt, improve efficiency, and deliver better products.</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>Are We Still Pretending Coding Was the Bottleneck?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</link>
				<pubDate>Mon, 01 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</guid>
				<description>AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output.</description>
			</item>
			<item>
				<title>Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</link>
				<pubDate>Mon, 21 Jul 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</guid>
				<description>Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success.</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>Resilience is Part of the Product, Not an Afterthought</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/</link>
				<pubDate>Mon, 09 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/</guid>
				<description>Resilience must be designed into your product from the start, not added later or left to individual heroics. Building resilience means engineering for failure containment, rapid recovery, and continuous improvement, using tools like telemetry, feature flags, and safe deployment practices. Make resilience a core part of your development process and culture, treating it as a critical feature to avoid costly outages and business risks.</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>Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/</link>
				<pubDate>Sat, 30 Nov 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/</guid>
				<description>Prioritising quality from the start is essential to protect your brand and build customer trust, and this requires empowering engineering teams to take ownership, address technical debt openly, and integrate practices like continuous integration, user experience, and security early in development. Fostering a culture of transparency, collaboration, and continuous improvement leads to better products and stronger technical leadership. Invest in your teams’ skills and encourage shared responsibility for quality to drive lasting value for your customers and organisation.</description>
			</item>
			<item>
				<title>Stop Testing Quality In: How Shifting Left Builds Better Software, Faster</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</link>
				<pubDate>Mon, 18 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</guid>
				<description>Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases.</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>Do More Staging Environments Really Reduce Deployment Risk</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</link>
				<pubDate>Wed, 26 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</guid>
				<description>Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates.</description>
			</item>
			<item>
				<title>Every delay increases the risk of failure</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</link>
				<pubDate>Mon, 10 Feb 2025 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</guid>
				<description>Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release.</description>
			</item>
			<item>
				<title>Stop Promoting Branches</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/</link>
				<pubDate>Thu, 06 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/</guid>
				<description>Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster.</description>
			</item>
			<item>
				<title>The Power of Technical Excellence in Agile Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</link>
				<pubDate>Thu, 27 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</guid>
				<description>Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive.</description>
			</item>
			<item>
				<title>Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</link>
				<pubDate>Wed, 09 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</guid>
				<description>Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success.</description>
			</item>
			<item>
				<title>How to Build for Business Resilience and Continuity</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</link>
				<pubDate>Mon, 26 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</guid>
				<description>Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement.</description>
			</item>
			<item>
				<title>Fragile by Design: The Cost of Pretending to Be Resilient</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/</link>
				<pubDate>Mon, 12 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/</guid>
				<description>Most systems fail under real pressure because resilience is often treated as a checkbox or afterthought rather than a core product capability that is engineered, tested, and verified in real-world conditions. High-profile outages at Spain’s grid, Oracle, and Heathrow show that bad engineering, shallow product thinking, and leadership denial lead to systemic fragility. To avoid costly failures, development managers must make resilience a disciplined, ongoing practice by designing for failure, testing recovery regularly, and confronting weaknesses head-on.</description>
			</item>
			<item>
				<title>How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</link>
				<pubDate>Wed, 25 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</guid>
				<description>You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready.</description>
			</item>
			<item>
				<title>Scrum doesn’t stop you from optimising flow</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it.</description>
			</item>
			<item>
				<title>Technical debt isn’t just messy code</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</link>
				<pubDate>Thu, 13 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</guid>
				<description>Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines.</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>Without Delivery, There Is No Value</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/without-delivery-there-is-no-value/</link>
				<pubDate>Mon, 10 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/without-delivery-there-is-no-value/</guid>
				<description>Value in software is only realised when products are delivered to users, so frequent releases are essential to validate assumptions, gather feedback, and adapt quickly. Delaying delivery increases costs, risks, and missed opportunities, while research shows that teams releasing often are more successful and resilient. Development managers should prioritise short feedback loops and empower teams to release working software regularly to maximise value and minimise waste.</description>
			</item>
			<item>
				<title>Why Handoffs Are Killing Your Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</link>
				<pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</guid>
				<description>Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness.</description>
			</item>
			<item>
				<title>Detecting Agile BS: Lessons from the Department of Defense</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/</link>
				<pubDate>Fri, 02 Aug 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/</guid>
				<description>Adopting Agile development practices is not enough if the rest of your organization remains slow and bureaucratic; true agility requires continuous delivery, high product quality, and minimal manual or bureaucratic steps across the entire process. Use the Department of Defense&amp;rsquo;s six-question test to assess your real agility, and focus on automating testing, streamlining deployment, and building quality in from the start. Regularly review and improve your processes to eliminate bottlenecks and ensure your whole ecosystem supports rapid, reliable delivery.</description>
			</item>
			<item>
				<title>Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</link>
				<pubDate>Wed, 04 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</guid>
				<description>Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software.</description>
			</item>
			<item>
				<title>Mastering Sustainable Scaling: Overcoming Product Development Challenges with Naked Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</link>
				<pubDate>Fri, 28 Feb 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</guid>
				<description>Scaling product development is complex and requires more than just adding people; it demands clear priorities, strong leadership, and systems designed for growth. Naked Agility helps organisations address common scaling challenges like alignment, technical debt, and slow feedback by eliminating bottlenecks, using data-driven decisions, and tailoring strategies to each team&amp;rsquo;s needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth.</description>
			</item>
			<item>
				<title>Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/</link>
				<pubDate>Thu, 06 Feb 2025 10:20:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/</guid>
				<description>Azure DevOps transformed from two-year release cycles to 880,000 deployments per year by adopting continuous delivery, shortening feedback loops, and using real-time data to guide decisions. This shift enabled rapid response to customer needs and market changes, helping them stay ahead of competitors. Development managers should focus on frequent, small releases and data-driven improvements to maximise value and agility.</description>
			</item>
			<item>
				<title>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</link>
				<pubDate>Thu, 05 Sep 2024 11:14:48 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</guid>
				<description>Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</link>
				<pubDate>Mon, 03 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</guid>
				<description>Measuring individual cycle time in Kanban misleads teams by focusing on personal speed instead of system flow, which ignores real bottlenecks and encourages counterproductive behaviors. To improve delivery, track system-wide metrics like lead time, work in progress, process cycle efficiency, and blockers, then address constraints at the process level. Development managers should shift measurement and improvement efforts from individuals to the overall workflow to achieve better outcomes.</description>
			</item>
			<item>
				<title>Professional Scrum teams build software that works</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</guid>
				<description>Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization&amp;rsquo;s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training.</description>
			</item>
			<item>
				<title>Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</link>
				<pubDate>Wed, 11 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</guid>
				<description>Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn.</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>Embracing Change: How Architectural Adaptation Fuels Software Development Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embracing-change-how-architectural-adaptation-fuels-software-development-success/</link>
				<pubDate>Thu, 06 Feb 2025 17:06:47 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embracing-change-how-architectural-adaptation-fuels-software-development-success/</guid>
				<description>Adapting software architecture to meet changing demands is essential for long-term product success. Investing in teams, enabling incremental changes, and maintaining a long-term vision, like the Azure DevOps team’s four-year transformation, help reduce risk and support continuous improvement. Development managers should foster adaptability, prioritize architectural health, and clearly communicate long-term goals to ensure sustained progress.</description>
			</item>
			<item>
				<title>Navigating the Unpredictability of Software Development: Embrace Agile for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/</link>
				<pubDate>Mon, 02 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/</guid>
				<description>Software development is inherently unpredictable, often leading to missed deadlines and budget overruns, but this can be managed by focusing on strong technical leadership and engineering excellence. Relying on a single best practice is a mistake; instead, adopting Agile principles like iterative development, continuous delivery, feedback, and testing helps teams adapt and deliver value. Development managers should foster these capabilities to navigate complexity and drive better project outcomes.</description>
			</item>
			<item>
				<title>Can the Definition of Done change per Sprint?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</link>
				<pubDate>Mon, 14 Oct 2019 13:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</guid>
				<description>The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint.</description>
			</item>
			<item>
				<title>Empowering Development Teams: Cultivating an Agile Mindset for Lasting Quality</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-development-teams-cultivating-an-agile-mindset-for-lasting-quality/</link>
				<pubDate>Tue, 07 Apr 2020 20:33:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-development-teams-cultivating-an-agile-mindset-for-lasting-quality/</guid>
				<description>Development teams often struggle with agile adoption due to a lack of intrinsic motivation and engagement with quality and customer feedback. Leadership must create an environment that fosters autonomy, mastery, and purpose, while bridging the gap between technical skills and mindset through practices like retrospectives, code reviews, and continuous feedback. Focus on building a culture that values quality and empowerment to achieve lasting agile transformation.</description>
			</item>
			<item>
				<title>DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/</link>
				<pubDate>Mon, 02 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/</guid>
				<description>DevOps enables organisations to modernise legacy systems without starting from scratch by introducing automation, continuous integration and deployment, and observability, which make change safer and more routine. These practices reduce bottlenecks, lower the cost of change, and help teams deliver improvements continuously. Development managers should focus on identifying friction points and adopting DevOps practices to make ongoing system improvements achievable and sustainable.</description>
			</item>
			<item>
				<title>Rethinking Dev-Test-Staging-Production Pipelines for Safety</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</link>
				<pubDate>Fri, 21 Feb 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</guid>
				<description>Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency.</description>
			</item>
			<item>
				<title>Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</link>
				<pubDate>Wed, 22 Jan 2025 14:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</guid>
				<description>Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps: Avoiding Common Pitfalls for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/</link>
				<pubDate>Tue, 09 Apr 2024 08:00:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/</guid>
				<description>Many teams misuse Azure DevOps by creating flat work item hierarchies, using custom work item types that do not fit agile practices, neglecting traceability, and overcomplicating processes, which reduces the platform’s effectiveness. Sticking to intended structures and keeping processes simple helps teams stay agile and productive. Review your team’s use of Azure DevOps to ensure alignment with agile principles and avoid these common pitfalls.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</link>
				<pubDate>Sat, 15 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</guid>
				<description>Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals.</description>
			</item>
			<item>
				<title>Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</link>
				<pubDate>Mon, 25 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</guid>
				<description>Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible.</description>
			</item>
			<item>
				<title>Why Tracking Individual Cycle Time Distorts Team Behaviour</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</link>
				<pubDate>Wed, 12 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</guid>
				<description>Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead.</description>
			</item>
			<item>
				<title>The Scrum Master is accountable for Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>Where Agile Went Wrong: Understanding the Competence Crisis</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/</link>
				<pubDate>Mon, 14 Oct 2024 07:00:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/</guid>
				<description>Agile has struggled because its founders assumed widespread competence and commitment to continuous learning, but most organizations lack enough skilled practitioners, especially in key roles like Scrum Master. This competence gap is worsened by low hiring standards and overreliance on basic certifications, leading to ineffective teams and missed opportunities for improvement. Development managers should prioritize hiring and promoting individuals with proven learning habits, deep contextual understanding, and advanced expertise to build high-performing Agile teams.</description>
			</item>
			<item>
				<title>Empowering Teams for Success: The Key to Thriving Product Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/</link>
				<pubDate>Tue, 07 May 2024 11:02:49 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/</guid>
				<description>Successful product development depends on empowered, engaged, and happy teams who understand the value of their work and are trusted to make decisions. Key drivers include fostering collaboration, providing continuous feedback, investing in skills development, and enabling direct customer engagement. Development managers should focus on creating an environment where team members feel valued and supported, as this leads to higher quality products and greater innovation.</description>
			</item>
			<item>
				<title>Toyota &#34;andon&#34; cord lets any worker stop production to fix defects</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</link>
				<pubDate>Mon, 12 May 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</guid>
				<description>Giving teams tools like Scrum events or defect reporting only works if you also create a culture where people feel safe to speak up and address problems. Without psychological safety and genuine empowerment, process changes alone will not lead to real improvement. Development managers should focus on building trust and openness so teams feel comfortable raising issues.</description>
			</item>
			<item>
				<title>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>Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-legacy-systems-how-to-embrace-automation-and-drive-innovation/</link>
				<pubDate>Mon, 28 Apr 2025 06:00:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-legacy-systems-how-to-embrace-automation-and-drive-innovation/</guid>
				<description>Legacy systems can and should be automated, with the main barrier being mindset rather than technology. By encouraging a culture that questions old processes and starting with small, incremental automation efforts, teams can reduce bottlenecks and unlock significant efficiency gains. Development managers should identify manual pain points and begin automating them to drive innovation and continuous improvement.</description>
			</item>
			<item>
				<title>Executives want predictability</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/</link>
				<pubDate>Mon, 31 Mar 2025 15:30:08 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/</guid>
				<description>If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating &amp;ldquo;Done&amp;rdquo; as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments.</description>
			</item>
			<item>
				<title>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</link>
				<pubDate>Wed, 16 Oct 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</guid>
				<description>There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Estimating Better in an Overloaded System Is a Poor Man’s Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</link>
				<pubDate>Mon, 08 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</guid>
				<description>Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning.</description>
			</item>
			<item>
				<title>Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/</link>
				<pubDate>Fri, 27 Jun 2025 06:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/</guid>
				<description>Focusing on real agility and DevOps means building adaptable teams and resilient systems, not just adopting the latest tools or trends. Key outcomes include smoother delivery, better feedback, and teams that can handle change without disruption. Prioritise embedding adaptability into your culture and processes so your teams can lead rather than react to change.</description>
			</item>
			<item>
				<title>Technical Debt Management for Long-Term Quality</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</link>
				<pubDate>Thu, 21 Nov 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</guid>
				<description>Technical debt results from choosing quick fixes over long-term solutions and can be both intentional and unintentional, eventually limiting your team&amp;rsquo;s ability to deliver value. The Azure DevOps team dramatically increased their feature delivery by prioritizing and paying down technical debt, showing that addressing it leads to faster delivery and higher product quality. Development managers should actively identify and pay back technical debt to maximize long-term productivity and value.</description>
			</item>
			<item>
				<title>Bridging the Gap: Understanding the True Meaning of &#34;Done&#34; in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/</link>
				<pubDate>Thu, 07 Dec 2023 11:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/</guid>
				<description>Many Agile teams misunderstand what &amp;ldquo;done&amp;rdquo; really means, leading to gaps in quality and unmet expectations. Clearly defining &amp;ldquo;done&amp;rdquo; with input from both leadership and the team ensures consistent quality, reduces rework, and builds trust with stakeholders. Development managers should regularly review and refine their team&amp;rsquo;s definition of done to align with evolving business needs and maintain high standards.</description>
			</item>
			<item>
				<title>Embrace Simplicity: How to Transform Complexity into Continuous Delivery Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/</link>
				<pubDate>Thu, 27 Feb 2025 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/</guid>
				<description>Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success.</description>
			</item>
			<item>
				<title>Navigating the Legacy System Dilemma: Balancing Stability and Innovation for Modernisation Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-dilemma-balancing-stability-and-innovation-for-modernisation-success/</link>
				<pubDate>Mon, 14 Apr 2025 06:00:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-dilemma-balancing-stability-and-innovation-for-modernisation-success/</guid>
				<description>Balancing stability and innovation in legacy systems is challenging, as rapid changes can cause technical debt and confusion, while inaction leads to stagnation. Gradual, collaborative modernisation focused on engineering best practices allows for progress without disrupting what works. Consider incremental improvements to maintain resilience and competitiveness while modernising.</description>
			</item>
			<item>
				<title>The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</link>
				<pubDate>Mon, 21 Oct 2024 05:32:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</guid>
				<description>Scrum Masters need deep knowledge of both agile practices and the technical work of their teams to drive real improvement in product delivery. Without this competence, teams stagnate and fail to deliver business value, while skilled Scrum Masters elevate team capabilities and outcomes. Development managers should ensure their Scrum Masters have practical expertise, not just facilitation skills, to maximize team impact.</description>
			</item>
			<item>
				<title>Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</link>
				<pubDate>Mon, 08 Jan 2024 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</guid>
				<description>Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting.</description>
			</item>
			<item>
				<title>Unlocking Rapid Delivery: Overcoming Common DevOps Challenges for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</link>
				<pubDate>Fri, 21 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</guid>
				<description>Many teams struggle to deliver products quickly due to slow feedback loops, limited automation, and resistance to change. Key improvements include automating processes, engaging compliance teams early to challenge assumptions, and fostering a culture open to experimentation. Development managers should review their delivery pipelines for bottlenecks and actively involve stakeholders to enable faster, more agile releases.</description>
			</item>
			<item>
				<title>Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/</link>
				<pubDate>Wed, 13 May 2020 05:03:57 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/</guid>
				<description>Story points often create confusion and unpredictability, so focusing on throughput and cycle time gives teams clearer insights and better delivery. Slightly larger teams with diverse roles can handle complex work and maintain quality more effectively. Embracing emergent architecture helps teams stay flexible and competitive, so consider shifting your metrics and team structures to support adaptability and faster value delivery.</description>
			</item>
			<item>
				<title>Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</link>
				<pubDate>Wed, 23 Apr 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</guid>
				<description>When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement.</description>
			</item>
			<item>
				<title>Rethinking Continuous Delivery: Why Best Practices Don&#39;t Exist in Complex Environments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don&#39;t-exist-in-complex-environments/</link>
				<pubDate>Thu, 23 Jan 2025 06:30:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don&#39;t-exist-in-complex-environments/</guid>
				<description>There are no universal best practices for continuous delivery in complex environments; instead, teams should adopt flexible, situation-specific approaches. Key strategies include audience-based delivery for rapid feedback, testing in production to validate real-world performance, and a commitment to quickly finding and fixing issues. Development managers should focus on continuous improvement and adaptability rather than rigid processes.</description>
			</item>
			<item>
				<title>Deciphering the Enigma of Story Points Across Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</link>
				<pubDate>Thu, 21 Sep 2023 08:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</guid>
				<description>Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes.</description>
			</item>
			<item>
				<title>If every release feels high-risk, you lack a true Definition of Done</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</link>
				<pubDate>Sat, 05 Apr 2025 15:30:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</guid>
				<description>If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team&amp;rsquo;s process to make releases predictable and low-stress.</description>
			</item>
			<item>
				<title>Special Sprints: Agile Banditry or Risk Management?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</link>
				<pubDate>Thu, 04 Jan 2024 11:09:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</guid>
				<description>Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk.</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>Hiring an Agile Coach: What to Look For in Both Technical and Leadership Engagement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-to-look-for-in-both-technical-and-leadership-engagement/</link>
				<pubDate>Tue, 21 Nov 2023 11:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-to-look-for-in-both-technical-and-leadership-engagement/</guid>
				<description>When hiring an Agile coach, prioritize candidates who can engage deeply with both technical teams and leadership, as this is key to a successful Agile transformation. Look for strong technical understanding relevant to your industry, business acumen to connect Agile practices to strategic goals, and excellent communication skills to influence at all levels. Choose a coach who fits your culture and can bridge gaps across the organization to drive real business outcomes.</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>Engineering Culture That Thrives: How to Build Teams Ready for Change, Not Just the Next Fire Drill</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/engineering-culture-that-thrives-how-to-build-teams-ready-for-change-not-just-the-next-fire-drill/</link>
				<pubDate>Fri, 20 Jun 2025 06:00:51 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/engineering-culture-that-thrives-how-to-build-teams-ready-for-change-not-just-the-next-fire-drill/</guid>
				<description>Engineering teams need a culture that embraces and adapts to change, not just one that reacts to emergencies or chases trends. The most effective teams learn quickly, reflect on their practices, and align with business goals, making continuous improvement and evidence-based decisions part of their routine. Development managers should focus on building a learning culture that expects and measures adaptation, ensuring teams remain resilient and relevant as technology evolves.</description>
			</item>
			<item>
				<title>Cloud Migration Without the Mayhem: How to Move Legacy Systems Safely and Set Your Teams Up for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/</link>
				<pubDate>Mon, 05 May 2025 06:00:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/</guid>
				<description>Cloud migration works best when approached gradually, using a hybrid model to reduce risk and avoid simply moving existing problems to the cloud. Success depends on understanding both your technology and how your teams work, aligning people and processes, and focusing on long-term maintainability. Treat migration as an ongoing journey, not a rushed project, and invest in shared understanding and continuous improvement to ensure a smooth transition.</description>
			</item>
			<item>
				<title>There a common belief that rollback is the ultimate safety net</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/</link>
				<pubDate>Thu, 13 Feb 2025 15:53:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/</guid>
				<description>Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes.</description>
			</item>
			<item>
				<title>The Importance of Visualizing Your Work in a Kanban Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</link>
				<pubDate>Thu, 07 Mar 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</guid>
				<description>Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process.</description>
			</item>
			<item>
				<title>Maximising ROI in Software Development: Unlocking Value Through Quality and Expertise</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/maximising-roi-in-software-development-unlocking-value-through-quality-and-expertise/</link>
				<pubDate>Fri, 13 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/maximising-roi-in-software-development-unlocking-value-through-quality-and-expertise/</guid>
				<description>Maximising ROI in software development requires treating code as a valuable asset, investing in quality, and ensuring regular reviews to maintain standards. Bridging the gap between business and technical expertise is essential, so equip your leadership with the right knowledge and consider external coaching if needed. Prioritise quality, technical skill, and hypothesis-driven practices to ensure your teams deliver the most value for your investment.</description>
			</item>
			<item>
				<title>Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/</link>
				<pubDate>Tue, 03 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/</guid>
				<description>To build a high-performing software delivery team, focus on developing both technical and business competence across all members, encouraging everyone to think like product developers rather than just coders. Embrace Agile, DevOps, Lean, and Scrum philosophies, adapt practices as needed, and ensure due diligence before making structural changes. Prioritise collaboration, open communication, and continuous improvement to maximise value delivery and drive business success.</description>
			</item>
			<item>
				<title>Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</link>
				<pubDate>Thu, 04 Jan 2024 12:14:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</guid>
				<description>Relying on special Sprints like Sprint Zero or bug fix Sprints undermines true Agile practices by encouraging risky behavior, diluting focus, and creating a false sense of security. Teams should instead prioritize delivering a usable product at the end of every Sprint, foster accountability, and integrate quality assurance into regular work. Development managers should avoid safety nets and focus on continuous improvement and value delivery each Sprint.</description>
			</item>
			<item>
				<title>Why do you trust Joanna to deliver Scrum.Org classes for NKD Agility?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-joanna-to-deliver-scrum-org-classes-for-nkd-agility/</link>
				<pubDate>Tue, 22 Aug 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-joanna-to-deliver-scrum-org-classes-for-nkd-agility/</guid>
				<description>Joanna delivers Scrum.Org classes that combine deep technical expertise with clear, practical Agile training, making complex concepts easy to understand and apply. Her sessions focus on real-world problem-solving, continuous improvement, and effective leadership, helping teams and individuals level up their Agile skills. Development managers should consider her training to boost team performance and confidently navigate Agile transformation.</description>
			</item>
			<item>
				<title>The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 16:30:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</guid>
				<description>Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings.</description>
			</item>
			<item>
				<title>Transforming Technical Debt: Unlocking Innovation and Value Through Quality Product Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/</link>
				<pubDate>Thu, 21 Nov 2024 17:01:52 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/</guid>
				<description>Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to persist leads to higher maintenance costs, slower delivery, and lower team morale, while prioritising high-quality product delivery enables greater agility, consistent value, and innovation. Development managers should regularly assess and address technical debt, foster a culture of quality, and communicate its impact to stakeholders to unlock their teams’ full potential.</description>
			</item>
			<item>
				<title>The Power of Kaizen: Continuous Improvement in Scrum and Beyond</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</link>
				<pubDate>Sun, 25 Aug 2024 22:00:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</guid>
				<description>Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum.</description>
			</item>
			<item>
				<title>Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/</link>
				<pubDate>Thu, 15 Aug 2024 07:04:39 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/</guid>
				<description>Using clear metrics and visual tools helps teams identify improvement areas, increase transparency, and make better decisions. Regularly reviewing processes, experimenting with small changes, and focusing on relevant, actionable data are key to ongoing improvement. Development managers should ensure their teams use these practices to drive meaningful and continuous workflow enhancements.</description>
			</item>
			<item>
				<title>Breaking the Silence: How to Combat the Hidden Dangers in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-the-hidden-dangers-in-agile-teams/</link>
				<pubDate>Fri, 10 Nov 2023 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-the-hidden-dangers-in-agile-teams/</guid>
				<description>Silence in Agile teams can lead to poor communication, lack of accountability, and misleading commitments, which undermine value delivery, erode trust, and stall growth. Managers should actively foster open communication, model vulnerability, and set clear expectations to prevent these issues. Prioritising honest dialogue and celebrating those who speak up will help teams deliver better results and maintain a healthy, agile culture.</description>
			</item>
			<item>
				<title>How important is DevOps in continuous delivery of value to customers?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</link>
				<pubDate>Mon, 20 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</guid>
				<description>DevOps is essential for delivering value to customers because it enables teams to quickly and effectively turn ideas into working software, closely aligning with agile principles. Both DevOps and agile focus on rapid feedback, continuous improvement, and adapting to customer needs, making them deeply interconnected. Development managers should ensure their teams integrate DevOps practices to accelerate delivery, validate value, and reduce risk.</description>
			</item>
			<item>
				<title>Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</link>
				<pubDate>Fri, 17 Apr 2020 18:57:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</guid>
				<description>To succeed with Agile transformation, focus on empowering teams through servant leadership, prioritising valuable product outcomes over feature lists, and fostering continuous improvement to manage technical debt. Enable product owners to drive value, build cross-functional teams, and measure results by customer impact rather than activity. Start with small changes to build momentum and consider expert support if needed.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</link>
				<pubDate>Mon, 16 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</guid>
				<description>DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues.</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>Getting started with Kanban</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/getting-started-with-kanban/</link>
				<pubDate>Wed, 14 Feb 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/getting-started-with-kanban/</guid>
				<description>Kanban helps teams improve workflow and productivity by visualizing work, setting clear processes, and using metrics like cycle time and throughput to drive continuous improvement. Start with a small, willing team, define and visualize your workflow, and use data to identify and address bottlenecks. Begin with a pilot, focus on collaboration and regular feedback, and use metrics to build credibility and guide ongoing enhancements.</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>Unlocking the True Potential of Scrum: Why Professionalism Matters in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</link>
				<pubDate>Thu, 20 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</guid>
				<description>Many software teams fall short of Scrum’s true potential because organizations prioritize speed over professionalism, leading to shortcuts and unprofessional practices. Achieving real value with Scrum requires a commitment to transparency, production-ready increments each iteration, and honest assessment of current capabilities, often revealing significant gaps. Development managers should focus on fostering a professional work ethic and closing these gaps to unlock Scrum’s full benefits.</description>
			</item>
			<item>
				<title>Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm</title>
				<link>https://engineering-leadership.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>Hiring an Agile Coach: What You Need to Know</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-you-need-to-know/</link>
				<pubDate>Wed, 22 Nov 2023 11:00:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-you-need-to-know/</guid>
				<description>When hiring an Agile coach, look for someone who can teach, mentor, and inspire your teams, not just coach them. The right coach will help teams deeply understand Agile practices, foster growth and accountability, and motivate continuous improvement, leading to better alignment, autonomy, and engagement. Prioritize candidates with hands-on experience, strong communication skills, and a good cultural fit to maximize the impact on your organization.</description>
			</item>
			<item>
				<title>Beware the Fake Agilists: How to Protect Your Team from the Agile Apocalypse</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/beware-the-fake-agilists-how-to-protect-your-team-from-the-agile-apocalypse/</link>
				<pubDate>Tue, 07 Nov 2023 07:36:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/beware-the-fake-agilists-how-to-protect-your-team-from-the-agile-apocalypse/</guid>
				<description>Relying on leaders with only Agile certifications but no real software development experience can harm team trust, stifle growth, and lead to ineffective processes. To protect your teams, prioritize practical experience over credentials, encourage ongoing learning, and focus on delivering value rather than just following procedures. Ensure Agile leadership is grounded in genuine expertise to maintain team effectiveness and resilience.</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>Empowering Agile Teams: The Transformative Power of Teaching the &#34;Why&#34;</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</guid>
				<description>Helping teams understand the reasons behind Agile practices is key to real engagement and lasting change. When team members grasp the value and purpose of what they do, they collaborate better, adapt more easily, and drive continuous improvement. Development managers should focus on explaining the &amp;ldquo;why&amp;rdquo; behind processes to empower teams and boost performance.</description>
			</item>
			<item>
				<title>Deploying Windows OS Directly to Production: Then vs Now</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</link>
				<pubDate>Sat, 22 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</guid>
				<description>Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness.</description>
			</item>
			<item>
				<title>Story Points: A Ghost of Agile Past</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</link>
				<pubDate>Fri, 29 Dec 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</guid>
				<description>Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance.</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>Frequent releases are not just a technical strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</link>
				<pubDate>Fri, 07 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</guid>
				<description>Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback.</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>Are there any Scrum courses that teach you how to scale Scrum?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/are-there-any-scrum-courses-that-teach-you-how-to-scale-scrum/</link>
				<pubDate>Wed, 18 Oct 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/are-there-any-scrum-courses-that-teach-you-how-to-scale-scrum/</guid>
				<description>There is no single course that teaches you exactly how to scale Scrum, but courses like Scaled Professional Scrum from Scrum.org provide tools and techniques to help you build a scaling framework tailored to your organization. Key to success are starting small, focusing on dependency management and alignment, and iterating based on feedback. Development managers should invest in team education, select relevant practices, and foster a culture of collaboration and continuous improvement to scale Scrum effectively.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</link>
				<pubDate>Mon, 22 May 2023 14:00:41 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</guid>
				<description>A Scrum Master is essential for team effectiveness because they guide teams by understanding business needs, technical practices like DevOps, and organisational change. Without this role, teams often struggle to deliver value quickly and improve continuously. Development managers should ensure their teams have access to a skilled Scrum Master or equivalent expertise to maximize productivity and quality.</description>
			</item>
			<item>
				<title>Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</link>
				<pubDate>Thu, 04 Jun 2020 05:33:42 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</guid>
				<description>Focus on team productivity rather than just feature count, and ensure everyone understands the difference between Definition of Done, which sets quality standards, and acceptance criteria, which specify requirements for each item. Use backlog refinement to address unknowns instead of relying on spikes, and plan sprint capacity to accommodate some ad hoc work while maintaining transparency and continuous improvement. Review your team’s approach to these areas to improve delivery and reduce disruptions.</description>
			</item>
			<item>
				<title>Too many teams overcomplicate their branching strategies</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</link>
				<pubDate>Thu, 06 Feb 2025 09:38:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</guid>
				<description>Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability.</description>
			</item>
			<item>
				<title>The Common Challenges of Adopting DevOps Practices</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</link>
				<pubDate>Tue, 20 Aug 2024 08:04:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</guid>
				<description>Adopting DevOps brings challenges like managing new types of risk and avoiding setbacks, especially as teams shift from long, structured cycles to rapid, continuous delivery. Success depends on quickly closing feedback loops, acting on real-world data from production, and adapting processes to maintain quality and flexibility. Development managers should focus on integrating feedback into daily workflows and using modern tools to manage risk without slowing down delivery.</description>
			</item>
			<item>
				<title>Unlocking Continuous Improvement: How Metrics and Visualisation Drive Workflow Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/</link>
				<pubDate>Mon, 19 Aug 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/</guid>
				<description>Continuous improvement relies on using the right metrics and clear visual tools to identify patterns, increase transparency, and drive meaningful workflow changes. Teams should focus on measuring what truly matters and ensure their visualisations support understanding and collaboration. Regularly reviewing and adjusting processes based on these insights is essential for ongoing success.</description>
			</item>
			<item>
				<title>Is Your Project Ecosystem Truly Agile?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</link>
				<pubDate>Wed, 31 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</guid>
				<description>Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile.</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>Building the wrong thing is worse than fixing a bug</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</link>
				<pubDate>Mon, 14 Apr 2025 15:30:31 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</guid>
				<description>Most features built by software teams do not deliver value, with 65 percent considered waste. Shortening feedback loops through frequent reviews and real user input helps teams focus on what matters and avoid building the wrong things. Act now to get faster, actionable feedback and prevent wasted time and resources.</description>
			</item>
			<item>
				<title>Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</link>
				<pubDate>Tue, 14 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</guid>
				<description>Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement.</description>
			</item>
			<item>
				<title>Unlocking Code Quality: The Transformative Power of Frequent Deployments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</link>
				<pubDate>Mon, 13 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</guid>
				<description>Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance.</description>
			</item>
			<item>
				<title>Rethinking Sprint Planning: Why Burndown Charts Are Agile Banditry and What to Do Instead</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/</link>
				<pubDate>Tue, 09 Jan 2024 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, which is ineffective given the high uncertainty and frequent changes in software development. Instead, start each Sprint with only enough planning to begin work, then reassess and adjust daily to stay flexible and focused on delivering value. Shift your team’s approach to minimal, just-in-time planning to reduce overhead and respond better to change.</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>If software is not delivered, it is not valuable</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</link>
				<pubDate>Sat, 01 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</guid>
				<description>Undelivered software provides no value, and long development cycles increase risk, cost, and missed opportunities. Research shows that teams releasing software frequently are more successful and efficient. To maximize value and learning, prioritize frequent delivery to users.</description>
			</item>
			<item>
				<title>A two-day Scrum Master certification doesn’t make you a Scrum Master</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</link>
				<pubDate>Thu, 27 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</guid>
				<description>A two-day Scrum Master certification alone is not enough to prepare someone for the real challenges of leading Scrum Teams and delivering value. Effective Scrum Masters have hands-on experience, understand code quality and DevOps, and have navigated real-world obstacles. Companies should prioritize hiring or developing Scrum Masters with proven experience rather than relying solely on certifications.</description>
			</item>
			<item>
				<title>Transforming Waste into Value: How to Boost ROI with Agile Metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</link>
				<pubDate>Tue, 17 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</guid>
				<description>Most organisations lose significant value due to waste and lack of focus on engineering excellence, with metrics showing that only a small fraction of development investment results in features customers actually use. Key insights include low innovation rates, poor feature usage, and lagging version adoption, all of which drastically reduce ROI. Development managers should measure and act on innovation and usage metrics, close feedback loops, and focus on delivering value rather than just reducing costs.</description>
			</item>
			<item>
				<title>Mastering Scrum: Essential Insights for New Teams from a Scrum Master&#39;s Journey</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</link>
				<pubDate>Tue, 28 Nov 2023 11:00:49 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</guid>
				<description>New Scrum teams succeed when they deeply understand Scrum principles, empiricism, and core values, which the Scrum Master should actively teach and reinforce. Practical workshops, real-world examples, and a focus on continuous learning help teams build trust, adapt to change, and improve over time. Development managers should ensure their teams have ongoing support and a safe environment to foster growth and agility.</description>
			</item>
			<item>
				<title>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>Staging Environments Do Not Prevent Production Failures</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</link>
				<pubDate>Fri, 28 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</guid>
				<description>Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems.</description>
			</item>
			<item>
				<title>Every unreleased feature is a cost</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</link>
				<pubDate>Wed, 05 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</guid>
				<description>Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team&amp;rsquo;s efforts translate into actual value.</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>Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</link>
				<pubDate>Wed, 20 Nov 2024 08:02:36 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</guid>
				<description>A team increased their annual feature delivery from 25 to 150 by breaking down work into smaller experiments, enabling faster feedback, reduced risk, and continuous learning without increasing headcount. This approach allowed them to quickly identify and focus on features that mattered most to customers, leading to better products. Development managers should consider adopting small, frequent experiments to drive both speed and quality in feature delivery.</description>
			</item>
			<item>
				<title>Navigating the Agile Apocalypse: How to Combat Judgment and Foster Team Growth</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-agile-apocalypse-how-to-combat-judgment-and-foster-team-growth/</link>
				<pubDate>Wed, 01 Nov 2023 11:30:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-agile-apocalypse-how-to-combat-judgment-and-foster-team-growth/</guid>
				<description>Judging teams by metrics like velocity, bug counts, or code volume can create fear and stifle growth, undermining Agile principles. Instead, focus on goals that reflect real progress, encourage open discussion about challenges, and regularly review metrics to ensure they support a healthy team environment. Review your current metrics and team culture to ensure they foster collaboration and innovation rather than fear or competition.</description>
			</item>
			<item>
				<title>Biggest contribution from a Product Owner that you know of</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/biggest-contribution-from-a-product-owner-that-you-know-of/</link>
				<pubDate>Tue, 13 Jun 2023 11:32:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/biggest-contribution-from-a-product-owner-that-you-know-of/</guid>
				<description>Brian Harry and Aaron Bjork at Microsoft transformed product development by shifting from slow, two-year release cycles to rapid, three-week feedback loops, driving a major cultural and process shift toward Agile across the organization. Their leadership and collaboration, supported by executive buy-in, embedded sustainable Agile practices and set a new industry standard for balancing scale with agility. Development managers should recognize the impact that visionary Product Owners can have in driving both process and cultural change, and prioritize empowering such leaders within their teams.</description>
			</item>
			<item>
				<title>Big Scrum: Are you doing mechanical Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</link>
				<pubDate>Wed, 24 Jun 2015 13:43:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</guid>
				<description>Many organizations adopt Scrum hoping for rapid productivity gains but are disappointed when they only follow the motions without embracing its core values and technical excellence. True effectiveness and faster delivery come from practicing Professional Scrum, which means living the principles and focusing on quality, not just the framework. Development managers should ensure their teams go beyond mechanical Scrum and invest in building a professional culture to achieve real results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</link>
				<pubDate>Fri, 25 Oct 2024 07:02:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</guid>
				<description>Many Scrum Masters misunderstand their true responsibilities, focusing on tools and rituals instead of the core principles and accountabilities defined by Scrum. Effective Scrum Masters balance support for the team, Product Owner, and organisation, acting as coaches and mentors rather than process enforcers. Development managers should ensure Scrum Masters are competent in Scrum’s philosophies and adapt practices to fit their context, not just follow common routines.</description>
			</item>
			<item>
				<title>Empowering Teams to Tailor Their Processes: A Path to True Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/</link>
				<pubDate>Fri, 26 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/</guid>
				<description>Empowering teams to adapt their processes to their specific needs leads to greater value, less waste, and more innovation, while rigid, one-size-fits-all processes can cause delays, unnecessary costs, and frustration. Development managers should assess whether their teams have the freedom to experiment, minimize bureaucracy, and focus on delivering customer value rather than just following procedures. To achieve true agility, encourage teams to tailor their ways of working and continuously improve based on what they learn.</description>
			</item>
			<item>
				<title>Empowering Your Team: Why Quick Fixes in Agile and DevOps Are a Myth</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-your-team-why-quick-fixes-in-agile-and-devops-are-a-myth/</link>
				<pubDate>Thu, 09 May 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-your-team-why-quick-fixes-in-agile-and-devops-are-a-myth/</guid>
				<description>There are no quick fixes for Agile or DevOps transformation; relying on external parties or contractors to deliver ready-made solutions does not build lasting capability. Sustainable change comes from empowering your own team through learning, collaboration, and continuous improvement, with consultants serving as guides rather than doers. Invest in developing your people and culture to achieve real, long-term agility.</description>
			</item>
			<item>
				<title>You can&#39;t stop the signal! But you can ignore it!</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</link>
				<pubDate>Wed, 17 Apr 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</guid>
				<description>Agile and Scrum frameworks highlight problems in team processes, but many organizations ignore these signals due to cultural barriers like fear of repercussions and resistance to change. Simply adopting these frameworks is not enough; their effectiveness depends on a culture that encourages transparency, feedback, and continuous improvement. Development managers should focus on building an environment where raising and addressing issues is supported and valued to fully realize the benefits of Agile and Scrum.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 3</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-3/</link>
				<pubDate>Wed, 25 Oct 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-3/</guid>
				<description>Scrum does not inherently lead to micromanagement; this misconception arises when organizations misapply Scrum by imposing top-down control instead of empowering teams. True Scrum gives developers autonomy over their work, encourages open collaboration, and relies on trust and technical expertise. Development managers should focus on enabling team decision-making and fostering a culture of trust to realize the full benefits of Agile.</description>
			</item>
			<item>
				<title>Can you align DevOps and Software Engineering Teams Through Scrum?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/can-you-align-devops-and-software-engineering-teams-through-scrum/</link>
				<pubDate>Fri, 16 Jun 2023 14:30:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/can-you-align-devops-and-software-engineering-teams-through-scrum/</guid>
				<description>Scrum can effectively align DevOps and software engineering teams by promoting transparency, regular delivery of usable products, and continuous feedback. Achieving this alignment requires discipline and integrating DevOps practices into Scrum workflows. Development managers should focus on embedding these practices to drive better collaboration and higher-quality outcomes.</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>Embracing Process Improvement: How Understanding Scrum Transformed a Developer&#39;s Mindset</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</link>
				<pubDate>Thu, 27 Jul 2017 19:14:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</guid>
				<description>Understanding and embracing Scrum processes can transform developer mindsets, leading to better collaboration, higher quality product delivery, and more empowered teams. Taking time to learn and refine processes is essential for sustainable success, not just individual productivity. Development managers should encourage their teams to invest in process improvement to drive long-term value and team growth.</description>
			</item>
			<item>
				<title>Modernising Legacy Systems: A Practical, Low-Risk Strategy for Real Business Transformation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-a-practical-low-risk-strategy-for-real-business-transformation/</link>
				<pubDate>Mon, 09 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-a-practical-low-risk-strategy-for-real-business-transformation/</guid>
				<description>Modernising legacy systems should be a strategic, low-risk process focused on understanding both technical and workflow bottlenecks, not a risky full replacement. Incremental changes, targeted automation, and addressing process issues often deliver the best results while minimising disruption. Development managers should map how work flows through their systems, prioritise fixes that offer the most value, and shift from reactive firefighting to proactive improvement.</description>
			</item>
			<item>
				<title>Navigating the Legacy System Labyrinth: Strategies for Modernisation Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-labyrinth-strategies-for-modernisation-success/</link>
				<pubDate>Mon, 07 Apr 2025 06:00:36 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-labyrinth-strategies-for-modernisation-success/</guid>
				<description>Modernising legacy systems is complex because they are deeply tied to business processes, compliance, and fragile integrations, making change risky and disruptive. Security vulnerabilities and lack of scalability add to the challenge, so a clear strategy focused on incremental improvements and strategic replacements is essential. Development managers should assess their systems holistically and pursue manageable, stepwise changes to enable long-term organisational success.</description>
			</item>
			<item>
				<title>Agile Is Not Easier Than Traditional Methods: Common Misconceptions</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/</link>
				<pubDate>Sat, 08 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/</guid>
				<description>Agile is often harder than traditional methods because it requires frequent delivery, decision-making with limited information, and handling uncertainty. Success depends on disciplined teams, strong collaboration, and a focus on delivering value, not just following a framework. Development managers should assess whether their teams are truly embracing Agile principles or simply following routines.</description>
			</item>
			<item>
				<title>Transforming Agile: How to Shift from Blame to Systemic Solutions for Better Team Dynamics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-agile-how-to-shift-from-blame-to-systemic-solutions-for-better-team-dynamics/</link>
				<pubDate>Fri, 29 Sep 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-agile-how-to-shift-from-blame-to-systemic-solutions-for-better-team-dynamics/</guid>
				<description>Problems in agile teams are usually caused by flawed measurement systems and processes, not individual intent. Metrics drive behavior, so focusing on changing how people are evaluated and incentivized is more effective than trying to change culture directly. Review your team’s metrics and processes to remove barriers and foster adaptability, which will lead to better collaboration and innovation.</description>
			</item>
			<item>
				<title>Live Site Culture &amp; Site Reliability Engineering</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</link>
				<pubDate>Wed, 17 Jun 2020 13:23:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</guid>
				<description>To stay competitive in a fast-changing market, teams must adopt DevOps and continuous delivery, shifting from infrequent releases to deploying updates daily. This requires faster feedback, shared responsibility for quality and operations, and new ways of working, as shown by Microsoft&amp;rsquo;s Azure DevOps team. Development managers should consider evolving their team structures and practices to support rapid, customer-focused delivery.</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>Empowering Teams to Maximize Value and Return on Investment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</link>
				<pubDate>Wed, 24 Jul 2024 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</guid>
				<description>Empowering teams to adapt their own processes is essential for maximizing value and return on investment in Agile environments. Teams that have autonomy, leadership support, and a culture of continuous improvement consistently outperform those forced to follow rigid, standardized processes. Development managers should trust teams to tailor their workflows, provide the necessary tools and support, and focus on outcomes rather than strict process adherence.</description>
			</item>
			<item>
				<title>How effectively does an APS prepare a team to do a solid, professional Scrum?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</link>
				<pubDate>Sat, 12 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</guid>
				<description>The Applied Professional Scrum (APS) course helps teams focus on delivering a working product every iteration and sheds unhelpful habits that slow progress. Through practical exercises like the &amp;ldquo;Barnacle Exercise,&amp;rdquo; teams identify and remove outdated practices, leading to more effective Scrum adoption. Development managers should consider APS to build teams that consistently deliver value and embody true Scrum principles.</description>
			</item>
			<item>
				<title>All technical debt is a risk to the product and to your business</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/</link>
				<pubDate>Mon, 25 Jan 2021 14:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/</guid>
				<description>Technical debt is a significant risk to your product and business, as it undermines quality, slows delivery, and can accumulate unnoticed until it becomes a major problem. The Microsoft Team Foundation Server example shows that ignoring technical debt leads to reduced productivity and competitiveness, while addressing it through transparency and shorter feedback cycles enables faster, higher-quality delivery. Development managers should prioritize eliminating technical debt and fostering a culture of quality to protect business value and avoid long-term risks.</description>
			</item>
			<item>
				<title>The Missing Lever in Agile Transformations</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/</link>
				<pubDate>Mon, 02 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/</guid>
				<description>Agile transformations often fail because they focus on following ceremonies instead of building real agency in people and systems. True agility comes from empowering individuals and teams to make decisions and adapt, supported by evidence-based management to measure outcomes and guide change. To succeed, shift your transformation efforts from compliance to fostering agency and use data to drive continuous improvement.</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>Fear is the real enemy of agility</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/</link>
				<pubDate>Wed, 07 May 2025 15:30:42 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/</guid>
				<description>Fear blocks true agility and leads to stagnation, regardless of how many Agile practices you follow. The main job of leaders is to remove fear so teams can learn, adapt, and deliver value. Focus on creating an environment where people feel safe to speak up and take risks.</description>
			</item>
			<item>
				<title>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>Overcoming the Plague of Rigidity: Embracing True Agility in Your Team</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/</link>
				<pubDate>Wed, 08 Nov 2023 11:00:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/</guid>
				<description>Rigidly sticking to tools and processes can cause teams to stagnate, resist change, and miss out on innovation. True agility comes from regularly reassessing practices, encouraging experimentation, and focusing on outcomes rather than methods. Development managers should foster a culture of continuous improvement and adaptability to keep their teams responsive and effective.</description>
			</item>
			<item>
				<title>What are the top 3 things a Scrum Master needs to bear in mind when adopting the coaching stance?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-are-the-top-3-things-a-scrum-master-needs-to-bear-in-mind-when-adopting-the-coaching-stance/</link>
				<pubDate>Mon, 18 Sep 2023 07:00:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-are-the-top-3-things-a-scrum-master-needs-to-bear-in-mind-when-adopting-the-coaching-stance/</guid>
				<description>A Scrum Master adopting a coaching stance should focus on guiding teams toward self-organisation, building trust and influence through expertise and empathy, and adapting their approach to the team’s unique context and culture. Key outcomes include stronger collaboration, empowered decision-making, and higher team satisfaction. To be effective, Scrum Masters should actively listen, foster a positive environment, and continuously develop their own skills.</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>Unlocking Agile Success: How Empirical Models Transform Project Outcomes</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</link>
				<pubDate>Wed, 12 Oct 2022 17:08:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</guid>
				<description>Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>Scaling Professional Scrum with Visual Studio Team Services</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/scaling-professional-scrum-with-visual-studio-team-services/</link>
				<pubDate>Wed, 06 Jul 2016 12:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/scaling-professional-scrum-with-visual-studio-team-services/</guid>
				<description>Visual Studio Team Services helps reduce friction and risks when scaling Scrum across multiple teams by providing robust automation and support for organizing work within a Nexus framework. Workshops and webcasts demonstrated how VSTS can be set up to manage many teams effectively, making it a strong choice for enterprise-scale Scrum. Development managers should consider VSTS when coordinating large, distributed Scrum teams to streamline processes and improve visibility.</description>
			</item>
			<item>
				<title>How to Be an Effective Agile Coach: Agnosticism in Practice</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</link>
				<pubDate>Tue, 14 Nov 2023 11:00:50 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</guid>
				<description>Effective Agile coaching means being flexible and not pushing one framework; instead, help teams understand core Agile, Lean, and Scrum principles so they can choose what works best for their context. Encourage experimentation, educate teams on different approaches, and support their decision-making process. Focus on enabling teams to own their process and continuously improve rather than prescribing solutions.</description>
			</item>
			<item>
				<title>Breaking Free from the Plagues of Agility: How to Cultivate Flexibility and Innovation in Your Team</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/breaking-free-from-the-plagues-of-agility-how-to-cultivate-flexibility-and-innovation-in-your-team/</link>
				<pubDate>Wed, 01 Nov 2023 09:42:43 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/breaking-free-from-the-plagues-of-agility-how-to-cultivate-flexibility-and-innovation-in-your-team/</guid>
				<description>Teams often lose true agility by becoming too attached to specific tools and processes, which leads to stagnation, inefficiency, and lower morale. Encouraging experimentation, holding regular retrospectives to review practices, and empowering teams to adapt workflows are key to maintaining flexibility and innovation. Development managers should regularly assess whether current methods still serve the team&amp;rsquo;s needs and foster a culture of continuous improvement.</description>
			</item>
			<item>
				<title>Cutting Through the Red Tape: How Eliminating Committees Can Boost Your Time to Market</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/cutting-through-the-red-tape-how-eliminating-committees-can-boost-your-time-to-market/</link>
				<pubDate>Mon, 02 Oct 2023 07:00:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/cutting-through-the-red-tape-how-eliminating-committees-can-boost-your-time-to-market/</guid>
				<description>Committees often slow down decision-making and stall teams, leading to missed business opportunities and delayed time to market. Empowering teams to make decisions and adopting modern collaboration tools can significantly improve speed, accountability, and innovation. Review your current processes and consider reducing committee involvement to stay competitive and agile.</description>
			</item>
			<item>
				<title>How Much of An Impact can Scrum Have in a DevOps Environment?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-scrum-have-in-a-devops-environment/</link>
				<pubDate>Thu, 15 Jun 2023 14:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-scrum-have-in-a-devops-environment/</guid>
				<description>Combining Scrum and DevOps creates a powerful approach that boosts speed, collaboration, and product quality in software development. Scrum provides structure and problem-solving strategies, while DevOps brings automation and efficient delivery. Development managers should consider integrating both to maximize team performance and deliver better products faster.</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>Unlocking the True Power of Continuous Delivery: How Automation Transforms Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</link>
				<pubDate>Fri, 06 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</guid>
				<description>The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently.</description>
			</item>
			<item>
				<title>Security by Design Building Secure Software</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/security-by-design-building-secure-software/</link>
				<pubDate>Tue, 26 Nov 2024 13:35:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/security-by-design-building-secure-software/</guid>
				<description>Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation.</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>Detecting Agile BS: Lessons from the US Department of Defense</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</link>
				<pubDate>Fri, 28 Jun 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</guid>
				<description>Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense&amp;rsquo;s &amp;ldquo;Detecting Agile BS&amp;rdquo; guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation.</description>
			</item>
			<item>
				<title>Illuminate Your Workflow: Harnessing Candan Strategies for Continuous Improvement and Transparency</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/</link>
				<pubDate>Fri, 08 Mar 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/</guid>
				<description>Adopting a Candan strategy helps teams achieve continuous improvement and greater transparency by using flow metrics to identify workflow issues and inefficiencies. Visualising these metrics enables more informed decisions and motivates action, especially for Scrum teams that lack built-in measurement tools. To maximise benefits, integrate flow metrics into your processes and seek expert support or training if needed.</description>
			</item>
			<item>
				<title>How long does it take to transition from project management to Kanban?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</link>
				<pubDate>Fri, 16 Feb 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</guid>
				<description>Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams.</description>
			</item>
			<item>
				<title>How to Measure Your Organization&#39;s Ability to Improve Value Through Innovation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-measure-your-organization&#39;s-ability-to-improve-value-through-innovation/</link>
				<pubDate>Thu, 25 Jan 2024 11:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-measure-your-organization&#39;s-ability-to-improve-value-through-innovation/</guid>
				<description>To improve your organization&amp;rsquo;s ability to deliver value, focus on measuring and enhancing your capacity for innovation using evidence-based management and key metrics like active branches, technical debt, innovation rate, and complexity overhead. Regularly monitor these metrics, set clear innovation goals, and foster a culture of continuous improvement to identify bottlenecks and drive better outcomes. Take action by simplifying processes, managing technical debt, and increasing time spent on new features to boost your team&amp;rsquo;s innovation and long-term success.</description>
			</item>
			<item>
				<title>The Overlooked Virtue of Agility: Diligence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/</link>
				<pubDate>Thu, 07 Dec 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/</guid>
				<description>Diligence, or consistently following through on quality standards like the definition of done, is often overlooked in Agile teams but is essential for reliable delivery and long-term success. Without diligence, teams risk inconsistent quality and increased rework, while a strong focus on it leads to better products and faster delivery over time. Development managers should ensure the definition of done is clear, visible, and enforced, and foster a culture of accountability and perseverance to make diligence a team habit.</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>Stop treating the end of the Sprint like a finish line</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</link>
				<pubDate>Thu, 05 Jun 2025 15:30:54 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</guid>
				<description>The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation.</description>
			</item>
			<item>
				<title>Mastering 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>Detecting Agile BS</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/detecting-agile-bs/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/detecting-agile-bs/</guid>
				<description>Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and critical evaluation questions.</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>7 Harbingers of the Agile apocalypse - Chaos</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-chaos/</link>
				<pubDate>Mon, 23 Oct 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-chaos/</guid>
				<description>Chaos in agile transformations often arises from unclear product vision and poor communication, leading to misalignment and confusion. To overcome this, development managers should establish a clear strategic direction, break it down into actionable goals, and reinforce it through ongoing communication and feedback. Focus on principles that empower teams and ensure everyone understands how their work contributes to shared objectives.</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>7 harbingers of the Agile apocalypse - Judgement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</link>
				<pubDate>Fri, 20 Oct 2023 11:00:13 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</guid>
				<description>Rigid, judgmental application of Agile frameworks stifles creativity and innovation, turning teams into rule-followers instead of problem-solvers. True agility comes from empowering teams with autonomy, transparency, and principles rather than enforcing one-size-fits-all rules. Development managers should focus on fostering a culture of openness and continuous learning, allowing teams to adapt practices to their unique needs.</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>From Unused Gym Memberships to Agile Implementation The Parallels of Misapplied Investments</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/</link>
				<pubDate>Thu, 03 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/</guid>
				<description>Adopting agile methods is like buying a gym membership; real benefits come only with consistent, committed practice rather than superficial adoption. Key to success are breaking down goals, fostering cross-functional teams, and maintaining quality instead of just following rituals. Development managers should focus on genuine agile implementation and ongoing improvement to avoid wasted investment and missed opportunities.</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>How does a Scrum team decide on a Sprint goal?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</guid>
				<description>A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable.</description>
			</item>
			<item>
				<title>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>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>Mastering Outcomes: How Evidence-Based Management Transforms Your Project Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-outcomes-how-evidence-based-management-transforms-your-project-success/</link>
				<pubDate>Thu, 12 Sep 2024 13:46:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-outcomes-how-evidence-based-management-transforms-your-project-success/</guid>
				<description>Defining clear, measurable outcomes and using both leading and lagging metrics are essential for project success. Evidence-based management helps teams make informed decisions by consistently collecting and analyzing data, then iterating based on insights. Development managers should focus on setting SMART goals, tracking the right metrics, and using data to guide continuous improvement.</description>
			</item>
			<item>
				<title>Mastering Agile: The Power of &#34;Just Enough and No More&#34; for Optimal Efficiency</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/</link>
				<pubDate>Tue, 05 Dec 2023 11:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/</guid>
				<description>Applying the principle of &amp;ldquo;just enough and no more&amp;rdquo; across backlog management, team size, refinement, and planning helps teams stay focused, efficient, and adaptable. Prioritising value, embracing simplicity, and iterating regularly reduces wasted effort and maximises productivity. Development managers should encourage teams to do only what is necessary to deliver value and continuously improve.</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>Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</link>
				<pubDate>Tue, 21 Jul 2020 18:00:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</guid>
				<description>Many teams claim to be agile but still operate with outdated management mindsets that stifle autonomy and engagement, leading to low adoption of core agile practices like short iterations and retrospectives. True agility requires transparency, regular feedback, and a focus on delivering value rather than just completing tasks. Development managers should assess whether their teams meet these criteria and actively foster a culture that supports genuine agile principles.</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>The Importance of Delivering Working Software Every Iteration</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</link>
				<pubDate>Wed, 26 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</guid>
				<description>Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort.</description>
			</item>
			<item>
				<title>How does a Scrum Master or Agile coach motivate a Scrum Team?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</link>
				<pubDate>Mon, 11 Sep 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</guid>
				<description>Scrum Masters and Agile coaches play a key role in keeping teams motivated by aligning goals with stakeholder value, celebrating achievements, and fostering open communication. Teams lose motivation when goals are misaligned or stakeholder engagement is lacking, so it is important to set achievable objectives, involve stakeholders, and encourage autonomy and continuous learning. Regularly review team morale, connect work to its broader impact, and create feedback loops to maintain a resilient and high-performing team.</description>
			</item>
			<item>
				<title>Unlocking Agility: How EPS Immersive Learning Transforms Your Team&#39;s Performance</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-eps-immersive-learning-transforms-your-team&#39;s-performance/</link>
				<pubDate>Wed, 16 Aug 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-eps-immersive-learning-transforms-your-team&#39;s-performance/</guid>
				<description>The EPS immersive learning experience offers structured, ongoing coaching and feedback that helps teams improve agility and effectiveness with minimal time investment. Through iterative assignments, tailored feedback, and additional coaching, teams can continuously adapt and enhance their practices. To get the most value, managers should actively engage with the process and integrate learnings into daily work.</description>
			</item>
			<item>
				<title>What would you advise a scrum team to do in their first 4 weeks?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</link>
				<pubDate>Thu, 16 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</guid>
				<description>In the first four weeks, a scrum team should focus on practicing scrum correctly, learning both what works and what does not, and experimenting to find the best fit for their context. Teams should document obstacles and improvements, address one key change per sprint, and use retrospectives to drive continuous improvement. This approach builds a strong foundation and helps make organizational issues visible for future action.</description>
			</item>
			<item>
				<title>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>Why Every Scrum Master Needs an Immersive Training Experience</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</link>
				<pubDate>Tue, 21 Nov 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</guid>
				<description>Immersive training is essential for Scrum Masters who already have hands-on experience, as it deepens practical skills, sharpens leadership abilities, and drives better team outcomes. Unlike standard courses, immersive classes focus on real-world challenges, immediate feedback, and peer learning, helping Scrum Masters maximize team value and effectiveness. Development managers should encourage experienced Scrum Masters to pursue immersive training to foster continuous improvement and stronger team leadership.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile Apocalypse - Famine</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-famine/</link>
				<pubDate>Thu, 19 Oct 2023 15:00:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-famine/</guid>
				<description>Resource scarcity in Agile organizations, such as lack of trust, funding, training, and tools, often stems from rigid, top-down management and can severely limit team performance and growth. Empowering teams with decision-making authority, flexible budgets, and a culture of trust and continuous learning leads to better outcomes and avoids costly mistakes. Development managers should prioritize investing in people and resources to enable agility and long-term success.</description>
			</item>
			<item>
				<title>Quotes: &#34;I estimate that 75% of those organisations using Scrum will not succeed in getting the benefits that they hope for from it.&#34; - Ken Schwaber</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</link>
				<pubDate>Fri, 06 Oct 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</guid>
				<description>Most organisations using Scrum do not achieve the benefits they expect because they focus on team-level practices instead of making broader organisational changes. Success requires adopting an agile mindset across the whole company, securing management support, and continuously improving processes. Development managers should drive holistic transformation beyond just the development team to increase the chances of real Scrum success.</description>
			</item>
			<item>
				<title>Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</link>
				<pubDate>Mon, 06 Mar 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</guid>
				<description>Many Scrum Masters focus too much on administrative tasks like Jira management instead of empowering their teams and supporting the Product Owner and organization. The Advanced PSM course highlights the importance of enabling team accountability, facilitating value delivery, and addressing organizational barriers. Development managers should encourage Scrum Masters to move beyond admin work and focus on building team capability and organizational agility.</description>
			</item>
			<item>
				<title>What is the hardest part of working with a brand-new scrum team?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</link>
				<pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</guid>
				<description>The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement.</description>
			</item>
			<item>
				<title>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>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>Challenging Misconceptions About Behaviour in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</link>
				<pubDate>Thu, 13 Feb 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</guid>
				<description>Agile is often misused to justify poor planning and lack of accountability, but true agility demands more discipline, professionalism, and clear alignment with the product vision. Teams that fail to deliver usable increments or start work without sufficient understanding are not practicing real Agile. Development managers should ensure their teams uphold high standards and address unprofessional behavior rather than excusing it as Agile.</description>
			</item>
			<item>
				<title>Embrace Kaizen: Unlocking Continuous Improvement for Personal and Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embrace-kaizen-unlocking-continuous-improvement-for-personal-and-team-success/</link>
				<pubDate>Wed, 14 Aug 2024 07:04:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embrace-kaizen-unlocking-continuous-improvement-for-personal-and-team-success/</guid>
				<description>Kaizen is a philosophy of making small, ongoing improvements that can lead to significant gains in team performance, collaboration, and personal growth. By regularly observing, measuring, and refining processes, teams can boost productivity and quality while fostering a culture where everyone feels empowered to suggest changes. Development managers should encourage open communication, celebrate small wins, and be patient as continuous improvement is a long-term journey.</description>
			</item>
			<item>
				<title>The Future of Scrum Training: Immersive Learning for Lasting Change</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</link>
				<pubDate>Thu, 23 Nov 2023 08:30:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</guid>
				<description>Immersive learning is more effective than traditional Scrum training because it provides ongoing support, real-time problem solving, and peer collaboration over several weeks, helping participants apply new skills in real situations. This approach leads to gradual, sustainable change and builds confidence through shared learning and continuous improvement. Development managers should consider immersive learning to achieve lasting transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 1</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</link>
				<pubDate>Tue, 24 Oct 2023 06:50:42 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</guid>
				<description>Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars.</description>
			</item>
			<item>
				<title>How does the APS course help people apply scrum effectively?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</link>
				<pubDate>Wed, 18 Jan 2023 08:57:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</guid>
				<description>The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption.</description>
			</item>
			<item>
				<title>Story Points &amp; Velocity are a sign of an unsuccessful team</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</link>
				<pubDate>Mon, 04 Jan 2021 14:20:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</guid>
				<description>Story points and velocity are not required by Scrum and relying on them long-term signals a team&amp;rsquo;s lack of maturity and adaptability. While they can help new teams start conversations and build shared understanding, they do not provide real predictability or confidence in delivery. Development managers should focus on transparency, concrete data, and metrics like cycle time to build true confidence and improve predictability for stakeholders.</description>
			</item>
			<item>
				<title>The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/evidence-based-management-guide/</link>
				<pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/evidence-based-management-guide/</guid>
				<description>Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and continuous experimentation.</description>
			</item>
			<item>
				<title>You want speed, adaptability, resilience</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</link>
				<pubDate>Sun, 11 May 2025 15:30:29 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</guid>
				<description>Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks.</description>
			</item>
			<item>
				<title>let-us be blunt, if a Scrum Team isn’t delivering, is it effective</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</link>
				<pubDate>Fri, 07 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</guid>
				<description>A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness.</description>
			</item>
			<item>
				<title>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>The Importance of Validation in Product Development: A Strategic Approach</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/</link>
				<pubDate>Mon, 02 Sep 2024 15:30:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/</guid>
				<description>Prioritizing features to close sales can fragment your product and lead to long-term costs that outweigh short-term gains. Shifting to a hypothesis-driven approach, where you define, track, and validate the value of new features using data, helps ensure you invest in what truly benefits users and the business. Equip product managers with the right telemetry and authority to make evidence-based decisions, and avoid building features that do not deliver measurable value.</description>
			</item>
			<item>
				<title>Hiring a Scrum Master is hard</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</link>
				<pubDate>Sun, 16 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</guid>
				<description>Hiring a Scrum Master is challenging because many organizations misunderstand the role and focus on the wrong qualifications. A strong Scrum Master needs deep knowledge of Scrum, the ability to drive team effectiveness, and enough technical understanding to support your teams and foster change. Look for candidates who demonstrate commitment, challenge assumptions, and coach teams to deliver real value, not just those with certifications or project management backgrounds.</description>
			</item>
			<item>
				<title>Transform Your Leadership: The Power of Evidence-Based Management in Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/</link>
				<pubDate>Wed, 29 Nov 2023 11:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/</guid>
				<description>Evidence-based management helps Agile leaders make better decisions by using data on team performance, customer satisfaction, and product quality, leading to continuous improvement and stronger collaboration. Real-world examples show that adopting EBM can improve delivery times, morale, and outcomes. Development managers should invest in EBM training, encourage data-driven practices, and support experimentation to drive team success.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Misconceptions to Empowering Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</link>
				<pubDate>Fri, 12 May 2023 14:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</guid>
				<description>The Scrum Master role is often misunderstood as tool administration or problem-solving, but its true value lies in empowering teams to self-organize and operate independently. Key insights include fostering team autonomy, guiding rather than controlling, and committing to continuous learning. Development managers should support Scrum Masters in becoming facilitators who enable teams to thrive without constant oversight.</description>
			</item>
			<item>
				<title>Ditch the Agile Bandit Mentality: How to Prioritise Value Over Estimates for Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/</link>
				<pubDate>Fri, 05 Jan 2024 11:00:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/</guid>
				<description>Focusing on estimates instead of value delivery can harm team morale and undermine Agile principles. Shifting attention to outcomes, fostering psychological safety, and using metrics that reflect real customer impact lead to better products and a more engaged team. Development managers should prioritise value and team well-being over tracking estimates to achieve lasting success.</description>
			</item>
			<item>
				<title>Mastering Complexity in Scrum: Transform Your Team with Agile Product Strategy Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/</link>
				<pubDate>Wed, 15 Nov 2023 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/</guid>
				<description>Understanding and managing complexity is essential for Scrum teams to plan and execute effectively, especially as unpredictability increases. Emphasizing transparency, inspection, and adaptation helps teams navigate complex work, improve processes, and foster continuous improvement. Consider investing in training or discussions that deepen your team&amp;rsquo;s grasp of these principles to boost effectiveness.</description>
			</item>
			<item>
				<title>How does Naked Agility select associate Scrum Trainers?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-naked-agility-select-associate-scrum-trainers/</link>
				<pubDate>Wed, 04 Jan 2023 14:35:57 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-naked-agility-select-associate-scrum-trainers/</guid>
				<description>Naked Agility selects associate Scrum Trainers based on real-world agile experience, proven problem-solving skills, and the ability to engage and inspire teams, not just theoretical knowledge. Trainers are evaluated through co-training and must demonstrate deep expertise as practitioners, coaches, or consultants who can address industry-specific challenges and empower teams to apply agile effectively. If you need agile training or coaching from experienced professionals who understand complex environments, consider reaching out to Naked Agility.</description>
			</item>
			<item>
				<title>You are doing it wrong if you are not using test first</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</link>
				<pubDate>Mon, 07 Dec 2020 12:00:58 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</guid>
				<description>Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices.</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>Harnessing Evidence-Based Management: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/</link>
				<pubDate>Wed, 14 Aug 2024 07:12:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/</guid>
				<description>Evidence-based management helps you make better decisions by using data to inform, not control, your actions and team behaviours. Focus on choosing the right metrics that align with your business goals, understand the context behind the numbers, and engage with teams to uncover root causes. Use data as a guide for continuous improvement and be ready to adapt your strategies as new insights emerge.</description>
			</item>
			<item>
				<title>Taming the Chaos Factor: How to Align Your Agile Teams for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/</link>
				<pubDate>Thu, 09 Nov 2023 10:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/</guid>
				<description>Chaos in Agile teams often results from unclear goals, poor communication, and lack of alignment, leading to disjointed work, low morale, and ineffective decisions. To address this, set clear objectives, ensure open communication, and align teams with the organisation’s vision. Focus on fostering collaboration and regularly reinforcing shared goals to create a more productive and unified environment.</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>Unlocking Continuous Delivery: How Feature Flags Transform Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</link>
				<pubDate>Thu, 16 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</guid>
				<description>Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management in Agile: Inform, Don’t Control</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</link>
				<pubDate>Wed, 11 Sep 2024 13:36:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</guid>
				<description>Evidence-Based Management helps you use data to guide decisions and understand team behaviors, but it should inform rather than control actions. Define clear outcomes, choose metrics that align with those goals, and use data as a conversation starter to uncover challenges and drive improvement. Regularly review metrics with your teams to stay aligned and focus on delivering real value, not just hitting targets.</description>
			</item>
			<item>
				<title>Cultivating Patience: The Secret Ingredient for Thriving Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/</link>
				<pubDate>Fri, 08 Dec 2023 11:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/</guid>
				<description>Patience is essential for agile teams to build trust, avoid blame, and support growth, leading to better collaboration and outcomes. Leaders should set realistic expectations, encourage open communication, and model patient behavior to foster a healthy team environment. Take time to invest in team development and celebrate progress to enable long-term success.</description>
			</item>
			<item>
				<title>7 harbingers of the Agile apocalypse- War</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-war/</link>
				<pubDate>Thu, 19 Oct 2023 13:00:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-war/</guid>
				<description>Unchecked conflict in agile teams can escalate from healthy debate to destructive infighting, undermining collaboration and progress. Leaders must foster open communication, empathy, and clear conflict resolution processes to keep disagreements constructive and aligned with shared goals. Proactively managing conflict is essential to prevent team dysfunction and support ongoing innovation and growth.</description>
			</item>
			<item>
				<title>What is the Sprint Review workshop and how will it help organisations?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</link>
				<pubDate>Fri, 30 Jun 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</guid>
				<description>The Sprint Review workshop helps teams align product development with stakeholder needs, adapt to market changes, and drive continuous improvement. It offers practical guidance on running effective reviews, boosting stakeholder engagement, and turning feedback into actionable improvements. Development managers should consider this workshop to enhance team performance and ensure products deliver real value.</description>
			</item>
			<item>
				<title>How Hard is it to Transition from Being a Developer to a Scrum developer?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-hard-is-it-to-transition-from-being-a-developer-to-a-scrum-developer/</link>
				<pubDate>Thu, 22 Jun 2023 11:00:25 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-hard-is-it-to-transition-from-being-a-developer-to-a-scrum-developer/</guid>
				<description>Transitioning from a traditional developer role to a Scrum developer is challenging but rewarding, requiring a shift to continuous delivery, testing, and improvement, along with strong engineering practices. Success depends on embracing ongoing learning and aligning coding with Agile principles. Development managers should support their teams with training and opportunities to practice Scrum to ensure high-quality, sustainable product delivery.</description>
			</item>
			<item>
				<title>Professional Scrum Training for the Ghana Police Service</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</link>
				<pubDate>Mon, 30 Oct 2017 19:26:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</guid>
				<description>The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams.</description>
			</item>
			<item>
				<title>Scaling Teams: How to Foster Innovation Without Falling into Bureaucracy</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scaling-teams-how-to-foster-innovation-without-falling-into-bureaucracy/</link>
				<pubDate>Thu, 27 Feb 2025 11:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scaling-teams-how-to-foster-innovation-without-falling-into-bureaucracy/</guid>
				<description>Scaling teams does not automatically lead to more innovation; it often results in bureaucracy, slower decision-making, and communication issues. To avoid this, focus on empowering teams, streamlining processes, and improving communication so growth enhances agility and innovation rather than stifling it. Development managers should reassess their scaling strategies to prioritize adaptability and team ownership for better outcomes.</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>Scrum doesn&#39;t solve problems, it reveals them. How, and why is that valuable?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</link>
				<pubDate>Wed, 27 Sep 2023 07:00:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</guid>
				<description>Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation.</description>
			</item>
			<item>
				<title>Harnessing the Power of Empiricism: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harnessing-the-power-of-empiricism-transform-your-decision-making-with-data-driven-insights/</link>
				<pubDate>Thu, 17 Aug 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harnessing-the-power-of-empiricism-transform-your-decision-making-with-data-driven-insights/</guid>
				<description>Using data to guide decisions helps teams make better choices, improve continuously, and build trust with stakeholders. The key is to ensure access to relevant data, act deliberately, and monitor results in a cycle of experimentation and learning. Development managers should foster a culture where decisions are based on evidence, not assumptions, and regularly review outcomes to adapt and improve.</description>
			</item>
			<item>
				<title>Why did so many of the early agile transformations fail?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-did-so-many-of-the-early-agile-transformations-fail/</link>
				<pubDate>Mon, 06 Feb 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-did-so-many-of-the-early-agile-transformations-fail/</guid>
				<description>Many agile transformations fail because decisions are made top-down without involving the teams who do the actual work, leading to poor fit and lack of buy-in. Teams have the best understanding of their environment and should be included in selecting and shaping agile solutions to ensure success. To improve outcomes, involve your teams in decision-making from the start rather than imposing off-the-shelf frameworks.</description>
			</item>
			<item>
				<title>When you scale Scrum, the challenge isn’t just delivery, it coherence</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/when-you-scale-scrum-the-challenge-isn-t-just-delivery-it-coherence/</link>
				<pubDate>Tue, 27 May 2025 15:30:33 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/when-you-scale-scrum-the-challenge-isn-t-just-delivery-it-coherence/</guid>
				<description>When scaling Scrum, the main challenge is maintaining coherence across teams, not just delivering work. Without coordination, teams create inconsistent user experiences and duplicate efforts. To address this, form a cross-team Community of Practice to develop shared frameworks and include them in your Definition of Done, promoting collaboration and consistency without adding hierarchy.</description>
			</item>
			<item>
				<title>Why More Teams Won&#39;t Speed Up Delivery: The Truth About Scaling Effectively</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-more-teams-won&#39;t-speed-up-delivery-the-truth-about-scaling-effectively/</link>
				<pubDate>Fri, 21 Feb 2025 07:59:43 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-more-teams-won&#39;t-speed-up-delivery-the-truth-about-scaling-effectively/</guid>
				<description>Adding more teams does not automatically speed up software delivery; it often creates more dependencies, coordination overhead, and technical debt, which can slow progress. Effective scaling focuses on reducing friction, structuring teams to minimize dependencies, and prioritizing quality over quantity. Development managers should ensure teams are set up to work independently and efficiently rather than simply increasing headcount.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 5</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-5/</link>
				<pubDate>Thu, 26 Oct 2023 07:00:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-5/</guid>
				<description>Scrum does not mean abandoning governance; instead, it requires teams to balance agility with necessary regulatory and organizational standards. Applying &amp;ldquo;just enough governance&amp;rdquo; ensures compliance and quality without stifling innovation, especially in regulated or complex environments. Development managers should regularly review and adapt governance practices to support both compliance and Agile delivery.</description>
			</item>
			<item>
				<title>Quotes: You can&#39;t connect the dots looking forward; you can only connect them looking backwards. Steve Jobs</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/quotes-you-can&#39;t-connect-the-dots-looking-forward-you-can-only-connect-them-looking-backwards-steve-jobs/</link>
				<pubDate>Fri, 13 Oct 2023 11:00:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/quotes-you-can&#39;t-connect-the-dots-looking-forward-you-can-only-connect-them-looking-backwards-steve-jobs/</guid>
				<description>Steve Jobs’ idea that you can only connect the dots looking backward highlights the value of learning from past experiences in Agile environments. Development managers should regularly reflect on previous outcomes, use data to inform decisions, and remain flexible to adapt strategies as new information emerges. Encourage your teams to balance lessons from the past with ongoing validation and iterative improvement to stay effective in a changing landscape.</description>
			</item>
			<item>
				<title>Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/</link>
				<pubDate>Thu, 13 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/</guid>
				<description>Delivering working software in small increments helps teams identify and address risks early, adapt to changes quickly, and get real feedback from users, while relying mainly on documentation can slow response to shifting needs. Documentation is still important, but focusing on usable products provides more value in fast-changing environments. Development managers should prioritize building and validating working software while maintaining just enough documentation to support adaptation and clarity.</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>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>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>The Pitfalls of Agile Burndowns: Stop Being Agile Bandits</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</link>
				<pubDate>Tue, 09 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, false confidence, and wasted effort, as most plans quickly become outdated and only a fraction of features are actually used. Instead, focus on minimal, just-in-time planning and continuous flow to adapt quickly, reduce overhead, and deliver real value. Encourage your teams to plan only what is needed for the next day, adjust daily, and prioritize delivering value over maintaining detailed charts.</description>
			</item>
			<item>
				<title>Agile Leadership: Empowering Managers with the Right Skills</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/agile-leadership-empowering-managers-with-the-right-skills/</link>
				<pubDate>Wed, 29 Nov 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/agile-leadership-empowering-managers-with-the-right-skills/</guid>
				<description>Managers often struggle to transition into effective leadership roles without proper training, especially in agile environments where servant leadership and data-driven decision making are key. Investing in Professional Agile Leadership and Evidence-Based Management training helps managers empower teams, align work with organizational goals, and make informed decisions. Consider prioritizing these training programs to boost both team performance and organizational success.</description>
			</item>
			<item>
				<title>How do you decide whether to pivot or stay the course? (Nokia story)</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-decide-whether-to-pivot-or-stay-the-course-nokia-story/</link>
				<pubDate>Wed, 13 Sep 2023 13:59:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-decide-whether-to-pivot-or-stay-the-course-nokia-story/</guid>
				<description>Product owners must confidently make pivotal decisions, often with incomplete information, by balancing data, instinct, and alignment with long-term goals. Success depends on staying connected with teams and stakeholders, monitoring market trends, and fostering a culture of continuous learning and adaptability. To lead effectively, embrace change, value feedback, and be prepared to pivot or persevere based on evidence rather than sunk costs.</description>
			</item>
			<item>
				<title>Unlocking the True Power of Agile: Embracing Change and Collaboration for Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-agile-embracing-change-and-collaboration-for-team-success/</link>
				<pubDate>Thu, 13 Jul 2023 07:38:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-agile-embracing-change-and-collaboration-for-team-success/</guid>
				<description>Agile works best when teams focus on collaboration, embrace change, and prioritize delivering real value to customers rather than rigidly following processes. Regular reflection, empowering team members, and experimenting with new approaches help teams adapt and improve. Development managers should foster a growth mindset and lead by example to create an environment where teams can thrive and continuously deliver better results.</description>
			</item>
			<item>
				<title>How big is the gap between an average developer and a great Agile Developer?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-big-is-the-gap-between-an-average-developer-and-a-great-agile-developer/</link>
				<pubDate>Tue, 06 Jun 2023 07:00:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-big-is-the-gap-between-an-average-developer-and-a-great-agile-developer/</guid>
				<description>The main difference between an average and a great Agile developer is deep engagement and a commitment to continuous learning and practice. Great Agile developers are proactive, embrace setbacks as learning opportunities, and thrive in environments that support self-directed and interactive learning. To close the gap, managers should foster a culture that encourages ongoing practice, flipped learning, and autonomy in professional development.</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>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</guid>
				<description>A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: Why Understanding Product Vision is Key to Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-why-understanding-product-vision-is-key-to-success/</link>
				<pubDate>Wed, 03 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-why-understanding-product-vision-is-key-to-success/</guid>
				<description>Teams that clearly understand the product vision and strategic goals are more aligned, empowered, and able to make decisions that deliver greater value. Regularly communicating the vision, involving the team in its development, and providing context and feedback opportunities foster ownership and agility. Development managers should ensure their teams know and connect with the product vision to maximize effectiveness and adaptability.</description>
			</item>
			<item>
				<title>Unlocking Naked Agility: How Happy Teams Drive Exceptional Products</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-naked-agility-how-happy-teams-drive-exceptional-products/</link>
				<pubDate>Fri, 10 May 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-naked-agility-how-happy-teams-drive-exceptional-products/</guid>
				<description>Happy, engaged teams are essential for building exceptional products; when people have autonomy, opportunities for growth, and a clear sense of purpose, their motivation and output improve significantly. Managers should empower decision-making, invest in skill development, and clearly communicate the vision to foster this environment. Prioritising team well-being leads to better products and more satisfied customers, so focus on creating a culture where your teams can thrive.</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 Product Backlog Management: Key Strategies for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/</link>
				<pubDate>Thu, 30 Nov 2023 11:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/</guid>
				<description>Effective product backlog management is crucial for Agile success; prioritising tasks, limiting work in progress, and holding regular refinement sessions help teams stay focused and deliver more value. Engaging stakeholders and using visual tools can further improve clarity and alignment. Development managers should regularly review their backlog practices to ensure they are working on the most valuable items and maintaining a manageable, focused backlog.</description>
			</item>
			<item>
				<title>The Power of Immersive Learning: Elevating Scrum Mastery in Your Organization</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-elevating-scrum-mastery-in-your-organization/</link>
				<pubDate>Wed, 22 Nov 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-elevating-scrum-mastery-in-your-organization/</guid>
				<description>Immersive learning is more effective than traditional training for developing Scrum Masters because it emphasizes hands-on assignments, real-world application, and knowledge sharing, which lead to lasting improvements in team performance. Teams immediately apply what they learn, receive real-time feedback, and benefit from collective insights, making Scrum practices like the Definition of Done part of daily work. To boost Scrum mastery and see real impact, prioritize immersive learning for your organization’s training programs.</description>
			</item>
			<item>
				<title>When is an APS course appropriate for a scrum team?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</link>
				<pubDate>Thu, 12 Oct 2023 08:32:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</guid>
				<description>An APS course is valuable for Scrum teams that want to deepen their understanding of core Scrum principles and shed ineffective practices that may have accumulated over time. It helps teams focus on delivering a working product each iteration and provides practical exercises, like the Barnacle Exercise, to identify and remove process inefficiencies. Consider APS if your team needs to realign with authentic Scrum practices and drive meaningful agile transformation.</description>
			</item>
			<item>
				<title>Why Agile Success Lies in Principles, Not Tools: A Shift in Focus</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-agile-success-lies-in-principles-not-tools-a-shift-in-focus/</link>
				<pubDate>Wed, 03 May 2023 07:00:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-agile-success-lies-in-principles-not-tools-a-shift-in-focus/</guid>
				<description>Focusing on Agile principles rather than tools leads to better decision-making, consistency, and long-term team success. Overreliance on tools can create rigid, ineffective processes, while principles support adaptability and collaboration. Development managers should reflect on whether their teams are prioritising principles and consider shifting their focus to foster continuous improvement.</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>Kendall Guide - A System of Work for AI Adoption</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/kendall-guide/</link>
				<pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/kendall-guide/</guid>
				<description>A practical framework guiding organisations to adopt AI by prioritising real problems, clarifying context, and enabling adaptive, evidence-based decision-making and collaboration.</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>The Power of Metrics: Why PAL-EBM is Essential for Your Organization</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/</link>
				<pubDate>Sat, 27 Jan 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/</guid>
				<description>The PAL-EBM class helps leaders and teams understand how to use metrics effectively to drive organizational success by focusing on real data, transparency, and the human impact of measurement. Participants learn through real-world stories why some metrics fail, how to avoid negative behaviors like those seen with Microsoft&amp;rsquo;s stack ranking, and how to foster strategic conversations that lead to better outcomes. Leadership teams are encouraged to take the class together to align on measuring success, iteratively strategize, and make informed decisions that support long-term goals.</description>
			</item>
			<item>
				<title>Understanding the True Role of a Scrum Master</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</link>
				<pubDate>Tue, 28 Nov 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</guid>
				<description>The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement.</description>
			</item>
			<item>
				<title>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>7 deadly sins of Agile: Wrath</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/</link>
				<pubDate>Mon, 16 Oct 2023 11:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/</guid>
				<description>Wrath in Agile teams shows up as blame and fear of mistakes, which stifles innovation and learning. Shifting from blame to shared accountability creates a safer environment for risk-taking and continuous improvement. Development managers should encourage open discussion of mistakes and support a culture where learning from errors is valued over perfection.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Organizational Structure</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-organizational-structure/</link>
				<pubDate>Thu, 19 Oct 2023 11:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-organizational-structure/</guid>
				<description>Traditional top-down management structures block true agility by centralizing decision-making and limiting team empowerment, especially for key roles like Product Owner. To become more agile, organizations need to decentralize authority, promote transparency, and adopt servant leadership, allowing teams closer to the customer to make decisions. Leaders should drive this shift by supporting teams and gradually implementing changes that focus on delivering customer value.</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>Unlocking the Scrum Master&#39;s Potential: Embracing Broader Responsibilities for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</guid>
				<description>Scrum Masters have a broader responsibility beyond supporting their teams; they also need to engage with the Product Owner and the wider organisation to remove obstacles and drive agility. Encouraging Scrum Masters to question outdated processes and model collaborative behaviours can lead to meaningful organisational change. Development managers should empower Scrum Masters to challenge the status quo and support their growth in these expanded roles.</description>
			</item>
			<item>
				<title>Scrum Master Effectiveness Begins with Consistent Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</link>
				<pubDate>Thu, 06 Mar 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</guid>
				<description>Scrum Master effectiveness depends on ensuring teams deliver something every sprint, as delivery enables feedback and improvement. Without delivery, there is no basis for learning or adding value. Development managers should prioritize consistent delivery as the foundation for team effectiveness and continuous improvement.</description>
			</item>
			<item>
				<title>Mastering Market Leadership: The Power of Frequent Product Releases</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/</link>
				<pubDate>Thu, 06 Feb 2025 11:02:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/</guid>
				<description>Frequent product releases help you lead the market by allowing rapid response to user feedback and emerging trends. Teams that adopt this approach see higher user engagement and improved morale, as they can quickly deliver value and adapt to change. To stay competitive, focus on releasing updates regularly and listening closely to your users.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning for Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-for-product-management/</link>
				<pubDate>Mon, 12 Aug 2024 10:03:43 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-for-product-management/</guid>
				<description>Immersive learning helps product management teams move beyond traditional training by combining extended, practical assignments with real-world application and reflection, leading to deeper understanding and organizational change. Focusing on outcome-based tasks and evidence-based metrics, rather than vanity measures, sparks valuable conversations and continuous improvement within teams. Development managers should consider adopting immersive learning approaches to drive lasting value and empower teams to deliver better results.</description>
			</item>
			<item>
				<title>Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</link>
				<pubDate>Wed, 17 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</guid>
				<description>Empowering teams to update or delete requirements based on user feedback is essential for true agility and delivering maximum value. Regularly engaging with the product team, keeping the backlog dynamic, and being willing to pivot or remove features ensures your product stays relevant and user-focused. Review your processes to make sure your teams have the authority and support to make these changes.</description>
			</item>
			<item>
				<title>How to Discover Unrealized Value in Your Product</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-discover-unrealized-value-in-your-product/</link>
				<pubDate>Wed, 24 Jan 2024 11:00:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-discover-unrealized-value-in-your-product/</guid>
				<description>Evidence-Based Management helps you find hidden opportunities to improve your product by using metrics like customer satisfaction, market share, and innovation to identify gaps between current performance and potential value. By adding these insights to your product backlog and prioritizing improvements, you can boost user satisfaction, reduce churn, and stay competitive. Regularly review feedback and involve stakeholders to ensure continuous improvement and maximize your product’s value.</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>Mastering Agile in a Distributed World: Tools and Strategies for Effective Team Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-agile-in-a-distributed-world-tools-and-strategies-for-effective-team-management/</link>
				<pubDate>Fri, 10 Apr 2020 18:35:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-agile-in-a-distributed-world-tools-and-strategies-for-effective-team-management/</guid>
				<description>Managing distributed Agile teams is effective when you choose tools that fit your team’s needs, such as GitHub for open-source, Microsoft Planner for simple task management, or Azure DevOps for comprehensive Agile support. Success depends on adapting practices, experimenting with tools, and maintaining regular feedback loops. Encourage continuous learning and collaboration to keep improving team performance.</description>
			</item>
			<item>
				<title>No Estimates and is it advisable for a Scrum Team to adopt it?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/</link>
				<pubDate>Thu, 22 Aug 2019 12:55:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/</guid>
				<description>Estimation is valuable mainly for the team discussions it generates, not the numbers themselves. New Scrum Teams benefit from using Story Points and Velocity, but as they mature, they should shift to flow-based metrics like Cycle Time and Throughput and consider dropping traditional estimation. Teams should regularly review and adapt their process, moving toward simpler sizing and continuous improvement as they gain experience.</description>
			</item>
			<item>
				<title>Design Sprints in Scrum: Common Questions and Practical Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</link>
				<pubDate>Wed, 04 Jun 2025 15:31:05 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</guid>
				<description>There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: The Essential Knowledge Every Coach Needs</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</link>
				<pubDate>Wed, 15 Nov 2023 11:01:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</guid>
				<description>Effective Agile coaching relies on a deep understanding of both frameworks like Scrum, Kanban, and Lean, and the principles behind them, along with strong technical knowledge. Continuous learning, community engagement, and practical experimentation are key to improving coaching skills and supporting teams. Development managers should prioritize ongoing education and active involvement to help their teams succeed with Agile.</description>
			</item>
			<item>
				<title>What will you learn on the professional scrum master course?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</link>
				<pubDate>Thu, 19 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</guid>
				<description>The Professional Scrum Master course teaches the theory and practical skills needed to be an effective scrum master, focusing on serving developers, product owners, and the organization to maximize team value. Participants learn through real-world examples, discussions, and case studies about empiricism, delivering working increments each sprint, and overcoming common challenges. Development managers should consider this course to strengthen their teams&amp;rsquo; ability to deliver value and navigate complexity.</description>
			</item>
			<item>
				<title>In what circumstances is agile consulting appropriate?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/in-what-circumstances-is-agile-consulting-appropriate/</link>
				<pubDate>Fri, 06 Jan 2023 04:52:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/in-what-circumstances-is-agile-consulting-appropriate/</guid>
				<description>Agile consulting is most effective when used for short-term engagements that build internal leadership and agile capabilities, rather than relying on long-term external coaches which can create dependency and erode core competencies. The main value lies in helping teams quickly identify and solve key problems, enabling sustainable improvement and momentum. Development managers should focus on developing internal agile leaders and use consultants to kickstart transformation, not as a permanent solution.</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>Balancing Speed and Stability: Why Quality Should Always Come First in Delivery Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/</link>
				<pubDate>Fri, 24 Jan 2025 06:30:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/</guid>
				<description>Rushing to meet deadlines often leads to poor-quality products that can damage your brand and erode customer trust, so prioritising stability and quality is essential even if it means missing deadlines or incurring fines. The long-term costs of sacrificing quality far outweigh any short-term gains from speed, as seen in real-world cases like Zoom. Development managers should educate stakeholders about these risks and always choose quality over speed to protect both reputation and customer relationships.</description>
			</item>
			<item>
				<title>Maximizing Transparency and Improvement in Software Engineering with Kanban</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</link>
				<pubDate>Mon, 29 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</guid>
				<description>Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement.</description>
			</item>
			<item>
				<title>Does Your Team Truly Understand Your Product Vision and Goals?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</link>
				<pubDate>Fri, 12 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</guid>
				<description>Many teams lack a true understanding of the product vision and strategic goals, which leads to misaligned decisions and reduced value for customers. Regularly communicating and reinforcing these goals helps team members see how their work contributes to the bigger picture, improving collaboration and decision-making. Development managers should frequently check team alignment and use practical strategies like workshops, visual roadmaps, and leadership engagement to ensure everyone is working toward shared objectives.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Don&#39;t have a working agreement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don&#39;t-have-a-working-agreement/</link>
				<pubDate>Fri, 01 Mar 2024 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don&#39;t-have-a-working-agreement/</guid>
				<description>Not having a working agreement causes chaos, misalignment, and inefficiency in teams using Kanban or similar frameworks. Clear agreements on roles, goals, processes, and workflows are essential for team alignment and success. Development managers should ensure their teams regularly create and review working agreements to avoid confusion and improve outcomes.</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>What is DevOps and how is it different to Agile?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-devops-and-how-is-it-different-to-agile/</link>
				<pubDate>Thu, 23 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-devops-and-how-is-it-different-to-agile/</guid>
				<description>DevOps and Agile are fundamentally the same, both aiming to deliver value to customers and organizations by focusing on rapid feedback, continuous improvement, and systems thinking. The main difference is perspective, with each emphasizing different aspects of the delivery process, but both require the right tools and practices to optimize the whole system. Development managers should ensure Agile and DevOps work together to maximize value and improve outcomes across the organization.</description>
			</item>
			<item>
				<title>What is your perspective on collocation?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/what-is-your-perspective-on-collocation/</link>
				<pubDate>Mon, 21 Oct 2019 13:05:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/what-is-your-perspective-on-collocation/</guid>
				<description>Collocation, where all team members work together in the same space, is not required for Scrum but is strongly recommended, especially for new teams, as it improves communication, focus, and team ownership. While remote work is possible with the right technology, it often requires extra effort to replicate the benefits of in-person interaction. If collocation is not feasible, managers should support teams with tools and practices to minimize communication challenges and continuously improve team effectiveness.</description>
			</item>
			<item>
				<title>Key Skills Scrum Masters Need: Technical, Business, Organisational</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/key-skills-scrum-masters-need-technical-business-organisational/</link>
				<pubDate>Tue, 18 Feb 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/key-skills-scrum-masters-need-technical-business-organisational/</guid>
				<description>Scrum Masters need strong technical, business, and organisational skills to lead teams, align with business goals, and remove obstacles effectively. Experience and real leadership matter more than certifications. To achieve true agility, hire Scrum Masters who demonstrate competence and bold leadership.</description>
			</item>
			<item>
				<title>Addressing Systemic Issues in Agile Organizations</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/addressing-systemic-issues-in-agile-organizations/</link>
				<pubDate>Wed, 24 Jan 2024 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/addressing-systemic-issues-in-agile-organizations/</guid>
				<description>Many organizations adopting Agile focus on surface-level rituals instead of addressing deeper systemic issues, which limits real improvement. To drive true effectiveness, leaders should measure meaningful outcomes like ROI, profit per team member, and time to learn, and be willing to make bold organizational changes rather than incremental tweaks. The key takeaway is that lasting Agile success requires courage to tackle root problems and transform the entire business system, not just follow ceremonies.</description>
			</item>
			<item>
				<title>How Do You Know the Value Currently Delivered in Your Organization?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/</link>
				<pubDate>Tue, 23 Jan 2024 11:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/</guid>
				<description>Evidence-Based Management helps organizations measure and improve the value they deliver by using key metrics like customer satisfaction, employee engagement, revenue per employee, product cost ratio, and customer usage. This approach enables clearer goals, better decisions, and ongoing improvement by relying on data instead of assumptions. Start small with relevant metrics, involve your team, and regularly review results to drive meaningful change.</description>
			</item>
			<item>
				<title>Navigating the Judgment Trap: How to Foster a Healthy Agile Environment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/</link>
				<pubDate>Thu, 09 Nov 2023 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/</guid>
				<description>Judgment in Agile teams, such as rigid rules and unhealthy metric comparisons, can lower morale, stifle innovation, and create a culture of blame. To avoid this, set meaningful goals, use adaptive metrics that encourage improvement, and foster open dialogue focused on learning. Development managers should prioritize creating a safe, collaborative environment where teams feel empowered to innovate and grow.</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 Transformation: Why Embracing Difficult Conversations with Agile Consultants is Key to Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-transformation-why-embracing-difficult-conversations-with-agile-consultants-is-key-to-success/</link>
				<pubDate>Mon, 01 May 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-transformation-why-embracing-difficult-conversations-with-agile-consultants-is-key-to-success/</guid>
				<description>Allowing agile consultants to ask tough questions and engage openly with teams is essential for real transformation, as it sparks critical thinking, learning, and accountability. Restricting dialogue stifles change and limits improvement. Development managers should foster a safe environment for open conversations and be ready to embrace discomfort to achieve lasting results.</description>
			</item>
			<item>
				<title>From Developer to Agile Advocate: How My Journey Unveiled the Power of Scrum and DevOps</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/from-developer-to-agile-advocate-how-my-journey-unveiled-the-power-of-scrum-and-devops/</link>
				<pubDate>Thu, 02 Mar 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/from-developer-to-agile-advocate-how-my-journey-unveiled-the-power-of-scrum-and-devops/</guid>
				<description>The author describes moving from traditional project management to Agile, highlighting that real change comes from rethinking processes and focusing on people rather than just adopting new tools. Key insights include the importance of simplifying workflows, avoiding unnecessary bureaucracy, and empowering teams through Agile and Scrum principles. Development managers should focus on enabling team autonomy and streamlining processes to unlock better results.</description>
			</item>
			<item>
				<title>How would you help organizations pitch the opportunity of agile internally?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</link>
				<pubDate>Wed, 08 Feb 2023 07:15:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</guid>
				<description>To successfully pitch agile internally, tailor your message to leadership by focusing on business outcomes they care about, such as reduced costs, faster time to market, and improved customer satisfaction, using clear metrics and financial examples. When engaging teams, use a consultative approach that involves them in problem-solving and framework selection to build buy-in and reduce resistance. The key action is to align agile benefits with stakeholder priorities and measure progress with relevant data to make a compelling, evidence-based case.</description>
			</item>
			<item>
				<title>Evolution not Transformation: This is the Inevitability of change</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/evolution-not-transformation-this-is-the-inevitability-of-change/</link>
				<pubDate>Mon, 13 Jul 2020 12:58:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/evolution-not-transformation-this-is-the-inevitability-of-change/</guid>
				<description>Change in software organizations is not a one-time transformation but an ongoing evolution that requires continuous experimentation, adaptation, and learning. Leaders must drive this process from within by fostering a culture of agility, empowering teams, and regularly reassessing goals and practices to stay competitive in a fast-changing market. The key takeaway is to embrace continuous improvement and own the change process rather than relying on external solutions or static best practices.</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>Breaking the Silence: How to Combat Communication Gaps in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/</link>
				<pubDate>Thu, 02 Nov 2023 11:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/</guid>
				<description>Communication gaps in Agile teams can lead to stagnation, loss of trust, and failure to deliver value. Silence often shows up as avoiding tough conversations, ignoring misalignment, withholding feedback, or making false promises. Development managers should actively foster open dialogue, model transparent communication, and create safe channels for feedback to keep teams aligned and effective.</description>
			</item>
			<item>
				<title>From Control to Collaboration: How Project Managers Can Embrace Agility and Thrive</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/from-control-to-collaboration-how-project-managers-can-embrace-agility-and-thrive/</link>
				<pubDate>Wed, 24 May 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/from-control-to-collaboration-how-project-managers-can-embrace-agility-and-thrive/</guid>
				<description>Project managers need to move from controlling every detail to supporting and collaborating with their teams to succeed with agile approaches. Embracing uncertainty, focusing on outcomes instead of outputs, and fostering open communication are key to this shift. To thrive, managers should let go of the need to have all the answers, encourage continuous learning, and be patient as their teams adapt.</description>
			</item>
			<item>
				<title>Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</link>
				<pubDate>Mon, 13 Mar 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</guid>
				<description>A great Scrum Master is defined by their fit with the team and their ability to build trust, which is best achieved when teams help select their own Scrum Master. Beyond supporting the team, the most effective Scrum Masters build relationships across the organisation to identify and address broader obstacles, empowering others to drive change. Development managers should involve teams in Scrum Master selection and support their efforts to connect with stakeholders for greater organisational impact.</description>
			</item>
			<item>
				<title>How does scrum help leadership teams pick the most valuable work to focus on?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-scrum-help-leadership-teams-pick-the-most-valuable-work-to-focus-on/</link>
				<pubDate>Fri, 10 Feb 2023 07:15:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-scrum-help-leadership-teams-pick-the-most-valuable-work-to-focus-on/</guid>
				<description>Scrum does not help leadership teams choose the most valuable work; it highlights issues and provides feedback to inform decision-making, but leaders must set priorities based on business understanding. Agile frameworks like Scrum are most effective when leaders have a clear vision and use them to validate ideas, improve feedback loops, and optimize delivery. Leadership should focus on defining strategic goals, while Scrum helps teams deliver and refine solutions that align with those goals.</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>Nexus Guide</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</link>
				<pubDate>Fri, 27 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</guid>
				<description>Ineffective Product Owners, whether due to lack of skills or organisational constraints, can hinder team performance and product success. Development managers should support Product Owners through relationship-building, organisational education, and open dialogue, while ensuring the team continues to deliver quality work. Take action by fostering collaboration and advocating for clear role expectations to help Product Owners and teams succeed.</description>
			</item>
			<item>
				<title>Is Your Scrum Master Struggling? Discover When to Choose an Agile Process Simulation Workshop</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</link>
				<pubDate>Wed, 05 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</guid>
				<description>If your Scrum Master is struggling with the team, first assess whether the issue is with their approach or deeper team dynamics. An Agile Process Simulation workshop can help by engaging the team in open dialogue and tailored learning, empowering them to decide if Scrum fits their needs. Prioritize collaboration and self-discovery over imposing solutions to achieve better team outcomes.</description>
			</item>
			<item>
				<title>The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</link>
				<pubDate>Fri, 31 Mar 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</guid>
				<description>The difference between a new and professional Scrum Master is less about labels and more about embracing accountability and a mindset focused on team effectiveness and value creation. Regardless of experience, a Scrum Master should guide the team, remove obstacles, and drive continuous improvement rather than micromanage. Development managers should support Scrum Masters in adopting a professional approach that prioritises team impact and organisational value.</description>
			</item>
			<item>
				<title>Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</link>
				<pubDate>Mon, 09 Jan 2023 12:36:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</guid>
				<description>Teaching Scrum through hands-on experience, including using Minecraft, helps participants move from initial chaos to a clear understanding of Scrum’s value. Students first experience confusion similar to real project starts, then learn to apply Scrum principles, leading to practical insights and improved teamwork. Development managers should consider experiential learning to help teams internalise agile practices and appreciate their real-world benefits.</description>
			</item>
			<item>
				<title>Maximising Value from Applying Professional Scrum Training</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</link>
				<pubDate>Mon, 09 Jun 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</guid>
				<description>The main benefit of Professional Scrum training is not just learning Scrum, but creating a clear list of organisational obstacles that slow delivery. When teams are empowered to identify these issues and leadership commits to addressing them, real transformation can begin. Development managers should ensure their teams have a change backlog and actively work with leadership to remove barriers.</description>
			</item>
			<item>
				<title>At the end of the day, Kanban is about improving flow</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/</link>
				<pubDate>Mon, 03 Mar 2025 15:46:26 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/</guid>
				<description>Kanban focuses on improving workflow by removing constraints and bottlenecks, not by pushing people to work harder or longer. Key to better delivery is reducing work in progress and identifying blockers to increase efficiency. Managers should identify and address the biggest constraint in their current workflow to see meaningful improvements.</description>
			</item>
			<item>
				<title>Mastering the Art of Scaling Agile: Strategies to Maintain Agility Across Multiple Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/</link>
				<pubDate>Wed, 26 Feb 2025 06:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/</guid>
				<description>Scaling agile across multiple teams introduces complexity and risks slowing down delivery, so it is crucial to choose a scaling approach that fits your organisation’s unique context. Key to success are mapping dependencies, proactively addressing communication pitfalls, and maintaining speed in delivering value as you grow. Consider a tailored, hands-on strategy to preserve agility and empower your teams as you scale.</description>
			</item>
			<item>
				<title>Mastering Product Development Costs: Empower Your Team for Financial Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-costs-empower-your-team-for-financial-success/</link>
				<pubDate>Fri, 20 Dec 2024 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-costs-empower-your-team-for-financial-success/</guid>
				<description>Understanding and managing product development costs, especially people and infrastructure, is essential for financial success. Empowering teams with financial awareness helps them make better decisions, align work with value, and focus on profitable outcomes. Development managers should foster a culture where teams track costs, measure value delivered, and continuously improve processes to drive profitability and innovation.</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>How Immersive Learning Transforms Aspiring Agile Leaders</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-immersive-learning-transforms-aspiring-agile-leaders/</link>
				<pubDate>Fri, 24 Nov 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-immersive-learning-transforms-aspiring-agile-leaders/</guid>
				<description>Immersive learning experiences like the PAL-E class help aspiring agile leaders overcome common barriers by providing time, practical assignments, and peer feedback to apply and reflect on agile practices in real-world settings. Leaders gain actionable tools to empower teams, foster collaboration, and focus on value delivery rather than just process. Consider enrolling your leadership team in such a program to drive sustainable agile transformation and maximize organizational impact.</description>
			</item>
			<item>
				<title>The Power of Community: Becoming an Awesome Agile Coach</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-community-becoming-an-awesome-agile-coach/</link>
				<pubDate>Thu, 16 Nov 2023 11:00:37 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-community-becoming-an-awesome-agile-coach/</guid>
				<description>To be an effective Agile coach, it is essential to engage with a diverse community that challenges your thinking and provides honest feedback, rather than staying in a comfortable echo chamber. Growth comes from seeking out different perspectives, embracing critique, and continuously evolving your approach, which ultimately leads to delivering greater value to your teams and customers. Development managers should encourage their coaches to actively participate in varied Agile communities and prioritize learning and feedback to drive continuous improvement.</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>The Importance of Patience and Trust in Building Agile Organizations</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-patience-and-trust-in-building-agile-organizations/</link>
				<pubDate>Fri, 08 Dec 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-patience-and-trust-in-building-agile-organizations/</guid>
				<description>Building a successful Agile organization requires patience and trust, as these enable teams to experiment, learn from failures, and innovate without fear of blame. Impatience leads to a blame culture, reduced quality, and stifled creativity, while patience supports empiricism and continuous improvement. Development managers should foster a culture that values learning from mistakes, sets realistic expectations, and avoids blame to strengthen trust and drive better outcomes.</description>
			</item>
			<item>
				<title>Navigating Team Conflict: From Healthy Disagreement to Agile Harmony</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/</link>
				<pubDate>Tue, 07 Nov 2023 11:30:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/</guid>
				<description>Team conflict is normal and can drive innovation, but if disagreements escalate unchecked, they can harm team dynamics and project outcomes. Managers should watch for signs of unhealthy conflict and use open communication, objective discussions, mediation, and clear team norms to de-escalate issues early. Addressing conflict directly helps maintain productivity and keeps teams focused on delivering value together.</description>
			</item>
			<item>
				<title>Taming the Chaos: How to Align Your Agile Team for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</link>
				<pubDate>Fri, 03 Nov 2023 05:11:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</guid>
				<description>Chaos in Agile teams is usually caused by unclear goals, lack of direction, and poor communication, which leads to inefficiency and confusion. Aligning teams through clear goals, regular check-ins, open communication, and visualising progress increases motivation, collaboration, and productivity. Development managers should prioritise establishing and communicating shared objectives to reduce chaos and drive team success.</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>Scrum is made up of Influencers, Entrepreneurs, and Makers</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/scrum-is-made-up-of-influencers-entrepreneurs-and-makers/</link>
				<pubDate>Mon, 01 Mar 2021 14:02:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/scrum-is-made-up-of-influencers-entrepreneurs-and-makers/</guid>
				<description>Scrum teams need a balance of three key roles: Influencers who lead and shape the environment, Entrepreneurs who define and communicate the product vision, and Makers who build the product. Each role has its own growth path and is essential for delivering high-value products. Development managers should ensure all three tracks are present and balanced in their teams to maximize success.</description>
			</item>
			<item>
				<title>Why Cost-Cutting During Recessions Is Counterproductive</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-cost-cutting-during-recessions-is-counterproductive/</link>
				<pubDate>Thu, 04 Jul 2024 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-cost-cutting-during-recessions-is-counterproductive/</guid>
				<description>Cutting costs during a recession, especially in areas like agile coaching and training, may offer short-term savings but undermines long-term business resilience and growth. Companies that invest in efficiency, team empowerment, and continuous improvement during downturns are better positioned to outperform competitors when the market recovers. Instead of layoffs and rigid controls, focus on building a culture of learning and value creation to ensure your organization thrives through uncertainty.</description>
			</item>
			<item>
				<title>Say-Do Metrics: Avoiding Agile Banditry in Your Organization</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</link>
				<pubDate>Fri, 05 Jan 2024 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</guid>
				<description>Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change.</description>
			</item>
			<item>
				<title>Navigating Team Conflict: How Scrum Masters Can Prevent &#39;War&#39; in Agile Projects</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-how-scrum-masters-can-prevent-&#39;war&#39;-in-agile-projects/</link>
				<pubDate>Mon, 30 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-how-scrum-masters-can-prevent-&#39;war&#39;-in-agile-projects/</guid>
				<description>Team conflict can quickly escalate from healthy debate to destructive arguments that harm collaboration and project outcomes. Scrum Masters play a key role in preventing this by fostering open communication, keeping discussions focused on issues rather than individuals, and de-escalating tensions early. Development managers should watch for early signs of conflict and support Scrum Masters in maintaining a productive team environment.</description>
			</item>
			<item>
				<title>What is your feeling on creating Agile apprenticeships?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-your-feeling-on-creating-agile-apprenticeships/</link>
				<pubDate>Fri, 17 Mar 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-your-feeling-on-creating-agile-apprenticeships/</guid>
				<description>Creating Agile apprenticeships is a natural next step from immersive learning, as ongoing engagement with trainees has organically formed a community of Agile learners. Key initiatives include open invitations for informal discussions, bonus consulting time, and a mentor-apprentice model that supports continuous growth and knowledge sharing. Development managers should consider fostering similar environments to encourage ongoing learning and mentorship within their teams.</description>
			</item>
			<item>
				<title>Why is Scrum so easy to understand but incredibly hard to master?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</link>
				<pubDate>Tue, 28 Feb 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</guid>
				<description>Scrum is challenging to master because true understanding and effective implementation require deep cultural change, transparency, and alignment with agile values, not just following the framework. Many teams struggle due to legacy mindsets, lack of comprehension, and misaligned organizational structures, leading to superficial adoption and missed opportunities for value creation. Development managers should focus on fostering a culture of transparency, learning, and value-driven collaboration to realize Scrum’s full benefits.</description>
			</item>
			<item>
				<title>2023 is predicted to be a very tough year. What do you think will be needed to win and improve?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/2023-is-predicted-to-be-a-very-tough-year-what-do-you-think-will-be-needed-to-win-and-improve/</link>
				<pubDate>Mon, 13 Feb 2023 22:00:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/2023-is-predicted-to-be-a-very-tough-year-what-do-you-think-will-be-needed-to-win-and-improve/</guid>
				<description>To succeed in a challenging year, organizations must clarify their strategy, focus on both customer and employee satisfaction, and invest in effective ways of working. Key actions include strengthening product ownership, conducting thorough market analysis, and providing agile training and practice for teams. Prioritizing these areas will help maintain competitiveness and performance even in tough market conditions.</description>
			</item>
			<item>
				<title>Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</link>
				<pubDate>Fri, 07 Oct 2022 10:41:41 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</guid>
				<description>Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs.</description>
			</item>
			<item>
				<title>Overview of the &#39;scaling with portfolio Kanban&#39; course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overview-of-the-&#39;scaling-with-portfolio-kanban&#39;-course/</link>
				<pubDate>Thu, 22 Feb 2024 07:00:26 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overview-of-the-&#39;scaling-with-portfolio-kanban&#39;-course/</guid>
				<description>The &amp;ldquo;Scaling Portfolio Kanban&amp;rdquo; course helps development leaders move from team-level to organization-wide workflow management, enabling better visibility, predictability, and value delivery across multiple teams. Key outcomes include improved forecasting, data-driven decision-making, and optimized flow of high-value projects. If your current workflow lacks predictability or efficiency, consider applying these Kanban strategies to drive measurable improvement.</description>
			</item>
			<item>
				<title>What is the one thing that no Agile team can survive?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-that-no-agile-team-can-survive/</link>
				<pubDate>Tue, 17 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-that-no-agile-team-can-survive/</guid>
				<description>No Agile team can survive a culture of contempt, which arises when team input is ignored and decisions are made without their involvement, leading to low morale and poor productivity. Leaders must foster open communication, include teams in decision-making, and address disconnects to build a positive, engaged workforce. If change is not possible, individuals may need to seek healthier environments to maintain well-being and performance.</description>
			</item>
			<item>
				<title>Unlocking Agility: How Decentralisation Empowers Teams to Maximise Value in Any Organisation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-decentralisation-empowers-teams-to-maximise-value-in-any-organisation/</link>
				<pubDate>Thu, 28 Sep 2023 11:09:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-decentralisation-empowers-teams-to-maximise-value-in-any-organisation/</guid>
				<description>Decentralising decision-making empowers teams to respond faster, innovate more, and feel greater ownership, which leads to higher value delivery. Involving team members in shaping the organisation’s goals and connecting their skills to outcomes boosts engagement and collaboration. Development managers should focus on pushing responsibility to teams and fostering a shared sense of purpose to maximise results.</description>
			</item>
			<item>
				<title>How do you think Agile is evolving since its inception in 2001?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</link>
				<pubDate>Wed, 15 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</guid>
				<description>Agile has evolved since 2001, but many organizations still rely on top-down management rather than empowering teams to make decisions. The next major shift will be moving beyond just adopting frameworks like Scrum to building true agile capabilities across leadership, partners, and teams, focusing on adaptability and customer value. Development managers should revisit agile principles and work to remove barriers that prevent teams from responding quickly to change.</description>
			</item>
			<item>
				<title>Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</link>
				<pubDate>Wed, 18 Nov 2020 16:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</guid>
				<description>The 2020 update to the Scrum Guide simplifies language and reduces prescriptive rules, emphasizing that Scrum Teams are self-managing and collectively accountable for delivering value each Sprint. Key changes include clear commitments for Product Goal, Sprint Goal, and Definition of Done, as well as a focus on cross-functional teams and improved Sprint Planning. Development managers should review the new guide to align their teams with these streamlined practices.</description>
			</item>
			<item>
				<title>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>The Key to Being an Effective Agile Coach: Understanding the Team’s Context</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-key-to-being-an-effective-agile-coach-understanding-the-team-s-context/</link>
				<pubDate>Fri, 17 Nov 2023 11:00:55 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-key-to-being-an-effective-agile-coach-understanding-the-team-s-context/</guid>
				<description>Effective Agile coaching requires understanding your team&amp;rsquo;s specific work and context, not just Agile frameworks. Coaches with domain experience or those who actively learn about their team&amp;rsquo;s challenges can offer more relevant, practical advice and build trust. Development managers should ensure their coaches engage deeply with teams&amp;rsquo; day-to-day realities to maximize impact.</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>Unlocking Agile Consulting: Transform Your Organisation with Diverse Strategies and Continuous Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-consulting-transform-your-organisation-with-diverse-strategies-and-continuous-learning/</link>
				<pubDate>Sat, 17 Jun 2023 07:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-consulting-transform-your-organisation-with-diverse-strategies-and-continuous-learning/</guid>
				<description>Agile consulting helps organisations improve by offering a range of strategies beyond a single framework, focusing on real-world challenges and maximising value through better feedback and collaboration. Success depends on engaging people at all levels, understanding the current state through interviews and reports, and fostering continuous learning and internal change. Development managers should consider diverse approaches and invest in building skills and relationships to drive meaningful transformation.</description>
			</item>
			<item>
				<title>Best Scrum advice you ever received?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</link>
				<pubDate>Mon, 05 Jun 2023 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</guid>
				<description>The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team&amp;rsquo;s unique context. Flexibility and continuous improvement are more important than strict adherence to the framework, so use Scrum as a guide and modify it as needed to maximize value and innovation. Encourage your teams to experiment and iterate, focusing on what works best for your organization.</description>
			</item>
			<item>
				<title>Kanban Guide for Scrum Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</guid>
				<description>Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery.</description>
			</item>
			<item>
				<title>The Power of Immersive Learning in Scrum Training</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training/</link>
				<pubDate>Fri, 02 Feb 2024 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training/</guid>
				<description>Immersive learning in Scrum training uses shorter, interactive sessions that reduce fatigue and boost engagement, leading to better retention and collaboration compared to traditional long-format training. Key benefits include lower cognitive load, higher energy, and more meaningful participation. Development managers should break up training into focused, hands-on segments to improve learning outcomes and team performance.</description>
			</item>
			<item>
				<title>Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/</link>
				<pubDate>Mon, 20 Nov 2023 07:51:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/</guid>
				<description>Immersive Professional Scrum Master training enables deeper learning by encouraging participants to question existing practices, apply new strategies, and collaborate with peers from diverse backgrounds. This approach helps Scrum Masters tackle real-world challenges, uncover organisational barriers, and continuously improve their methods. Consider enrolling in immersive training to foster a culture of reflection and shared problem-solving within your teams.</description>
			</item>
			<item>
				<title>Does &#39;starting with why&#39; - Simon Sinek - really matter?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/does-&#39;starting-with-why&#39;-simon-sinek-really-matter/</link>
				<pubDate>Thu, 19 Oct 2023 08:22:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/does-&#39;starting-with-why&#39;-simon-sinek-really-matter/</guid>
				<description>Starting with a clear purpose is essential for Agile teams because it boosts motivation, engagement, and alignment. Focusing on intrinsic motivators like autonomy, mastery, and purpose leads to better results than relying on financial incentives. Development managers should ensure their teams understand the broader vision and regularly connect daily work to that purpose for sustained success.</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>Mastering the Art of Scaling Product Development: Why Adding More Developers Isn&#39;t the Answer</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-product-development-why-adding-more-developers-isn&#39;t-the-answer/</link>
				<pubDate>Tue, 18 Feb 2025 07:08:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-product-development-why-adding-more-developers-isn&#39;t-the-answer/</guid>
				<description>Adding more developers does not solve scaling challenges in product development; without fixing underlying system issues, it can actually slow progress. Key problems include lack of alignment, unmanaged technical debt, and slow feedback loops, which all hinder effective scaling. Focus on clarifying priorities, reducing process bottlenecks, and enabling fast, coordinated team movement before increasing headcount.</description>
			</item>
			<item>
				<title>Turning User Feedback into Actionable Work: A Guide to Maximizing Product Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/</link>
				<pubDate>Wed, 10 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/</guid>
				<description>Turning user feedback into actionable work quickly is essential for delivering real product value and staying truly agile. Teams that engage users regularly, prioritize feedback effectively, and integrate it into each Sprint see higher satisfaction and better business results. Review feedback weekly, involve stakeholders, and empower your team to act fast so your product evolves in line with user needs.</description>
			</item>
			<item>
				<title>Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/</link>
				<pubDate>Thu, 13 Jul 2023 07:41:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/</guid>
				<description>This Scrum Master training focuses on immediate real-world application, building a supportive peer community, and flexible learning to help participants address actual workplace challenges as they learn. The program’s structure allows for ongoing feedback and shared problem-solving, which boosts confidence and competence. Development managers should consider this approach to accelerate team growth and foster lasting professional networks.</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>Empowering Teams with Financial Insights: The Key to Maximising ROI and Fostering Ownership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-with-financial-insights-the-key-to-maximising-roi-and-fostering-ownership/</link>
				<pubDate>Thu, 12 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-teams-with-financial-insights-the-key-to-maximising-roi-and-fostering-ownership/</guid>
				<description>Giving your teams clear financial insights and ownership over their work leads to better decision-making and higher returns. When teams understand both the value they create and the costs involved, they align their efforts with business goals and are more motivated to improve. Start sharing financial context and encourage team-level profit and loss analysis to drive accountability and smarter product decisions.</description>
			</item>
			<item>
				<title>Manifesto for Agile Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/manifesto-for-agile-software-development/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/manifesto-for-agile-software-development/</guid>
				<description>Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement.</description>
			</item>
			<item>
				<title>Transform Your Product Development: Unleash the Power of Experimentation and Collaboration</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/</link>
				<pubDate>Sun, 11 Aug 2024 22:00:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/</guid>
				<description>This course teaches development managers how to boost user value and ROI by using experimentation, agile practices, and better collaboration with stakeholders. Key outcomes include reducing waste, speeding up time-to-market, and unlocking creative solutions by focusing on real problems. Consider applying these methods to streamline your process, make data-driven decisions, and deliver higher-impact products.</description>
			</item>
			<item>
				<title>Reasons to do an APS Course in 60 Seconds</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-an-aps-course-in-60-seconds/</link>
				<pubDate>Mon, 10 Jul 2023 14:30:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-an-aps-course-in-60-seconds/</guid>
				<description>An APS (Agile Professional Scrum) course helps teams new to Scrum get started effectively and provides experienced teams with a valuable refresher to ensure they are applying Scrum correctly. It aligns everyone on best practices and clarifies what professional Scrum should look like in your organisation. Consider enrolling your team to boost their Scrum skills and improve how you deliver software.</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>Worst agile advice you&#39;ve ever heard?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/worst-agile-advice-you&#39;ve-ever-heard/</link>
				<pubDate>Tue, 09 May 2023 09:30:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/worst-agile-advice-you&#39;ve-ever-heard/</guid>
				<description>Rigid rules like requiring everyone to stand during daily meetings go against Agile’s core values of flexibility and respect for individuals. Teams should adapt processes to fit their unique needs and prioritize inclusivity and human-centric practices. Development managers should focus on outcomes and team well-being rather than enforcing one-size-fits-all routines.</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>Agile and Scrum are often misunderstood</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</link>
				<pubDate>Sun, 04 May 2025 15:30:30 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</guid>
				<description>Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team&amp;rsquo;s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance.</description>
			</item>
			<item>
				<title>Navigating Complexity: How to Foster Agility and Innovation in Business Decision-Making</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-how-to-foster-agility-and-innovation-in-business-decision-making/</link>
				<pubDate>Thu, 03 Oct 2024 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-how-to-foster-agility-and-innovation-in-business-decision-making/</guid>
				<description>There are no universal rules for making good business decisions in complex environments, so teams must focus on adaptability, creativity, and continuous learning to stay competitive. Relying on standard tools or processes can lead to bureaucracy and stifle innovation, so regularly reassess what adds value and be ready to change approaches as needed. Encourage a culture that questions the status quo and adapts quickly to new information or challenges.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of Digital Whiteboards in Agile Collaboration</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-digital-whiteboards-in-agile-collaboration/</link>
				<pubDate>Tue, 19 Sep 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-digital-whiteboards-in-agile-collaboration/</guid>
				<description>Digital whiteboards are essential for effective team collaboration, especially in remote or hybrid agile environments, as they boost engagement, visual communication, and flexibility. Choosing the right tool, setting clear objectives, encouraging participation, and keeping sessions organised are key to maximising their value. Development managers should adopt and actively leverage digital whiteboards to enhance team alignment and productivity.</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>Navigating Client Needs: How Agile Consultants Can Uncover True Value Beyond Initial Requests</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-client-needs-how-agile-consultants-can-uncover-true-value-beyond-initial-requests/</link>
				<pubDate>Wed, 01 Mar 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-client-needs-how-agile-consultants-can-uncover-true-value-beyond-initial-requests/</guid>
				<description>Clients often think they know what they need, but the real value comes from consultants who dig deeper to uncover their true challenges and guide them toward solutions that deliver real benefits. Focusing on sustainable growth, quality over quantity, and selective project engagement helps avoid common pitfalls like overcommitment and declining standards. Development managers should look beyond surface requests and work with consultants to identify and address the root issues for lasting improvement.</description>
			</item>
			<item>
				<title>Evidence-Based Portfolio Management</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/evidence-based-portfolio-management/</link>
				<pubDate>Wed, 16 Dec 2020 13:11:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/evidence-based-portfolio-management/</guid>
				<description>Explains how evidence-based portfolio management helps organisations extend agile practices beyond teams, enabling greater responsiveness and improved business outcomes.</description>
			</item>
			<item>
				<title>Why Copying Scaled Agile Frameworks Fails in Your Business</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>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>The Fallacy of Equating Agility with Speed: What Agile Really Means</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</link>
				<pubDate>Thu, 11 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</guid>
				<description>Agile is not about working faster but about focusing on delivering the most valuable outcomes by prioritizing, experimenting, and adapting based on real customer needs. Speed alone can lead to building the wrong product, while Agile helps teams avoid wasted effort by eliminating unnecessary work and bureaucracy. Development managers should ensure their teams use Agile to maximize value, not just to increase velocity.</description>
			</item>
			<item>
				<title>My journey with Kanban and why I actively recommend it to clients</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/</link>
				<pubDate>Fri, 23 Feb 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/</guid>
				<description>Kanban is a practical strategy for improving workflow and predictability by making work processes more transparent and data-driven, which builds trust and enables better decision-making. Integrating Kanban with Scrum helps teams deliver more consistently and reduces stakeholder uncertainty. Development managers should consider adopting Kanban to optimize team performance and deliver greater value across any context.</description>
			</item>
			<item>
				<title>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>Dogma versus Empiricism in a consulting engagement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/dogma-versus-empiricism-in-a-consulting-engagement/</link>
				<pubDate>Fri, 11 Aug 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/dogma-versus-empiricism-in-a-consulting-engagement/</guid>
				<description>Rigid adherence to fixed methods limits innovation and effectiveness in consulting; instead, teams should move from strict training routines to flexible, evidence-based approaches that adapt to changing needs. Building relationships through empathy and mutual respect is key, and embracing continuous learning and empirical adaptation leads to better outcomes. Development managers should encourage adaptability and ongoing learning to stay responsive and successful.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Use vanity metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</link>
				<pubDate>Thu, 29 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</guid>
				<description>Relying on vanity metrics like story points and velocity can undermine your Kanban strategy, as they do not provide actionable insights. Instead, focus on key metrics such as work in progress, cycle time, throughput, and work item age to identify bottlenecks, optimize flow, and improve predictability. Use data from your workflow tools to drive continuous improvement and make informed decisions for better team performance.</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>Discipline versus motivation?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/discipline-versus-motivation/</link>
				<pubDate>Mon, 15 May 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/discipline-versus-motivation/</guid>
				<description>Motivation gets Agile transformations started, but discipline is what sustains progress and ensures teams stick to Scrum practices and values. Both are essential for lasting success; motivation inspires teams to begin, while discipline keeps them committed through challenges. Development managers should foster both to drive effective Agile adoption and continuous improvement.</description>
			</item>
			<item>
				<title>Why do you think the PSU course has become so popular for product development?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-the-psu-course-has-become-so-popular-for-product-development/</link>
				<pubDate>Tue, 21 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-the-psu-course-has-become-so-popular-for-product-development/</guid>
				<description>The PSU course is popular because it fills a major gap in Scrum by teaching teams how to integrate user experience and design thinking into product development, not just how to execute work. It helps teams prioritize and validate the most valuable work, ensuring they build the right products for the right users rather than just delivering features efficiently. Development managers should consider this course to improve decision-making and deliver products that truly meet customer needs.</description>
			</item>
			<item>
				<title>Getting Started with Objectives &amp; Key Results</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/getting-started-with-objectives-key-results/</link>
				<pubDate>Mon, 18 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/getting-started-with-objectives-key-results/</guid>
				<description>OKRs only work when there is a clear strategy, a culture of transparency and adaptation, empowered teams, and a focus on outcomes over output. They help connect strategy to execution but require ongoing review, learning, and refinement to be effective. Before adopting OKRs, ensure your leadership, culture, and processes support these foundations or the framework will not deliver real value.</description>
			</item>
			<item>
				<title>The FBI Sentinel project was textbook waterfall</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</link>
				<pubDate>Wed, 11 Jun 2025 15:30:44 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</guid>
				<description>The FBI&amp;rsquo;s Sentinel project failed after years and massive spending using a traditional waterfall approach, delivering nothing. Switching to a small, focused Agile team produced a working product in a year at a fraction of the cost. Consider adopting iterative methods to avoid wasted time and resources and deliver real value sooner.</description>
			</item>
			<item>
				<title>Why Is It So Important that Senior Leadership Teams are Engaged During an Agile Consulting Engagement?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-is-it-so-important-that-senior-leadership-teams-are-engaged-during-an-agile-consulting-engagement/</link>
				<pubDate>Fri, 23 Jun 2023 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-is-it-so-important-that-senior-leadership-teams-are-engaged-during-an-agile-consulting-engagement/</guid>
				<description>Active involvement from senior leadership is essential for successful Agile transformation because systemic change and faster market response require alignment and participation at all levels. Without leadership engagement, teams face barriers to adaptability and meaningful change. Development managers should ensure senior leaders are directly involved to enable organisation-wide transformation and maximise the value of Agile initiatives.</description>
			</item>
			<item>
				<title>How good is the APSPO course in helping leaders determine product direction and Why?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-good-is-the-apspo-course-in-helping-leaders-determine-product-direction-and-why/</link>
				<pubDate>Wed, 22 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-good-is-the-apspo-course-in-helping-leaders-determine-product-direction-and-why/</guid>
				<description>The APSPO course does not directly tell leaders how to set product direction, but it provides valuable tools and frameworks that help them identify gaps and strengthen their approach. It highlights six key roles for product owners, encouraging a balance between customer focus, innovation, collaboration, and decisive leadership. Leaders should use the course to broaden their skills and continuously improve their product ownership capabilities.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: Your Guide to the Professional Scrum Foundations Class and PSM I Assessment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-your-guide-to-the-professional-scrum-foundations-class-and-psm-i-assessment/</link>
				<pubDate>Thu, 28 May 2020 05:34:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-your-guide-to-the-professional-scrum-foundations-class-and-psm-i-assessment/</guid>
				<description>The Professional Scrum Foundations class offers hands-on, team-based learning to build practical Scrum skills and prepare for the PSM I assessment, with a focus on clear roles, transparency, and empirical process control. Participants who take the assessment soon after the class and use provided resources are more likely to succeed. Investing in this training can improve team collaboration and Agile adoption across your organisation.</description>
			</item>
			<item>
				<title>You can’t deliver change through memos</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</link>
				<pubDate>Sat, 31 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</guid>
				<description>Change cannot be achieved through memos or top-down mandates; real progress happens when everyone is trained together and understands the reasons behind new approaches. Broad-based training helps people identify problems and suggest improvements, making change more effective and sustainable. To drive meaningful change, involve all stakeholders in learning and improvement, not just managers or specialists.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>Unlocking the Power of Assumptions in Product Development: Why the PPDV Course is a Game-Changer</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-assumptions-in-product-development-why-the-ppdv-course-is-a-game-changer/</link>
				<pubDate>Fri, 09 Aug 2024 05:27:35 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-assumptions-in-product-development-why-the-ppdv-course-is-a-game-changer/</guid>
				<description>The PPDV course helps product teams avoid the common pitfall of building features without understanding real user needs by teaching them to identify and challenge assumptions throughout the product development process. It emphasizes a cycle of discovery, delivery, and validation, encouraging evidence-based decisions and continuous learning. Development managers should consider this course to shift their teams from a feature factory mindset to one focused on delivering real value.</description>
			</item>
			<item>
				<title>No successful company thrives by copying others’ ways of working</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/no-successful-company-thrives-by-copying-others-ways-of-working/</link>
				<pubDate>Sat, 26 Apr 2025 15:30:29 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/no-successful-company-thrives-by-copying-others-ways-of-working/</guid>
				<description>Successful companies do not achieve success by copying others’ processes; instead, they create ways of working tailored to their unique challenges, culture, and customers. Relying on packaged frameworks like SAFe or the Spotify Model can hinder genuine growth and adaptation. Development managers should focus on designing and evolving their own approaches to scaling rather than outsourcing this critical work to external models.</description>
			</item>
			<item>
				<title>How to Achieve Predictability in Business through Agile Principles</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/</link>
				<pubDate>Tue, 08 Oct 2024 10:33:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/</guid>
				<description>Predictability in software development is achieved by aligning teams around clear goals, optimizing systems, and adopting Agile principles that balance planning with adaptability. Key insights include the importance of well-defined processes, empowering teams to make decisions, and tailoring Agile frameworks to fit your unique business needs, as seen in Microsoft’s transformation. To improve predictability, focus on continuous improvement, effective communication, and collaboration both within teams and with customers.</description>
			</item>
			<item>
				<title>Unlocking Organisational Agility: How to Empower Your Team for Rapid Market Response</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-organisational-agility-how-to-empower-your-team-for-rapid-market-response/</link>
				<pubDate>Fri, 01 Sep 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-organisational-agility-how-to-empower-your-team-for-rapid-market-response/</guid>
				<description>Organisational agility is about enabling your teams to respond quickly to market changes by empowering those closest to the customer to make decisions and reducing communication bottlenecks. Focusing on speed, clear context, and ownership helps capture opportunities faster than competitors. Review your decision-making processes and give teams the information and authority they need to act swiftly.</description>
			</item>
			<item>
				<title>In high competition markets, how does scrum product development help acquire and retain customers?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</link>
				<pubDate>Mon, 13 Feb 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</guid>
				<description>Scrum does not directly acquire or retain customers, but it helps teams deliver value quickly and adapt based on customer feedback, which can lead to competitive advantage. Its main strengths are making problems and opportunities visible, enabling rapid execution, and supporting a culture of innovation, but leaders and teams must still identify what customers need and how to deliver it. To succeed, focus on building strong teams, understanding market value, and using Scrum to consistently deliver and validate valuable features.</description>
			</item>
			<item>
				<title>Why are recessions a great time for organizations to evaluate the opportunity of agile?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</link>
				<pubDate>Thu, 09 Feb 2023 07:15:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</guid>
				<description>Recessions are an ideal time for organizations to consider agile because uncertainty highlights the need to adapt quickly, focus on customer value, and empower teams to make decisions. Agile enables rapid learning, continuous improvement, and faster response to market changes compared to traditional management. Development managers should pilot agile practices in small, iterative cycles to test their impact and build on what works.</description>
			</item>
			<item>
				<title>Why does Agile focus on values and principles rather than a prescribed set of steps?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-does-agile-focus-on-values-and-principles-rather-than-a-prescribed-set-of-steps/</link>
				<pubDate>Mon, 23 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-does-agile-focus-on-values-and-principles-rather-than-a-prescribed-set-of-steps/</guid>
				<description>Agile focuses on values and principles instead of fixed steps because software development is complex work with unpredictable challenges, so no set process can guarantee success. Teams must adapt, experiment, and continuously learn, using values like commitment, courage, focus, openness, and respect as guides. Development managers should foster a culture that supports flexibility and ongoing improvement rather than relying on rigid procedures.</description>
			</item>
			<item>
				<title>How do you make a good Forecast?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</link>
				<pubDate>Mon, 09 Sep 2019 11:20:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</guid>
				<description>To make better forecasts in agile projects, shift from using metrics like story points and velocity to flow-based metrics such as cycle time, throughput, and work in process, which improve predictability by encouraging smaller, more manageable work items. For budgeting and staffing, calculate team costs per sprint and extrapolate for annual needs, moving from project-based to team-based budgeting. Involve stakeholders early in this transition to address concerns and ensure smoother adoption.</description>
			</item>
			<item>
				<title>How do you incorporate a Design Sprint in Scrum?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</link>
				<pubDate>Fri, 16 Aug 2019 12:35:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</guid>
				<description>Design Sprints should not be treated as separate or special sprints in Scrum; instead, design and UX work should be integrated into regular sprints as part of the team&amp;rsquo;s ongoing activities or handled during backlog refinement for future work. All team members should collaborate on these tasks, leveraging individual skills without creating silos or specialist-only phases. Development managers should ensure design activities are visible, collaborative, and aligned with sprint goals, using communities of practice to share knowledge across teams.</description>
			</item>
			<item>
				<title>US Department of Defence and the History of Waterfall Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/</link>
				<pubDate>Sun, 08 Jun 2025 15:30:25 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/</guid>
				<description>The US Department of Defence has moved away from traditional waterfall delivery and now requires lean-agile approaches in its procurement rules, recognizing that agility is essential for complex, high-stakes projects. This shift is now mandated, not just recommended, showing that even large, regulated organizations can make the change. Development managers should reconsider stage-gate processes and focus on enabling real agility rather than clinging to outdated controls.</description>
			</item>
			<item>
				<title>What are 3 key takeaways for a scrum team after attending an APS immersive learning experience course?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-are-3-key-takeaways-for-a-scrum-team-after-attending-an-aps-immersive-learning-experience-course/</link>
				<pubDate>Mon, 14 Aug 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-are-3-key-takeaways-for-a-scrum-team-after-attending-an-aps-immersive-learning-experience-course/</guid>
				<description>The APS immersive course helps Scrum teams deeply understand core principles, apply them to real-world challenges, and distinguish essential Scrum practices from unnecessary add-ons. It provides practical, actionable insights for overcoming early implementation hurdles. Teams are encouraged to revisit and refine their Scrum approach for greater effectiveness.</description>
			</item>
			<item>
				<title>Transforming Training: How Immersive Learning and DevOps Drive Real Value in Organisations</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-training-how-immersive-learning-and-devops-drive-real-value-in-organisations/</link>
				<pubDate>Thu, 16 Mar 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-training-how-immersive-learning-and-devops-drive-real-value-in-organisations/</guid>
				<description>Shifting to immersive, hands-on training and spreading sessions over a longer period leads to better knowledge retention and practical application for teams, even if it means fewer classes and less immediate revenue. Prioritising value creation over short-term gains results in more satisfied clients and stronger organisational outcomes. Development managers should consider adopting training approaches that focus on real learning impact rather than volume.</description>
			</item>
			<item>
				<title>How is agile product development different to waterfall project management?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-is-agile-product-development-different-to-waterfall-project-management/</link>
				<pubDate>Wed, 11 Jan 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-is-agile-product-development-different-to-waterfall-project-management/</guid>
				<description>Agile product development differs from traditional waterfall project management by empowering teams to make decisions, delivering value in small, frequent increments, and adapting quickly to customer feedback and market changes. Waterfall relies on upfront planning and command-and-control management, which can lead to wasted effort if requirements shift, while agile focuses on collaboration, continuous improvement, and prioritizing the most valuable work. For complex or innovative projects, consider shifting toward agile practices to reduce risk and better meet evolving customer needs.</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 more needs to happen before traditional organisations consider Agile?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-more-needs-to-happen-before-traditional-organisations-consider-agile/</link>
				<pubDate>Thu, 06 Jul 2023 07:08:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-more-needs-to-happen-before-traditional-organisations-consider-agile/</guid>
				<description>Traditional organisations must go beyond surface-level Agile adoption and commit to deep cultural change if they want to stay competitive, attract top talent, and respond quickly to market shifts. True Agile transformation requires honest readiness assessment, willingness to dismantle old structures, and embracing the discomfort of change. Leaders should act now to drive genuine, organisation-wide agility or risk falling behind more adaptive competitors.</description>
			</item>
			<item>
				<title>How does a Scrum team estimate what can be delivered in a Sprint?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-estimate-what-can-be-delivered-in-a-sprint/</link>
				<pubDate>Thu, 01 Jun 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-estimate-what-can-be-delivered-in-a-sprint/</guid>
				<description>Scrum teams do not precisely estimate what can be delivered in a Sprint; instead, they focus on understanding the size and complexity of backlog items to make informed guesses. This approach acknowledges the unpredictability of creative work and the high level of uncertainty in software development. Managers should allow flexibility in Sprint goals and use estimation tools to foster shared understanding rather than to set rigid deadlines.</description>
			</item>
			<item>
				<title>Would you recommend the APS course to a newbie scrum team, and Why?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/would-you-recommend-the-aps-course-to-a-newbie-scrum-team-and-why/</link>
				<pubDate>Thu, 23 Mar 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/would-you-recommend-the-aps-course-to-a-newbie-scrum-team-and-why/</guid>
				<description>The APS course is highly recommended for new Scrum teams because it simplifies Scrum concepts, helps teams identify and address necessary organizational changes, and empowers both team members and leaders to drive improvements. Key benefits include creating an actionable Organizational Change Backlog and fostering team engagement and alignment. Development managers should consider enrolling their teams to ensure a strong start with Scrum and ongoing alignment with agile principles.</description>
			</item>
			<item>
				<title>OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/okr-guide/</link>
				<pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/guides/okr-guide/</guid>
				<description>Comprehensive guide to using OKRs for shared focus, measurable outcomes, and strategic learning, including roles, events, best practices, and common pitfalls.</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>In WIP, less is more.  Why?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/</link>
				<pubDate>Tue, 09 May 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/</guid>
				<description>Limiting work in progress leads to higher productivity because multitasking and context switching reduce efficiency and slow down progress. Keeping tasks small and focusing on finishing before starting new work helps teams deliver more in less time. Development managers should encourage teams to reduce simultaneous tasks and prioritize completing work to improve outcomes.</description>
			</item>
			<item>
				<title>How can companies derive greater benefits from training by investing in a private training course?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-can-companies-derive-greater-benefits-from-training-by-investing-in-a-private-training-course/</link>
				<pubDate>Fri, 05 May 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-can-companies-derive-greater-benefits-from-training-by-investing-in-a-private-training-course/</guid>
				<description>Private training courses offer companies a safe environment for open discussion, enabling teams to address real challenges and discover untapped capabilities within their organisation. These sessions foster candid conversations and provoke valuable insights that often lead to meaningful change. Development managers should consider private training to unlock deeper team engagement and drive more effective Agile and DevOps adoption.</description>
			</item>
			<item>
				<title>What are some big red flags when hiring an agile consultant?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-are-some-big-red-flags-when-hiring-an-agile-consultant/</link>
				<pubDate>Wed, 25 Jan 2023 07:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-are-some-big-red-flags-when-hiring-an-agile-consultant/</guid>
				<description>When hiring an agile consultant, watch out for those who are not active in the agile community, lack deep understanding of core agile concepts, or come from consultancies that prioritize volume over quality and expertise. These red flags suggest the consultant may not be able to adapt to your team&amp;rsquo;s needs or deliver meaningful results. Take time to assess their community involvement, knowledge, and the consultancy&amp;rsquo;s focus before making a decision.</description>
			</item>
			<item>
				<title>Product Goal is an Intermediate Strategic Goal</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/product-goal-is-an-intermediate-strategic-goal/</link>
				<pubDate>Mon, 21 Dec 2020 14:27:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/product-goal-is-an-intermediate-strategic-goal/</guid>
				<description>Product Goals serve as intermediate steps that help teams evaluate and adapt progress toward broader strategic objectives, especially in uncertain environments. Focusing on outcomes over outputs, investing in discovery through flexible team allocation, and running hypothesis-driven experiments are key to delivering real value. Development managers should shift away from traditional project management and factory-style practices, adopting a data-driven, experimental approach to stay competitive and responsive.</description>
			</item>
			<item>
				<title>Before You Call Yourself an Agile Coach: The Importance of Real Experience</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/</link>
				<pubDate>Mon, 13 Nov 2023 11:00:29 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/</guid>
				<description>To be an effective Agile coach, you need real hands-on experience working with teams to build products, not just theoretical knowledge. Practical involvement helps you understand team dynamics, earn credibility, and offer advice that resonates with teams. If you aspire to coach, seek opportunities to join or volunteer with Agile teams so you can build the trust and insight needed to guide others successfully.</description>
			</item>
			<item>
				<title>What would be an example of a great agile consulting outcome for a client?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-would-be-an-example-of-a-great-agile-consulting-outcome-for-a-client/</link>
				<pubDate>Thu, 26 Jan 2023 07:00:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-would-be-an-example-of-a-great-agile-consulting-outcome-for-a-client/</guid>
				<description>A great agile consulting outcome is helping an organization become consistently adaptable to both unexpected opportunities and threats by removing barriers to responsiveness and fostering a culture of flexibility and decentralized decision-making. Key results include shifting from rigid, top-down management to empowered, autonomous teams and building resilience throughout the organization, not just in isolated groups. Development managers should focus on enabling this mindset and structure across all levels to achieve lasting agility and improved business results.</description>
			</item>
			<item>
				<title>Unlocking Agile Mastery: How the Minecraft Case Study Transforms Training and Team Dynamics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-how-the-minecraft-case-study-transforms-training-and-team-dynamics/</link>
				<pubDate>Tue, 29 Aug 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-how-the-minecraft-case-study-transforms-training-and-team-dynamics/</guid>
				<description>The Minecraft case study developed by Simon offers an engaging and practical way for teams to experience Agile concepts, closely mirroring real project challenges and improving team collaboration. Participants report higher engagement, better understanding of complexity, and stronger teamwork compared to traditional training. Development managers should consider innovative, interactive training methods like this to boost Agile adoption and team effectiveness.</description>
			</item>
			<item>
				<title>Momentum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/momentum/</link>
				<pubDate>Tue, 16 May 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/momentum/</guid>
				<description>Momentum in product delivery means not just moving quickly but ensuring everyone is aligned and moving in the same direction, which is essential for achieving shared goals. Teams with strong momentum can inspire and pull others along, making a real difference between stagnation and progress. To build and sustain this momentum, consider investing in Agile and Scrum training or coaching to foster collaboration and continuous improvement.</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>Transform Your Product Development: Unlock User Value, Reduce Waste, and Enhance Collaboration with Structured Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unlock-user-value-reduce-waste-and-enhance-collaboration-with-structured-learning/</link>
				<pubDate>Tue, 27 Aug 2024 07:07:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unlock-user-value-reduce-waste-and-enhance-collaboration-with-structured-learning/</guid>
				<description>A structured learning course in product development can help your teams better understand user needs through experimentation, reduce waste by making evidence-based decisions, and improve collaboration with stakeholders using data-driven discussions. The course also encourages creative problem-solving and provides practical tools you can apply immediately. Consider investing in this training to boost user value, efficiency, and team alignment.</description>
			</item>
			<item>
				<title>The Importance of Batch to Optimise Flow</title>
				<link>https://engineering-leadership.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/</guid>
				<description>Explains how breaking large tasks into smaller batches improves workflow, predictability, and delivery speed, using hands-on exercises based on queuing theory principles.</description>
			</item>
			<item>
				<title>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</link>
				<pubDate>Thu, 15 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</guid>
				<description>Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions.</description>
			</item>
			<item>
				<title>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>When should an organisation consider a professional agile consultant?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/when-should-an-organisation-consider-a-professional-agile-consultant/</link>
				<pubDate>Tue, 28 Mar 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/when-should-an-organisation-consider-a-professional-agile-consultant/</guid>
				<description>Organisations should consider a professional agile consultant when facing significant project failure or when seeking continuous improvement, as an external expert can provide valuable perspective and help identify opportunities for change. It is important to avoid being swayed by consultants who lack real agile expertise and instead choose someone with proven experience. Whether recovering from setbacks or aiming to enhance performance, bringing in the right agile consultant can help teams evolve and deliver better results.</description>
			</item>
			<item>
				<title>Introducing Kanban for Professional Scrum Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</link>
				<pubDate>Mon, 26 Feb 2018 15:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</guid>
				<description>A new Professional Scrum with Kanban class and guide now enable Scrum teams to integrate Kanban practices like workflow visualization, limiting work in progress, and flow-based metrics without changing Scrum itself. This approach helps teams focus on value delivery and can replace traditional metrics like velocity with more actionable measures such as throughput and cycle time. Development managers should consider reviewing the Kanban Guide for Scrum Teams and exploring the training to enhance their teams&amp;rsquo; effectiveness.</description>
			</item>
			<item>
				<title>Customer Working Agreement</title>
				<link>https://engineering-leadership.hinshelwood.com/workshops/customer-working-agreement/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/workshops/customer-working-agreement/</guid>
				<description>Defines a collaborative workshop to create a Statement of Work and clarify customer and provider responsibilities, agility level, and key commitments for project success.</description>
			</item>
			<item>
				<title>Unlocking Agile Mastery: Why Spaced Learning Outshines Traditional Courses</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-why-spaced-learning-outshines-traditional-courses/</link>
				<pubDate>Thu, 13 Jul 2023 07:45:48 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-why-spaced-learning-outshines-traditional-courses/</guid>
				<description>Spaced learning, where Agile and Scrum training is spread over several weeks, leads to better retention, real-world application, and ongoing support compared to traditional short courses. Participants can practice and apply concepts in their actual work, get guidance as challenges arise, and benefit from peer collaboration. Development managers should consider longer, cohort-based training formats to achieve more lasting and practical results for their teams.</description>
			</item>
			<item>
				<title>Essential Skills Every Agile Consultant Needs: Mastering Domain Knowledge, Active Listening, and Honest Communication</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/essential-skills-every-agile-consultant-needs-mastering-domain-knowledge-active-listening-and-honest-communication/</link>
				<pubDate>Fri, 14 Apr 2023 07:00:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/essential-skills-every-agile-consultant-needs-mastering-domain-knowledge-active-listening-and-honest-communication/</guid>
				<description>Agile consultants are most effective when they understand the business domain, actively listen to all team members to uncover gaps in transparency, and communicate difficult truths honestly, even to leadership. These skills help build trust and drive meaningful change. Development managers should ensure consultants are empowered to ask tough questions and share candid feedback to improve team performance.</description>
			</item>
			<item>
				<title>What is the most common Aha moment people have in a scrum course?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</link>
				<pubDate>Fri, 03 Mar 2023 07:15:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/</guid>
				<description>The most common realization in scrum courses is understanding the deep purpose behind each element of the scrum framework, especially its foundation in empiricism, rather than just following procedures. Many experienced practitioners discover they have been missing the true value of scrum by not connecting its events and artefacts to their intended outcomes. To unlock high performance, teams should focus on mastering the fundamentals and intentionally applying scrum’s principles, not just its mechanics.</description>
			</item>
			<item>
				<title>Scaling Smart: How to Build Sustainable Growth Without the Chaos</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-build-sustainable-growth-without-the-chaos/</link>
				<pubDate>Wed, 19 Feb 2025 07:25:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-build-sustainable-growth-without-the-chaos/</guid>
				<description>Scaling should focus on building sustainable value, not just growing quickly, and simply adopting frameworks without addressing underlying issues will only make problems worse. Effective scaling requires understanding constraints, simplifying processes, and ensuring teams are aligned to deliver value. Before scaling, assess whether your approach will truly improve outcomes and use agile methods to enable smarter, not just faster, growth.</description>
			</item>
			<item>
				<title>Transforming Training: The Power of Immersive Learning in Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</link>
				<pubDate>Wed, 08 May 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</guid>
				<description>Traditional two-day Scrum training is ineffective for lasting change because participants retain little and struggle to apply what they learn. Immersive learning, with shorter sessions spread over time, hands-on assignments, and ongoing feedback, leads to better retention, practical application, and continuous improvement. Development managers should consider adopting immersive training formats to drive real, sustainable transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>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>What Does a Poor Product Backlog Look Like?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-does-a-poor-product-backlog-look-like/</link>
				<pubDate>Mon, 19 Jun 2023 13:01:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-does-a-poor-product-backlog-look-like/</guid>
				<description>A poor product backlog is disorganised, lacks clear priorities, and confuses both teams and stakeholders. A strong backlog is clearly ordered and understood by everyone, aligning team efforts with business goals. Review your backlog regularly to ensure clarity and shared understanding across your team.</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>What is the most interesting outcome you have achieved as an agile consultant?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-interesting-outcome-you-have-achieved-as-an-agile-consultant/</link>
				<pubDate>Mon, 20 Mar 2023 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-interesting-outcome-you-have-achieved-as-an-agile-consultant/</guid>
				<description>The most interesting outcome as an agile consultant was seeing how full company-wide commitment to agile, from leadership to frontline staff, led to lasting transformation and improved ownership at Backcountry, while lack of buy-in at another company caused agile efforts to fail and key advocates to leave. Key insights are that success depends on broad engagement and leadership support, and that agile can create a ripple effect across organizations. Development managers should ensure all levels of the company are involved and committed to agile practices for meaningful and sustainable change.</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>Overview of &#39;applying metrics for predictability&#39; Kanban course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</link>
				<pubDate>Tue, 20 Feb 2024 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</guid>
				<description>The &amp;ldquo;Applying Metrics for Predictability&amp;rdquo; Kanban course teaches teams how to use key Kanban metrics and probabilistic forecasting to improve delivery predictability, enabling more accurate planning and increased stakeholder trust. Participants learn to interpret data, identify bottlenecks, and make informed decisions that drive efficiency and consistent value delivery. Development managers whose teams struggle with predictability should consider this course to enhance forecasting and workflow reliability.</description>
			</item>
			<item>
				<title>In Scrum, we don’t do UX separately</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</link>
				<pubDate>Thu, 12 Jun 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</guid>
				<description>UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed.</description>
			</item>
			<item>
				<title>The false claim that Scrum is immutable</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/</link>
				<pubDate>Tue, 25 Jun 2024 11:37:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/</guid>
				<description>Scrum is meant to be flexible and adaptable, not rigid, despite some claims that it is &amp;ldquo;immutable.&amp;rdquo; The Scrum Guide&amp;rsquo;s reference to immutability applies to its definition, not to how teams must implement it, so teams can adapt Scrum as needed as long as they are transparent about changes. Development managers should focus on delivering value, getting feedback, adapting plans, and reflecting regularly rather than debating strict adherence to the Scrum Guide.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Key to Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-key-to-agile-success/</link>
				<pubDate>Fri, 26 Jan 2024 07:00:25 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-key-to-agile-success/</guid>
				<description>Focusing only on agile frameworks does not guarantee business success; organizations need to use evidence-based management to track real business outcomes and adapt based on data. Successful companies transform their leadership, processes, and decision-making using key metrics like current value, unrealized value, ability to innovate, and time to market. Development managers should prioritize data-driven decisions and organizational adaptability over simply following agile practices.</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>Navigating My Most Memorable Challenge as an Agile Consultant: Lessons in Readiness and Engagement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-my-most-memorable-challenge-as-an-agile-consultant-lessons-in-readiness-and-engagement/</link>
				<pubDate>Tue, 04 Apr 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-my-most-memorable-challenge-as-an-agile-consultant-lessons-in-readiness-and-engagement/</guid>
				<description>Organisations must be ready and willing to engage for agile consulting to be effective; without this, even the best advice will be ignored and no real progress will happen. Repeated experiences showed that lack of readiness and follow-through leads to wasted effort and stagnation. Development managers should ensure their teams are prepared to listen and act before bringing in external help.</description>
			</item>
			<item>
				<title>Unlocking the Superpower of Software Development: How Shifting Left Transforms Quality Assurance</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</link>
				<pubDate>Fri, 22 Nov 2024 14:04:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</guid>
				<description>Shifting quality assurance to the start of the development process leads to higher product quality, faster delivery, and lower costs by catching issues early and fostering better collaboration. Teams that adopt this approach see improved morale and stakeholder confidence. To get started, educate your team, involve QA early, encourage collaboration, use automation, and focus on continuous improvement.</description>
			</item>
			<item>
				<title>The Definition of Done: Ensuring Quality without Compromising Value</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</link>
				<pubDate>Wed, 27 Sep 2023 09:59:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</guid>
				<description>The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team&amp;rsquo;s delivery.</description>
			</item>
			<item>
				<title>Transform Your Agile Training: The Power of Immersive Learning for Lasting Impact</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transform-your-agile-training-the-power-of-immersive-learning-for-lasting-impact/</link>
				<pubDate>Thu, 08 Jun 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transform-your-agile-training-the-power-of-immersive-learning-for-lasting-impact/</guid>
				<description>Immersive learning in Agile training connects theory directly to participants&amp;rsquo; real work, leading to better retention and practical application compared to traditional classroom methods. Spreading sessions over time, using real assignments, and fostering peer feedback help teams apply new concepts and drive meaningful change in their organizations. Consider adopting this approach to make Agile training more relevant and impactful for your teams.</description>
			</item>
			<item>
				<title>Why do you think that 4 half days is a better format than 2 full days?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-that-4-half-days-is-a-better-format-than-2-full-days/</link>
				<pubDate>Fri, 10 Mar 2023 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-that-4-half-days-is-a-better-format-than-2-full-days/</guid>
				<description>Spreading training over four half days instead of two full days leads to better knowledge retention, more opportunities for reflection, and improved practical application. This approach reduces cognitive overload and supports continuous learning and improvement. Consider adopting or experimenting with more flexible training formats to maximize learning outcomes for your teams.</description>
			</item>
			<item>
				<title>How effective is scrum training via digital delivery?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-effective-is-scrum-training-via-digital-delivery/</link>
				<pubDate>Tue, 31 Jan 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-effective-is-scrum-training-via-digital-delivery/</guid>
				<description>While in-person Scrum training offers slightly more engagement and interaction, digital delivery is nearly as effective and brings unique advantages such as greater accessibility, exposure to global perspectives, and alignment with how remote teams now work. Online courses allow immediate application of learning, foster diverse collaboration, and introduce valuable digital tools. Development managers should consider digital training as a practical, effective option that fits modern team dynamics and broadens participation.</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>Scrum Master versus seasoned Agile Coach?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-master-versus-seasoned-agile-coach/</link>
				<pubDate>Tue, 27 Jun 2023 11:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-master-versus-seasoned-agile-coach/</guid>
				<description>A Scrum Master and a seasoned Agile Coach both support Agile practices, but an Agile Coach brings deeper knowledge and extensive experience across multiple frameworks like Scrum, Lean, and Kanban. Agile Coaches have a proven track record of guiding organizations through complex challenges and embedding Agile at a deeper level. If your goal is to drive significant Agile transformation and long-term success, consider engaging a seasoned Agile Coach.</description>
			</item>
			<item>
				<title>Navigating Agile Learning: Embrace Change and Community in Uncertain Times</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-agile-learning-embrace-change-and-community-in-uncertain-times/</link>
				<pubDate>Wed, 01 Apr 2020 16:26:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-agile-learning-embrace-change-and-community-in-uncertain-times/</guid>
				<description>Adapting to remote work and uncertainty, agile learning now emphasizes flexibility in teaching, flow management to help teams handle remote challenges, and gamified tools for better engagement. Building a strong, interactive community and gathering feedback are key to effective virtual learning. Managers should support team adaptability and encourage participation in collaborative, skill-building opportunities.</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>What is a product backlog?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-backlog/</link>
				<pubDate>Thu, 18 May 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-backlog/</guid>
				<description>A product backlog is a prioritized list of features or improvements that guides the development team and fosters collaboration. It should be flexible, clearly understood by everyone involved, and regularly pruned to stay lean and effective. Development managers should ensure their teams maintain a focused and well-understood backlog to maximize productivity and alignment.</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>How to Choose the Right Agile Coach for Your Business Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-choose-the-right-agile-coach-for-your-business-success/</link>
				<pubDate>Fri, 24 Nov 2023 11:00:52 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-choose-the-right-agile-coach-for-your-business-success/</guid>
				<description>To get the most value from Agile coaching, choose someone who is adaptable, experienced across multiple frameworks, and committed to continuous learning rather than a coach who only uses one method. A versatile coach will tailor their approach to your team&amp;rsquo;s unique needs and challenges, leading to better outcomes. When hiring, ask about their experience with different industries and how they customize solutions so you get guidance that truly fits your business.</description>
			</item>
			<item>
				<title>How will the immersive learning experience help coach people on the job?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-help-coach-people-on-the-job/</link>
				<pubDate>Tue, 08 Aug 2023 07:00:22 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-help-coach-people-on-the-job/</guid>
				<description>Immersive learning spreads Agile training over several weeks, allowing participants to apply lessons directly to their work and receive valuable feedback in each session. This approach leads to deeper understanding, practical skill development, and stronger collaboration among team members. Development managers should consider immersive learning to foster real-world growth and continuous improvement within their teams.</description>
			</item>
			<item>
				<title>Rethinking the Statement of Work: How to Truly Meet Client Needs Beyond the Contract</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-the-statement-of-work-how-to-truly-meet-client-needs-beyond-the-contract/</link>
				<pubDate>Thu, 22 Jun 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-the-statement-of-work-how-to-truly-meet-client-needs-beyond-the-contract/</guid>
				<description>Focusing strictly on the statement of work often fails to address clients&amp;rsquo; real problems, leading to temporary fixes and dissatisfaction. Building trust, adapting to actual needs, and prioritising value over rigid contract terms result in better outcomes and lasting change. Development managers should emphasise relationships and flexibility to deliver solutions that truly matter to clients.</description>
			</item>
			<item>
				<title>What is Scrum?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-scrum/</link>
				<pubDate>Fri, 19 May 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-scrum/</guid>
				<description>Scrum is a framework that helps teams organize around shared goals and is especially effective for tackling complex, unpredictable work where you learn as you go. It is designed to help teams navigate tasks that are novel or constantly changing, making it ideal for software development environments. Consider exploring Scrum further to boost your team&amp;rsquo;s productivity and adaptability.</description>
			</item>
			<item>
				<title>The market isn’t slowing down for anyone</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-market-isn-t-slowing-down-for-anyone/</link>
				<pubDate>Wed, 16 Apr 2025 15:30:49 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-market-isn-t-slowing-down-for-anyone/</guid>
				<description>Success in today&amp;rsquo;s market depends on how quickly your organization can respond and adapt, not on which framework you use. Relying on old control methods with superficial agile practices slows you down and puts you at risk of falling behind. To stay competitive, focus on building a truly responsive system that enables fast, smart decisions and real adaptability.</description>
			</item>
			<item>
				<title>3 core practices of Kanban. Actively managing work items in a workflow</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</link>
				<pubDate>Mon, 26 Feb 2024 14:06:47 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</guid>
				<description>Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow.</description>
			</item>
			<item>
				<title>Czym różni się zwinne przywództwo od tradycyjnego zarządzania</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/czym-r%C3%B3%C5%BCni-si%C4%99-zwinne-przyw%C3%B3dztwo-od-tradycyjnego-zarz%C4%85dzania/</link>
				<pubDate>Wed, 09 Aug 2023 14:59:44 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/czym-r%C3%B3%C5%BCni-si%C4%99-zwinne-przyw%C3%B3dztwo-od-tradycyjnego-zarz%C4%85dzania/</guid>
				<description>Agile leadership differs from traditional management by focusing on building creative, collaborative, and high-performing teams that drive better customer experiences. Empowering and inspiring teams leads to continuous improvement and stronger results. Consider agile training or coaching to help your teams evolve and perform at their best.</description>
			</item>
			<item>
				<title>FBI Launched Outdated Criminal Records System in 1995</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/</link>
				<pubDate>Fri, 06 Jun 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/</guid>
				<description>The FBI launched a criminal records system in 1995 that was already outdated, and it remained in use for 15 years. Relying on big, infrequent releases means technology and user needs quickly outpace your delivery. To avoid delivering obsolete solutions, shift to frequent, incremental releases so you can keep up with changing requirements and user expectations.</description>
			</item>
			<item>
				<title>Transforming Technical Debt: Unlocking Opportunities for Innovation and Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</link>
				<pubDate>Wed, 20 Nov 2024 16:53:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</guid>
				<description>Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to accumulate slows delivery, increases maintenance costs, and lowers team morale, while proactively addressing it empowers teams, improves agility, and enhances value delivery. Make technical debt management a regular part of your workflow and educate stakeholders to unlock your team&amp;rsquo;s full potential.</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>Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team&#39;s Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</link>
				<pubDate>Mon, 08 Jan 2024 11:00:37 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</guid>
				<description>Relying on story points and velocity as performance metrics creates mistrust and pressure, undermining team collaboration and the core values of Agile. Instead, focus on objective measures like cycle time and throughput to better understand team efficiency and foster a healthier, more productive environment. Shift your metrics to support transparency and continuous improvement rather than arbitrary targets.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 2</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-2/</link>
				<pubDate>Tue, 24 Oct 2023 11:00:39 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-2/</guid>
				<description>Story points are not required by Scrum and are often misused, leading to confusion and pressure on teams. Their real value is in sparking conversations about uncertainty during backlog refinement, not as ongoing metrics or time proxies. Development managers should focus on open dialogue, use story points only as needed for understanding, and consider alternative estimation methods to better support team effectiveness and value delivery.</description>
			</item>
			<item>
				<title>Why is Lego a shit idea for a Scrum Trainer - Part 1</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-1/</link>
				<pubDate>Mon, 02 Oct 2023 11:00:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-1/</guid>
				<description>Using Lego in Scrum training can undermine the seriousness of the message, create a mismatch between the training method and professional context, and risk disengaging senior participants. The playful approach may trivialize key concepts and reduce credibility with experienced professionals. Development managers should choose training tools that align with the professional environment and reinforce the importance of cultural transformation.</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>Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</link>
				<pubDate>Wed, 21 Jun 2023 11:00:52 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</guid>
				<description>The Scrum Master is not a manager or authority figure but a servant leader who facilitates team processes, removes obstacles, and encourages autonomy. Misconceptions like expecting status updates or report writing from the Scrum Master undermine team ownership and collaboration. Development managers should empower Scrum Masters to support teams rather than control them, fostering a culture of trust and shared responsibility.</description>
			</item>
			<item>
				<title>How do you select the most valuable items for the sprint backlog?</title>
				<link>https://engineering-leadership.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>Hiring the Right Agile Coach: What You Need to Know</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/hiring-the-right-agile-coach-what-you-need-to-know/</link>
				<pubDate>Thu, 23 Nov 2023 11:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/hiring-the-right-agile-coach-what-you-need-to-know/</guid>
				<description>Hiring the right Agile coach is crucial for successful transformation, so focus on candidates with a proven track record, relevant experience in organizations similar to yours, and strong references. Look for coaches who demonstrate empathy, adaptability, and clear communication, and ensure they fit your culture and can tailor their approach to your needs. Involve key stakeholders in the selection process to maximize the chances of finding a coach who will drive lasting agility and continuous improvement.</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>Choosing a Process Template for your Team Project</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</link>
				<pubDate>Tue, 16 May 2017 10:40:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</guid>
				<description>For agile software teams using TFS or VSTS, choose the Scrum process template to minimize friction and avoid legacy constraints found in the Agile and CMMI templates. The Scrum template is lightweight, flexible, and easier to customize for your team&amp;rsquo;s needs, while the other templates enforce outdated practices and create unnecessary barriers. Start with the Scrum template and tailor it as needed to support your workflow and adoption.</description>
			</item>
			<item>
				<title>3 Core Practices of Kanban: Improving a Workflow</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</link>
				<pubDate>Wed, 28 Feb 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</guid>
				<description>Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements.</description>
			</item>
			<item>
				<title>Why Immersive Learning Keeps Scrum Students Excited and Engaged</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</link>
				<pubDate>Thu, 01 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</guid>
				<description>Immersive learning keeps Scrum students engaged by making each session a hands-on journey of discovery, allowing them to apply new concepts in real time and reflect on their experiences. Spreading content over multiple sessions helps teams assimilate knowledge, experiment safely, and continuously improve through feedback. Development managers should break training into manageable pieces, encourage experimentation, and foster regular feedback to maintain excitement and drive ongoing growth.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Pride</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/</link>
				<pubDate>Fri, 13 Oct 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/</guid>
				<description>Excessive pride in Agile can lead teams to make decisions based on assumptions or ego rather than real customer value and data. To avoid wasted effort and missed opportunities, managers should ensure decisions are data-driven, learn from failures, and focus on meaningful metrics. Foster a culture of humility and continuous learning to keep teams aligned with business goals.</description>
			</item>
			<item>
				<title>5 tools that Scrum Masters love. Part 1</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</link>
				<pubDate>Thu, 14 Sep 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</guid>
				<description>Liberating structures are a set of frameworks that help Scrum Masters run more engaging and effective meetings by matching specific techniques to clear objectives. Using these tools can boost team participation, break down communication barriers, and drive better outcomes. Consider adopting liberating structures to turn routine meetings into productive sessions that support team growth and innovation.</description>
			</item>
			<item>
				<title>1 thing you wish you knew at the start of your Scrum journey?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/1-thing-you-wish-you-knew-at-the-start-of-your-scrum-journey/</link>
				<pubDate>Fri, 04 Aug 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/1-thing-you-wish-you-knew-at-the-start-of-your-scrum-journey/</guid>
				<description>Integrating Lean principles with Scrum from the start can significantly boost team success by combining effective collaboration with data-driven insights. Many only discover the benefits of Lean years into their Scrum journey, but adopting both early leads to better outcomes and deeper understanding. Development managers should consider exploring and applying Lean alongside Scrum now rather than waiting, to maximize team performance and innovation.</description>
			</item>
			<item>
				<title>Temperance in Agile: Why Less is More</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</link>
				<pubDate>Tue, 05 Dec 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</guid>
				<description>Focusing on just enough work and keeping your backlog, planning, and team size lean helps your team deliver more value and avoid waste or burnout. Prioritize only high-impact tasks, limit work in progress, and avoid over-refining or over-planning. Say no to non-essential work, balance short-term wins with long-term goals, and seek coaching if you struggle to maintain this balance.</description>
			</item>
			<item>
				<title>5 critical Skills to master as an Agile Consultant?  Part 1</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/5-critical-skills-to-master-as-an-agile-consultant-part-1/</link>
				<pubDate>Mon, 07 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/5-critical-skills-to-master-as-an-agile-consultant-part-1/</guid>
				<description>To be effective as an Agile consultant, it is crucial to recognize that fully understanding a client&amp;rsquo;s context is rarely possible, so rely on experience, embrace trial and error, and continuously adapt your approach. Success comes from learning from setbacks, identifying universally effective strategies, and maintaining a commitment to ongoing learning. Development managers should foster a culture of experimentation and adaptability within their teams.</description>
			</item>
			<item>
				<title>Unlocking Growth: The Transformative Power of Poly Immersive Learning Experiences</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-growth-the-transformative-power-of-poly-immersive-learning-experiences/</link>
				<pubDate>Thu, 13 Jul 2023 12:20:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-growth-the-transformative-power-of-poly-immersive-learning-experiences/</guid>
				<description>Poly immersive learning experiences help teams adapt to complexity by encouraging learning from real-world feedback, fostering collaboration, and providing time for reflection. They reinforce knowledge through structured assignments and practical experiments, which build habits of continuous improvement. Development managers should integrate these approaches to drive ongoing learning and accountability within their teams.</description>
			</item>
			<item>
				<title>The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</link>
				<pubDate>Thu, 03 Jul 2025 05:22:41 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</guid>
				<description>The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together.</description>
			</item>
			<item>
				<title>Reasons to do a PSPO-A Course in 60 Seconds</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-a-pspo-a-course-in-60-seconds/</link>
				<pubDate>Tue, 11 Jul 2023 14:00:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-a-pspo-a-course-in-60-seconds/</guid>
				<description>The PSPO-A course helps product managers and product owners master Agile and Scrum principles, improving their ability to manage products efficiently and respond to change. It offers practical insights to boost collaboration, innovation, and effectiveness in product management. Consider enrolling to enhance your skills and drive better results for your team and business.</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>Too many organisations hide behind excuses:&#34;</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/</link>
				<pubDate>Sat, 07 Jun 2025 15:30:25 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/</guid>
				<description>Even large, regulated, and traditionally slow organizations like the DOD and FBI have successfully adopted iterative delivery, showing that excuses for not embracing agile are unfounded. Agile helps reduce risk, increase flexibility, and deliver value incrementally, which is especially important in regulated industries. Development managers should challenge resistance and prioritize agile practices to improve outcomes regardless of organizational constraints.</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>Unlocking Product Value: Why Real User Feedback is Your Best Asset</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-product-value-why-real-user-feedback-is-your-best-asset/</link>
				<pubDate>Fri, 07 Feb 2025 07:52:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-product-value-why-real-user-feedback-is-your-best-asset/</guid>
				<description>Product value is only proven when real users interact with your product, so early and ongoing user feedback is essential to validate assumptions and guide development. Engaging users early, testing with prototypes or MVPs, and iterating based on feedback help ensure your product meets real needs and delivers genuine value. Prioritise getting your product in front of users quickly to maximise impact and avoid wasted effort.</description>
			</item>
			<item>
				<title>The Ghosts of Agile Past: Why Burndown Charts Might Be Holding You Back</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-ghosts-of-agile-past-why-burndown-charts-might-be-holding-you-back/</link>
				<pubDate>Mon, 01 Jan 2024 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-ghosts-of-agile-past-why-burndown-charts-might-be-holding-you-back/</guid>
				<description>Burndown charts often hinder Agile teams by promoting rigid, upfront planning and fixed scopes, which do not reflect how real Agile work unfolds. Teams are more effective when they focus on delivering a steady flow of value, adapt plans as they learn, and make decisions based on actual progress rather than predictions. Consider moving away from burndown charts and instead prioritize flexibility, just-in-time planning, and empirical management to improve your team&amp;rsquo;s outcomes.</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>One thing a client can do to ensure a successful Agile consulting engagement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/one-thing-a-client-can-do-to-ensure-a-successful-agile-consulting-engagement/</link>
				<pubDate>Fri, 05 May 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/one-thing-a-client-can-do-to-ensure-a-successful-agile-consulting-engagement/</guid>
				<description>The most important thing a client can do for a successful Agile consulting engagement is to be open to being challenged and provoked to rethink their current ways of working. Allowing consultants to question established practices helps uncover hidden issues and drives meaningful change. Development managers should encourage honest dialogue and introspection to enable real improvement and agility.</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>What Does the Assessment Phase of a Consulting Engagement Look and Feel Like?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-does-the-assessment-phase-of-a-consulting-engagement-look-and-feel-like/</link>
				<pubDate>Mon, 19 Jun 2023 10:00:25 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-does-the-assessment-phase-of-a-consulting-engagement-look-and-feel-like/</guid>
				<description>The assessment phase in consulting should be minimal and flexible, with consultants continuously learning and adapting as they engage with teams rather than relying on a rigid upfront evaluation. Starting to help right away and adjusting based on real-time insights leads to better understanding and outcomes. Development managers should focus on early collaboration and ongoing adaptation instead of lengthy initial assessments.</description>
			</item>
			<item>
				<title>Unpacking Assumptions: How to Elevate Your Product Development Beyond the Feature Factory</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unpacking-assumptions-how-to-elevate-your-product-development-beyond-the-feature-factory/</link>
				<pubDate>Tue, 13 Aug 2024 07:14:40 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unpacking-assumptions-how-to-elevate-your-product-development-beyond-the-feature-factory/</guid>
				<description>Many teams focus on delivering features quickly but often overlook the assumptions behind what users truly need, leading to wasted effort and misaligned products. The PPD V course helps product teams identify and challenge these assumptions through structured discovery, experimentation, and validation, fostering better collaboration and evidence-based decisions. Consider investing in approaches that prioritise learning and user value over simply shipping features.</description>
			</item>
			<item>
				<title>The Power of Continuous Learning for Product Owners</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-continuous-learning-for-product-owners/</link>
				<pubDate>Tue, 19 Dec 2023 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-continuous-learning-for-product-owners/</guid>
				<description>Continuous learning is the most important factor for product owners to succeed, helping them make better decisions and stay ahead in a changing industry. Focus on mastering practical tools like evidence-based management, A/B testing, and OKRs, and engage with the community through reading, networking, and professional training. Prioritize learning what works best for your team rather than chasing every new trend, and invest in your ongoing development to maximize your value as a leader.</description>
			</item>
			<item>
				<title>Where is consensus valuable and where does it kill great product development?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/where-is-consensus-valuable-and-where-does-it-kill-great-product-development/</link>
				<pubDate>Mon, 25 Sep 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/where-is-consensus-valuable-and-where-does-it-kill-great-product-development/</guid>
				<description>Consensus is essential in product development but can slow progress if overused, especially in fast-moving markets where quick decisions are needed. Building trust and involving the team in decision-making helps achieve effective consensus, but leaders must know when to seek agreement and when to act decisively. Development managers should balance collaboration with timely leadership to drive successful outcomes.</description>
			</item>
			<item>
				<title>Why do you trust Russell to deliver the PSPO course for NKD Agility?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-russell-to-deliver-the-pspo-course-for-nkd-agility/</link>
				<pubDate>Thu, 24 Aug 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-russell-to-deliver-the-pspo-course-for-nkd-agility/</guid>
				<description>Russell is a highly experienced and versatile PSPO trainer whose background spans both technical and strategic aspects of product development, including work in aerospace and mentoring Product Owners. His teaching focuses on maximizing product value through practical, real-world insights and engaging, comprehensive learning experiences. Development managers looking to elevate their teams&amp;rsquo; product ownership skills should consider his course for actionable strategies and proven results.</description>
			</item>
			<item>
				<title>Harvesting Agility: What Mushroom Foraging Taught Me About Scrum and Team Dynamics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harvesting-agility-what-mushroom-foraging-taught-me-about-scrum-and-team-dynamics/</link>
				<pubDate>Thu, 10 Aug 2023 13:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harvesting-agility-what-mushroom-foraging-taught-me-about-scrum-and-team-dynamics/</guid>
				<description>Applying Agile and Scrum effectively requires understanding your team&amp;rsquo;s environment, being willing to step outside your comfort zone, and having patience for gradual improvement. Success comes from researching your context, iterating carefully, and focusing on continuous learning rather than just quick wins. Development managers should invest time in understanding team dynamics and encourage steady, mindful progress for lasting results.</description>
			</item>
			<item>
				<title>Why does project management not work in complex environments?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-does-project-management-not-work-in-complex-environments/</link>
				<pubDate>Tue, 23 May 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-does-project-management-not-work-in-complex-environments/</guid>
				<description>Traditional project management is not effective in complex environments because it relies on predictability and low variance, while complex projects involve many unknowns and frequent surprises. In these situations, traditional methods struggle to adapt and deliver results. Development managers should consider adopting Agile or Scrum approaches that are better suited to handling uncertainty and change.</description>
			</item>
			<item>
				<title>Overview of Applying Professional Kanban course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</link>
				<pubDate>Wed, 21 Feb 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</guid>
				<description>The Applying Professional Kanban course teaches how to integrate Kanban into any workflow to improve efficiency, identify bottlenecks, and drive continuous improvement using data and visualizations. Key outcomes include better workflow management, data-driven decision-making, and increased value delivery to stakeholders. Development managers should consider this course to optimize their team&amp;rsquo;s processes and deliver more value quickly.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning in Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile/</link>
				<pubDate>Sat, 03 Feb 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile/</guid>
				<description>Immersive learning helps teams internalize Agile principles by engaging them in hands-on, real-world scenarios, leading to genuine mindset shifts rather than just following rituals. This approach enables teams to connect Agile concepts to their daily challenges, adapt their behaviors based on experience, and achieve more effective Agile transformations. To maximize impact, create safe spaces for experimentation, use relevant scenarios, and allow time for reflection.</description>
			</item>
			<item>
				<title>Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</link>
				<pubDate>Wed, 23 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</guid>
				<description>Kanban can be applied to any workflow to provide visibility into how work moves through your system, enabling teams to optimise delivery speed and manage capacity effectively. By using data analysis and probabilistic forecasting, such as Monte Carlo simulations, you can set realistic expectations with stakeholders and make more informed decisions. Consider adopting Kanban to improve transparency, predictability, and continuous improvement in your development processes.</description>
			</item>
			<item>
				<title>8-Week Immersive Learning Course in 60 Seconds</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/8-week-immersive-learning-course-in-60-seconds/</link>
				<pubDate>Mon, 05 Jun 2023 11:00:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/8-week-immersive-learning-course-in-60-seconds/</guid>
				<description>Scrum.org’s 8-week immersive learning courses combine theory with hands-on practice, blending classroom and offline work to help participants apply new skills directly in their organizations. Learners benefit from practical assignments, collaborative feedback, and a structure designed to drive real change. Consider enrolling to quickly gain actionable strategies and improve your team’s Agile performance.</description>
			</item>
			<item>
				<title>Is a Product Owner an Agile Project Manager?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/is-a-product-owner-an-agile-project-manager/</link>
				<pubDate>Thu, 25 May 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/is-a-product-owner-an-agile-project-manager/</guid>
				<description>A Product Owner is not an Agile Project Manager; the Product Owner focuses on delivering product value, while an Agile Project Manager is concerned with project success. These roles have different objectives and responsibilities, and their priorities may not always align. Development managers should ensure clear role definitions to avoid confusion and maximize both product and project outcomes.</description>
			</item>
			<item>
				<title>Rethinking Budgeting: How to Break Free from Traditional Constraints and Maximise Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-budgeting-how-to-break-free-from-traditional-constraints-and-maximise-value/</link>
				<pubDate>Mon, 09 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-budgeting-how-to-break-free-from-traditional-constraints-and-maximise-value/</guid>
				<description>Traditional annual budgeting creates rigidity, discourages innovation, and often leads to missed opportunities and wasted resources. Adopting a more flexible, value-driven approach like Beyond Budgeting allows teams to allocate funds dynamically, respond quickly to changing needs, and focus on delivering real value. Development managers should consider shifting to iterative funding models to maximise impact and avoid costly missed opportunities.</description>
			</item>
			<item>
				<title>Mastering Kanban: A Simple Guide to Its Core Principles</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</link>
				<pubDate>Mon, 01 Jul 2024 07:00:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</guid>
				<description>Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency.</description>
			</item>
			<item>
				<title>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>Understanding the Power of Kanban in Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</link>
				<pubDate>Mon, 05 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</guid>
				<description>Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery.</description>
			</item>
			<item>
				<title>Understanding Kanban: A Tool for Transparency and Continuous Improvement</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</link>
				<pubDate>Mon, 24 Jun 2024 06:48:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</guid>
				<description>Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements.</description>
			</item>
			<item>
				<title>Why Validate Your Advanced Product Ownership Skills with a PSPO-A</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-validate-your-advanced-product-ownership-skills-with-a-pspo-a/</link>
				<pubDate>Thu, 08 Jun 2023 11:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-validate-your-advanced-product-ownership-skills-with-a-pspo-a/</guid>
				<description>Validating your skills with a PSPO-A demonstrates advanced product ownership abilities that go beyond the basics, positioning you as a visionary leader who can bridge departments and drive product success. Advanced Product Owners act like mini-CEOs, integrating business, strategy, and Agile leadership to deliver greater value. Consider pursuing the PSPO-A to elevate your impact and lead innovation within your organization.</description>
			</item>
			<item>
				<title>Navigating the Unknown: How to Fund Your Product Like a Venture Capitalist</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-unknown-how-to-fund-your-product-like-a-venture-capitalist/</link>
				<pubDate>Tue, 10 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-unknown-how-to-fund-your-product-like-a-venture-capitalist/</guid>
				<description>Treat product funding like a venture capitalist by running small, low-risk experiments to validate ideas before committing significant resources. Require clear business plans, proof of concept, and ongoing iteration based on real user feedback to manage risk and maximize learning. Balance data-driven decisions with vision and passion, and be prepared to discard failed experiments while investing further in those that show promise.</description>
			</item>
			<item>
				<title>The Power of Charity in Agile: How Helping Others Elevates Teams and Organizations</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-charity-in-agile-how-helping-others-elevates-teams-and-organizations/</link>
				<pubDate>Wed, 06 Dec 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-charity-in-agile-how-helping-others-elevates-teams-and-organizations/</guid>
				<description>Charity, or helping others without expecting anything in return, is a key driver of Agile team and organizational success because it builds trust, collaboration, and a shared sense of purpose. Encouraging this behavior leads to higher motivation, better product quality, and long-term growth. Development managers should actively foster a culture of giving and collective achievement to unlock these benefits.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Envy</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-envy/</link>
				<pubDate>Mon, 09 Oct 2023 11:17:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-envy/</guid>
				<description>Avoid copying Agile models like Spotify without considering your team&amp;rsquo;s unique context, as imitation and trend-driven decisions often lead to poor results. Instead, focus on adapting practices to fit your specific needs, encourage creativity and autonomy, and foster a positive, customer-focused culture. Assess new tools and methods carefully before adopting them to ensure they truly benefit your organization.</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>1 thing that sinks a consulting engagement before it starts gaining traction?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/1-thing-that-sinks-a-consulting-engagement-before-it-starts-gaining-traction/</link>
				<pubDate>Sat, 19 Aug 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/1-thing-that-sinks-a-consulting-engagement-before-it-starts-gaining-traction/</guid>
				<description>Overly detailed contracts that specify exact deliverables, timelines, and costs can undermine consulting engagements because they do not account for the unpredictable nature of software development. Focusing on outcomes and the value delivered, rather than rigid outputs, leads to better results. Development managers should prioritize flexibility in contracts to adapt to changing requirements and ensure project success.</description>
			</item>
			<item>
				<title>Hiring a Product Owner? Avoid copying job specs from the internet</title>
				<link>https://engineering-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>Why Limiting Work in Progress is Key to Success in Kanban</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</link>
				<pubDate>Mon, 22 Jul 2024 06:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</guid>
				<description>Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable.</description>
			</item>
			<item>
				<title>Mastering the Agile Balance: Navigating Flexibility and Inflexibility for Project Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-the-agile-balance-navigating-flexibility-and-inflexibility-for-project-success/</link>
				<pubDate>Thu, 19 Sep 2024 11:05:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-the-agile-balance-navigating-flexibility-and-inflexibility-for-project-success/</guid>
				<description>Balancing flexibility and structure in agile is key to project success; while agile enables teams to adapt quickly and reallocate resources as needed, it can also create challenges with data quality and decision-making. Clear goals and regular context evaluation help teams decide when to be flexible or structured. Development managers should focus on aligning team adjustments with business objectives and ensure data integrity to support informed decisions.</description>
			</item>
			<item>
				<title>Unlocking the Power of Caman: Why It’s the Perfect Companion to Scrum for Process Optimisation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/</link>
				<pubDate>Tue, 13 Aug 2024 07:04:49 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/</guid>
				<description>Caman is a strategy that complements Scrum by increasing transparency and providing deeper insights into workflows, helping teams identify bottlenecks and optimise processes. It is universally applicable across different systems and industries, not just software development. Development managers should use Caman alongside Scrum by mapping processes, involving teams in discussions, and iterating improvements to enhance value delivery.</description>
			</item>
			<item>
				<title>Znaczenie znajomości terenu</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/znaczenie-znajomo%C5%9Bci-terenu/</link>
				<pubDate>Thu, 10 Aug 2023 14:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/znaczenie-znajomo%C5%9Bci-terenu/</guid>
				<description>Understanding your environment, much like knowing the terrain when foraging for mushrooms, is crucial for agile teams to adapt and succeed. Fostering a creative and collaborative workforce leads to better customer experiences and continuous improvement. Consider investing in agile training or coaching to help your teams perform at their best.</description>
			</item>
			<item>
				<title>Do you think we are on the slope of enlightenment in Gartner&#39;s Hype Cycle?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/do-you-think-we-are-on-the-slope-of-enlightenment-in-gartner&#39;s-hype-cycle/</link>
				<pubDate>Fri, 07 Jul 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/do-you-think-we-are-on-the-slope-of-enlightenment-in-gartner&#39;s-hype-cycle/</guid>
				<description>Most organizations are still struggling with Agile due to unrealistic expectations and a focus on process over people, but a growing number are starting to see real benefits by prioritizing human interactions and learning from successful pioneers. The shift toward true Agile maturity is underway, though widespread enlightenment has not yet been reached. Development managers should focus on setting realistic goals, fostering a people-first culture, and learning from those who have achieved genuine Agile success.</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>The Importance of Product Backlog Management in Today&#39;s Agile Landscape</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today&#39;s-agile-landscape/</link>
				<pubDate>Fri, 01 Dec 2023 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today&#39;s-agile-landscape/</guid>
				<description>Effective product backlog management is essential for team focus, stakeholder alignment, and delivering real value, yet many organizations neglect it, leading to confusion and wasted effort. Key issues include oversized or outdated backlogs, lack of regular refinement, insufficient detail, and poor stakeholder involvement. To improve, keep the backlog lean, refine it regularly with the whole team, ensure transparency and clarity, and use data to guide priorities; making this a priority will boost team performance and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>What has the initial response been to the immersive learning experiences, how do you see that evolving?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-has-the-initial-response-been-to-the-immersive-learning-experiences-how-do-you-see-that-evolving/</link>
				<pubDate>Mon, 28 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-has-the-initial-response-been-to-the-immersive-learning-experiences-how-do-you-see-that-evolving/</guid>
				<description>Immersive learning is quickly replacing traditional two-day workshops, with businesses reporting better knowledge retention, higher engagement, and greater return on investment as employees apply new skills in real time. This approach uses ongoing sessions, real-time collaboration, and continuous feedback, allowing for tailored and incremental development. Development managers should consider adopting immersive learning formats to foster deeper skill growth and more sustainable professional development within their teams.</description>
			</item>
			<item>
				<title>You don’t own your market</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/you-don-t-own-your-market/</link>
				<pubDate>Fri, 18 Apr 2025 15:30:32 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/you-don-t-own-your-market/</guid>
				<description>Your customers control the market, not you, so failing to listen or respond quickly means losing them to competitors. Many organizations prioritize internal views over real customer needs, leading to late product launches and missed opportunities. To stay relevant, focus on genuine customer feedback and ensure your teams are closely connected to those you serve.</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>The Power of Peer Feedback in Immersive Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/</link>
				<pubDate>Wed, 07 Feb 2024 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/</guid>
				<description>Peer feedback in immersive learning accelerates skill development by enabling participants to apply Scrum techniques in real situations, share experiences, and collaboratively solve problems. Facilitated debriefs deepen understanding and build a shared knowledge base, leading to better retention and real-world results. Encourage your teams to actively engage in peer feedback during training to drive continuous improvement and more effective Scrum adoption.</description>
			</item>
			<item>
				<title>Unlocking Startup Success: Why Every Entrepreneur Needs to Master Product Management Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-startup-success-why-every-entrepreneur-needs-to-master-product-management-value/</link>
				<pubDate>Tue, 16 May 2023 14:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-startup-success-why-every-entrepreneur-needs-to-master-product-management-value/</guid>
				<description>Mastering product management value is critical for startup success, as it helps ensure you deliver what customers truly need and avoid common causes of failure. Key actions include focusing on value, communicating a clear vision, using practical tools, and regularly engaging with your team and customers to adapt based on feedback. Investing in product management training like the PSPO course can strengthen your foundation and support long-term growth.</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>One limitation of reading a book vs attending a course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/one-limitation-of-reading-a-book-vs-attending-a-course/</link>
				<pubDate>Mon, 08 May 2023 09:30:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/one-limitation-of-reading-a-book-vs-attending-a-course/</guid>
				<description>Reading books provides valuable knowledge, but they cannot answer your questions or offer interactive discussions like a course can. Courses enable active engagement, idea exchange, and collaborative learning, which are essential for deeper understanding and team growth. Consider supplementing reading with interactive training to maximize learning and team performance.</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>2-day PSPO Versus 8-week PSPO</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/2-day-pspo-versus-8-week-pspo/</link>
				<pubDate>Wed, 07 Jun 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/2-day-pspo-versus-8-week-pspo/</guid>
				<description>Both the 2-day and 8-week Product Owner courses provide the same core knowledge, practical insights, and a recognized credential, but differ in pace and depth. The 2-day option offers fast, focused learning, while the 8-week course allows for deeper integration with real work and ongoing feedback. Choose the format that best fits your team&amp;rsquo;s learning style and how you want to apply new skills on the job.</description>
			</item>
			<item>
				<title>What is a Sprint Backlog?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-backlog/</link>
				<pubDate>Mon, 29 May 2023 12:01:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-backlog/</guid>
				<description>The Sprint Backlog is a combination of the Sprint Goal, selected tasks, and a clear plan for achieving them, providing transparency on current work and progress. It should balance goal-driven work with essential tasks like bug fixes, remain flexible to adapt to new needs during the Sprint, and set teams up for achievable success. Development managers should ensure Sprint Goals are realistic and use the Sprint Backlog to maintain focus while staying adaptable.</description>
			</item>
			<item>
				<title>Mastering Assumptions: Unlocking Success in Product Development Through Hypothesis-Driven Strategies</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-assumptions-unlocking-success-in-product-development-through-hypothesis-driven-strategies/</link>
				<pubDate>Tue, 20 Aug 2024 07:06:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-assumptions-unlocking-success-in-product-development-through-hypothesis-driven-strategies/</guid>
				<description>Success in product development depends on identifying, prioritising, and validating assumptions through structured hypotheses and targeted experiments. Focusing on the most critical assumptions, using data-driven testing, and avoiding attachment to unproven ideas leads to better decision-making and outcomes. Development managers should foster a culture of learning and adaptability by encouraging teams to challenge assumptions and iterate based on evidence.</description>
			</item>
			<item>
				<title>Unlocking User Insights: The Key to Meaningful Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-user-insights-the-key-to-meaningful-software-development/</link>
				<pubDate>Fri, 09 Aug 2024 05:39:57 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-user-insights-the-key-to-meaningful-software-development/</guid>
				<description>To deliver real value, development managers need to go beyond what users say and use data to understand their true needs, avoid copying competitors without clear alignment to user goals, and foster strong collaboration with stakeholders. Focus on evidence-based decisions and ongoing engagement to ensure your team builds solutions that genuinely matter. Make it a priority to regularly question assumptions and validate user needs with data and stakeholder input.</description>
			</item>
			<item>
				<title>Mastering Your Kanban Board: A Practical Guide to Visualising Workflows for Maximum Efficiency</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/</link>
				<pubDate>Mon, 08 Jul 2024 06:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/</guid>
				<description>A clear and accurate Kanban board is essential for understanding and improving your team&amp;rsquo;s workflow. Map your actual process, adjust columns to reflect real work stages, and use visual cues to highlight priorities and bottlenecks. Regularly review and adapt your board to boost team collaboration, identify issues early, and drive continuous improvement.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning in Agile: Overcoming Cognitive Bias</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</link>
				<pubDate>Mon, 05 Feb 2024 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</guid>
				<description>Immersive learning is essential for Agile teams because it exposes knowledge gaps and helps overcome overconfidence, leading to real skill growth. By focusing on hands-on practice, continuous feedback, and regular reflection, teams can drive ongoing improvement and avoid common pitfalls. Development managers should encourage immersive, practical learning environments to ensure their teams keep evolving and truly master Agile principles.</description>
			</item>
			<item>
				<title>A view into the PSM Training from Scrum.org</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/a-view-into-the-psm-training-from-scrum-org/</link>
				<pubDate>Sat, 24 Jul 2021 07:58:47 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/a-view-into-the-psm-training-from-scrum-org/</guid>
				<description>The Scrum.org PSM training provides a practical overview of Scrum principles and how to apply them effectively in real projects. Key insights include the importance of understanding Scrum roles, events, and artifacts, and how to foster team collaboration for better outcomes. Development managers should consider this training to help their teams adopt Scrum practices more successfully.</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>How will the Immersive Learning experience change the game for people with a couple of years experience in the field?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-change-the-game-for-people-with-a-couple-of-years-experience-in-the-field/</link>
				<pubDate>Tue, 01 Aug 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-change-the-game-for-people-with-a-couple-of-years-experience-in-the-field/</guid>
				<description>Immersive learning helps experienced Agile practitioners deepen their expertise by connecting real-world challenges with advanced theory and practical assignments, leading to more meaningful breakthroughs. It leverages their existing knowledge, encourages nuanced questions, and tailors learning to specific needs. Development managers should consider immersive learning to accelerate team growth and address complex, real-world problems more effectively.</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>Agile at Microsoft</title>
				<link>https://engineering-leadership.hinshelwood.com/podcasts/agile-at-microsoft/</link>
				<pubDate>Thu, 25 Apr 2024 08:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/podcasts/agile-at-microsoft/</guid>
				<description>The podcast highlights the critical role of clear and precise language in Agile environments, emphasizing that transparency and accuracy in communication directly impact team effectiveness. Hosts Simon Reindl and Martin Hinshelwood share practical insights on how word choice shapes understanding and outcomes. Development managers should ensure their teams use language carefully to avoid misunderstandings and improve collaboration.</description>
			</item>
			<item>
				<title>Empowering Users: Transforming Products from Burdens to Essential Tools</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-users-transforming-products-from-burdens-to-essential-tools/</link>
				<pubDate>Mon, 11 Dec 2023 11:00:47 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-users-transforming-products-from-burdens-to-essential-tools/</guid>
				<description>Products succeed when users see them as empowering tools rather than burdens, which requires empathy, clear communication of value, and proactive support. Open feedback channels and acting on user input help build trust and drive continuous improvement. Development managers should prioritize user relationships and feedback loops to ensure products are seen as essential and beneficial.</description>
			</item>
			<item>
				<title>Unlocking Success: How Lean Product Development Transforms Decision-Making and Value Creation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-lean-product-development-transforms-decision-making-and-value-creation/</link>
				<pubDate>Thu, 28 Sep 2023 08:29:48 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-lean-product-development-transforms-decision-making-and-value-creation/</guid>
				<description>Lean product development is gaining traction because it helps teams make better decisions, reduce risk, and create more value with fewer resources. Adopting this mindset enables organisations to focus on building products that truly meet customer needs and avoid wasted effort. Development managers should consider exploring lean practices to improve product outcomes and maximise return on investment.</description>
			</item>
			<item>
				<title>What is the most valuable thing you have learned through training people?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</link>
				<pubDate>Tue, 07 Feb 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</guid>
				<description>The most valuable lesson from training people worldwide is that teams everywhere face the same core challenges when adopting agile and Scrum, regardless of culture or location. Shared experiences in training help participants realize their problems are not unique, which builds confidence and accelerates learning. Development managers should leverage global perspectives and proven Scrum practices to address common issues and drive improvement in their teams.</description>
			</item>
			<item>
				<title>Introduction to Agility’s Ghosts: Shedding Dogma and Embracing Pragmatism</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/introduction-to-agility-s-ghosts-shedding-dogma-and-embracing-pragmatism/</link>
				<pubDate>Thu, 28 Dec 2023 08:40:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/introduction-to-agility-s-ghosts-shedding-dogma-and-embracing-pragmatism/</guid>
				<description>Rigid adherence to Agile rules can harm teams and stifle progress; true agility means adapting processes to fit the team’s needs and focusing on delivering value. Flexibility and pragmatism are essential for creating inclusive, effective environments, while dogmatic approaches undermine collaboration and innovation. Development managers should prioritize outcomes and continuous improvement over strict rule-following to support team success.</description>
			</item>
			<item>
				<title>Agile Training versus Agile Consulting</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/agile-training-versus-agile-consulting/</link>
				<pubDate>Thu, 07 Sep 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/agile-training-versus-agile-consulting/</guid>
				<description>Agile training builds a shared understanding and foundational skills across teams, while Agile consulting focuses on solving specific problems with tailored solutions in a short timeframe. Both approaches are effective but serve different needs. Consider using training for broad knowledge and consulting for targeted improvements.</description>
			</item>
			<item>
				<title>Rethinking Software Estimation: Embrace Probabilistic Forecasting for Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/rethinking-software-estimation-embrace-probabilistic-forecasting-for-agile-success/</link>
				<pubDate>Thu, 05 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/rethinking-software-estimation-embrace-probabilistic-forecasting-for-agile-success/</guid>
				<description>Traditional software estimation is often inaccurate and burdens teams, so shifting to probabilistic forecasting based on historical data provides more realistic delivery predictions and reduces pressure. Breaking work into smaller pieces and aiming for high confidence levels, such as 85 percent, helps teams adapt to uncertainty and improve outcomes. Development managers should move away from precise estimates and instead use probability-based forecasts to guide planning and decision-making.</description>
			</item>
			<item>
				<title>Unlocking Success: Join Me for a Virtual Coffee to Tackle Your Agile and Technical Challenges</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-join-me-for-a-virtual-coffee-to-tackle-your-agile-and-technical-challenges/</link>
				<pubDate>Wed, 06 Dec 2023 11:01:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-join-me-for-a-virtual-coffee-to-tackle-your-agile-and-technical-challenges/</guid>
				<description>If you are facing agile or technical challenges, I am offering free virtual coffee chats to help you find practical solutions tailored to your organisation. This approach focuses on empowering teams, sharing knowledge, and creating positive impacts beyond your company. Book a session to discuss your issues and walk away with actionable ideas that support both your team&amp;rsquo;s and the wider community&amp;rsquo;s success.</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>What are immersive training courses?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-are-immersive-training-courses/</link>
				<pubDate>Wed, 15 Mar 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-are-immersive-training-courses/</guid>
				<description>Immersive training courses move beyond traditional or flipped classroom formats by having participants apply new concepts directly in their own work environments, then return to share and learn from real experiences. This approach, often spread over several weeks, leads to deeper engagement and more practical learning outcomes. Consider adopting immersive training to drive real change and knowledge retention within your teams.</description>
			</item>
			<item>
				<title>How did you come to be a preferred Scrum training supplier for Microsoft?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-did-you-come-to-be-a-preferred-scrum-training-supplier-for-microsoft/</link>
				<pubDate>Wed, 10 May 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-did-you-come-to-be-a-preferred-scrum-training-supplier-for-microsoft/</guid>
				<description>Becoming a preferred Scrum training supplier for Microsoft was achieved through long-term relationship building, deep expertise in both DevOps and Scrum, and consistently delivering value that led to strong referrals and repeat clients. Engaging directly with Microsoft’s teams and culture further strengthened credibility and visibility. Development managers should focus on building trust, developing dual-domain expertise, and maintaining ongoing client relationships to achieve similar recognition.</description>
			</item>
			<item>
				<title>Mastering Product Development: From Assumptions to Hypotheses</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-from-assumptions-to-hypotheses/</link>
				<pubDate>Sat, 10 Aug 2024 07:00:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-from-assumptions-to-hypotheses/</guid>
				<description>This course teaches development managers how to identify, prioritize, and validate assumptions in product development by turning them into testable hypotheses, focusing on data-driven decision-making rather than gut feelings. Key insights include learning to distinguish critical assumptions from trivial ones, balancing the cost and confidence of experiments, and using experiment results to guide strategy. The main takeaway is to adopt a mindset that values learning and evidence, leading to more effective and efficient product development.</description>
			</item>
			<item>
				<title>What is a product vision?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision/</link>
				<pubDate>Mon, 29 May 2023 14:00:36 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision/</guid>
				<description>A product vision gives your team clear direction by defining the long-term goal and desired outcome for your product, serving as a guiding reference beyond short-term objectives. It aligns everyone toward a shared future state and inspires both the team and stakeholders. Make sure your team understands and uses the product vision to guide decisions and maintain focus on the big picture.</description>
			</item>
			<item>
				<title>What was your best day as an Agile consultant?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-was-your-best-day-as-an-agile-consultant/</link>
				<pubDate>Mon, 27 Mar 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-was-your-best-day-as-an-agile-consultant/</guid>
				<description>A brief Agile and Scrum engagement with a Java development team led to lasting positive change, as confirmed by a team member’s email seven years later describing its ongoing impact on their team and organization. The experience showed that even short, focused workshops can be a catalyst for significant transformation. Consider investing in Agile and Scrum training to spark similar long-term improvements in your teams.</description>
			</item>
			<item>
				<title>What is Kanban?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-kanban/</link>
				<pubDate>Mon, 12 Feb 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-kanban/</guid>
				<description>Kanban is a flexible strategy for improving existing workflows by making processes visible, tracking data, and enabling continuous, incremental improvements. Key steps include documenting your current workflow, visualizing work to spot issues, and using metrics to guide changes. Start by mapping your team&amp;rsquo;s process and use the insights to drive efficiency and effectiveness.</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>Slaying the Dragons and How to Successfully Descale at Scale</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/slaying-the-dragons-and-how-to-successfully-descale-at-scale/</link>
				<pubDate>Mon, 30 Mar 2020 08:21:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/slaying-the-dragons-and-how-to-successfully-descale-at-scale/</guid>
				<description>Most organizations fail to improve software delivery because they resist real change and try to scale without embracing core agile values and principles. The few that succeed focus on small, meaningful changes rather than just scaling existing practices. To achieve true improvement at scale, prioritize genuine transformation over superficial scaling.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Lust</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-lust/</link>
				<pubDate>Thu, 12 Oct 2023 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-lust/</guid>
				<description>Agile transformation is not a quick fix or something that can be bought off the shelf; it requires genuine commitment, adaptation, and alignment with your organisation’s unique context. Many companies make the mistake of seeking instant results or copying generic models, which often leads to disappointment. Development managers should focus on building a tailored Agile journey through ongoing learning, experimentation, and a willingness to evolve.</description>
			</item>
			<item>
				<title>Empowering Employees: The Crucial Link Between Financial Awareness and Motivation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empowering-employees-the-crucial-link-between-financial-awareness-and-motivation/</link>
				<pubDate>Tue, 03 Sep 2024 03:33:58 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empowering-employees-the-crucial-link-between-financial-awareness-and-motivation/</guid>
				<description>Employees often lack awareness of the financial impact of their work, which can lead to missed opportunities and poor decisions. Promoting financial literacy and open discussions about costs helps teams make better choices, increases motivation, and drives accountability. Development managers should actively foster financial awareness to empower teams and improve business outcomes.</description>
			</item>
			<item>
				<title>Why is Lego a shit idea for a scrum trainer - Part 3</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-3/</link>
				<pubDate>Thu, 05 Oct 2023 07:00:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-3/</guid>
				<description>Lego is avoided in Scrum training because its simplicity fails to reflect the real complexity and chaos of software development, while Minecraft is sometimes used for specific scenarios to better simulate overwhelming and collaborative environments. The choice of tool should support realistic learning experiences and evoke the pressures teams actually face. Focus on selecting training tools that mirror real-world challenges rather than just simplifying concepts.</description>
			</item>
			<item>
				<title>The Importance of Evaluating Direction: Are You Heading the Right Way?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</link>
				<pubDate>Sat, 20 Jan 2024 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</guid>
				<description>Regularly evaluating your direction at every level, developer, product owner, and organization, is essential to avoid wasted effort and ensure you are building the right things for your users. Key insights include aligning work with the product vision, listening to feedback, and being willing to pivot based on data rather than sticking to outdated plans. Make time for honest retrospectives and be ready to change course when needed to achieve better outcomes.</description>
			</item>
			<item>
				<title>Why &#39;Definition of Done&#39; is Crucial for Success in Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/why-&#39;definition-of-done&#39;-is-crucial-for-success-in-scrum/</link>
				<pubDate>Tue, 14 Nov 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/why-&#39;definition-of-done&#39;-is-crucial-for-success-in-scrum/</guid>
				<description>The Definition of Done sets clear quality standards for all work, ensuring every deliverable meets your organization&amp;rsquo;s expectations regardless of the specific feature or project. It aligns teams, reduces defects, and protects your brand by making sure nothing is released before it is truly ready. Regularly review and adapt your Definition of Done with your team to maintain high quality and customer satisfaction.</description>
			</item>
			<item>
				<title>The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/</link>
				<pubDate>Tue, 17 Oct 2023 13:14:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/</guid>
				<description>The article draws parallels between the seven deadly sins of ancient Greece and common pitfalls in agile software development, highlighting issues like pride, envy, gluttony, lust, greed, sloth, and wrath as barriers to true agility. Key insights include the dangers of overconfidence, blind imitation, overloading backlogs, chasing quick fixes, prioritising short-term gains, lack of motivation, and blame culture. Development managers should regularly reflect on team behaviours, focus on genuine value delivery, and foster a culture of accountability and continuous improvement to avoid these traps.</description>
			</item>
			<item>
				<title>Rethinking &#39;User Stories&#39;: A Call for Clarity in Product Backlog Management</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/rethinking-&#39;user-stories&#39;-a-call-for-clarity-in-product-backlog-management/</link>
				<pubDate>Thu, 31 Aug 2023 13:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/rethinking-&#39;user-stories&#39;-a-call-for-clarity-in-product-backlog-management/</guid>
				<description>The author argues that using the term &amp;ldquo;User Stories&amp;rdquo; for all work items leads to confusion and unnecessary complexity, as not all tasks fit this format. Switching to a more generic term like &amp;ldquo;Product Backlog Item&amp;rdquo; allows teams to describe work more clearly and flexibly, improving communication and transparency. Development managers should consider updating their backlog terminology to better reflect the true nature of their work and support more effective product development.</description>
			</item>
			<item>
				<title>Empathy in Agile: Building Trust and Stronger Relationships for Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/</link>
				<pubDate>Tue, 12 Dec 2023 11:00:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/</guid>
				<description>Empathy, modesty, and respect are essential for building trust and strong relationships in agile teams, leadership, and with customers, leading to better collaboration and outcomes. Avoiding assumptions and seeking diverse perspectives through open questions and feedback helps prevent bias and supports continuous improvement. Development managers should prioritise empathy and active listening to create a culture where everyone feels valued and engaged.</description>
			</item>
			<item>
				<title>Agile Scotland 2023: Why does this matter to you and why should people come to the event?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/agile-scotland-2023-why-does-this-matter-to-you-and-why-should-people-come-to-the-event/</link>
				<pubDate>Wed, 28 Jun 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/agile-scotland-2023-why-does-this-matter-to-you-and-why-should-people-come-to-the-event/</guid>
				<description>Agile 2023 in Scotland is a growing event that brings together passionate Agile professionals to share knowledge, connect with thought leaders, and discuss the latest trends in Agile practices. The conference highlights the importance of community, collaboration, and continuous learning in driving innovation within the tech sector. Development managers should consider engaging with local Agile events to gain fresh insights and foster a culture of improvement in their teams.</description>
			</item>
			<item>
				<title>Many organisations are lured to SAFe by the song of the Sirens</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/many-organisations-are-lured-to-safe-by-the-song-of-the-sirens/</link>
				<pubDate>Wed, 01 Jul 2020 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/many-organisations-are-lured-to-safe-by-the-song-of-the-sirens/</guid>
				<description>Many organisations adopt SAFe hoping for quick agility but end up replacing old rigid processes with new ones, without addressing real business challenges or fostering true innovation. SAFe often reinforces bureaucracy and stifles the adaptability needed in today’s fast-changing environment. Development managers should focus on evolving their organisations for genuine business agility rather than relying on prescriptive frameworks.</description>
			</item>
			<item>
				<title>What is Taylorism and how did it influence project management?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-taylorism-and-how-did-it-influence-project-management/</link>
				<pubDate>Wed, 22 Feb 2023 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-taylorism-and-how-did-it-influence-project-management/</guid>
				<description>Taylorism established command-and-control management focused on efficiency, standardization, and strict hierarchies, which shaped traditional project management and works well for simple or repeatable tasks. However, this approach fails in complex environments where creativity, collaboration, and adaptability are needed, leading to the rise of Agile methods. Development managers should recognize where traditional project management fits and adopt Agile practices for complex, uncertain projects to stay effective.</description>
			</item>
			<item>
				<title>A Titanic Misfit: The Alpha Organization&#39;s Wasteful Endeavor in Red Markets</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/a-titanic-misfit-the-alpha-organization&#39;s-wasteful-endeavor-in-red-markets/</link>
				<pubDate>Thu, 06 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/a-titanic-misfit-the-alpha-organization&#39;s-wasteful-endeavor-in-red-markets/</guid>
				<description>Traditional hierarchical organizations that thrived in stable markets are now struggling in today’s fast-paced, innovation-driven environments, leading to wasted resources, stifled creativity, and missed customer needs. Slow decision-making and rigid structures prevent them from adapting quickly, leaving talent and opportunities untapped. Development managers should consider shifting toward more agile, decentralized models to stay competitive and reduce waste.</description>
			</item>
			<item>
				<title>Most Rewarding Part of Being a Scrum Developer?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/most-rewarding-part-of-being-a-scrum-developer/</link>
				<pubDate>Fri, 23 Jun 2023 11:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/most-rewarding-part-of-being-a-scrum-developer/</guid>
				<description>The most rewarding part of being a Scrum developer is building software that truly matters to people, which gives purpose and fuels passion for the work. When developers see their efforts making a real impact, it drives higher quality and creativity. Managers should encourage teams to focus on meaningful outcomes to boost motivation and results.</description>
			</item>
			<item>
				<title>Learn Scrum with Minecraft Education Edition</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/learn-scrum-with-minecraft-education-edition/</link>
				<pubDate>Tue, 10 Jan 2023 07:48:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/learn-scrum-with-minecraft-education-edition/</guid>
				<description>Using Minecraft Education Edition in Scrum training creates a more realistic and engaging environment for learning complex product development compared to traditional website-building exercises. This approach ensures full team participation, better simulates real-world complexity, and is accessible across devices. Development managers should ensure participants can install Minecraft Education on an unrestricted device and join sessions off VPN for the best experience.</description>
			</item>
			<item>
				<title>The Art of Negotiation for Product Owners: Essential Skills to Master</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-art-of-negotiation-for-product-owners-essential-skills-to-master/</link>
				<pubDate>Wed, 13 Dec 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-art-of-negotiation-for-product-owners-essential-skills-to-master/</guid>
				<description>Strong negotiation skills are essential for Product Owners to balance stakeholder demands, technical realities, and leadership requests, ensuring the product delivers maximum value. Key techniques include active listening, asking probing questions, and guiding others to see the bigger picture, which helps avoid unnecessary features and maintain focus. Development managers should encourage Product Owners to build these skills through training, reflection, and coaching to improve outcomes and stakeholder relationships.</description>
			</item>
			<item>
				<title>The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/</link>
				<pubDate>Thu, 07 Sep 2023 14:01:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/</guid>
				<description>The main point is that true organisational agility is about responding to market changes faster than competitors, not about adopting specific frameworks like SAFe or Scrum. Successful companies build processes tailored to their unique needs rather than copying others, and relying on outdated rules or hybrid models slows adaptation. Development managers should focus on creating flexible, custom processes that enable rapid response and continuous adaptation to stay competitive.</description>
			</item>
			<item>
				<title>What is a product vision, and why does it matter?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision-and-why-does-it-matter/</link>
				<pubDate>Wed, 17 May 2023 14:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision-and-why-does-it-matter/</guid>
				<description>A clear product vision is essential because it aligns teams, prevents chaos, and ensures everyone understands the direction and purpose of their work. Without it, efforts become fragmented and counterproductive. Development managers should prioritize creating and communicating a shared vision so teams can work cohesively toward common goals.</description>
			</item>
			<item>
				<title>Mastering the Art of Product Ownership: The Power of Marketing Your Vision</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-the-power-of-marketing-your-vision/</link>
				<pubDate>Fri, 15 Dec 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-the-power-of-marketing-your-vision/</guid>
				<description>Product Owners need to actively market their product vision to engage teams, stakeholders, and customers, not just manage backlogs. Consistent, emotionally resonant communication boosts participation in Sprint Reviews, improves feedback, and aligns everyone around shared goals. Development managers should encourage Product Owners to treat vision-sharing as an ongoing marketing effort to drive engagement and maximize product value.</description>
			</item>
			<item>
				<title>Online is the new co-located</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/online-is-the-new-co-located/</link>
				<pubDate>Mon, 16 Nov 2020 15:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/online-is-the-new-co-located/</guid>
				<description>With modern video technology and fast internet, online meetings can now provide the same level of non-verbal communication as being in the same room, so keeping cameras on is essential for team transparency and engagement. Development managers should encourage camera use during online events to maximize communication and adapt interactions, but also respect occasional needs for cameras off. If team members cannot use video reliably, consider in-person participation instead.</description>
			</item>
			<item>
				<title>Adaptive Operating Model</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/adaptive-operating-model/</link>
				<pubDate>Fri, 16 Jan 2026 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/adaptive-operating-model/</guid>
				<description>An adaptive operating model is an organisational structure designed to enable value delivery in environments characterised by uncertainty, complexity, and ongoing change. Unlike traditional models that rely on prediction, control, and centralised authority, the adaptive operating model is built around principles of learning, rapid feedback, and decentralised decision-making. Its core features include organising work around outcomes rather than tasks or projects, distributing decision rights to those closest to emerging information, embedding explicit learning loops for continuous adjustment, maintaining stable teams and roles while allowing flexible execution, and implementing governance that supports flow and transparency rather than rigid compliance. This model serves as the foundational structure for product-centric organisations and underpins specialised approaches such as product operating models and agile product operating models, which apply adaptive principles specifically to product delivery. The adaptive operating model is not a set of delivery practices, a process framework, or a superficial change initiative; rather, it fundamentally redefines how work is coordinated, how decisions are made, and how value is discovered within an organisation. Organisations adopt this model when they face rapidly evolving customer needs, technological uncertainty, high coordination costs, bottlenecks from centralised control, and when the speed of learning is more critical than adherence to plans. In such contexts, adaptability becomes essential for survival, making the adaptive operating model particularly valuable in agile, DevOps, product development, and modern organisational design, where empiricism, accountability, and the ability to respond to change are paramount.</description>
			</item>
			<item>
				<title>Predictive Operating Model</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/predictive-operating-model/</link>
				<pubDate>Mon, 24 Nov 2025 13:22:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/predictive-operating-model/</guid>
				<description>The Predictive Operating Model is a traditional framework for organizing work that originated during the industrial revolution and is grounded in scientific management principles, notably those of Frederick Taylor and Henry Ford. It is characterized by hierarchical structures, centralized planning and control, functional specialization, and a strong emphasis on efficiency, standardization, and minimizing variability. This model assumes that customer demand and market conditions are stable, work can be fully specified in advance, and performance is best improved through detailed planning, specialization, and strict adherence to procedures. It operates through mechanisms such as predictive plans, fixed scopes and resources, stage gates, and individual accountability, with success measured by output consistency, cost control, and on-time delivery. The Predictive Operating Model excels in stable, predictable environments where repeatable processes and operational excellence provide competitive advantage, enabling organizations to scale efficiently and maintain clear accountability. However, it faces significant limitations in dynamic or uncertain contexts, such as slow adaptation to change, siloed functions, long feedback loops, and limited capacity for learning or innovation. As markets and customer needs become more volatile and complex, many organizations are transitioning toward more adaptive models that emphasize flexibility, cross-functional collaboration, and iterative learning. Understanding the Predictive Operating Model is crucial for organizations aiming to evolve their operating practices, as it highlights both the strengths that can be leveraged in stable settings and the constraints that must be addressed to succeed in agile, DevOps, or product-centric environments.</description>
			</item>
			<item>
				<title>Product Operating Model</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-operating-model/</link>
				<pubDate>Mon, 24 Nov 2025 13:21:58 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-operating-model/</guid>
				<description>A product operating model is a structured framework that defines how an organization designs, delivers, and manages its products throughout their lifecycle. It typically outlines the roles, processes, governance structures, and supporting technologies required to align product strategy with execution. Originating from the need to bridge the gap between business objectives and day-to-day product development activities, a product operating model provides clarity on decision-making authority, resource allocation, and performance measurement. Such a model is valuable because it enables cross-functional collaboration, empowers product teams to make decisions, and ensures that teams can respond quickly to changing customer needs. By establishing clear guidelines and responsibilities, a product operating model helps organizations reduce inefficiencies, improve time-to-market, and deliver higher value to customers, making it a critical component of effective organizational design and product management.</description>
			</item>
			<item>
				<title>AI Product Operating Model</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/ai-product-operating-model/</link>
				<pubDate>Mon, 24 Nov 2025 13:21:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/ai-product-operating-model/</guid>
				<description>An AI Product Operating Model is an operating model that guides how organizations design, develop, deploy, and manage artificial intelligence (AI) products within their business context. As a specialization of the Adaptive Operating Model, it addresses the unique requirements and challenges of AI-powered product delivery, including data management, model lifecycle, ethical considerations, and continuous learning. It originates from the need to align AI initiatives with organizational goals, ensuring that AI solutions are integrated into existing processes, teams, and value streams rather than developed in isolation. This model outlines roles, responsibilities, workflows, governance structures, and feedback mechanisms specific to AI product development. An AI Product Operating Model provides clarity and repeatability, enabling cross-functional teams to collaborate effectively, manage risks, and deliver AI-driven value. It supports organizations in scaling AI capabilities, maintaining compliance, and adapting to rapid technological changes, thereby fostering innovation while ensuring responsible and sustainable AI adoption. Organizations may implement AI Product Operating Models using various delivery approaches, though iterative methods are generally recommended for managing AI uncertainty.</description>
			</item>
			<item>
				<title>Objective Key Results</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/objective-key-results/</link>
				<pubDate>Tue, 03 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/objective-key-results/</guid>
				<description>Objective &amp;amp; Key Results (OKR) are a structured method for translating strategic goals into measurable outcomes, enabling clarity, alignment, and accountability within teams and organizations. Originating from John Doerr&amp;rsquo;s &amp;ldquo;Measure What Matters,&amp;rdquo; this approach defines an Objective as a meaningful, directional goal, and Key Results as specific, measurable indicators of progress toward that goal. Rather than tracking tasks or individual efforts, Objective Key Results emphasize outcomes and evidence of actual progress. Their value lies in creating a transparent system that encourages teams to focus on critical priorities, align their efforts clearly, regularly inspect progress, and adapt accordingly. Properly implemented, Objective Key Results foster a culture of accountability and continuous improvement, pushing teams beyond comfort zones to achieve meaningful results. In agile, DevOps, product development, and organizational design contexts, Objective Key Results serve as a foundational practice for ensuring strategic alignment, outcome-driven decision-making, and iterative learning.</description>
			</item>
			<item>
				<title>Ethos</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/ethos/</link>
				<pubDate>Tue, 13 May 2025 10:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/ethos/</guid>
				<description>Ethos is the foundation beneath principles, practices, and strategies. It informs how we lead, how we coach, and how we build systems that endure. Without a clearly defined ethos, teams drift into rituals without results, Scrum becomes status theatre, DevOps becomes tool automation, and transformation stalls. Ethos brings coherence and conviction to how we work. It’s not a mindset. It’s a disciplined stance.</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>First Principal</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/first-principal/</link>
				<pubDate>Tue, 13 May 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/first-principal/</guid>
				<description>A First Principle is an irreducible, self-evident truth that forms the foundation of a system of thought or action. In Lean-Agile, Scrum, and DevOps contexts, first principles guide decision-making by anchoring practices, strategies, and heuristics to immutable truths. Unlike derived principles, which are context-dependent and adaptive, first principles remain stable across domains and serve as the baseline for evaluating whether a system’s design, behaviour, or outcome is valid. First principles are not suggestions ,  they are non-negotiable constraints that define the boundary of professionalism.</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>Service Level Expectation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/</link>
				<pubDate>Mon, 05 May 2025 09:46:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/</guid>
				<description>A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team&amp;rsquo;s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team&amp;rsquo;s ability to deliver reliably and respond to change.</description>
			</item>
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>Definition of Workflow</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/</guid>
				<description>The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability.</description>
			</item>
			<item>
				<title>Liberating Structures</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/liberating-structures/</link>
				<pubDate>Mon, 14 Apr 2025 14:50:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/liberating-structures/</guid>
				<description>Liberating Structures are a modular toolkit of facilitation techniques used to structure team interactions, promote equal participation, and improve collaboration. Designed as plug-and-play alternatives to conventional meeting formats, each structure provides a clear pattern for group engagement, making them easy to learn and adapt. In Agile, Lean, and DevOps contexts, they support team self-organisation by enabling rapid idea generation, shared understanding, and collective decision-making. When applied intentionally, these methods enhance team effectiveness and help build a culture of trust and psychological safety, without requiring major changes to existing workflows.</description>
			</item>
			<item>
				<title>Lead Time</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lead-time/</guid>
				<description>Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments.</description>
			</item>
			<item>
				<title>Agnostic Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agnostic-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:49:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agnostic-agile/</guid>
				<description>Agnostic Agile is a movement that advocates for a flexible and context-driven approach to agility, emphasising the importance of principles over rigid frameworks. Originating from the need for adaptability in various methodologies, it encourages teams to tailor their practices based on specific requirements rather than conforming to a single ideology. This pragmatic approach allows practitioners to integrate diverse methodologies such as Scrum, Kanban, Lean, and Extreme Programming, fostering an environment that values critical thinking and professionalism. By prioritising value delivery, Agnostic Agile equips teams to respond effectively to evolving circumstances, ensuring predictable and sustainable value generation. This adaptability is essential in today&amp;rsquo;s dynamic environments, where the capacity to pivot and innovate can significantly influence an organisation&amp;rsquo;s success. Furthermore, Agnostic Agile promotes ethical practices by avoiding brand loyalty to specific frameworks, thereby nurturing a culture of continuous improvement and learning. This mindset empowers teams to experiment and refine their processes, ultimately supporting a long-term, systemic approach to agility that enhances organisational resilience and effectiveness. As such, Agnostic Agile is a crucial concept in contemporary product development and delivery, providing valuable insights for teams striving to thrive in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Company as a Product</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/company-as-a-product/</link>
				<pubDate>Thu, 10 Apr 2025 14:47:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/company-as-a-product/</guid>
				<description>Company as a Product (CaaP) is an organisational strategy that conceptualises the entire company as a dynamic product, evolving continuously based on customer feedback and measurable outcomes. Originating from the principles of agile and product development, this approach emphasises the alignment of all organisational components, people, processes, and systems, towards delivering customer value. CaaP fosters a culture of cross-functional collaboration and experimentation, enabling teams to respond swiftly to market changes and customer needs. This strategy represents a significant shift from traditional hierarchical structures to a more fluid and responsive organisational model, encouraging leaders to view their company&amp;rsquo;s capabilities as adaptable. By promoting a mindset of continuous improvement, CaaP ensures that every aspect of the organisation is open to refinement and innovation, which is crucial for maintaining competitiveness and relevance in a rapidly changing environment. Ultimately, by treating the organisation as a product, CaaP facilitates predictable and sustainable value delivery, establishing a resilient framework that supports long-term success and adaptability.</description>
			</item>
			<item>
				<title>Open Space Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/open-space-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:45:16 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/open-space-agile/</guid>
				<description>Open Space Agile is a progressive methodology for enhancing organisational agility, rooted in the principles of Open Space Technology. Developed by Daniel Mezick and the Open Leadership Network, this approach enables self-organisation and collaborative engagement among large groups, allowing all members of an organisation to actively influence the transformation process. By creating an environment characterised by psychological safety and shared ownership, Open Space Agile promotes authentic dialogue and collective decision-making, moving away from conventional top-down management styles. This method is particularly beneficial in complex settings where adaptability is essential, as it aligns with Agile principles by encouraging practices that emerge from the actual needs of teams rather than rigid plans. Teams are empowered to set their own priorities and actions, which enhances their capacity to deliver value in a predictable and sustainable manner. Furthermore, Open Space Agile not only supports immediate collaboration but also fosters a culture of continuous improvement and innovation, making it an integral aspect of contemporary organisational design. By valuing the insights of those closest to the work, it transforms the process of change into a shared journey towards increased agility and responsiveness.</description>
			</item>
			<item>
				<title>Ability to Innovate</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/ability-to-innovate/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/ability-to-innovate/</guid>
				<description>Ability to Innovate refers to an organisation&amp;rsquo;s capacity to generate, implement, and sustain innovative solutions effectively, which is essential for delivering value in a predictable and sustainable manner. This concept is rooted in the need for organisations to adapt to changing market demands and customer needs, thereby maintaining competitiveness. It encompasses various measures, such as the frequency of experiments, innovation throughput, and learning cycles, which collectively provide insight into an organisation&amp;rsquo;s innovation capabilities. By focusing on systemic growth and adaptability rather than specific methodologies, the Ability to Innovate fosters a culture that views failure as a learning opportunity, promoting psychological safety and collaboration among teams. This cultural embedding of innovation empowers teams to explore new ideas and solutions, leading to enhanced customer satisfaction and increased business agility. The emphasis on continuous improvement and experimentation ensures that innovation becomes a sustained effort rather than a sporadic occurrence, positioning it as a fundamental aspect of modern product development and organisational design.</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>Unrealised Value</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/unrealised-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:19:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/unrealised-value/</guid>
				<description>Unrealised Value refers to the potential value that an organisation has yet to capture, highlighting opportunities for improvement and innovation. It encompasses various indicators that assess untapped possibilities, such as latent market demand or areas ripe for enhancement. By focusing on Unrealised Value, teams can identify opportunities to optimise processes, innovate products, or better meet customer needs, ultimately leading to increased competitiveness and sustainability. This concept is crucial for enabling teams to deliver value predictably and sustainably, as it promotes a proactive approach to recognising and addressing gaps in performance and capability. Systematically measuring and analysing Unrealised Value fosters a culture of continuous improvement, motivating teams to explore new ideas and solutions. This long-term focus not only enhances current operations but also positions organisations to adapt to changing market conditions and customer expectations. Understanding Unrealised Value empowers teams to make informed decisions about resource allocation, ensuring they are strategically planning for future growth and success rather than merely reacting to immediate challenges. This perspective shifts the focus from delivering current value to actively seeking and realising potential value, which is essential for thriving in today’s dynamic business landscape.</description>
			</item>
			<item>
				<title>Hybrid Agile</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/hybrid-agile/</link>
				<pubDate>Thu, 10 Apr 2025 10:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/hybrid-agile/</guid>
				<description>Hybrid Agile refers to the practice of integrating agile methodologies into existing project management frameworks, often with the aim of achieving greater flexibility while maintaining a sense of control. This approach is commonly adopted by organisations that seek to enhance their project delivery processes but frequently results in ineffective outcomes. Instead of successfully merging the advantages of agile practices with traditional governance structures, Hybrid Agile often leads to a scenario where the rigidity of conventional methods undermines the intended agility, creating a situation described as the &amp;ldquo;worst of both worlds.&amp;rdquo; This concept highlights the challenges faced by delivery teams that encounter conflicting expectations, as leadership may cling to fixed plans while reducing agile roles to mere ceremonial functions rather than fostering genuine accountability. The persistence of command-and-control mindsets, coupled with the superficial adoption of agile terminology, creates a disconnect between the intended agile principles and the actual organisational structure. As such, Hybrid Agile is not a sustainable long-term solution; it can erode trust, hinder timely feedback, and perpetuate dysfunction within teams. This analysis serves to critique ineffective hybrid implementations and underscores the necessity for coherent systems of work that prioritise true agility over tactical compromises.</description>
			</item>
			<item>
				<title>Discipline</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/discipline/</link>
				<pubDate>Thu, 10 Apr 2025 10:30:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/discipline/</guid>
				<description>A discipline is a structured and evolving field of study and practice that encompasses shared principles, codified knowledge, and established standards of professional behaviour, extending beyond mere tools or techniques. In modern work systems, disciplines such as Project Management, Systems Engineering, and Product Strategy are recognised as mature capabilities that organisations depend on to achieve consistent, high-quality outcomes. The essence of a discipline lies not only in the actions of its practitioners but also in their cognitive processes, their ability to navigate complexity, and their commitment to continuous learning and improvement. This includes the governance structures, ethical considerations, and frameworks that inform professional conduct across diverse contexts. Understanding the systemic application and maturation of a discipline is crucial, as it highlights how these fields are formed, evolve over time, and ultimately influence organisational performance at scale. This knowledge is particularly valuable in agile, DevOps, and product development environments, where adaptability and effective collaboration are essential for success.</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>Throughput</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/throughput/</link>
				<pubDate>Wed, 09 Apr 2025 14:41:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/throughput/</guid>
				<description>Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance.</description>
			</item>
			<item>
				<title>Scaling</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scaling/</link>
				<pubDate>Wed, 09 Apr 2025 13:53:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/scaling/</guid>
				<description>Scaling refers to the capacity of an organisation to effectively coordinate multiple teams in the delivery of complex products while maintaining agility. This concept originates from the need to align efforts, optimise workflow, and enhance value delivery across the enterprise. It is particularly important in the contexts of agile methodologies and DevOps, as it allows organisations to respond swiftly to market changes without compromising on quality or speed. By implementing lean principles and adaptive product structures, scaling promotes a cohesive approach to product development, enabling teams to operate autonomously while remaining aligned with broader business objectives. This alignment is crucial for maximising efficiency and minimising waste, thereby leveraging the organisation&amp;rsquo;s collective capabilities. Furthermore, scaling fosters a culture of continuous improvement, where feedback loops and collaboration are integral to the development process. By prioritising these aspects, organisations can achieve sustainable growth and deliver value consistently, enhancing their competitive advantage in a rapidly changing environment. Ultimately, scaling is not just about increasing size but about establishing a robust framework that supports innovation and responsiveness throughout the organisation.</description>
			</item>
			<item>
				<title>Capability</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/capability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/capability/</guid>
				<description>Capability refers to a persistent competence that enables teams or organisations to deliver value in a predictable, sustainable, and adaptive manner. Unlike transient tools or one-off techniques, capabilities are cultivated over time and become embedded in organisational culture and processes. They are crucial for fostering an environment where teams can effectively respond to changing demands, leveraging collective skills and knowledge to ensure value delivery aligns with strategic objectives. The development of capabilities involves a commitment to learning and collaboration, enhancing individual competencies while building cohesive team dynamics essential for high performance. As teams grow in their capabilities, they become adept at proactively identifying and addressing issues, leading to improved outcomes and reduced risk. Capabilities also facilitate alignment across various functions within an organisation, serving as a common language that bridges gaps between teams, which is particularly important in agile and DevOps environments. They are dynamic, evolving through feedback loops that inform future practices, and are actionable and measurable, allowing organisations to track progress and make informed development decisions. Ultimately, investing in capabilities enhances agility, resilience, and the ability to deliver consistent value, positioning organisations to thrive in an ever-changing landscape and enabling teams to navigate complexity and uncertainty with confidence.</description>
			</item>
			<item>
				<title>Framework</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/framework/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/framework/</guid>
				<description>A framework is a structured approach that provides guidelines, principles, and rules to facilitate process implementation while allowing flexibility in execution. Originating from methodologies like Scrum, SAFe, and ITIL, frameworks serve as foundational blueprints that organisations can adapt to their specific contexts, enabling effective team operations within a defined structure. Their importance lies in fostering predictable and sustainable value delivery by establishing a common language and shared understanding among team members, which enhances collaboration and reduces ambiguity in fast-paced environments. Frameworks support teams in navigating complex challenges, allowing them to focus on high-quality outcomes without being hindered by uncertainty. Designed for long-term systemic use, frameworks promote continuous improvement and adaptability, encouraging organisations to reflect on practices and evolve in response to technological advancements and changing customer needs. They empower teams to experiment and refine their approaches, ultimately enhancing performance and customer satisfaction. Unlike methods, which have a narrower focus, and practices, which are habitual actions, frameworks provide an overarching structure that guides the selection and application of various methods and practices in alignment with strategic objectives. Importantly, frameworks are not prescriptive; they offer a flexible structure that teams can tailor to their unique circumstances, dispelling misconceptions about rigidity and fostering an environment conducive to creativity and innovation. In summary, frameworks are vital enablers of effective collaboration, continuous improvement, and sustainable value delivery, guiding teams through the complexities of modern product development while promoting learning and growth.</description>
			</item>
			<item>
				<title>Method</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/method/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/method/</guid>
				<description>Method refers to a structured, step-by-step approach employed to achieve specific objectives within a system, distinguishing itself from frameworks that provide broader guidelines. In Agile, Lean, and DevOps environments, methods are vital for guiding teams through systematic processes that enhance collaborative work, value delivery, and continuous improvement. They are utilised to optimise workflows, manage iterative development, and measure progress effectively. For example, the Scrum method outlines a sequence of events such as Sprint Planning and Daily Scrum to facilitate work in short cycles, while the Kanban method aids in visualising workflows and limiting work in progress. Methods ensure consistency and predictability in outcomes by breaking down complex processes into manageable tasks, allowing teams to execute with precision and adapt to real-time feedback. In Lean, methods focus on eliminating waste to maximise value delivery, whereas in DevOps, practices like Continuous Integration and Continuous Delivery enable rapid and reliable software releases. It is crucial to differentiate methods from frameworks, which provide structural foundations, and practices, which are individual techniques within broader methods. By adhering to structured methods, teams can enhance efficiency, ensure alignment, and consistently deliver value, empowering them to be proactive and adaptable in problem-solving, ultimately leading to improved performance and outcomes. Methods are flexible and can be tailored to fit the unique context of a team or project, allowing for continuous refinement while maintaining a clear path toward goal achievement.</description>
			</item>
			<item>
				<title>Model</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/model/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/model/</guid>
				<description>A model is a conceptual representation that aids teams in understanding and analysing complex systems or problems by simplifying intricate dynamics into more manageable forms. This simplification enhances clarity, enabling teams to visualise relationships, processes, and outcomes, which in turn fosters effective communication and collaboration through a shared framework for discussing challenges and opportunities. Models are particularly valuable in Agile, Lean, and DevOps environments, where rapid change and adaptability are essential. They serve as foundational tools for decision-making and systems thinking, distinguishing themselves from frameworks or methodologies by focusing on the underlying dynamics rather than structured approaches. For example, the Cynefin Framework assists teams in identifying problem complexity, while the Three Ways of DevOps model optimises software delivery through visualising flow and enabling feedback loops. By providing insight into the structural relationships that govern a system, models empower organisations to navigate complexity confidently, make informed decisions, align with organisational goals, and enhance agility and resilience. Ultimately, effective use of models allows teams to optimise their responses to challenges, ensure consistent value delivery, and drive sustainable organisational growth.</description>
			</item>
			<item>
				<title>Observability</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/observability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/observability/</guid>
				<description>Observability is the practice of gaining comprehensive insights into systems and processes, enabling teams to understand work flows and value delivery. It transcends traditional monitoring by offering a holistic view of system behaviour, which allows teams to identify patterns, diagnose issues, and make informed decisions based on real-time data. This capability is essential for fostering transparency and collaboration within teams and across organisational silos. By implementing observability, organisations can improve their ability to deliver value predictably and sustainably, supporting continuous improvement through learning and adaptation. It encompasses not only technical telemetry but also signals reflecting team dynamics, product experiences, and alignment with strategic goals, thus providing a complete view of performance that includes both human and technical factors. When integrated into daily practices, observability cultivates a feedback-rich environment that enhances decision-making and strengthens delivery capabilities. It represents a cultural shift that empowers teams to take ownership of their processes and outcomes, aligning with Lean and Agile principles focused on understanding flow and eliminating waste. By embedding observability into the organisational framework, teams can create a resilient environment that leverages data-driven insights, ultimately leading to improved products, stronger teams, and more strategic business outcomes.</description>
			</item>
			<item>
				<title>Practice</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/practice/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/practice/</guid>
				<description>Practice refers to the consistent and repeatable techniques or habits that teams employ to improve their effectiveness, collaboration, and value delivery. Originating from Agile, Lean, and DevOps methodologies, practices such as Pair Programming, Continuous Deployment, and Retrospectives are integral to fostering ongoing, systematic routines that enhance team dynamics and performance. Unlike structured methods, which provide defined steps, practices focus on the habitual actions that teams incorporate into their workflows. For instance, Pair Programming not only boosts code quality but also promotes knowledge sharing, while Retrospectives allow teams to reflect on their processes and identify areas for improvement, thus supporting continuous enhancement. Although tools like Kanban boards can facilitate these practices, the essence lies in how teams manage their workflows and adapt their routines to evolving challenges. The long-term value of practices is evident in their ability to embed behaviours that lead to predictable and sustainable outcomes, such as the frequent and reliable software releases enabled by Continuous Deployment. Ultimately, practices are crucial for effective teamwork, as they shape collaboration, drive continuous improvement, and ensure responsiveness to both internal and external demands, making them essential in the fast-paced environments characteristic of modern product development and organisational design.</description>
			</item>
			<item>
				<title>Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/strategy/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/strategy/</guid>
				<description>Strategy is a high-level approach that directs an organisation towards its long-term objectives, distinguishing itself from methods and practices that focus on execution. It serves as an overarching framework that integrates various methods, practices, and decision-making processes, ensuring that daily activities and tactical choices contribute to the organisation&amp;rsquo;s broader goals. In Agile and DevOps contexts, strategy aligns teams and technologies with business aims, exemplified by approaches like Lean Product Development, which prioritises value delivery and waste reduction. Leadership plays a crucial role in strategy by establishing vision and direction while empowering teams to operate within this framework. Strategic planning in Agile organisations incorporates evidence-based management to inform decisions and maintain alignment with customer needs and market dynamics. Unlike methods that prescribe specific procedures, strategy offers a flexible guiding framework that can adapt to changing circumstances, fostering resilience and responsiveness to both internal and external challenges. Ultimately, strategy provides clarity, focus, and adaptability, enabling organisations to navigate complexity and achieve sustained success in a dynamic environment.</description>
			</item>
			<item>
				<title>Tenet</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/tenet/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/tenet/</guid>
				<description>A tenet is a specific, actionable guiding rule or doctrine that reinforces a larger philosophy within an organisation, distinguishing itself from values and principles by providing prescriptive direction for team behaviour in specific situations. Originating from frameworks like Kanban and Agile, tenets such as &amp;ldquo;Flow efficiency over resource efficiency&amp;rdquo; and &amp;ldquo;decentralised decision-making&amp;rdquo; translate overarching philosophies into concrete actions, thereby enhancing operational efficiency and responsiveness. Their importance lies in their ability to create a consistent organisational culture, guiding decision-making and behaviour across teams while remaining stable amidst changing practices. By embedding tenets into daily operations, organisations can align actions with broader philosophical frameworks, fostering a culture of continuous improvement and learning, which is essential for sustainable success in dynamic environments. Tenets serve as the foundation for collective behaviour, ensuring that teams work cohesively towards shared goals, ultimately driving adaptability and effectiveness in product development and organisational design.</description>
			</item>
			<item>
				<title>Test First Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/test-first-development/</link>
				<pubDate>Tue, 25 Mar 2025 07:40:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/test-first-development/</guid>
				<description>Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership.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>Evidence Based Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/evidence-based-management/</link>
				<pubDate>Fri, 21 Mar 2025 14:44:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/evidence-based-management/</guid>
				<description>Evidence-Based Management (EBM) is a strategic approach designed to enhance organisational agility by providing a framework for assessing and improving value delivery. Unlike traditional frameworks or methodologies, EBM focuses on empirical data to inform decision-making, enabling organisations to move beyond superficial metrics and truly understand their performance. It centres on four critical areas: Current Value, which evaluates immediate value delivery; Time to Market, which measures responsiveness and speed; Ability to Innovate, which assesses the capacity for creating new value amidst existing challenges; and Unrealised Value, which identifies potential opportunities for growth. By utilising these metrics, leaders can make informed decisions about resource allocation and prioritisation, ultimately fostering a culture of continuous improvement. EBM is particularly valuable in the contexts of agile, DevOps, and product development, as it encourages a shift from output-focused practices to outcome-driven strategies. This empirical approach not only clarifies organisational goals but also provides the necessary feedback to adapt and evolve, ensuring that efforts are aligned with delivering real value rather than merely maintaining the status quo. In a landscape where many organisations struggle with agility, EBM offers a practical solution for those seeking to enhance their effectiveness and responsiveness in a complex and dynamic environment.</description>
			</item>
			<item>
				<title>Artifact</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/artifact/</link>
				<pubDate>Fri, 21 Mar 2025 13:59:46 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/concepts/artifact/</guid>
				<description>An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change.</description>
			</item>
			<item>
				<title>Continuous Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/</link>
				<pubDate>Fri, 21 Mar 2025 13:37:32 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/</guid>
				<description>Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations.</description>
			</item>
			<item>
				<title>Continuous Improvement</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/continuous-improvement/</guid>
				<description>Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation&amp;rsquo;s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation&amp;rsquo;s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of &amp;ldquo;Kaizen,&amp;rdquo; which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value.</description>
			</item>
			<item>
				<title>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>DevOps</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/devops/</link>
				<pubDate>Thu, 20 Mar 2025 11:04:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/devops/</guid>
				<description>DevOps is a philosophy that integrates people, processes, and technology to facilitate continuous value delivery in software development. Originating from the need to bridge the gap between development and operations, it emphasises collaboration and automation to enhance the quality and speed of software delivery. The core principles of DevOps prioritise flow efficiency over mere resource utilisation, advocate for rapid feedback loops to align with customer needs, and promote automation to minimise errors and delays. Additionally, it fosters shared accountability among developers, operations, and security teams, ensuring collective responsibility for product quality. DevOps encourages a culture of continuous improvement, where teams are committed to experimentation and adaptation. In practice, organisations embracing DevOps focus on eliminating silos, integrating quality and security measures early in the development process, leveraging data for informed decision-making, and automating as many processes as possible. This approach is crucial in agile and DevOps environments as it enables organisations to deliver software more reliably and efficiently, ultimately enhancing their ability to respond to market demands and customer expectations. DevOps is viewed not as a final goal but as an ongoing journey towards improved software delivery.</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>Internal Developer Platform</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/</link>
				<pubDate>Mon, 24 Feb 2025 13:04:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/</guid>
				<description>An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery.</description>
			</item>
			<item>
				<title>Acceptance Test Driven Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/</guid>
				<description>Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users.</description>
			</item>
			<item>
				<title>Agile Frameworks</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/</guid>
				<description>Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape.</description>
			</item>
			<item>
				<title>Agile Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-leadership/</guid>
				<description>Agile Leadership refers to the practice of guiding teams and organisations through change by creating an environment that emphasises adaptability, empowerment, and continuous improvement. Originating from agile methodologies, this leadership style moves beyond traditional management by enabling teams to self-organise, collaborate on decision-making, and swiftly respond to market changes. Its significance lies in fostering a culture that encourages experimentation and learning, which is essential for teams to innovate and deliver value consistently. Agile Leaders exemplify transparency and trust, establishing psychological safety that allows team members to express their ideas and concerns freely. They align organisational goals with team objectives, ensuring a unified focus on outcomes. By utilising frameworks like Scrum and Kanban, Agile Leaders enhance workflows, collaboration, and overall performance. This approach is not just about project management; it represents a transformation in organisational mindset, embedding agility as a fundamental value. Ultimately, Agile Leadership is a long-term commitment to cultivating a resilient organisational culture capable of adapting to change, thereby driving sustained success and value delivery in a fast-paced environment.</description>
			</item>
			<item>
				<title>Agile Philosophy</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-philosophy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-philosophy/</guid>
				<description>Agile philosophy is a mindset that emphasises flexibility, collaboration, and a focus on customer needs in the realm of product development. Originating from the desire to improve traditional project management approaches, it serves as a foundational ethos that guides teams beyond specific methodologies like Scrum or Kanban. This philosophy is vital as it promotes incremental and iterative value delivery, enabling organisations to swiftly adapt to evolving market conditions and customer feedback. By fostering a culture of continuous improvement and learning, Agile philosophy allows teams to refine their processes over time, ensuring ongoing effectiveness and relevance. It encourages cross-functional collaboration, dismantling silos and fostering shared ownership of outcomes, which enhances team dynamics and aligns organisational objectives with customer expectations. Furthermore, Agile philosophy nurtures an environment conducive to experimentation and innovation, empowering teams to make data-driven decisions that lead to superior products and services. Its emphasis on adaptability and responsiveness distinguishes Agile philosophy from other frameworks, making it an essential component in achieving organisational excellence and resilience.</description>
			</item>
			<item>
				<title>Agile Planning</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-planning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-planning/</guid>
				<description>Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development.</description>
			</item>
			<item>
				<title>Agile Planning Tools</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/</guid>
				<description>Agile Planning Tools are vital resources that support effective backlog management, forecasting, and collaboration within Agile teams. Originating from the principles of Agile methodology, these tools enable teams to visualise their work, prioritise tasks, and monitor progress in real-time, ensuring alignment and focus on delivering value. Their importance lies in enhancing predictability and sustainability in value delivery, allowing teams to make informed decisions based on empirical data, which fosters a culture of continuous improvement and adaptability in dynamic environments. By providing a structured approach to planning, Agile Planning Tools help teams anticipate challenges and respond to changing requirements, streamlining workflows and promoting a collaborative atmosphere. Unlike Agile Project Management or Agile Product Management, which target specific project execution or product lifecycle aspects, these tools form the foundational layer that underpins all Agile practices. They facilitate not just task management but also the creation of an environment conducive to team innovation and customer satisfaction through effective planning and execution. Integrating Agile Planning Tools into daily operations enhances organisational agility and resilience, ultimately leading to improved outcomes and sustained success.</description>
			</item>
			<item>
				<title>Agile Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-strategy/</guid>
				<description>Agile Strategy is a holistic framework that aligns an organisation&amp;rsquo;s vision with its operational execution and adaptability, enabling teams to consistently and sustainably deliver value. Originating from the principles of agile methodologies, this approach transcends individual practices by promoting the systemic integration of agile values throughout the organisation. It is essential for fostering an environment that encourages responsiveness to change, continuous innovation, and a strong focus on customer needs. By cultivating a culture of collaboration and transparency, Agile Strategy helps dismantle silos and enhances cross-functional teamwork. It advocates for the use of metrics and feedback loops to guide decision-making, allowing teams to adapt their strategies based on real-time insights. This level of adaptability is vital in today&amp;rsquo;s rapidly evolving market, where the capacity to pivot swiftly can significantly influence success. Furthermore, Agile Strategy is about embedding agility into the organisational culture, ensuring that it becomes a sustained capability rather than a temporary initiative. This long-term focus on aligning strategic objectives with operational execution equips organisations to navigate complexity and uncertainty more effectively, ultimately leading to improved customer satisfaction and enhanced business resilience.</description>
			</item>
			<item>
				<title>Agile Transformation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-transformation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-transformation/</guid>
				<description>Agile Transformation refers to the comprehensive process of altering an organisation&amp;rsquo;s culture, mindset, and operational practices to adopt Agile principles and methodologies. Originating from the need for more adaptive and responsive work environments, this transformation is essential for enabling teams to deliver value in a predictable and sustainable manner. By emphasising collaboration, customer feedback, and iterative development, organisations can significantly improve their capacity for innovation and responsiveness to market changes. Agile Transformation is a long-term commitment that requires systemic changes across all organisational levels, evolving processes, structures, and behaviours to foster continuous improvement and learning. It empowers teams to self-organise, make informed decisions, and take ownership of their work, which enhances motivation and performance. Unlike specific Agile Frameworks or leadership roles that focus on particular methodologies, Agile Transformation adopts a holistic approach that integrates diverse practices and principles throughout the organisation. This creates an ecosystem that supports agility, aligning every team member with the organisation&amp;rsquo;s strategic goals and values. By embedding Agile thinking into the organisational culture, companies can achieve greater resilience, improve customer satisfaction, and drive sustainable growth through a dedication to delivering high-quality products and services.</description>
			</item>
			<item>
				<title>Agile Values and Principles</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agile-values-and-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agile-values-and-principles/</guid>
				<description>Agile Values and Principles are fundamental guidelines that underpin effective Agile practices, serving as a framework for teams to consistently and sustainably deliver value. Originating from the Agile Manifesto, these values prioritise human interactions and collaboration over rigid processes and tools, fostering an environment where customer feedback and adaptability are central. Their importance lies in their ability to enable organisations to respond swiftly to change, ensuring that products remain relevant and aligned with customer needs. By promoting a culture of continuous improvement, Agile encourages teams to regularly assess their processes and outcomes, which enhances efficiency and drives innovation. This systemic approach builds organisational resilience, equipping teams to navigate the complexities and uncertainties of modern product development. By embedding these values into the organisational culture, teams gain the autonomy to self-organise and make informed decisions, maintaining a focus on high-quality outcomes. Ultimately, embracing Agile Values and Principles transcends a mere tactical adjustment; it acts as a strategic enabler that transforms operational dynamics, fostering a mindset oriented towards long-term success and value creation, thereby driving meaningful change and sustainable growth across the organisation.</description>
			</item>
			<item>
				<title>Artificial Intelligence</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/artificial-intelligence/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/artificial-intelligence/</guid>
				<description>Artificial Intelligence (AI) is the capability of machines to perform tasks that typically require human intelligence, such as learning, reasoning, and problem-solving. In organisational settings, AI enhances decision-making by providing data-driven insights, automating repetitive tasks, and fostering innovation. This is particularly important in Agile, DevOps, and modern product development, as it enables teams to respond quickly to changing market demands and customer needs. By streamlining workflows, optimising resource allocation, and improving forecasting accuracy, AI allows organisations to deliver value predictably and sustainably. Integrating AI into practices not only supports immediate project goals but also promotes a culture of continuous improvement and learning. The long-term advantages of AI include the ability to adapt to complex environments and make informed decisions based on real-time data analysis, empowering teams to concentrate on high-value activities. This ultimately leads to better products and services that align with customer expectations. Furthermore, AI plays a crucial role in enhancing collaboration and team performance, aligning with Agile and Lean methodologies, and driving organisations towards greater agility and resilience in a rapidly evolving landscape.</description>
			</item>
			<item>
				<title>Asynchronous Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/</guid>
				<description>Asynchronous Development is a collaborative approach that enables team members to work independently and at different times, rather than depending on real-time interactions. This method is particularly advantageous for distributed teams, as it accommodates diverse time zones and personal schedules, facilitating continuous progress without the limitations of synchronous communication. By utilising tools and practices that support asynchronous workflows, teams can improve their efficiency and flexibility, leading to more predictable and sustainable value delivery. This concept is vital in contemporary product development, where rapid adaptation and responsiveness are essential. Asynchronous Development creates an environment where team members can contribute insights and work at their own pace, minimising bottlenecks caused by waiting for others. It fosters a culture of ownership and accountability, encouraging individuals to take responsibility for their tasks while remaining aligned with team objectives. Additionally, this approach aligns with Lean and Agile principles, promoting continuous improvement and learning. By allowing teams to operate asynchronously, organisations can better manage complexity and enhance collaboration, ensuring consistent value delivery to customers without the friction of traditional synchronous methods. This systemic shift not only boosts productivity but also nurtures a more engaged and motivated workforce, ultimately driving long-term success and innovation.</description>
			</item>
			<item>
				<title>Automated Testing</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/automated-testing/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/automated-testing/</guid>
				<description>Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment.</description>
			</item>
			<item>
				<title>Azure Boards</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/azure-boards/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/azure-boards/</guid>
				<description>Azure Boards is an integral component of the Azure DevOps suite, specifically designed to enhance the management of Agile projects. It provides teams with tools to track work items, manage backlogs, and optimise planning through visual boards that accommodate methodologies such as Scrum and Kanban. By offering a comprehensive view of tasks, progress, and team capacity, Azure Boards promotes collaboration and communication, ensuring that all team members are aligned on priorities and deliverables. Its importance lies in fostering transparency and accountability within teams, enabling them to deliver value in a predictable and sustainable manner. The tool supports continuous improvement by allowing teams to analyse workflows, identify bottlenecks, and adapt processes based on real-time data, which streamlines project management and enhances responsiveness to changing requirements and customer feedback. Unlike other tools that may focus solely on task management, Azure Boards integrates seamlessly with other Azure DevOps services, creating a unified environment for development, testing, and deployment. This integration is vital for maintaining a consistent workflow and ensuring that all facets of product development are interconnected, ultimately leading to improved outcomes and greater organisational agility. The long-term advantages of adopting Azure Boards extend beyond immediate project needs, as it fosters a culture of continuous delivery and improvement, reinforcing the principles of Agile and Lean methodologies across the organisation.</description>
			</item>
			<item>
				<title>Azure Pipelines</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/</guid>
				<description>Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements.</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>Behaviour Driven Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/behaviour-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/behaviour-driven-development/</guid>
				<description>Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality.</description>
			</item>
			<item>
				<title>Beta Codex</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/beta-codex/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/beta-codex/</guid>
				<description>Beta Codex is a transformative framework for organisational design that promotes decentralised, adaptive, and human-centric structures, moving beyond traditional hierarchical models. Originating from the need for organisations to become more agile and responsive, this concept empowers teams to make decisions autonomously, embedding agility into the organisational culture rather than treating it as a set of practices. The significance of Beta Codex lies in its ability to enhance innovation and responsiveness to change, which are critical in today&amp;rsquo;s rapidly evolving market. By decentralising decision-making, organisations can respond more swiftly to customer needs, fostering collaboration and transparency that dismantle silos and create a unified purpose among team members. This approach cultivates resilience and adaptability, essential for success in complex environments. Furthermore, Beta Codex aligns with Lean and Agile principles, emphasising continuous value delivery and prioritising human interactions, trust, and psychological safety. By unlocking the potential of teams, organisations can achieve sustained performance and innovation, while also improving operational efficiency and fostering a culture of continuous improvement, ensuring they remain competitive and relevant in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Collaboration Tools</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/collaboration-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/collaboration-tools/</guid>
				<description>Collaboration tools are vital platforms that enhance communication and coordination among Agile teams, enabling improved effectiveness and efficiency in their workflows. Originating from the need to streamline processes in product development, these tools facilitate real-time information sharing, progress tracking, and task management, thereby reducing friction and fostering transparency. Their importance is underscored by their role in promoting a culture of continuous improvement and learning, as they provide a shared space for feedback and discussion essential for iterative development and innovation. Regular engagement through these tools strengthens team relationships and cultivates a sense of shared purpose, which in turn boosts overall performance. Furthermore, collaboration tools are integral to the systemic nature of Agile practices, aligning with Lean and DevOps principles by minimising waste and allowing teams to concentrate on delivering high-quality products. By embedding these tools into their workflows, organisations can foster an environment that supports agility and responsiveness, ensuring that teams are well-prepared to adapt to changing customer needs and market dynamics, ultimately driving sustained value creation.</description>
			</item>
			<item>
				<title>Continuous Integration</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/continuous-integration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/continuous-integration/</guid>
				<description>Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development.</description>
			</item>
			<item>
				<title>Continuous Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/continuous-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/continuous-learning/</guid>
				<description>Continuous Learning is the practice of nurturing a growth mindset and facilitating knowledge sharing within teams to achieve ongoing improvement. Originating from the need to adapt to rapidly changing environments, this concept underscores the significance of learning from both successes and failures to enhance skills, processes, and products. It is crucial in agile and DevOps contexts, as it enables teams to respond swiftly to challenges, ensuring consistent and sustainable value delivery. By embedding continuous learning into an organisation&amp;rsquo;s culture, teams become more resilient and innovative, fostering an environment that encourages experimentation and reflection. This approach not only refines practices and boosts performance but also integrates insights from diverse sources to inform strategic decision-making. Unlike Continuous Improvement, which focuses on incremental changes, Continuous Learning adopts a broader perspective, enhancing individual competencies and strengthening team dynamics. It promotes active knowledge sharing, leading to collective intelligence that drives superior outcomes. Continuous Learning is a long-term commitment rather than a one-off initiative, essential for organisations to remain competitive and relevant in a fast-evolving landscape. By prioritising this practice, organisations can cultivate a culture of excellence that enhances value delivery and customer satisfaction across all operations.</description>
			</item>
			<item>
				<title>Cross Functional Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/</guid>
				<description>Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise.</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>Customer Retention</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-retention/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/customer-retention/</guid>
				<description>Customer retention encompasses the strategies and practices that organisations implement to maintain user engagement with their products or services over time, thereby minimising customer churn. This concept is vital as it significantly influences an organisation&amp;rsquo;s sustainability and profitability. By prioritising customer retention, teams can consistently deliver value, fostering loyalty and encouraging repeat business. Effective retention strategies often incorporate continuous feedback loops, enabling teams to adapt and enhance their offerings based on user needs and preferences, which aligns with Agile principles that emphasise responsiveness to change and customer collaboration. Retaining customers not only stabilises revenue but also lowers the costs associated with acquiring new customers, making it a more efficient growth strategy. Furthermore, a strong focus on customer retention promotes a culture of long-term thinking within teams, encouraging the development of relationships over mere transactional interactions. This systemic emphasis on value delivery allows organisations to thrive in competitive markets, ensuring they remain relevant and responsive to changing customer expectations. By prioritising retention, teams can establish a sustainable business model that supports ongoing innovation and improvement, ultimately leading to increased customer satisfaction and loyalty.</description>
			</item>
			<item>
				<title>Customer Satisfaction</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-satisfaction/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/customer-satisfaction/</guid>
				<description>Customer satisfaction is the assessment of how effectively a product or service meets or surpasses user expectations, serving as a crucial indicator of product-market fit and a key feedback mechanism for teams aiming to deliver value. This concept originates from the need to understand user experiences and is integral to fostering a customer-centric culture within organisations. By prioritising customer satisfaction, teams can adapt and innovate based on genuine user feedback, which helps identify pain points and opportunities for enhancement, leading to iterative improvements that align with user needs. In the context of agile, DevOps, and product development, customer satisfaction is vital for long-term success, promoting a proactive approach to quality and responsiveness in a rapidly evolving market. Emphasising this principle enables organisations to establish a resilient framework that supports continuous improvement and value delivery, ensuring that customer satisfaction transcends being merely a metric and becomes a foundational element that influences all aspects of product development and delivery.</description>
			</item>
			<item>
				<title>Cycle Time</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/cycle-time/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/cycle-time/</guid>
				<description>Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success.</description>
			</item>
			<item>
				<title>Daily Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
			<item>
				<title>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>Deployment Frequency</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/</guid>
				<description>Deployment Frequency is a key metric that measures the rate at which software is released into production, playing a vital role in contemporary product development. It originates from the need for organisations to enhance their responsiveness to customer needs by facilitating quicker feedback loops and adjustments. By optimising deployment frequency, teams can not only release features and fixes more frequently but also validate their assumptions and learn from real-world usage promptly. This concept is crucial for cultivating a culture of continuous improvement and innovation, allowing teams to experiment, iterate, and adapt to market changes effectively. A high deployment frequency reflects a mature DevOps practice characterised by automation, collaboration, and efficient processes that enable rapid delivery without sacrificing quality. Additionally, it fosters a sense of accountability and ownership among team members, as they can directly observe the impact of their contributions on end-users. By prioritising deployment frequency, organisations can establish a sustainable delivery rhythm that enhances customer satisfaction and drives long-term business success through consistent value delivery and adaptability. This systemic approach not only promotes resilience and agility but also ensures that teams remain competitive in an ever-evolving digital landscape.</description>
			</item>
			<item>
				<title>Deployment Strategies</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/</guid>
				<description>Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases.</description>
			</item>
			<item>
				<title>Digital Transformation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/digital-transformation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/digital-transformation/</guid>
				<description>Digital Transformation refers to the strategic integration of modern digital technologies within organisations to improve agility and foster innovation. This process goes beyond merely adopting new tools; it fundamentally alters operational frameworks, enabling organisations to swiftly adapt to market dynamics and customer demands. By embedding digital solutions across various processes, teams can optimise workflows, enhance collaboration, and improve decision-making capabilities. This transformation is vital for delivering consistent and sustainable value, as it aligns technological advancements with business objectives, ensuring that all initiatives contribute meaningfully to overarching goals. It empowers teams to utilise data-driven insights, promoting continuous improvement and a culture of experimentation. Unlike Agile Transformation, which is centred on implementing Agile methodologies, Digital Transformation encompasses a wider scope, affecting every aspect of an organisation. Its long-term, systemic nature necessitates a commitment to ongoing evolution rather than a singular project, fostering an environment conducive to innovation. By embracing Digital Transformation, organisations can not only keep pace with competitors but also establish themselves as leaders in their markets, enhancing their resilience and adaptability in an increasingly complex and uncertain landscape.</description>
			</item>
			<item>
				<title>Empirical Process Control</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/empirical-process-control/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/empirical-process-control/</guid>
				<description>Empirical Process Control is a key principle that focuses on making decisions grounded in observation and experimentation rather than assumptions. Originating from methodologies such as Agile, Lean, and DevOps, it empowers teams to refine their processes and outputs through ongoing inspection and transparency. This reliance on real data and feedback enables organisations to discern effective practices from ineffective ones, fostering a culture of continuous learning and improvement. By adopting this approach, teams can deliver value in a predictable and sustainable manner, adjusting their strategies based on actual performance rather than theoretical frameworks. It promotes a mindset of experimentation, where hypotheses are tested in real-world scenarios, leading to informed decisions that enhance product quality and customer satisfaction. Beyond being a tactical tool, Empirical Process Control serves as a long-term enabler of organisational agility, creating an environment where teams can swiftly adapt to changing conditions and remain aligned with customer needs and market dynamics. In today&amp;rsquo;s fast-paced development landscape, the ability to pivot based on evidence is crucial for success. By integrating empirical practices into their workflows, organisations can cultivate a more resilient and responsive operational model that prioritises value delivery and continuous improvement.</description>
			</item>
			<item>
				<title>Engineering Practices</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/engineering-practices/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/engineering-practices/</guid>
				<description>Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software&amp;rsquo;s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance.</description>
			</item>
			<item>
				<title>Entrepreneurship</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/entrepreneurship/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/entrepreneurship/</guid>
				<description>Entrepreneurship within an organisational knowledge taxonomy represents a crucial framework for fostering innovation, risk-taking, and value-driven decision-making in rapidly changing markets. It encourages teams to identify opportunities, experiment with new ideas, and adapt swiftly to feedback and evolving conditions, thereby nurturing a culture of creativity that effectively addresses customer needs. By embedding entrepreneurial principles, organisations can significantly enhance their agility, leading to more predictable and sustainable value delivery. This approach not only yields immediate results but also builds long-term resilience and adaptability, promoting a holistic view of challenges and facilitating collaboration across various functions while dismantling silos that impede progress. Furthermore, entrepreneurship transcends the mere act of launching new products; it embodies a mindset focused on continuous learning and improvement, closely aligned with Agile and Lean methodologies that prioritise experimentation and customer feedback. By embracing entrepreneurship, organisations can cultivate an environment that supports innovation at all levels, equipping teams to navigate complexity and consistently deliver meaningful outcomes.</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>Experimentation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/experimentation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/experimentation/</guid>
				<description>Experimentation is a fundamental practice within agile workflows that utilises hypothesis-driven methods to test ideas and validate assumptions. Originating from the need to systematically address uncertainties, this approach enables teams to make informed decisions based on empirical evidence rather than relying solely on intuition. The importance of experimentation is underscored by its ability to facilitate predictable and sustainable value delivery, fostering a culture where failure is perceived as a learning opportunity that drives continuous improvement and resilience. Through iterative testing and feedback loops, teams can refine their products and processes, ensuring they align with customer needs and organisational objectives. Furthermore, experimentation promotes long-term systemic change by integrating a scientific mindset into the organisational culture, enhancing collaboration among cross-functional teams and boosting engagement as team members witness the direct impact of their efforts. By prioritising experimentation, organisations can create an environment that values learning and adaptability, which is essential for effective and innovative product development in today&amp;rsquo;s complex and rapidly changing landscape. This practice serves not just as a tactic but as a foundational element that influences how teams operate and evolve.</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>Frequent Releases</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/frequent-releases/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/frequent-releases/</guid>
				<description>Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape.</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>Large Scale Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/large-scale-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/large-scale-agility/</guid>
				<description>Large Scale Agility is the implementation of agile principles and practices throughout entire organisations, moving beyond individual teams to cultivate a culture of adaptability, collaboration, and continuous improvement. Originating from the need for enterprises to respond quickly to market dynamics and customer demands, this approach ensures that value delivery remains both predictable and sustainable. By adopting agile methodologies at scale, organisations can dismantle silos, improve cross-functional collaboration, and align strategic objectives with operational execution. This concept prioritises systemic change, focusing on the organisation as a cohesive unit rather than isolated teams, and encourages the use of frameworks like the Scaled Agile Framework (SAFe) or Large Scale Scrum (LeSS) to provide structured methods for scaling agile practices. The holistic perspective of Large Scale Agility enhances transparency, decision-making, and a shared understanding of goals across all organisational levels. The long-term advantages include increased capacity for innovation, improved employee engagement, and stronger alignment between business and technology. By creating an environment conducive to experimentation, learning, and adaptation, organisations can better navigate the complexities of a rapidly changing landscape, ultimately achieving sustained competitive advantage through agility at scale.</description>
			</item>
			<item>
				<title>Lean Principles</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lean-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lean-principles/</guid>
				<description>Lean Principles are a methodology aimed at minimising waste and maximising value through iterative learning and continuous improvement, primarily used in product development processes. Originating from manufacturing practices, these principles are now widely adopted across various sectors to enhance organisational efficiency and responsiveness. The importance of Lean Principles lies in their ability to foster a culture of experimentation and feedback, enabling teams to identify and eliminate non-value-adding activities, streamline workflows, and optimise resource utilisation. By focusing on value delivery, Lean ensures that all actions align with customer needs, promoting sustainable product development. Techniques such as value stream mapping are employed to visualise the flow of information and materials, helping to identify bottlenecks and areas for improvement. This comprehensive approach not only enhances current processes but also establishes a foundation for long-term agility and adaptability. Unlike Agile frameworks that may concentrate on iterative cycles, Lean Principles advocate for a holistic perspective, integrating insights from various methodologies to create a cohesive strategy for continuous improvement. This enables organisations to effectively respond to changing market demands while maintaining a commitment to delivering high-quality products that meet customer expectations. By embedding Lean thinking into the organisational culture, teams can foster an environment of ongoing learning and innovation, ultimately driving sustained success and resilience in a competitive landscape.</description>
			</item>
			<item>
				<title>Lean Product Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lean-product-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lean-product-development/</guid>
				<description>Lean Product Development is a methodology that centres on minimising waste and maximising learning throughout the product creation process, drawing from Lean principles that prioritise efficiency and value delivery by eliminating non-value-adding activities. This approach is utilised to foster a culture of continuous improvement, enabling teams to swiftly adapt to changing market demands and customer feedback, thereby ensuring the development of relevant and high-quality products. By empowering cross-functional teams to collaborate effectively and employing tools like Kanban to visualise workflows and identify bottlenecks, Lean Product Development promotes iterative cycles of experimentation that allow for the validation of assumptions and necessary pivots. This is particularly vital in today’s fast-paced environment, where responsiveness is key. The focus on systemic thinking aligns all aspects of product development with organisational goals, encouraging a sustainable approach to innovation. By integrating Lean practices, organisations can enhance their capacity to deliver value predictably, cultivating a culture that values learning and adaptability over rigid processes. This long-term emphasis on efficiency and responsiveness equips teams to excel in a competitive landscape, ultimately leading to improved outcomes for both the organisation and its customers.</description>
			</item>
			<item>
				<title>Lean Startup</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lean-startup/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lean-startup/</guid>
				<description>Lean Startup is a methodology that integrates Lean principles into the development of new business ideas, prioritising rapid experimentation and validated learning. Originating from the need to minimise risk and investment in product development, it advocates for the creation of a minimum viable product (MVP) to test assumptions about customer needs and market viability. This approach allows teams to collect real-time feedback, facilitating informed decisions to pivot or persevere based on empirical evidence rather than mere speculation. By cultivating a culture of experimentation, Lean Startup enables organisations to innovate continuously and adapt quickly to shifting market dynamics. It promotes cross-functional collaboration, ensuring that insights from diverse stakeholders shape product development. While it shares similarities with Agile methodologies, Lean Startup uniquely emphasises the validation of business models and market fit, thereby supporting long-term sustainability. This systemic approach embeds learning within the organisation, fostering resilience and adaptability in a constantly changing environment. Ultimately, Lean Startup enhances the likelihood of delivering products that meet genuine customer demands, optimising resource allocation and aligning organisational goals with customer needs.</description>
			</item>
			<item>
				<title>Lean Thinking</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lean-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lean-thinking/</guid>
				<description>Lean Thinking is a methodology aimed at maximising value by minimising waste within organisational processes, originating from manufacturing practices and now widely applied across various sectors. It focuses on understanding customer needs and aligning workflows to efficiently deliver products and services that meet those needs. The importance of Lean Thinking lies in its ability to foster a culture of continuous improvement, where teams are encouraged to identify non-value-adding activities, streamline operations, and enhance productivity. This approach is not solely about cost reduction; rather, it aims to create sustainable systems that support long-term value delivery. By adopting Lean principles, organisations can respond more swiftly to changing market demands while ensuring high quality and customer satisfaction. Furthermore, integrating Lean practices leads to greater predictability in delivery cycles, reduced lead times, and improved collaboration among cross-functional teams. This systemic approach empowers individuals at all levels to engage in process enhancements, cultivating a sense of ownership that drives innovation and resilience. Ultimately, Lean Thinking transforms organisational operations, enabling them to remain competitive and responsive in a rapidly evolving landscape.</description>
			</item>
			<item>
				<title>Market Share</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/market-share/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/market-share/</guid>
				<description>Market share is the percentage of a market that a specific company or product occupies, serving as a key indicator of its competitive standing within that sector. This metric is vital for organisations as it is closely linked to potential revenue, brand reputation, and customer loyalty. By analysing and striving to increase market share, teams can uncover growth opportunities, optimise how they allocate resources, and make informed strategic decisions. Emphasising market share allows teams to align their product development with customer needs and market trends, which is crucial for delivering consistent and sustainable value in agile settings. This alignment promotes a culture of adaptability and responsiveness, enabling teams to refine their products to better meet customer expectations while maintaining a competitive advantage. Additionally, a robust market share can facilitate investment in innovation and improvements, empowering organisations to adopt new technologies and practices that enhance performance. This comprehensive approach not only yields immediate benefits but also fosters long-term resilience and agility, equipping organisations to thrive in a dynamic environment. Therefore, understanding market share is essential for cultivating a proactive approach that prioritises value delivery and continuous enhancement.</description>
			</item>
			<item>
				<title>Mentoring</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/mentoring/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/mentoring/</guid>
				<description>Mentoring is a crucial process where experienced professionals guide and support less experienced colleagues, particularly within agile, lean, and DevOps environments. This relationship transcends mere knowledge transfer; it focuses on nurturing skills, fostering critical thinking, and promoting a culture of continuous learning. By encouraging open dialogue and sharing insights, mentoring aids individuals in navigating complex challenges, thereby enhancing team performance and organisational agility. Its importance lies in establishing a sustainable framework for knowledge transfer and skill enhancement, empowering team members to take ownership of their learning journeys, which boosts their confidence and competence. This empowerment enables teams to deliver value predictably and sustainably, as individuals become more skilled in problem-solving and innovation. Mentoring also fosters psychological safety, allowing team members to experiment and learn from failures without fear of retribution. Unlike coaching, which targets specific skills or immediate performance, mentoring is a long-term investment in personal and professional growth, aligning individual aspirations with organisational goals. By integrating mentoring into the organisational culture, companies can develop resilient teams that adapt to change and drive continuous improvement, ensuring that knowledge and expertise are retained and evolved. This systemic approach is vital for maintaining a competitive edge in fast-paced markets, as it cultivates a collaborative culture of shared learning essential for success in modern product development.</description>
			</item>
			<item>
				<title>Minimum Viable Product</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/minimum-viable-product/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/minimum-viable-product/</guid>
				<description>Minimum Viable Product (MVP) is a fundamental concept in product development that emphasises the creation of a product version with just enough features to meet the needs of early adopters and facilitate feedback for subsequent iterations. Originating from lean startup methodologies, the MVP approach enables teams to quickly test hypotheses and validate market assumptions, thereby minimising the risk associated with investing substantial resources in untested ideas. This strategy not only accelerates product launches but also fosters a culture of experimentation and learning, which is essential for organisations seeking sustainable innovation. By promoting cross-functional collaboration, teams can collectively determine the essential features of the product, enhancing its relevance and aligning team members around common objectives. The MVP framework is not solely focused on speed; it establishes a basis for continuous improvement and value delivery, allowing organisations to remain responsive to evolving market conditions and customer preferences. Ultimately, this approach supports long-term success and resilience in a competitive environment by ensuring that products are developed in a manner that maximises value over time.</description>
			</item>
			<item>
				<title>Operational Practices</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/operational-practices/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/operational-practices/</guid>
				<description>Operational Practices refer to the techniques and strategies that organisations implement to improve their operational efficiency and delivery capabilities. Originating from methodologies such as Lean, Agile, and DevOps, these practices are utilised to streamline workflows, minimise waste, and optimise resource allocation. Their importance lies in fostering a culture of continuous improvement, enabling teams to swiftly adapt to changing demands while ensuring high-quality outputs. By establishing clear processes and enhancing collaboration, Operational Practices empower teams to make data-driven decisions, which collectively enhance performance and customer satisfaction. This systemic approach ensures that operational improvements are ingrained within the organisational culture, promoting resilience and adaptability rather than being merely reactive. Furthermore, Operational Practices align team efforts with strategic goals, ensuring that every action contributes to the organisation&amp;rsquo;s overarching mission. By prioritising these practices, organisations can create an environment conducive to innovation and consistent value delivery, ultimately leading to a more agile and responsive structure capable of navigating the complexities of modern product development and market dynamics.</description>
			</item>
			<item>
				<title>Organisational Culture</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/organisational-culture/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/organisational-culture/</guid>
				<description>Organisational culture refers to the collective values, beliefs, and behaviours that define how teams function within an organisation. It originates from the shared experiences and practices of employees and plays a crucial role in shaping decision-making processes, collaboration, and the agility of teams. A robust organisational culture is vital as it cultivates an environment conducive to innovation, enabling teams to swiftly adapt to changes and challenges. This adaptability is essential for delivering consistent and sustainable value, fostering a mindset of continuous improvement and learning. The long-term effects of organisational culture are significant, establishing a foundation of trust and psychological safety that encourages team members to express ideas and concerns openly. Such an environment enhances problem-solving capabilities and collaboration, which are critical in agile and DevOps methodologies. Unlike specific frameworks, organisational culture is an overarching element that influences every facet of an organisation, affecting strategy execution and team interactions. By prioritising a positive organisational culture, companies can improve their capacity for innovation and adaptability, thereby facilitating successful transformations and achieving strategic objectives. This cultural alignment serves not just as a backdrop but as a dynamic force that drives teams towards excellence and resilience in a constantly changing landscape.</description>
			</item>
			<item>
				<title>Portfolio Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/portfolio-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/portfolio-management/</guid>
				<description>Portfolio Management is a strategic methodology that aligns an organisation&amp;rsquo;s investments with its overarching objectives, ensuring effective resource allocation to maximise value delivery. Originating from the need to continuously assess and prioritise projects and initiatives, this approach enables teams to concentrate on the most impactful work. Its importance lies in fostering a culture of transparency and accountability, as it provides a data-driven framework for decision-making that empowers teams to deliver value predictably and sustainably, while also reducing waste and enhancing overall efficiency. Unlike Agile Project Management, which focuses on individual projects, Portfolio Management adopts a holistic perspective, considering the interdependencies and potential synergies among multiple initiatives. By embedding Portfolio Management within the organisational structure, companies can develop a long-term vision that promotes innovation and adaptability. This systemic approach not only drives performance but also cultivates a resilient organisational culture, equipping teams to effectively navigate complexity and uncertainty. The emphasis on continuous improvement and learning ensures that organisations remain competitive and responsive in a rapidly changing environment, ultimately enhancing their ability to deliver consistent value.</description>
			</item>
			<item>
				<title>Pragmatic Thinking</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/pragmatic-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/pragmatic-thinking/</guid>
				<description>Pragmatic Thinking is a practical approach to problem-solving that emphasises experience-based insights in complex environments, allowing teams to effectively navigate challenges. Originating from the need for actionable strategies in dynamic settings, this methodology prioritises real-world applicability over theoretical frameworks, enabling teams to adapt their approaches to deliver consistent value. Its significance lies in fostering a culture of experimentation and learning, particularly in contexts marked by uncertainty and rapid change. By embracing Pragmatic Thinking, teams can identify and implement tailored solutions that meet their unique circumstances, enhancing their responsiveness to customer needs and building resilience against shifting market conditions. Furthermore, this approach promotes long-term systemic improvements by instilling a continuous learning mindset within organisations, empowering teams to reflect on their experiences, iterate on processes, and refine their methods. Ultimately, integrating Pragmatic Thinking into daily practices cultivates a robust framework for sustained innovation and effective problem-solving, ensuring organisations remain competitive and relevant in their industries.</description>
			</item>
			<item>
				<title>Product Discovery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-discovery/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-discovery/</guid>
				<description>Product Discovery is a vital process in product development that focuses on identifying customer needs and defining valuable product features that align with those needs. Originating from the necessity to ensure that teams deliver solutions that resonate with users, this phase allows organisations to validate assumptions, explore market opportunities, and refine their product vision. The importance of Product Discovery lies in its ability to enable teams to deliver value predictably and sustainably. By employing techniques such as user interviews, prototyping, and iterative testing, teams can gather insights that inform decision-making and mitigate the risk of developing products that fail to meet market demands. This process fosters a culture of experimentation and learning, empowering organisations to adapt swiftly to evolving customer preferences and technological changes. Unlike Agile Planning or Product Management, which concentrate on execution and delivery, Product Discovery is exploratory and systemic, emphasising the understanding of the underlying reasons for product features. This long-term approach not only enhances customer satisfaction but also drives innovation and competitive advantage, making Product Discovery an essential practice for organisations dedicated to creating meaningful products that endure over time.</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 Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-strategy/</guid>
				<description>Product strategy is the systematic process of establishing a clear vision and roadmap for developing a competitive and sustainable product. It involves understanding market needs, aligning product goals with organisational objectives, and creating a decision-making framework that guides product development. This strategic approach is vital as it enables teams to deliver value in a predictable and sustainable manner, ensuring that every feature and enhancement aligns with customer expectations and business outcomes. A well-defined product strategy encourages long-term thinking, allowing organisations to anticipate market changes and adapt effectively. It acts as a guiding principle for cross-functional teams, ensuring coordinated efforts focused on maximising value. By incorporating insights from customer feedback and market analysis, product strategy helps mitigate risks in product development, allowing for innovation while maintaining a clear focus on objectives. Unlike Agile frameworks, which concentrate on the execution of tasks, product strategy provides the overarching direction that informs these methodologies, ensuring that tactical decisions support a larger vision. This approach empowers teams to navigate complexity and uncertainty, ultimately driving sustained success in a competitive environment.</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>Professional Scrum</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/professional-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/professional-scrum/</guid>
				<description>Professional Scrum is a disciplined approach to the Scrum framework that emphasises empiricism, technical excellence, and the continuous delivery of value. Originating from the principles of Scrum, it prioritises the intentional and accountable ways in which individuals, teams, and organisations operate, rather than merely adhering to prescribed rituals or frameworks. This methodology underscores the importance of transparency, the definition of &amp;lsquo;Done&amp;rsquo;, and the necessity of empirical practices, positioning Product Owners as strategic leaders, Scrum Masters as catalysts for change, and Developers as skilled engineers. By embracing complexity as a dynamic to respond to rather than a challenge to control, Professional Scrum encourages rapid learning, frequent delivery, and ongoing improvement. Its significance lies in its ability to infuse professionalism, responsibility, and rigor into the process of complex product delivery, making it a valuable framework for organisations seeking to enhance their agility, foster collaboration, and achieve sustainable success in product development.</description>
			</item>
			<item>
				<title>Project Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/project-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/project-management/</guid>
				<description>Project Management is the systematic discipline focused on planning, executing, and overseeing projects to achieve specific goals while adhering to constraints such as time, cost, and scope. It encompasses the coordination of people, processes, and technologies to ensure successful project outcomes in a structured and repeatable manner. Originating from various methodologies, modern project management incorporates both traditional frameworks like Waterfall and PRINCE2, as well as more flexible approaches such as Agile and hybrid models, which are adapted based on the project&amp;rsquo;s complexity and context. The importance of project management lies in its ability to align teams around common objectives, proactively manage risks, and maintain stakeholder engagement throughout the project lifecycle. Additionally, it fosters a culture of continuous improvement by emphasising lessons learned and the regular review of performance metrics. Ultimately, effective project management aims to deliver value consistently while adeptly navigating change, uncertainty, and complexity, making it a critical component in agile practices, DevOps, product development, and organisational design.</description>
			</item>
			<item>
				<title>Psychological Safety</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/psychological-safety/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/psychological-safety/</guid>
				<description>Psychological safety is the shared belief within a team that it is safe to take interpersonal risks, allowing members to express their thoughts, ask questions, and admit mistakes without fear of negative repercussions. This concept originates from research in organisational behaviour and is increasingly recognised as vital in environments that prioritise collaboration and innovation. In the context of agile methodologies, DevOps practices, and product development, psychological safety is essential as it fosters open communication and encourages team members to contribute ideas, challenge existing norms, and provide constructive feedback. Such an environment not only enhances employee engagement and retention but also improves overall team performance and resilience. By promoting a culture of learning where experimentation is welcomed and failures are seen as growth opportunities, organisations can better adapt to challenges and navigate complexity. Ultimately, psychological safety serves as a foundational element that empowers teams to thrive in dynamic settings, cultivating trust and collaboration that are crucial for success in contemporary organisational design.</description>
			</item>
			<item>
				<title>Release Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/release-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/release-management/</guid>
				<description>Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty.</description>
			</item>
			<item>
				<title>Remote Working</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/remote-working/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/remote-working/</guid>
				<description>Remote working is a practice that enables teams to collaborate and deliver value from various locations, moving beyond the constraints of a physical office. This approach has gained prominence in today&amp;rsquo;s technology-driven landscape, allowing organisations to access a wider talent pool, improve employee satisfaction, and sustain productivity irrespective of geographical limitations. By utilising digital collaboration tools and nurturing a culture of trust and accountability, remote working empowers teams to function effectively, adapting quickly to market changes and customer demands. Its systemic nature fosters sustainable practices through continuous communication and feedback loops, which are crucial for iterative development. This flexibility supports agile methodologies and aligns with lean principles by reducing waste and optimising resource use. Additionally, remote working enhances team members&amp;rsquo; sense of ownership, boosting engagement and motivation. As teams embrace this model, they cultivate resilience and agility, equipping them to tackle challenges and seize opportunities in a dynamic environment. Ultimately, the emphasis on delivering value ensures that organisations can thrive in a competitive landscape while promoting innovation and collaboration among dispersed teams.</description>
			</item>
			<item>
				<title>Scrum Team</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</guid>
				<description>A Scrum Team is a fundamental component of the Scrum framework, tasked with delivering value through iterative and incremental work. Comprising a Scrum Master, Product Owner, and Developers, the team operates collaboratively towards a unified Product Goal. Characterised by its self-managing and cross-functional nature, the Scrum Team eschews sub-teams and hierarchies, holding collective accountability for producing a usable Increment at the end of each Sprint. While individual members may have specific roles, the team&amp;rsquo;s shared responsibility encompasses all facets of product delivery, including stakeholder engagement, development, validation, and release. This structure empowers the Scrum Team to autonomously manage its work, making it a vital element in agile methodologies, DevOps practices, and effective organisational design. Understanding the dynamics and responsibilities of the Scrum Team is crucial for navigating complex and adaptive environments, as it highlights the importance of collaboration and accountability in achieving successful product outcomes.</description>
			</item>
			<item>
				<title>Scrum Values</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scrum-values/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/scrum-values/</guid>
				<description>The Scrum Values are fundamental principles that form the backbone of the Scrum framework, consisting of commitment, courage, focus, openness, and respect. Originating from the need to create a structured yet flexible approach to project management, these values are essential for fostering a collaborative and high-performing team environment. Their importance lies in their ability to enhance a team&amp;rsquo;s capacity to deliver value consistently and sustainably, as they promote a culture of trust and accountability. Commitment drives team members to pursue their goals diligently, while courage encourages them to take risks and express concerns. Focus helps streamline efforts towards critical tasks, boosting productivity and efficiency. Openness facilitates transparent communication and collaboration, leading to effective problem-solving, and respect nurtures a supportive environment that values diverse perspectives, fostering innovation. The long-term benefits of integrating Scrum Values into daily practices are significant, enabling teams to effectively navigate complexities and adapt to evolving circumstances. By embedding these values within their organisational culture, companies can cultivate resilience, prioritise continuous improvement, and align their activities with overarching goals, ensuring that value delivery remains central to their product development and delivery processes.</description>
			</item>
			<item>
				<title>Self Organisation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/self-organisation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/self-organisation/</guid>
				<description>Self-organisation is the capacity of teams to independently manage their work, make decisions, and adapt to evolving circumstances without external oversight. Originating from principles in Agile, Lean, and DevOps methodologies, this concept is vital for fostering a culture of ownership and accountability within teams. By empowering individuals to take initiative, self-organisation enhances collaboration and innovation, leading to improved problem-solving and value delivery. In such environments, teams leverage their collective skills and insights, which boosts engagement and drives continuous improvement through experimentation and learning from failures. This autonomy not only enhances productivity but also contributes to long-term organisational resilience, enabling teams to thrive in dynamic contexts. Unlike traditional hierarchical structures, self-organisation aligns with the need for adaptability and responsiveness, creating a framework that optimises workflows and ensures that organisations remain competitive and responsive to market demands. Ultimately, this approach cultivates an environment where innovation can flourish, equipping teams to navigate complexity with confidence and agility.</description>
			</item>
			<item>
				<title>Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/software-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/software-development/</guid>
				<description>Software Development refers to the systematic techniques and methodologies used to create high-quality software solutions that align with user needs and business objectives. Originating from various practices such as Agile, Lean, and DevOps, it aims to improve collaboration, efficiency, and adaptability within development teams. This approach is vital as it allows organisations to deliver value in a predictable and sustainable manner, fostering a culture of continuous improvement and responsiveness to change. By emphasising iterative development, teams can swiftly adapt to feedback and changing requirements, ensuring the software remains relevant and effective. Additionally, the focus on automation, testing, and integration mitigates the risk of defects and accelerates delivery cycles, leading to more frequent releases and increased customer satisfaction. Software Development also encourages a comprehensive view of the software lifecycle, promoting cross-functional collaboration and knowledge sharing among team members. This long-term, systemic approach not only enhances software quality but also nurtures an innovative environment, enabling organisations to stay competitive in a fast-evolving market. The incorporation of evidence-based management principles further aids informed decision-making, equipping teams to effectively navigate complexity and uncertainty. By prioritising these practices, organisations can secure a sustainable competitive advantage through improved software development capabilities that align with their strategic goals and customer expectations.</description>
			</item>
			<item>
				<title>Team Collaboration</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/team-collaboration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/team-collaboration/</guid>
				<description>Team collaboration is the practice of enhancing teamwork, communication, and shared ownership among team members to achieve high performance. Originating from the need for effective interaction within teams, it is crucial for enabling organisations to deliver value in a predictable and sustainable manner. By fostering a culture of openness and trust, team collaboration empowers individuals to contribute their ideas and skills, thereby enhancing problem-solving capabilities and accelerating decision-making. This collaborative approach helps break down silos, facilitating the free flow of knowledge and expertise across functions, which in turn improves efficiency and adaptability in response to changing requirements and customer feedback. The long-term advantages of strong collaboration include increased innovation, higher employee engagement, and improved overall performance, aligning teams more closely with organisational goals and customer needs. Furthermore, the use of effective collaboration tools and practices is essential in agile, lean, and DevOps environments, supporting seamless communication and coordination. Ultimately, team collaboration serves as a foundational element that drives continuous improvement and value delivery, making it vital for modern product development and organisational success.</description>
			</item>
			<item>
				<title>Team Performance</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/team-performance/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/team-performance/</guid>
				<description>Team performance is the consistent ability of a team to deliver outcomes through its established system of work, reflecting delivery capability over time as indicated by observable patterns in flow, responsiveness, and quality. This concept originates from the understanding that performance is shaped by the structure and constraints of the operational system, influenced by factors such as team composition, collaboration habits, skill alignment, and clarity of purpose. As a system-level capability, team performance transcends individual or cultural traits, making it crucial for organisations aiming to enhance their agile and DevOps practices. By employing flow metrics, retrospectives, and empirical signals to evaluate performance, organisations can discern whether teams are improving, stagnating, or hindered by external dependencies. High-performing teams demonstrate both consistency and adaptability in their delivery, even amidst change. Enhancing team performance involves a focus on system design, which includes limiting work in progress, refining collaboration patterns, and increasing visibility into obstacles. This systemic approach ensures that improvements are not only effective but also sustainable and repeatable across the organisation, ultimately contributing to more efficient product development and organisational design.</description>
			</item>
			<item>
				<title>Technical Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/technical-leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/technical-leadership/</guid>
				<description>Technical leadership refers to the practice of guiding development teams by leveraging technical expertise and agile methodologies to enhance their performance and output. Originating from the need for effective direction in software development, it is employed to ensure that teams can deliver value in a predictable and sustainable manner. This role is vital in the context of agile, DevOps, and product development as it fosters an environment conducive to innovation and continuous improvement. Technical leaders help teams navigate complex challenges, ensuring that technical decisions are aligned with both organisational objectives and customer requirements. They promote long-term thinking and systemic approaches, enabling the creation of adaptable solutions. By cultivating a culture of experimentation and learning, technical leaders facilitate collaboration across various disciplines, breaking down silos and encouraging shared ownership of project outcomes. Distinct from Agile leadership, which focuses on team dynamics, technical leadership prioritises the technical skills necessary for informed decision-making regarding architecture, design, and implementation. This focus on empowering teams to pursue technical excellence not only enhances the quality of deliverables but also strengthens the organisation&amp;rsquo;s capacity to respond effectively to market changes and customer feedback, ultimately contributing to long-term success and resilience in a fast-paced environment.</description>
			</item>
			<item>
				<title>Test Automation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/test-automation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/test-automation/</guid>
				<description>Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements.</description>
			</item>
			<item>
				<title>Transparency</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/transparency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/transparency/</guid>
				<description>Transparency is the practice of fostering openness and visibility within agile processes, which is essential for building trust and accountability among team members. Originating from agile methodologies, transparency enables teams to share information freely, allowing all members to grasp project status, challenges, and progress. This clarity is vital for effective collaboration, empowering individuals to make informed decisions and contribute significantly to team objectives. By promoting transparency, organisations can more easily identify bottlenecks and inefficiencies, facilitating continuous improvement and creating a culture that values feedback and adaptability. This openness not only enhances team dynamics but also aligns efforts towards common goals, ensuring that all members work together to deliver value in a predictable and sustainable manner. Furthermore, transparency supports a long-term approach to organisational health by cultivating an environment of psychological safety, where team members feel secure in expressing concerns and proposing innovations without fear of retribution. This ultimately results in a more resilient organisation, capable of navigating the complexities and uncertainties inherent in product development. By embedding transparency into daily operations, teams can improve their performance and achieve meaningful outcomes that resonate with stakeholders and customers.</description>
			</item>
			<item>
				<title>Trend Analysis</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/trend-analysis/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/trend-analysis/</guid>
				<description>Trend analysis is the practice of identifying patterns and shifts within data over time to support strategic decision-making in organisations. This method is essential for businesses seeking to adapt and succeed in rapidly changing environments. By systematically examining trends, teams can gain insights that inform product development, resource allocation, and market positioning, thereby improving their capacity to deliver value consistently and sustainably. The long-term focus of trend analysis allows organisations to anticipate changes and respond proactively, aligning their strategies with evolving market demands, customer preferences, and technological advancements. Unlike methodologies such as Agile Planning or Continuous Improvement, which concentrate on immediate processes, trend analysis offers a comprehensive view that combines historical data with future projections. By employing trend analysis, organisations can cultivate a culture of evidence-based decision-making, ensuring that choices are informed by data rather than assumptions. This not only boosts operational efficiency but also encourages innovation by revealing growth and improvement opportunities. As teams enhance their ability to recognise and interpret trends, they develop a more resilient and adaptable organisational mindset, which is crucial for navigating the complexities of contemporary product development.</description>
			</item>
			<item>
				<title>Value Stream Mapping</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/</guid>
				<description>Value Stream Mapping is a visual tool designed to analyse and optimise workflows within an organisation by focusing on the flow of materials and information necessary for delivering a product or service. This method involves mapping each step of the process to identify inefficiencies, bottlenecks, and areas of waste, thereby enabling teams to streamline operations and enhance value delivery. Its importance lies in facilitating predictable and sustainable value delivery, empowering teams to make informed decisions based on empirical data, and allowing for adjustments that improve overall performance. By aligning processes with customer needs, Value Stream Mapping ensures that every step adds value towards the end goal. It is not a one-time exercise but a long-term, systemic practice that promotes ongoing reflection and adaptation, helping teams remain agile in response to changing demands and market conditions. This ultimately leads to improved customer satisfaction and organisational resilience. The insights gained from Value Stream Mapping can drive strategic initiatives and foster a culture of collaboration and shared understanding across cross-functional teams, which is essential for achieving sustained success in modern product development.</description>
			</item>
			<item>
				<title>Working Agreements</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/working-agreements/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/working-agreements/</guid>
				<description>Working agreements are foundational norms and principles that teams establish to improve collaboration and effectiveness in their work processes. Originating from the need for clear communication and decision-making frameworks, these agreements delineate how team members interact and fulfil their responsibilities, thereby fostering a shared understanding of expectations. Their importance is underscored in agile and DevOps environments, where accountability and trust are essential for delivering consistent value. By aligning on working agreements, teams can minimise interpersonal conflicts and distractions, allowing them to concentrate on their objectives and engage in continuous improvement. Furthermore, these agreements facilitate long-term systemic change within organisations by empowering teams to self-organise and adapt to challenges, enhancing resilience and agility. By embedding working agreements into the team&amp;rsquo;s culture, organisations can create an environment conducive to collaboration, ultimately leading to improved performance and value delivery. The clarity and commitment provided by working agreements are vital for navigating the complexities of modern product development, ensuring that teams remain aligned with their goals and values.</description>
			</item>
			<item>
				<title>Working Software</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/working-software/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/working-software/</guid>
				<description>Working Software is a fundamental artifact in Agile, Scrum, and Lean frameworks, serving as the tangible output of a team&amp;rsquo;s efforts throughout the development process. It emerges from iterative development cycles and acts as a demonstration of progress and value delivery. In Scrum, working software is the primary success metric for each Sprint, encapsulated in the Increment artifact, which is subject to inspection and adaptation based on stakeholder feedback. The Definition of Done ensures that the software meets established quality criteria, making it valuable and ready for release. The importance of working software lies in its ability to provide a concrete measure of progress, aligning teams and stakeholders around completed work and remaining tasks. It transcends mere code, representing deliverables that address real-world needs and customer expectations, thereby maintaining a focus on value delivery. In agile methodologies, the emphasis on working software fosters continuous feedback and improvement, enabling teams to release increments iteratively and adapt to evolving requirements. This focus enhances collaboration, increases transparency, and drives ongoing improvement within organisations. Ultimately, working software is not solely about technical execution; it is about consistently delivering value, responding to customer needs, and ensuring long-term sustainability, thereby contributing to customer satisfaction, innovation, and overall business success.</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>Application Lifecycle Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/application-lifecycle-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/application-lifecycle-management/</guid>
				<description>Application Lifecycle Management (ALM) is the systematic approach to managing software applications throughout their entire lifecycle, from initial development to eventual retirement. Originating from the need for structured processes in software development, ALM integrates various practices, tools, and team collaboration to streamline workflows and enhance communication. Its importance lies in its ability to provide organisations with a comprehensive view of application development, aligning technical efforts with business goals while remaining adaptable to evolving requirements. By implementing methodologies such as continuous integration and continuous delivery, ALM fosters rapid feedback and iterative enhancements, which are critical in dynamic environments. This approach not only reduces deployment risks but also cultivates a culture of accountability and transparency within teams. Furthermore, ALM aids organisations in effectively managing their application portfolios, ensuring optimal resource allocation and proactive technical debt management. This long-term focus is essential for driving innovation and maintaining a competitive edge, as it allows teams to concentrate on delivering high-quality software that satisfies user demands and contributes to overall business success. The synergy between ALM and frameworks like Agile and DevOps amplifies its impact, establishing a solid foundation for ongoing improvement and value creation.</description>
			</item>
			<item>
				<title>Azure DevOps</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/azure-devops/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/azure-devops/</guid>
				<description>Azure DevOps is a comprehensive suite of tools developed by Microsoft that supports continuous integration and continuous delivery (CI/CD), enhances collaboration, and streamlines agile project management. It encompasses various functionalities, including Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for automating builds and deployments, and Azure Test Plans for managing testing efforts. This platform is crucial for organisations seeking to deliver value in a predictable and sustainable manner, as it promotes a culture of collaboration and transparency among teams. By providing a unified environment for development and operations, Azure DevOps facilitates the adoption of best practices in agile methodologies and DevOps principles, ensuring efficient software delivery that is responsive to evolving business needs. Its systemic approach encourages continuous improvement and learning, enabling organisations to swiftly adapt to market demands while upholding high-quality standards. The integration of tools within Azure DevOps mitigates silos, enhances communication, and fosters a shared understanding of project objectives, ultimately leading to improved outcomes and a culture of innovation. This capability is vital for organisations aiming to achieve operational excellence and maintain a competitive advantage in a fast-changing landscape.</description>
			</item>
			<item>
				<title>Complexity Thinking</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/complexity-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/complexity-thinking/</guid>
				<description>Complexity Thinking is an approach that utilises principles from complexity science to address the intricate dynamics present within organisations and systems. It acknowledges that many challenges faced by organisations are complex rather than merely complicated, characterised by unpredictable interactions and emergent behaviours. This perspective is vital for teams striving to deliver value in a predictable and sustainable manner, as it promotes a deeper understanding of the interdependencies within systems. By employing Complexity Thinking, teams can better foresee how changes in one area may have cascading effects throughout the organisation, leading to unintended consequences. This understanding nurtures a culture of adaptability, enabling teams to respond effectively to changing circumstances rather than relying on linear planning. It empowers organisations to embrace uncertainty, fostering experimentation and learning, which are critical for innovation. Furthermore, Complexity Thinking aligns with Agile and Lean principles by advocating for iterative processes and continuous feedback loops, shifting the focus from isolated tasks to the overall health and performance of the system. This systemic approach not only improves decision-making but also builds resilience, ensuring organisations can thrive in the face of change and complexity. By integrating Complexity Thinking into their practices, teams can discover new avenues for growth and improvement, ultimately enhancing their ability to deliver value consistently and effectively.</description>
			</item>
			<item>
				<title>Decision Theory</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/decision-theory/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/decision-theory/</guid>
				<description>Decision Theory is a systematic framework designed to aid in making informed choices amidst uncertainty, drawing on heuristics, probability, and principles from behavioural economics. It is particularly valuable in agile, DevOps, and product development contexts, as it provides teams with essential tools to navigate complex decision-making scenarios by systematically assessing risks and benefits. By implementing Decision Theory, organisations can enhance their capacity to deliver value in a predictable and sustainable manner, fostering a culture of evidence-based decision-making that relies on data and empirical insights rather than mere intuition. This structured approach supports long-term strategic planning, enabling teams to comprehend the implications of their decisions on future performance and adaptability. In rapidly changing environments, Decision Theory serves as a crucial enabler, allowing teams to pivot effectively while remaining aligned with organisational objectives. Integrating this theory into organisational practices not only improves responsiveness to market dynamics and enhances collaboration but also drives better outcomes by mitigating risks and promoting a mindset of continuous learning and improvement. Ultimately, the emphasis on systematic evaluation and informed risk-taking empowers organisations to seize opportunities more effectively, ensuring competitiveness and resilience in the face of challenges.</description>
			</item>
			<item>
				<title>Enterprise Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/enterprise-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/enterprise-agility/</guid>
				<description>Enterprise Agility is the capacity of an organisation to swiftly and effectively adapt to changes in the market and customer demands, extending agile principles beyond individual teams to encompass the entire enterprise. This concept is vital as it cultivates a culture of adaptability, allowing organisations to pivot quickly in response to new information or shifting priorities. By integrating agility into the organisational structure, processes, and culture, teams can deliver value in a predictable and sustainable manner, ensuring alignment with customer needs. Enterprise Agility focuses on long-term systemic change rather than temporary solutions, fostering a mindset that prioritises continuous improvement and learning across all levels. It promotes cross-functional collaboration, dismantling silos that can impede responsiveness, thereby enhancing operational efficiency and creating an environment conducive to innovation. By emphasising agility at the enterprise level, organisations are better equipped to navigate complexity and uncertainty, leading to improved customer satisfaction and business outcomes. This proactive approach ensures that agility transcends mere practices, becoming a fundamental organisational capability that drives sustained success.</description>
			</item>
			<item>
				<title>Flow Efficiency</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/</guid>
				<description>Flow efficiency is the optimisation of work throughput within a value stream, aimed at minimising waste and reducing bottlenecks. This concept is essential for organisations seeking to deliver value in a predictable and sustainable manner, as it significantly influences the speed at which teams can respond to customer demands and market fluctuations. By examining and enhancing flow efficiency, teams can pinpoint delays and implement targeted improvements that boost overall performance. This methodology is closely aligned with Lean principles, which emphasise the removal of non-value-adding activities. Unlike metrics such as cycle time or lead time that focus on specific durations, flow efficiency offers a comprehensive view of how effectively work progresses through the system, promoting collaboration across various teams and disciplines to ensure seamless operation throughout the value stream. By emphasising flow efficiency, organisations foster a culture of continuous improvement, empowering teams to innovate and experiment. This not only increases productivity but also enhances resilience, allowing teams to adapt to evolving circumstances while consistently delivering value. Ultimately, the focus on flow efficiency nurtures an environment conducive to sustainable practices, leading to long-term success and heightened customer satisfaction.</description>
			</item>
			<item>
				<title>Kanban</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/kanban/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/kanban/</guid>
				<description>Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments.</description>
			</item>
			<item>
				<title>Lean</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/lean/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/categories/lean/</guid>
				<description>Lean is a strategic methodology focused on maximising value while minimising waste, originating from the principles of the Toyota Production System. It is utilised to enhance organisational efficiency by delivering customer value through streamlined processes and fostering a culture of continuous improvement and respect for individuals. By systematically identifying and eliminating non-value-adding activities, Lean enables teams to optimise workflows, boost productivity, and swiftly adapt to changing market conditions. This approach transcends mere tools, embodying a mindset that prioritises long-term sustainability and systemic transformation. Techniques such as value stream mapping and flow efficiency allow teams to visualise their processes, pinpoint bottlenecks, and improve resource allocation, leading to the reliable delivery of high-quality products and services, which in turn enhances customer satisfaction and loyalty. Lean&amp;rsquo;s focus on empirical decision-making and iterative learning aligns seamlessly with Agile and DevOps principles, creating a collaborative environment that fosters rapid innovation while maintaining a commitment to value delivery. By promoting a culture of experimentation and feedback, Lean equips organisations to navigate and thrive in a dynamic landscape, ensuring their competitiveness and relevance in the market.</description>
			</item>
			<item>
				<title>Metrics and Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/</guid>
				<description>Metrics and Learning is a fundamental concept that centres on the utilisation of data, metrics, and feedback to drive continuous improvement within teams and organisational processes. Originating from the need for empirical decision-making, this approach allows organisations to enhance their value delivery by systematically collecting and analysing performance metrics. By doing so, teams can pinpoint areas for enhancement, monitor their progress, and adjust their strategies in alignment with changing customer demands. The focus on learning through metrics fosters a culture of experimentation and adaptability, enabling teams to respond swiftly to feedback and pivot as necessary. This systemic approach not only facilitates immediate improvements but also lays the groundwork for sustained development and innovation. Unlike methodologies that may be prescriptive, Metrics and Learning empowers teams to take ownership of their performance, which is essential for maintaining agility in a fast-paced environment. By integrating metrics into everyday operations, organisations can establish a continuous feedback loop that informs practices and strategies, ultimately leading to more effective and resilient product development.</description>
			</item>
			<item>
				<title>Platform Engineering</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/platform-engineering/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/platform-engineering/</guid>
				<description>Platform Engineering is the discipline focused on the design, construction, and maintenance of internal platforms that empower developers to deliver value independently, reliably, and swiftly. Originating from the need to streamline software development processes, it aims to alleviate cognitive load by abstracting the complexities of infrastructure and operations through well-crafted interfaces, tools, and APIs. This approach treats platforms as products, ensuring clear ownership, regular feedback, and ongoing enhancements based on developer requirements. A robust platform engineering capability fosters paved paths and self-service tools that facilitate secure, observable, and resilient software delivery while avoiding constraints that stifle innovation. By creating an environment conducive to rapid feedback, safe experimentation, and autonomous delivery across teams, Platform Engineering not only provides essential tools but also cultivates a cohesive developer experience that aligns with organisational strategy, ultimately enabling continuous value delivery at scale.</description>
			</item>
			<item>
				<title>Product Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-delivery/</guid>
				<description>Product Delivery refers to the comprehensive process of delivering functional software products to customers, integrating various stages such as planning, development, testing, and deployment into a unified workflow. Originating from methodologies like Agile, Lean, and DevOps, this approach is essential for organisations aiming to deliver consistent value in a predictable and sustainable manner, ensuring that products align with customer needs and expectations. By emphasising an end-to-end delivery process, Product Delivery enhances collaboration among cross-functional teams, streamlines workflows, and reduces cycle times. It fosters a culture of continuous improvement and adaptability, driven by feedback loops that allow teams to respond swiftly to customer insights and market changes. This systemic approach not only improves product quality but also establishes a resilient organisational framework conducive to long-term success. Prioritising Product Delivery cultivates an environment where innovation flourishes and team ownership is encouraged, leading to increased employee engagement and satisfaction. Ultimately, this focus on delivering value through a structured process is vital for maintaining competitiveness and responsiveness in a rapidly changing landscape, positioning Product Delivery as a cornerstone of contemporary product development.</description>
			</item>
			<item>
				<title>Sociotechnical Systems</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/sociotechnical-systems/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/sociotechnical-systems/</guid>
				<description>Sociotechnical systems encompass the complex interactions between social and technical components within an organisation, particularly relevant to software delivery and team performance. This concept highlights that technology is not an isolated entity; rather, it is intricately linked to the organisational culture, structures, and processes. Understanding this duality allows teams to recognise how their workflows, communication styles, and tools impact overall effectiveness. The importance of sociotechnical systems lies in their capacity to create environments where teams can deliver value in a predictable and sustainable manner. When social factors, such as collaboration, trust, and motivation, are harmonised with technical capabilities, including tools and processes, organisations can enhance efficiency and foster innovation. This alignment equips teams to swiftly adapt to evolving market demands and customer expectations, thereby improving agility. Furthermore, sociotechnical systems advocate for a long-term, systemic approach to problem-solving, promoting continuous improvement and learning. By concentrating on the interplay between human and technological elements, organisations can establish resilient frameworks that facilitate ongoing adaptation and growth, ensuring optimal utilisation of both human and technical resources to drive value creation. This comprehensive perspective is crucial for navigating the complexities of contemporary product development and achieving sustained success in a competitive environment.</description>
			</item>
			<item>
				<title>Systems Thinking</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/systems-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/systems-thinking/</guid>
				<description>Systems Thinking is a holistic methodology that helps organisations comprehend and manage complexity by perceiving systems as interconnected entities rather than as separate components. Originating from various disciplines, this approach is utilised to enhance decision-making and facilitate sustainable change within organisations. Its significance lies in fostering a culture of collaboration and shared understanding, enabling teams to foresee the repercussions of their actions throughout the entire system. By recognising interdependencies, organisations can pinpoint leverage points that yield substantial improvements in performance and value delivery. Systems Thinking aligns with Agile, Lean, and DevOps principles by promoting continuous learning and adaptation, allowing teams to respond effectively to feedback and changing requirements. Integrating Systems Thinking into organisational practices not only bolsters innovation and consistent value delivery but also establishes a resilient framework that supports long-term success. This comprehensive perspective aids in problem-solving and nurtures an environment conducive to team growth, ultimately leading to more effective and sustainable outcomes.</description>
			</item>
			<item>
				<title>Technical Excellence</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/technical-excellence/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/technical-excellence/</guid>
				<description>Technical Excellence encompasses the quality of engineering practices that facilitate high-quality software delivery, enhanced agility, and ongoing improvement within development teams. Originating from methodologies that prioritise best practices, it empowers teams to create maintainable, scalable, and resilient software. In the context of Agile, Technical Excellence is vital as it allows teams to swiftly adapt to changing requirements and market demands while ensuring product quality and sustainability. Key practices such as Test-Driven Development (TDD) and Continuous Integration and Continuous Delivery (CI/CD) play a significant role in maintaining high standards by automating testing and deployment processes, thus enabling more frequent and reliable software releases. Additionally, modular architecture supports scalability and responsiveness to new requirements, while emergent design principles promote flexibility in adapting software designs as understanding evolves. By fostering a culture of continuous improvement, Technical Excellence encourages teams to regularly evaluate and refine their practices, ensuring they can maintain quality and responsiveness to change. Embedding this capability within an organisation&amp;rsquo;s culture not only addresses immediate customer needs but also establishes a sustainable foundation for long-term success, allowing organisations to consistently deliver high-quality software while remaining adaptable and efficient in their development processes.</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>
			<item>
				<title>Value Stream Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/value-stream-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/value-stream-management/</guid>
				<description>Value Stream Management is a strategic methodology aimed at improving the flow of value within an organisation by optimising processes, reducing waste, and aligning efforts with customer outcomes. Originating from the need to enhance operational efficiency, it involves mapping the entire value stream from ideation to delivery, enabling teams to identify and address bottlenecks and inefficiencies that impede performance. This approach is vital in the context of agile, DevOps, and product development, as it fosters a culture of continuous improvement and responsiveness to market changes. By promoting collaboration across departments and breaking down silos, Value Stream Management ensures a shared understanding of how work contributes to overarching business goals. It empowers teams to focus on delivering high-quality products that satisfy customer needs while balancing speed and efficiency. Unlike specific Agile frameworks or Lean principles that concentrate on particular practices, Value Stream Management offers a comprehensive perspective on the entire process, ensuring that each step adds value. This long-term, systemic approach not only enhances operational performance but also nurtures an environment conducive to innovation, ultimately leading to greater organisational resilience and adaptability in a fast-changing landscape.</description>
			</item>
			<item>
				<title>Collective Intelligence</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/collective-intelligence/</link>
				<pubDate>Thu, 23 Jan 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/collective-intelligence/</guid>
				<description>Collective Intelligence represents the enhanced problem-solving and innovation capabilities that emerge when humans with agency effectively collaborate with AI agents as team members. This concept goes beyond traditional human collaboration to encompass human-AI partnerships where both parties contribute complementary strengths, human creativity, judgment, and contextual understanding combined with AI processing power, pattern recognition, and consistent execution. Unlike passive tool usage, Collective Intelligence requires humans to have genuine agency and AI systems to operate with designed autonomy within appropriate constraints. The resulting synergy enables teams to navigate complex socio-technical environments, make more informed decisions, and deliver superior outcomes that neither humans nor AI could achieve independently. This form of agentic agility is essential for modern product development, where the volume and complexity of information, rapid change cycles, and need for continuous adaptation exceed purely human cognitive capabilities. By cultivating Collective Intelligence, organisations can harness the full potential of human-AI collaboration, transforming how value is created and delivered in digital product development.</description>
			</item>
			<item>
				<title>Agentic Software Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agentic-software-delivery/</link>
				<pubDate>Tue, 21 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agentic-software-delivery/</guid>
				<description>Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation&amp;rsquo;s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term &amp;lsquo;agentic&amp;rsquo; implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-developer/</guid>
				<description>Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.</description>
			</item>
	</channel>
</rss>
