<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Pragmatic Thinking on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/pragmatic-thinking/</link>
		<description>Recent content in Pragmatic Thinking on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/pragmatic-thinking/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stop Building Silos. Start Building Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</link>
				<pubDate>Mon, 07 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</guid>
				<description>Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system.</description>
			</item>
			<item>
				<title>Don’t Manage Dependencies, Remove Them</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</link>
				<pubDate>Mon, 29 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</link>
				<pubDate>Mon, 11 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</guid>
				<description>Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change.</description>
			</item>
			<item>
				<title>Rethinking Capacity Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/</link>
				<pubDate>Mon, 21 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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>Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</link>
				<pubDate>Mon, 15 Sep 2025 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</guid>
				<description>Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies.</description>
			</item>
			<item>
				<title>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Velocity isn’t how many story points a team burns down</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Scrum Masters are not glorified meeting schedulers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/</link>
				<pubDate>Sun, 09 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/</guid>
				<description>Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility.</description>
			</item>
			<item>
				<title>Should You Use One Project to Rule Them All in Azure DevOps?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership-preview.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-preview.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>Engineering can fix technical debt, but leadership has to invest in it</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</link>
				<pubDate>Mon, 03 Mar 2025 16:30:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</guid>
				<description>Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements.</description>
			</item>
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</guid>
				<description>The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications.</description>
			</item>
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/</link>
				<pubDate>Mon, 04 Aug 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/</guid>
				<description>Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization.</description>
			</item>
			<item>
				<title>Testing in Production Maximises Quality and Value</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Are We Still Pretending Coding Was the Bottleneck?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</link>
				<pubDate>Wed, 02 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</guid>
				<description>Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality.</description>
			</item>
			<item>
				<title>Resilience is Part of the Product, Not an Afterthought</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</link>
				<pubDate>Wed, 21 Aug 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</guid>
				<description>DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results.</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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/stop-promoting-branches/</link>
				<pubDate>Thu, 06 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</link>
				<pubDate>Thu, 04 Jun 2020 02:05:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</guid>
				<description>The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust.</description>
			</item>
			<item>
				<title>Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/</link>
				<pubDate>Mon, 08 Sep 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/</guid>
				<description>Big Bang rewrites of legacy systems usually fail due to high costs, delays, and unchanged team mindsets, while incremental in-place improvements deliver ongoing value and reduce risk. Sustainable change comes from building a culture of continuous improvement and engineering excellence, where teams refactor and modernise systems piece by piece. Development managers should focus on fostering this culture and invest in gradual, disciplined transformation rather than risky all-at-once rewrites.</description>
			</item>
			<item>
				<title>How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it.</description>
			</item>
			<item>
				<title>Technical debt isn’t just messy code</title>
				<link>https://engineering-leadership-preview.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-preview.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>Transforming Chaos into Clarity: How Optimising Systems Fuels Engineering Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</link>
				<pubDate>Mon, 16 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</guid>
				<description>Unmanaged chaos in software delivery leads to poor quality, technical debt, and wasted resources. Optimising systems and processes, as shown by Microsoft’s transformation of their DevOps team, enables faster delivery, higher productivity, and better products by reducing technical debt and improving testing practices. Development managers should prioritise system optimisation and technical leadership to empower teams and drive sustainable engineering excellence.</description>
			</item>
			<item>
				<title>A better way than staggered iterations for delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</link>
				<pubDate>Thu, 10 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</guid>
				<description>Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality.</description>
			</item>
			<item>
				<title>Without Delivery, There Is No Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/</link>
				<pubDate>Mon, 10 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</link>
				<pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</link>
				<pubDate>Mon, 11 Aug 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</guid>
				<description>Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible.</description>
			</item>
			<item>
				<title>Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation</title>
				<link>https://engineering-leadership-preview.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-preview.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>Scaling Smart: How to Tackle Technical Debt for Sustainable Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</link>
				<pubDate>Tue, 25 Feb 2025 06:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</guid>
				<description>Unchecked technical debt slows development, increases bugs, and reduces team productivity, making scaling risky and inefficient. Addressing weak points through sustainable architecture, automated testing, and continuous integration enables faster feedback, more reliable releases, and confident growth. Development managers should prioritize managing technical debt and automation to support sustainable scaling and maintain innovation.</description>
			</item>
			<item>
				<title>Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</link>
				<pubDate>Tue, 19 Nov 2024 09:58:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</guid>
				<description>Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success.</description>
			</item>
			<item>
				<title>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</link>
				<pubDate>Thu, 05 Sep 2024 11:14:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</guid>
				<description>Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</guid>
				<description>Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization&amp;rsquo;s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training.</description>
			</item>
			<item>
				<title>Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agility-balancing-engineering-excellence-and-effective-processes-in-a-rapidly-changing-business-landscape/</link>
				<pubDate>Wed, 25 Mar 2020 21:07:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agility-balancing-engineering-excellence-and-effective-processes-in-a-rapidly-changing-business-landscape/</guid>
				<description>Balancing strong engineering practices with effective processes is essential for thriving in today’s fast-changing business environment; neglecting either can lead to costly failures or products that miss user needs. Success with Agile requires more than process changes, it demands a culture of transparency, collaboration, and continuous learning, along with well-trained product owners and meaningful outcome-focused metrics. Development managers should invest in engineering excellence, support ongoing training, and adopt an experimental, evidence-based approach to drive real agility and business value.</description>
			</item>
			<item>
				<title>Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done</title>
				<link>https://engineering-leadership-preview.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-preview.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>Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</link>
				<pubDate>Wed, 28 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</guid>
				<description>Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline.</description>
			</item>
			<item>
				<title>The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</link>
				<pubDate>Thu, 01 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</guid>
				<description>Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change.</description>
			</item>
			<item>
				<title>Navigating the Unpredictability of Software Development: Embrace Agile for Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</link>
				<pubDate>Mon, 14 Oct 2019 13:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</guid>
				<description>The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint.</description>
			</item>
			<item>
				<title>Why Organisations Believe Their Software Is Too Complex for CD</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</link>
				<pubDate>Mon, 24 Feb 2025 10:51:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</guid>
				<description>Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity.</description>
			</item>
			<item>
				<title>Mastering Technical Debt: Strategies to Transform Challenges into Opportunities for Your Development Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</link>
				<pubDate>Thu, 28 Nov 2024 06:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</guid>
				<description>Technical debt results from choosing quick fixes over robust solutions, leading to future costs and risks that can hinder your team&amp;rsquo;s productivity. Proactively paying down technical debt, as shown by the Azure DevOps team&amp;rsquo;s shift to agile practices, can dramatically increase feature delivery and product quality. Make refactoring, short feedback loops, and a focus on quality part of your regular process to unlock long-term gains and sustainable success.</description>
			</item>
			<item>
				<title>Avoid the pick-n-mix branching anti-pattern</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</link>
				<pubDate>Mon, 14 Jul 2014 15:35:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</guid>
				<description>Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability.</description>
			</item>
			<item>
				<title>DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/</link>
				<pubDate>Mon, 28 Jul 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/</guid>
				<description>Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Evolving Engineering Practices to Improve Sprint Workflow in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/</link>
				<pubDate>Thu, 29 May 2025 15:30:45 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/</guid>
				<description>To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress.</description>
			</item>
			<item>
				<title>Why Tracking Individual Cycle Time Distorts Team Behaviour</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>Where Agile Went Wrong: Understanding the Competence Crisis</title>
				<link>https://engineering-leadership-preview.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-preview.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>DevOps: Elevating Your Organization’s Performance Through Bespoke Solutions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/</link>
				<pubDate>Fri, 16 Aug 2024 07:18:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/</guid>
				<description>Tailoring DevOps to your organization’s unique needs starts with assessing your current state, streamlining processes, and choosing the right tools, which leads to higher quality and more frequent software deliveries. Key actions include conducting solo interviews to uncover real issues, automating and rationalizing tools, and empowering teams with end-to-end ownership while ensuring compliance does not block DevOps practices. Start with small, controlled deployments and strategic timing to minimize risk and maximize efficiency.</description>
			</item>
			<item>
				<title>Empowering Teams for Success: The Key to Thriving Product Development</title>
				<link>https://engineering-leadership-preview.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-preview.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>If a client hasn&#39;t considered DevOps consulting as part of their Agile Consulting needs, why should they?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn&#39;t-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/</link>
				<pubDate>Mon, 21 Aug 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn&#39;t-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/</guid>
				<description>Relying on Agile alone limits your team&amp;rsquo;s ability to deliver quality software quickly and efficiently; integrating DevOps consulting breaks down silos, accelerates time to market, and embeds quality from the start. DevOps is more than tools, it is a culture shift that harmonizes development and operations, enabling continuous improvement and resilient deployments. To maximize Agile&amp;rsquo;s benefits, development managers should invest in DevOps consulting to create a truly high-performing, adaptable software delivery process.</description>
			</item>
			<item>
				<title>Toyota &#34;andon&#34; cord lets any worker stop production to fix defects</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</guid>
				<description>Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible.</description>
			</item>
			<item>
				<title>Why Engineering Teams Use Staging Environments for Risk Reduction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/</link>
				<pubDate>Fri, 14 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/</guid>
				<description>Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead.</description>
			</item>
			<item>
				<title>Getting started with a modern source control system and DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/</link>
				<pubDate>Mon, 13 Jul 2020 18:41:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/</guid>
				<description>Modern source control systems are essential for managing not just code but the entire software development lifecycle, supporting DevOps practices and providing critical metadata for process visibility. Key practices include always using source control, automating release pipelines, minimizing branches with feature flags, moving to Git, and ensuring regular feedback and testing. To stay competitive, development managers should ensure all code is in source control, automate releases, and adopt integrated platforms like VSTS that support any technology and enable continuous delivery.</description>
			</item>
			<item>
				<title>The Insufficiency of Scrum is a fallacy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</link>
				<pubDate>Sat, 23 Mar 2013 17:37:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</guid>
				<description>Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes.</description>
			</item>
			<item>
				<title>The Sprint is a container for Planning and not necessarily for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</link>
				<pubDate>Tue, 29 Nov 2011 04:36:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</guid>
				<description>Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality.</description>
			</item>
			<item>
				<title>How to Stop Chasing Tech Hype and Start Making Smarter, Evidence-Based Decisions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-stop-chasing-tech-hype-and-start-making-smarter-evidence-based-decisions/</link>
				<pubDate>Fri, 30 May 2025 06:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-stop-chasing-tech-hype-and-start-making-smarter-evidence-based-decisions/</guid>
				<description>Chasing every new technology trend wastes resources, demoralises teams, and creates technical debt. Instead, use structured, evidence-based frameworks to evaluate tech choices based on strategic fit, ROI, team capability, and timing. Make disciplined decision-making a repeatable part of your process so you lead with intent rather than react to hype.</description>
			</item>
			<item>
				<title>Executives want predictability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</link>
				<pubDate>Mon, 31 Mar 2025 15:30:08 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>Why Scrum Masters Need Technical Expertise to Guide Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/</link>
				<pubDate>Fri, 28 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/</guid>
				<description>Scrum Masters are most effective when they have hands-on experience and technical understanding relevant to their team&amp;rsquo;s work, such as development practices or domain-specific knowledge. This expertise helps them guide teams toward improvement without doing the work themselves. Development managers should ensure Scrum Masters have sufficient technical background to enable, not just facilitate, their teams.</description>
			</item>
			<item>
				<title>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</link>
				<pubDate>Wed, 16 Oct 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</guid>
				<description>There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Estimating Better in an Overloaded System Is a Poor Man’s Strategy</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Embrace Simplicity: How to Transform Complexity into Continuous Delivery Success</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Why Azure DevOps Wins for Governance, Security, and Scale, Right Out of the Box</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/</link>
				<pubDate>Mon, 01 Sep 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/</guid>
				<description>Azure DevOps provides integrated governance, security, compliance, and scalability out of the box, eliminating the need for complex tool setups and manual integration. Its seamless traceability, audit trails, and ability to handle thousands of users make it ideal for large-scale, secure software development. Development managers should consider Azure DevOps to reduce operational friction and focus on delivering value rather than managing disparate tools.</description>
			</item>
			<item>
				<title>Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/</link>
				<pubDate>Thu, 08 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/</guid>
				<description>Aiming for a resilient, fast, and fault-tolerant token counting system, the author replaced fragile server restarts with a batch-wide server lifecycle, added retry logic for transient failures, and implemented a local fallback to ensure uninterrupted processing. These changes improved reliability, reduced downtime, and provided clear logs for troubleshooting. Development managers should focus on building systems that handle real-world failures gracefully, prioritize flow, and include observability and fallback mechanisms from the start.</description>
			</item>
			<item>
				<title>I’ll never understand teams that manage bugs instead of fixing them</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/</link>
				<pubDate>Thu, 01 May 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/</guid>
				<description>Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate.</description>
			</item>
			<item>
				<title>Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Special Sprints: Agile Banditry or Risk Management?</title>
				<link>https://engineering-leadership-preview.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-preview.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>Engineering Culture That Thrives: How to Build Teams Ready for Change, Not Just the Next Fire Drill</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</link>
				<pubDate>Thu, 07 Mar 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</guid>
				<description>Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process.</description>
			</item>
			<item>
				<title>Stop Chasing the Hottest Tech Stack: Why Context-Driven Choices Win Every Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-the-hottest-tech-stack-why-context-driven-choices-win-every-time/</link>
				<pubDate>Fri, 06 Jun 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-the-hottest-tech-stack-why-context-driven-choices-win-every-time/</guid>
				<description>Choosing technology based on trends rather than your team’s needs often leads to wasted effort and complexity. Focus on your business goals, team maturity, and constraints to shape a tech strategy that truly fits. Prioritise what delivers value for your context instead of chasing the latest tools.</description>
			</item>
			<item>
				<title>Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Are technical skills required to be a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</link>
				<pubDate>Sun, 01 Sep 2019 15:37:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</guid>
				<description>Technical skills are not strictly required to be a Scrum Master, but having a solid understanding of technical, business, and organizational contexts makes a Scrum Master much more effective. Mastery in these areas helps Scrum Masters better support their teams, guide Product Owners, and drive meaningful organizational change. Development managers should ensure their Scrum Masters are equipped with broad contextual knowledge to maximize team and business value.</description>
			</item>
			<item>
				<title>Modernising Legacy Systems: How to Tackle Security Risks Without Breaking Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/</link>
				<pubDate>Mon, 12 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/</guid>
				<description>Modernising legacy systems is essential for security, but rushing the process can create new risks; instead, map your workflows, embed security throughout development, empower teams, and focus on maintainability and compliance. Treat security as an ongoing mindset, not a one-time task, and continuously adapt as threats evolve. Start by assessing how work and security practices flow in your organisation before making changes.</description>
			</item>
			<item>
				<title>The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Power of Kaizen: Continuous Improvement in Scrum and Beyond</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</link>
				<pubDate>Sun, 25 Aug 2024 22:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</guid>
				<description>Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum.</description>
			</item>
			<item>
				<title>Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow</title>
				<link>https://engineering-leadership-preview.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-preview.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>Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape</title>
				<link>https://engineering-leadership-preview.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-preview.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>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</link>
				<pubDate>Tue, 13 Sep 2011 20:40:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</guid>
				<description>Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</link>
				<pubDate>Thu, 21 Mar 2024 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</guid>
				<description>Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively.</description>
			</item>
			<item>
				<title>Mastering Agile: 3 Essential Strategies to Boost Your Team&#39;s Sprint Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</link>
				<pubDate>Thu, 16 Nov 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</guid>
				<description>To improve your team&amp;rsquo;s Sprint outcomes, clearly define what &amp;ldquo;done&amp;rdquo; means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place.</description>
			</item>
			<item>
				<title>Unlocking the Power of Sprint Planning: Transform Your Agile Approach for Success</title>
				<link>https://engineering-leadership-preview.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-preview.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>Why Using a Blocked Column in Azure DevOps Is a Mistake</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/</link>
				<pubDate>Thu, 20 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/</guid>
				<description>Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Transformative Power of Teaching the &#34;Why&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</guid>
				<description>Helping teams understand the reasons behind Agile practices is key to real engagement and lasting change. When team members grasp the value and purpose of what they do, they collaborate better, adapt more easily, and drive continuous improvement. Development managers should focus on explaining the &amp;ldquo;why&amp;rdquo; behind processes to empower teams and boost performance.</description>
			</item>
			<item>
				<title>Deploying Windows OS Directly to Production: Then vs Now</title>
				<link>https://engineering-leadership-preview.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-preview.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>Branch promotion is a relic of slow, manual software delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</link>
				<pubDate>Sat, 08 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</guid>
				<description>Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery.</description>
			</item>
			<item>
				<title>Frequent releases are not just a technical strategy</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Transforming Enterprises: How DevOps Drives Collaboration and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/</link>
				<pubDate>Tue, 16 Jun 2020 12:16:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/</guid>
				<description>DevOps can transform enterprise software teams by fostering collaboration, encouraging continuous improvement, and enabling automation, which together lead to faster delivery and higher quality. Focusing on a customer-centric approach helps teams respond quickly to feedback and market changes. Development managers should prioritize building a culture that supports these principles to drive meaningful organizational change.</description>
			</item>
			<item>
				<title>From Firefighting to Focus: How CTOs Can Lead with Clarity Instead of Chasing the Next Big Thing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-firefighting-to-focus-how-ctos-can-lead-with-clarity-instead-of-chasing-the-next-big-thing/</link>
				<pubDate>Fri, 23 May 2025 06:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-firefighting-to-focus-how-ctos-can-lead-with-clarity-instead-of-chasing-the-next-big-thing/</guid>
				<description>CTOs should stop chasing every new technology and instead focus on making their systems and decision-making processes visible to identify real improvement opportunities. Effective leadership means building a clear, context-driven strategy and fostering sustainable innovation by investing in team learning and system evolution. Take action by stepping back from survival mode, clarifying how work happens, and leading with intention for long-term value.</description>
			</item>
			<item>
				<title>Understanding Blocked Columns and Stalled Work in Project Boards</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/</link>
				<pubDate>Tue, 04 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/</guid>
				<description>Using a separate &amp;ldquo;Blocked&amp;rdquo; column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible.</description>
			</item>
			<item>
				<title>Too many teams overcomplicate their branching strategies</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Is Your Project Ecosystem Truly Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</link>
				<pubDate>Wed, 31 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Big Scrum: All you need and not enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</link>
				<pubDate>Wed, 01 Jul 2015 16:33:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</guid>
				<description>Scaling Scrum requires truly professional teams who embody agile values and strong engineering practices, not just following processes superficially. Off-the-shelf frameworks do not fit every organization, so adapting Scrum to your unique context is essential. Focus on building skilled teams, fostering effective communication, and adopting only the practices that support your specific scaling needs.</description>
			</item>
			<item>
				<title>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</link>
				<pubDate>Fri, 09 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</guid>
				<description>Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction.</description>
			</item>
			<item>
				<title>Building the wrong thing is worse than fixing a bug</title>
				<link>https://engineering-leadership-preview.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-preview.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>Not all delays are the same</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/not-all-delays-are-the-same/</link>
				<pubDate>Sat, 15 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/not-all-delays-are-the-same/</guid>
				<description>Not all delays are equal; waiting for approval is different from being blocked by missing dependencies. Treating all delays as blocks hides real workflow issues and reduces accountability. Make delay sources explicit, track idle time, and highlight true blockers to identify and fix underlying problems.</description>
			</item>
			<item>
				<title>Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>From Chaos to Clarity: My Journey Through DevOps and the Three Key Challenges to Overcome</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</link>
				<pubDate>Thu, 04 Apr 2024 11:34:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</guid>
				<description>The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster.</description>
			</item>
			<item>
				<title>Rethinking Sprint Planning: Why Burndown Charts Are Agile Banditry and What to Do Instead</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</link>
				<pubDate>Mon, 14 Dec 2020 13:03:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</guid>
				<description>A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what &amp;ldquo;done&amp;rdquo; means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product.</description>
			</item>
			<item>
				<title>Metrics that matter with evidence-based management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</link>
				<pubDate>Tue, 25 Feb 2014 13:29:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</guid>
				<description>Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement.</description>
			</item>
			<item>
				<title>Building a release pipeline with Release Management with Visual Studio 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</link>
				<pubDate>Tue, 18 Feb 2014 16:30:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</guid>
				<description>Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices.</description>
			</item>
			<item>
				<title>Quality enablement to achieve predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</link>
				<pubDate>Wed, 24 Jul 2013 09:46:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</guid>
				<description>Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance.</description>
			</item>
			<item>
				<title>During a massive flood in London, nearly every datacentre went down.&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/during-a-massive-flood-in-london-nearly-every-datacentre-went-down/</link>
				<pubDate>Fri, 16 May 2025 15:30:31 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/during-a-massive-flood-in-london-nearly-every-datacentre-went-down/</guid>
				<description>Rackspace was the only London datacentre to stay online during a major flood because they regularly tested their backup systems by simulating real failures. Practising failure recovery under controlled but challenging conditions built true resilience in their operations. Development managers should regularly test their systems and teams under realistic failure scenarios to ensure they can recover when it matters most.</description>
			</item>
			<item>
				<title>If software is not delivered, it is not valuable</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>The Evolution of My Journey with Azure DevOps: Lessons and Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/</link>
				<pubDate>Wed, 31 Jul 2024 09:21:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/</guid>
				<description>Azure DevOps has evolved from TFS to a powerful, flexible platform that can transform team workflows, but successful adoption and migration require careful planning and sometimes custom solutions. Key lessons include the importance of assessing your environment, choosing the right migration tools, and leveraging expert guidance for complex needs. Development managers should ensure their teams are trained and consider consulting support to maximize the benefits and scalability of Azure DevOps.</description>
			</item>
			<item>
				<title>Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</link>
				<pubDate>Wed, 05 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>Biggest contribution from a Product Owner that you know of</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</link>
				<pubDate>Fri, 25 Oct 2024 07:02:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</guid>
				<description>Many Scrum Masters misunderstand their true responsibilities, focusing on tools and rituals instead of the core principles and accountabilities defined by Scrum. Effective Scrum Masters balance support for the team, Product Owner, and organisation, acting as coaches and mentors rather than process enforcers. Development managers should ensure Scrum Masters are competent in Scrum’s philosophies and adapt practices to fit their context, not just follow common routines.</description>
			</item>
			<item>
				<title>Empowering Teams to Tailor Their Processes: A Path to True Agility</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</link>
				<pubDate>Wed, 17 Apr 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</guid>
				<description>Agile and Scrum frameworks highlight problems in team processes, but many organizations ignore these signals due to cultural barriers like fear of repercussions and resistance to change. Simply adopting these frameworks is not enough; their effectiveness depends on a culture that encourages transparency, feedback, and continuous improvement. Development managers should focus on building an environment where raising and addressing issues is supported and valued to fully realize the benefits of Agile and Scrum.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 3</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking Value in DevOps: My Role as a Consultant in Driving Change and Overcoming Bottlenecks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</link>
				<pubDate>Tue, 02 May 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</guid>
				<description>As a DevOps consultant, my main focus is helping teams rethink how they deliver value by identifying and addressing both technical and process bottlenecks, such as slow builds or approval delays. I do this by asking targeted questions and encouraging teams to examine their workflows, which leads to continuous improvement and better customer outcomes. Development managers should regularly review their processes to spot and resolve the biggest sources of delay.</description>
			</item>
			<item>
				<title>If your backlog is not refined then you are doing it wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</link>
				<pubDate>Thu, 17 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</guid>
				<description>If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints.</description>
			</item>
			<item>
				<title>Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World</title>
				<link>https://engineering-leadership-preview.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-preview.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>Modernising Legacy Systems: A Practical, Low-Risk Strategy for Real Business Transformation</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Scrum Masters and Product Owners are held accountable for results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</link>
				<pubDate>Mon, 17 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/</guid>
				<description>Scrum Masters and Product Owners are often held accountable for results without having the authority needed to influence outcomes. This mismatch leads to empty expectations and limits team effectiveness. To achieve better results, organisations should empower Scrum Masters with real authority, not just expect them to coach from the sidelines.</description>
			</item>
			<item>
				<title>Agile Is Not Easier Than Traditional Methods: Common Misconceptions</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Most teams don’t fail because they lack frameworks</title>
				<link>https://engineering-leadership-preview.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-preview.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>Here the dirty secret behind many agile transformations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</link>
				<pubDate>Fri, 02 May 2025 15:30:32 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</guid>
				<description>Many agile transformations fail because organizations maintain tight control over how work is done while claiming to empower teams. True agility requires leadership to set clear goals and priorities but let teams decide how to achieve them. To foster commitment and improvement, review where your processes still dictate the how and shift toward real team autonomy.</description>
			</item>
			<item>
				<title>Empowering Teams to Maximize Value and Return on Investment</title>
				<link>https://engineering-leadership-preview.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-preview.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>All technical debt is a risk to the product and to your business</title>
				<link>https://engineering-leadership-preview.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-preview.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>Release Management with Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</link>
				<pubDate>Wed, 24 Apr 2013 17:38:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</guid>
				<description>Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality.</description>
			</item>
			<item>
				<title>Professional Scrum Developer (.NET) Training in London</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</link>
				<pubDate>Fri, 18 Jun 2010 15:53:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</guid>
				<description>Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies.</description>
			</item>
			<item>
				<title>The Missing Lever in Agile Transformations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/</link>
				<pubDate>Mon, 02 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Fear is the real enemy of agility</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/too-much-refinement-wastes-time/</link>
				<pubDate>Tue, 29 Apr 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</link>
				<pubDate>Wed, 05 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</guid>
				<description>Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</link>
				<pubDate>Thu, 14 Sep 2023 14:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</guid>
				<description>Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: How Empirical Models Transform Project Outcomes</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</link>
				<pubDate>Wed, 12 Oct 2022 17:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</guid>
				<description>Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/</link>
				<pubDate>Thu, 29 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/</guid>
				<description>Upgrading legacy .NET projects to SDK-style makes your codebase easier to maintain, improves build and CI/CD integration, and prepares you for future .NET upgrades. Converting class libraries is straightforward and highly recommended, while web apps require more care and are best handled with the MSBuild.SDK.SystemWeb package if you want SDK-style; otherwise, you can leave them in the old format. Start by converting class libraries now to simplify your engineering system and reduce technical debt.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile Apocalypse - Plague</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-plague/</link>
				<pubDate>Fri, 20 Oct 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-plague/</guid>
				<description>Many organizations are undermined by unqualified Agile coaches and Scrum Masters who lack real understanding and experience, leading to harmful practices, lost trust in Agile, and reduced team performance. Key issues include rigid rule enforcement, lack of inclusivity, and prioritizing process over people. To avoid these pitfalls, prioritize hiring experienced, continuously learning Agile leaders who embody true Agile values and focus on team empowerment and value delivery.</description>
			</item>
			<item>
				<title>Cutting Through the Red Tape: How Eliminating Committees Can Boost Your Time to Market</title>
				<link>https://engineering-leadership-preview.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-preview.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>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/security-by-design-building-secure-software/</link>
				<pubDate>Tue, 26 Nov 2024 13:35:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</link>
				<pubDate>Fri, 28 Jun 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</guid>
				<description>Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense&amp;rsquo;s &amp;ldquo;Detecting Agile BS&amp;rdquo; guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation.</description>
			</item>
			<item>
				<title>Illuminate Your Workflow: Harnessing Candan Strategies for Continuous Improvement and Transparency</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</link>
				<pubDate>Fri, 16 Feb 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</guid>
				<description>Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams.</description>
			</item>
			<item>
				<title>How to Measure Your Organization&#39;s Ability to Improve Value Through Innovation</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</link>
				<pubDate>Mon, 13 Nov 2023 06:56:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</guid>
				<description>A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk.</description>
			</item>
			<item>
				<title>Stop treating the end of the Sprint like a finish line</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</link>
				<pubDate>Thu, 05 Jun 2025 15:30:54 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/</guid>
				<description>The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management for Agile Success</title>
				<link>https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/</guid>
				<description>Evidence-Based Management helps Agile teams make better decisions by using data from four key areas: current value, unrealized value, ability to innovate, and time to market. By collecting and analyzing relevant metrics, teams can prioritize improvements, boost innovation, and deliver more value to customers. Start by tracking a few key metrics with simple tools, then use those insights to guide your team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Stop Starting and Start Finishing: The Key to Team Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>7 harbingers of the Agile apocalypse - Judgement</title>
				<link>https://engineering-leadership-preview.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-preview.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>How Usable Working Products Are Your Ultimate Weapon Against Risks</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</link>
				<pubDate>Tue, 23 Aug 2022 16:53:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</guid>
				<description>The Scaled Professional Scrum course helps teams address common challenges in scaling Scrum, such as managing cross-team dependencies, maintaining self-management, and ensuring transparency. Through hands-on, interactive sessions, participants gain practical techniques and tools to structure and manage large agile projects effectively. Development managers looking to scale Scrum without unnecessary overhead should consider this course to equip their teams with proven practices and ongoing support.</description>
			</item>
			<item>
				<title>Evidence-based Management: Gathering the metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</link>
				<pubDate>Wed, 30 Dec 2020 14:02:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Continuous value delivery with modern business applications</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</link>
				<pubDate>Tue, 27 Nov 2012 23:00:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</guid>
				<description>Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates.</description>
			</item>
			<item>
				<title>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>Mastering Outcomes: How Evidence-Based Management Transforms Your Project Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>From Software Engineer to Scrum Trainer: How My Journey Shapes Effective DevOps Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-software-engineer-to-scrum-trainer-how-my-journey-shapes-effective-devops-training/</link>
				<pubDate>Fri, 20 Jan 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-software-engineer-to-scrum-trainer-how-my-journey-shapes-effective-devops-training/</guid>
				<description>The author’s journey from software engineer to Scrum trainer, including recognition as a Microsoft MVP and extensive DevOps consulting across multiple industries, shapes a practical and relatable training style. Key insights include the value of learning from both successes and failures, the motivational power of real-world stories, and the belief that any team can move toward continuous delivery. Development managers should consider leveraging trainers with hands-on experience to inspire teams and drive meaningful change.</description>
			</item>
			<item>
				<title>Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-tech-hype-how-evidence-based-decisions-empower-real-leadership/</link>
				<pubDate>Fri, 04 Jul 2025 06:00:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-tech-hype-how-evidence-based-decisions-empower-real-leadership/</guid>
				<description>Chasing technology trends because competitors do is not a real strategy; instead, focus on making your systems visible, use evidence to guide decisions, and choose tools that fit your actual needs. This approach helps you defend your roadmap with confidence and creates sustainable results for your teams and business. Prioritise clarity and alignment over hype to lead effectively and avoid unnecessary complexity.</description>
			</item>
			<item>
				<title>The Importance of Delivering Working Software Every Iteration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</link>
				<pubDate>Wed, 26 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</guid>
				<description>Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort.</description>
			</item>
			<item>
				<title>How does a Scrum Master or Agile coach motivate a Scrum Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</link>
				<pubDate>Mon, 11 Sep 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</guid>
				<description>Scrum Masters and Agile coaches play a key role in keeping teams motivated by aligning goals with stakeholder value, celebrating achievements, and fostering open communication. Teams lose motivation when goals are misaligned or stakeholder engagement is lacking, so it is important to set achievable objectives, involve stakeholders, and encourage autonomy and continuous learning. Regularly review team morale, connect work to its broader impact, and create feedback loops to maintain a resilient and high-performing team.</description>
			</item>
			<item>
				<title>Unlocking Agility: How EPS Immersive Learning Transforms Your Team&#39;s Performance</title>
				<link>https://engineering-leadership-preview.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-preview.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 is your favourite DevOps consulting outcome?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/</link>
				<pubDate>Tue, 18 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/</guid>
				<description>A fragmented, multi-billion-dollar software project with 80 to 90 teams across nine countries was transformed by unifying processes and source control onto Azure DevOps, greatly improving collaboration and efficiency. The key outcomes were simplification, system unification, and a shift toward a &amp;lsquo;One Engineering System&amp;rsquo; approach. Development managers should consider consolidating tools and processes to drive similar improvements in productivity and teamwork.</description>
			</item>
			<item>
				<title>What would you advise a scrum team to do in their first 4 weeks?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</link>
				<pubDate>Thu, 16 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</guid>
				<description>In the first four weeks, a scrum team should focus on practicing scrum correctly, learning both what works and what does not, and experimenting to find the best fit for their context. Teams should document obstacles and improvements, address one key change per sprint, and use retrospectives to drive continuous improvement. This approach builds a strong foundation and helps make organizational issues visible for future action.</description>
			</item>
			<item>
				<title>Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</link>
				<pubDate>Sun, 14 Apr 2024 12:17:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</guid>
				<description>Achieving true agility requires more than adopting Agile practices; organisations often fall into seven common traps such as seeking quick fixes, overloading backlogs, focusing on resource utilisation over value, lacking accountability, fostering blame, copying others blindly, and letting pride block learning. These behaviours hinder innovation, value delivery, and team effectiveness. Development managers should regularly assess and address these pitfalls, tailor Agile to their context, and foster a culture of continuous improvement and honest reflection.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile Apocalypse - Famine</title>
				<link>https://engineering-leadership-preview.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-preview.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>Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</link>
				<pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</guid>
				<description>The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement.</description>
			</item>
			<item>
				<title>Professional Scrum is for everyone in your organisation</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>Challenging Misconceptions About Behaviour in Agile Teams</title>
				<link>https://engineering-leadership-preview.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-preview.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>Scrum is like communism, it doesn&#39;t work. Myth 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</link>
				<pubDate>Tue, 24 Oct 2023 06:50:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</guid>
				<description>Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars.</description>
			</item>
			<item>
				<title>How does the APS course help people apply scrum effectively?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</link>
				<pubDate>Wed, 18 Jan 2023 08:57:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</guid>
				<description>The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption.</description>
			</item>
			<item>
				<title>Story Points &amp; Velocity are a sign of an unsuccessful team</title>
				<link>https://engineering-leadership-preview.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-preview.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>You want speed, adaptability, resilience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</link>
				<pubDate>Sun, 11 May 2025 15:30:29 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>How Top Scrum Masters Are Selected by Their Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/</link>
				<pubDate>Wed, 19 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/</guid>
				<description>The most effective Scrum Masters are chosen by their teams based on trust, experience, and proven leadership, not assigned from outside. Teams naturally follow those who have already guided them through challenges and earned their respect. To ensure real impact and avoid resistance, let the team identify who they trust to lead as Scrum Master.</description>
			</item>
			<item>
				<title>The Importance of Validation in Product Development: A Strategic Approach</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking Agile Success: Embrace Continuous Forecasting and Transform Your Training Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/</link>
				<pubDate>Thu, 21 May 2020 05:26:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/</guid>
				<description>Continuous forecasting in Agile, supported by metrics and tools like Monte Carlo simulations, enables teams to plan flexibly and adapt quickly rather than committing to a full sprint plan upfront. Virtual training with interactive tools and follow-up sessions has improved learning and engagement. Development managers should consider adopting continuous forecasting and leveraging available training resources to enhance team performance and responsiveness.</description>
			</item>
			<item>
				<title>Everyone has a disaster recovery plan, on paper</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/</link>
				<pubDate>Wed, 14 May 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/</guid>
				<description>Many organizations have disaster recovery plans, but these often fail in real situations because critical dependencies are overlooked and not tested end to end. Successful drills can give a false sense of security if they do not include all essential systems, like authentication services. To ensure true resilience, regularly test your recovery process under real conditions and verify that all dependencies are restored and functional.</description>
			</item>
			<item>
				<title>Great Scrum Masters and Product Owners don’t micromanage</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</link>
				<pubDate>Sun, 23 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</guid>
				<description>Effective Scrum Masters and Product Owners avoid micromanaging by providing clear direction, supporting team autonomy, and ensuring accountability. Teams perform best when they understand the vision and operate within a structured framework that balances freedom with alignment. Leaders should focus on removing obstacles and maintaining this balance to enable true agility; consider how your organization supports both autonomy and structure.</description>
			</item>
			<item>
				<title>Hiring a Scrum Master is hard</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</link>
				<pubDate>Sun, 16 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>How CTOs Can Cut Through the Noise: Building Real Clarity and Confidence in a World of AI Hype and Microservices Madness</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-ctos-can-cut-through-the-noise-building-real-clarity-and-confidence-in-a-world-of-ai-hype-and-microservices-madness/</link>
				<pubDate>Fri, 16 May 2025 06:00:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-ctos-can-cut-through-the-noise-building-real-clarity-and-confidence-in-a-world-of-ai-hype-and-microservices-madness/</guid>
				<description>CTOs face constant pressure to adopt new technologies like AI and microservices, but chasing every trend often leads to confusion and technical debt. The key is to focus on understanding your organisation’s real challenges, build decision-making capability at all levels, and invest in clarity rather than hype. Partnering with experts who help you see your true constraints and strengths can enable you to set your own pace and lead with confidence.</description>
			</item>
			<item>
				<title>“Teams are self-managing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</link>
				<pubDate>Fri, 21 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</guid>
				<description>Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance.</description>
			</item>
			<item>
				<title>Ditch the Agile Bandit Mentality: How to Prioritise Value Over Estimates for Team Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Focusing Beyond &#34;Agile&#34;: Building True Capability in Organizations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/focusing-beyond-agile-building-true-capability-in-organizations/</link>
				<pubDate>Fri, 11 Oct 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/focusing-beyond-agile-building-true-capability-in-organizations/</guid>
				<description>Focusing only on Agile as a label limits organizational growth; instead, prioritize building real capability, hiring and promoting competent people from within, and fostering continuous learning. Many teams struggle because key roles are filled by underqualified individuals, often due to poor hiring practices and a lack of investment in development. To improve effectiveness and value delivery, hire for potential, promote proven team members, and create a culture where learning and leadership are central.</description>
			</item>
			<item>
				<title>Harnessing Evidence-Based Management: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership-preview.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-preview.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>Combatting the Agile Apocalypse: How to Overcome the Famine of Feedback and Engagement</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</link>
				<pubDate>Wed, 11 Oct 2023 12:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Why is Satya Nadella a better example of agile leadership than Steve Jobs?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</link>
				<pubDate>Wed, 01 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</guid>
				<description>Satya Nadella is a stronger example of agile leadership than Steve Jobs because he built a culture of innovation and empowered teams across Microsoft, rather than centralizing decision-making and innovation in one person. Nadella decentralized authority, focused on meaningful metrics that drive customer value, and fostered continuous improvement and collaboration throughout the organization. Development managers should consider enabling team autonomy and aligning incentives with customer outcomes to drive sustainable innovation.</description>
			</item>
			<item>
				<title>There is no &#34;do agile&#34; there is only &#34;be agile&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-do-agile-there-is-only-be-agile/</link>
				<pubDate>Sun, 01 Sep 2013 22:31:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-do-agile-there-is-only-be-agile/</guid>
				<description>Explores the difference between adopting agile practices superficially and truly embracing agile values, highlighting the need for deep organisational change and continuous learning.</description>
			</item>
			<item>
				<title>Testing in the modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/</link>
				<pubDate>Tue, 25 Sep 2012 02:00:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/</guid>
				<description>Explores challenges and solutions for manual testing in agile software development, focusing on tracking, automation, actionable bugs, and integrated test management tools.</description>
			</item>
			<item>
				<title>Balance of Leadership and Control in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</link>
				<pubDate>Mon, 17 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</guid>
				<description>Scrum Masters and Product Owners are expected to deliver results, so they need both influence and enough authority to remove obstacles, enforce alignment, and ensure accountability. Too much control stifles team autonomy, but too little makes teams ineffective; the right balance depends on the organisation and situation. Development managers should empower these roles with the authority needed to drive change while maintaining team ownership and continuous improvement.</description>
			</item>
			<item>
				<title>Unlocking Continuous Delivery: How Feature Flags Transform Software Development</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking the Future of Software Development: Why Automation is Your Key to Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</link>
				<pubDate>Wed, 15 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</guid>
				<description>Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management in Agile: Inform, Don’t Control</title>
				<link>https://engineering-leadership-preview.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-preview.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>What is the Sprint Review workshop and how will it help organisations?</title>
				<link>https://engineering-leadership-preview.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-preview.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>Professional Scrum Training for the Ghana Police Service</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</link>
				<pubDate>Mon, 30 Oct 2017 19:26:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</guid>
				<description>The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>Scrum doesn&#39;t solve problems, it reveals them. How, and why is that valuable?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</link>
				<pubDate>Wed, 27 Sep 2023 07:00:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</guid>
				<description>Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation.</description>
			</item>
			<item>
				<title>Harnessing the Power of Empiricism: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Everyone loves the idea of self-managing teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</link>
				<pubDate>Tue, 18 Mar 2025 09:51:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</guid>
				<description>Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability.</description>
			</item>
			<item>
				<title>Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</link>
				<pubDate>Tue, 01 May 2018 01:02:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</guid>
				<description>The US Department of Defense has updated its procurement rules to require agile, iterative development instead of traditional waterfall methods, following high-profile failures like the FBI’s Sentinel project. Agile approaches have proven to deliver higher success rates, lower costs, and reduced risk, and these changes are now influencing government and vendor practices across the US and UK. Development managers working with government clients should adopt agile methods to align with new regulations and improve project outcomes.</description>
			</item>
			<item>
				<title>My journey into Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</link>
				<pubDate>Wed, 04 Feb 2015 10:53:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</guid>
				<description>Professional Scrum has been key to my success in software development and consulting, showing that most team challenges are cultural rather than technical. Building professional, adaptable individuals and teams leads to greater business agility and consistent delivery of valuable software. Avoid one-size-fits-all approaches to scaling Scrum; instead, tailor frameworks and practices to your organisation’s unique culture and needs.</description>
			</item>
			<item>
				<title>Overcoming Project Blockers and Challenging Organisational Inertia</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/</link>
				<pubDate>Sat, 22 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/</guid>
				<description>Teams are often held responsible for project outcomes without having the authority to remove blockers or challenge ineffective practices, which leads to frustration and failure. True accountability requires giving teams both autonomy and the power to influence their environment. Development managers should ensure teams have the authority needed to address obstacles and drive results, not just the responsibility.</description>
			</item>
			<item>
				<title>No one questions a Product Owner authority</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</link>
				<pubDate>Wed, 19 Mar 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/</guid>
				<description>Product Owners are trusted with authority to make decisions that drive product success, but Scrum Masters often lack similar authority despite being responsible for team effectiveness and removing obstacles. Relying only on persuasion limits their impact; Scrum Masters need the power to enforce good practices and address issues directly. Development managers should ensure Scrum Masters have the authority needed to fulfill their role and support team agility.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Critical Role of User Feedback in Requirement Changes</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</link>
				<pubDate>Mon, 06 May 2024 14:12:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</guid>
				<description>Many common beliefs about Scrum, such as it being just meetings, requiring story points, encouraging micromanagement, lacking planning, or having no governance, are misconceptions that hinder its effectiveness. Scrum events are purposeful, story points are optional, teams should self-organise, planning is integral, and governance is flexible to business needs. Development managers should challenge these myths to help teams fully benefit from Agile and deliver greater value.</description>
			</item>
			<item>
				<title>Redefining Agile’s Core: Beyond Rituals and Procedures</title>
				<link>https://engineering-leadership-preview.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-preview.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>Agile Leadership: Empowering Managers with the Right Skills</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</link>
				<pubDate>Fri, 26 May 2023 14:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</guid>
				<description>Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes.</description>
			</item>
			<item>
				<title>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</guid>
				<description>A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: Why Understanding Product Vision is Key to Success</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Importance of Evidence-Based Management in Agile Environments</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</link>
				<pubDate>Thu, 12 Oct 2023 08:32:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</guid>
				<description>An APS course is valuable for Scrum teams that want to deepen their understanding of core Scrum principles and shed ineffective practices that may have accumulated over time. It helps teams focus on delivering a working product each iteration and provides practical exercises, like the Barnacle Exercise, to identify and remove process inefficiencies. Consider APS if your team needs to realign with authentic Scrum practices and drive meaningful agile transformation.</description>
			</item>
			<item>
				<title>Mastering Scrum: Effective Planning and Prioritisation for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/</link>
				<pubDate>Fri, 24 Mar 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/</guid>
				<description>Effective Scrum planning and prioritisation require aligning work with business goals, regularly communicating with stakeholders, and keeping the product backlog lean and focused on near-term priorities. Use a simple value, risk, and size formula to help order backlog items, and continuously adjust based on customer data and outcomes. Keep your backlog manageable and iterate often to ensure your team delivers meaningful results that support business objectives.</description>
			</item>
			<item>
				<title>Kendall Guide - A System of Work for AI Adoption</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kendall-guide/</link>
				<pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Would you hire a Junior CISO? A Junior Financial Director</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/</link>
				<pubDate>Mon, 17 Feb 2025 10:06:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/</guid>
				<description>Hiring a junior Scrum Master is risky because the role requires proven expertise in technical, business, and organisational areas from the start, similar to senior roles like CISO or Financial Director. Scrum Masters must lead teams and drive change, not learn on the job. Only hire experienced Scrum Masters to ensure your team&amp;rsquo;s success and true agility.</description>
			</item>
			<item>
				<title>Daily Scrum Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</guid>
				<description>Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals.</description>
			</item>
			<item>
				<title>The Power of Metrics: Why PAL-EBM is Essential for Your Organization</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</link>
				<pubDate>Tue, 28 Nov 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</guid>
				<description>The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</link>
				<pubDate>Mon, 23 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</guid>
				<description>Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions.</description>
			</item>
			<item>
				<title>Create a Release Management pipeline for Professional Developers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</link>
				<pubDate>Thu, 04 Dec 2014 12:15:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</guid>
				<description>This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles.</description>
			</item>
			<item>
				<title>Avoid the Bug as Task anti-pattern in Azure DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</link>
				<pubDate>Wed, 06 Aug 2014 14:46:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</guid>
				<description>Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers guidance for agile teams to avoid it.</description>
			</item>
			<item>
				<title>Does your company culture resemble Survivor?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/</link>
				<pubDate>Wed, 10 Jul 2013 19:37:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/</guid>
				<description>Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering teamwork in software development.</description>
			</item>
			<item>
				<title>Scrum isn’t limited to building features</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</link>
				<pubDate>Fri, 30 May 2025 15:30:41 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</guid>
				<description>Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Organizational Structure</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</link>
				<pubDate>Fri, 08 Sep 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</guid>
				<description>Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Transforming Agile Training into Action: Experimentation and Engagement in the Workplace</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agile-training-into-action-experimentation-and-engagement-in-the-workplace/</link>
				<pubDate>Mon, 24 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agile-training-into-action-experimentation-and-engagement-in-the-workplace/</guid>
				<description>Agile training is most effective when participants actively experiment with new tools and techniques in their own work environments, adapting them to fit their team’s context. Techniques like &amp;ldquo;One, Two, Four, All&amp;rdquo; foster inclusive engagement and help turn group ideas into actionable plans, even in virtual settings. Development managers should encourage their teams to try these approaches and create safe spaces for sharing, which leads to better collaboration and practical results.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning for Product Management</title>
				<link>https://engineering-leadership-preview.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-preview.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>How to Discover Unrealized Value in Your Product</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>What my father taught me about Evidence-based Management (34 years before it was invented!)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</guid>
				<description>Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in both business and software contexts.</description>
			</item>
			<item>
				<title>Unlocking Agile Leadership: Transform Your Skills with Scrum.org&#39;s Essentials Workshop</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-leadership-transform-your-skills-with-scrum-org&#39;s-essentials-workshop/</link>
				<pubDate>Tue, 07 Jul 2020 20:10:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-leadership-transform-your-skills-with-scrum-org&#39;s-essentials-workshop/</guid>
				<description>The Scrum.org Professional Agile Leadership Essentials workshop helps leaders shift from traditional management to effective agile leadership by providing hands-on learning, practical coaching skills, and tools for driving cultural change. It emphasises organisational alignment and collaboration, enabling leaders to support agile teams and measure the impact of agility. Attending this workshop can help you guide your teams through agile transformation and improve your organisation’s responsiveness and performance.</description>
			</item>
			<item>
				<title>TFS for cross team and cross business line work item tracking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/</link>
				<pubDate>Tue, 04 Mar 2014 16:34:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/</guid>
				<description>Explains how to use a single Team Project and Team Field in TFS to streamline cross-team work item tracking, reporting, and collaboration across business lines.</description>
			</item>
			<item>
				<title>Design Sprints in Scrum: Common Questions and Practical Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</link>
				<pubDate>Wed, 04 Jun 2025 15:31:05 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</guid>
				<description>There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.</description>
			</item>
			<item>
				<title>Scrum Myth Debunked: Unfinished Work is Allowed in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</link>
				<pubDate>Sat, 24 May 2025 15:30:17 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</guid>
				<description>Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries.</description>
			</item>
			<item>
				<title>In what circumstances is agile consulting appropriate?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/there-is-no-place-like-production/</link>
				<pubDate>Mon, 28 Dec 2020 14:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>Navigating DevOps: Crafting Unique Solutions for Unique Organizations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-devops-crafting-unique-solutions-for-unique-organizations/</link>
				<pubDate>Fri, 23 Aug 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-devops-crafting-unique-solutions-for-unique-organizations/</guid>
				<description>DevOps success depends on tailoring solutions to your organization’s unique context rather than following a one-size-fits-all approach. Bringing in external experts can provide valuable new perspectives and help spark innovation, while long-term commitment to continuous improvement and adaptation is essential. Focus on developing a flexible DevOps philosophy, regularly refine your practices, and seek outside help when needed to sustain progress.</description>
			</item>
			<item>
				<title>Maximizing Transparency and Improvement in Software Engineering with Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</link>
				<pubDate>Mon, 29 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</guid>
				<description>Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement.</description>
			</item>
			<item>
				<title>Does Your Team Truly Understand Your Product Vision and Goals?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Key Skills Scrum Masters Need: Technical, Business, Organisational</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/addressing-systemic-issues-in-agile-organizations/</link>
				<pubDate>Wed, 24 Jan 2024 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>From Developer to Agile Advocate: How My Journey Unveiled the Power of Scrum and DevOps</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>From Control to Collaboration: How Project Managers Can Embrace Agility and Thrive</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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 to Tackle the Challenge of an Ineffective Product Owner in Agile Teams</title>
				<link>https://engineering-leadership-preview.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-preview.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>Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</link>
				<pubDate>Mon, 09 Jan 2023 12:36:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</guid>
				<description>Teaching Scrum through hands-on experience, including using Minecraft, helps participants move from initial chaos to a clear understanding of Scrum’s value. Students first experience confusion similar to real project starts, then learn to apply Scrum principles, leading to practical insights and improved teamwork. Development managers should consider experiential learning to help teams internalise agile practices and appreciate their real-world benefits.</description>
			</item>
			<item>
				<title>Maximising Value from Applying Professional Scrum Training</title>
				<link>https://engineering-leadership-preview.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-preview.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>How I Used Generative AI to Transform Site Tagging and Categories</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/</link>
				<pubDate>Thu, 15 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/</guid>
				<description>Migrating a large, legacy blog to Hugo enabled the use of generative AI for automated tagging and categorisation, significantly improving content discoverability and editorial consistency while reducing manual effort. The system combines AI-driven suggestions with human oversight, using multi-factor scoring, penalty logic, and transparent reasoning to ensure quality and accountability. Development managers considering similar automation should maintain human control over final decisions and leverage AI to streamline, not replace, editorial processes.</description>
			</item>
			<item>
				<title>At the end of the day, Kanban is about improving flow</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>How Immersive Learning Transforms Aspiring Agile Leaders</title>
				<link>https://engineering-leadership-preview.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-preview.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>Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness</title>
				<link>https://engineering-leadership-preview.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-preview.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>Resilience is not a department</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/resilience-is-not-a-department/</link>
				<pubDate>Sat, 17 May 2025 15:30:21 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/resilience-is-not-a-department/</guid>
				<description>Resilience must be built into your product from the start, not treated as a separate concern or afterthought. Focusing only on performance, cost, or speed can lead to fragile systems that fail in real-world conditions. Make sure your disaster recovery plans are tested under real scenarios, not just documented, to avoid turning your product into a liability.</description>
			</item>
			<item>
				<title>Scrum Masters: Why Influence Alone May Not Be Enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</link>
				<pubDate>Thu, 20 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</guid>
				<description>Relying only on influence limits a Scrum Master&amp;rsquo;s ability to drive real change, especially when teams or leaders resist Agile practices. Sustainable agility needs Scrum Masters who can enforce the framework, remove obstacles, and hold teams accountable, not just suggest improvements. Development managers should ensure Scrum Masters have enough authority to lead effectively, not just influence.</description>
			</item>
			<item>
				<title>How Do You Know How Long It Takes to Deliver Value?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>7 deadly sins of Agile: Gluttony</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/</link>
				<pubDate>Wed, 11 Oct 2023 11:35:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Why Frameworks Alone will-not Transform Your Team Culture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-frameworks-alone-will-not-transform-your-team-culture/</link>
				<pubDate>Wed, 28 May 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-frameworks-alone-will-not-transform-your-team-culture/</guid>
				<description>Relying on frameworks alone will not change your team culture; the main barriers are existing habits and lack of true commitment. Real transformation requires a clear vision, visible leadership support, and active involvement from everyone to identify and address obstacles. As a development manager, focus on building shared understanding and genuine engagement rather than just rolling out new processes.</description>
			</item>
			<item>
				<title>Breaking Free from Vendor Lock-In: How to Regain Control and Future-Proof Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-free-from-vendor-lock-in-how-to-regain-control-and-future-proof-your-business/</link>
				<pubDate>Mon, 19 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-free-from-vendor-lock-in-how-to-regain-control-and-future-proof-your-business/</guid>
				<description>Vendor lock-in from legacy contracts and proprietary systems limits your team’s ability to adapt, often forcing you to work around outdated decisions and maintain inflexible vendor models. To regain control, identify your real constraints, map dependencies, and enable transparent decision-making that prioritises your business needs. Focus on building flexibility into your systems and processes rather than simply replacing tools, and start by challenging existing assumptions and mapping where you are truly locked in.</description>
			</item>
			<item>
				<title>Why Cost-Cutting During Recessions Is Counterproductive</title>
				<link>https://engineering-leadership-preview.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-preview.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>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-preview.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-preview.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-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</link>
				<pubDate>Fri, 07 Oct 2022 10:41:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</guid>
				<description>Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs.</description>
			</item>
			<item>
				<title>Professional Organisational Change at the Ghana Police Service</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-organisational-change-at-the-ghana-police-service/</link>
				<pubDate>Mon, 04 Sep 2017 13:09:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-organisational-change-at-the-ghana-police-service/</guid>
				<description>The Ghana Police Service is undergoing a major transformation to address long-standing issues by adopting a clear vision, a strategic framework based on Scrum, and empowering change agents across the organization. Top leadership, including the IGP and the President, are fully committed, and the approach emphasizes servant leadership, transparency, and adapting frameworks like Kanban to fit unique team needs. Development managers should note that lasting change requires a flexible framework rather than rigid methodologies, with leadership focused on enabling teams rather than controlling them.</description>
			</item>
			<item>
				<title>Unlocking Agility: How Decentralisation Empowers Teams to Maximise Value in Any Organisation</title>
				<link>https://engineering-leadership-preview.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-preview.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 handle conflict in a Scrum Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</link>
				<pubDate>Mon, 07 Oct 2019 16:32:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</guid>
				<description>When conflict arises in a Scrum Team, first encourage the team to resolve it themselves and use facilitation techniques that ensure everyone is heard, such as structured group discussions. The Scrum Master should coach team members and escalate only if necessary, involving HR or considering team changes as a last resort. Focus on building conflict resolution skills within the team and iteratively adapt your approach to find the best solution.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking Agile Consulting: Transform Your Organisation with Diverse Strategies and Continuous Learning</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</link>
				<pubDate>Mon, 05 Jun 2023 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</guid>
				<description>The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team&amp;rsquo;s unique context. Flexibility and continuous improvement are more important than strict adherence to the framework, so use Scrum as a guide and modify it as needed to maximize value and innovation. Encourage your teams to experiment and iterate, focusing on what works best for your organization.</description>
			</item>
			<item>
				<title>Finding the problem on a partially succeeded build on Team Foundation Build Services 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/finding-the-problem-on-a-partially-succeeded-build-on-team-foundation-build-services-2010/</link>
				<pubDate>Thu, 04 Mar 2010 17:48:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/finding-the-problem-on-a-partially-succeeded-build-on-team-foundation-build-services-2010/</guid>
				<description>Learn how to diagnose and resolve partially succeeded builds in Team Foundation Build Services 2010 by tracing test failures, identifying code issues, and managing bugs.</description>
			</item>
			<item>
				<title>Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training</title>
				<link>https://engineering-leadership-preview.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-preview.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>David thought he already knew Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</link>
				<pubDate>Mon, 26 May 2025 15:30:28 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</guid>
				<description>Even experienced teams often fall into old habits and misunderstand Scrum, leading to ineffective practices that only look agile on the surface. Regularly revisiting the fundamentals and purpose of Scrum helps prevent complacency and ensures real improvement. Consider challenging your team&amp;rsquo;s understanding of Scrum to maintain true agility and drive meaningful change.</description>
			</item>
			<item>
				<title>Companies often say &#34;we-are going Agile!&#34; as if declaring it makes it so</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Is a PSM II certification validation of your skills, or does it develop your skill and capability as a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</link>
				<pubDate>Mon, 17 Apr 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/</guid>
				<description>The PSM II course is designed to develop your skills and capabilities as a Scrum Master, not just validate what you already know. The class focuses on advanced facilitation techniques and deepens your understanding of Scrum Master accountability to the team, Product Owner, and organization. If you want to grow as a Scrum Master and apply practical tools with your teams, attending the course is recommended over just taking the assessment.</description>
			</item>
			<item>
				<title>Open-source with VSTS or TFS and Github for better DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</link>
				<pubDate>Tue, 10 May 2016 16:19:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</guid>
				<description>You can use VSTS or TFS for full DevOps and agile capabilities while keeping your open-source code on Github by setting up automated two-way synchronization between the platforms. This approach lets you manage private work and processes in VSTS, then publish selected branches to Github for public access and contributions. Set up automated builds in VSTS to sync code in both directions, using personal tokens for authentication, so you get the best of both tools without extra manual effort.</description>
			</item>
			<item>
				<title>Transform Your Product Development: Unleash the Power of Experimentation and Collaboration</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Myth of Knowing Everything Upfront in Software Development</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</link>
				<pubDate>Sun, 04 May 2025 15:30:30 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</guid>
				<description>Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team&amp;rsquo;s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance.</description>
			</item>
			<item>
				<title>Lack of Authority Blocks Progress on Critical Projects</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</link>
				<pubDate>Sun, 16 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</guid>
				<description>Scrum Masters need real authority to remove obstacles and drive project success, but many are blocked by bureaucracy and lack of support. Without empowerment, they cannot be held accountable for outcomes and become ineffective. Development managers should ensure Scrum Masters have the authority to act if they expect meaningful results.</description>
			</item>
			<item>
				<title>Navigating Complexity: How to Foster Agility and Innovation in Business Decision-Making</title>
				<link>https://engineering-leadership-preview.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-preview.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>Navigating Client Needs: How Agile Consultants Can Uncover True Value Beyond Initial Requests</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/guides/evidence-based-portfolio-management/</link>
				<pubDate>Wed, 16 Dec 2020 13:11:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>Transforming Scope Creep into Success: Embrace Agility and Deliver Value in a Changing Market</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</link>
				<pubDate>Wed, 25 Oct 2023 13:30:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</guid>
				<description>Effective planning is essential for Agile and Scrum teams, not something to skip; key Scrum events like sprint planning, backlog refinement, and daily standups all revolve around planning. The goal is to find the right balance, plan enough to provide direction and coordination, especially in large teams, but avoid over-planning that wastes resources. Development managers should ensure their teams have clear goals, roadmaps, and themes to align efforts and adapt as needed.</description>
			</item>
			<item>
				<title>Rethinking Product Backlog: Navigating Through the Weeds of Complexity</title>
				<link>https://engineering-leadership-preview.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-preview.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>Why do you think the PSU course has become so popular for product development?</title>
				<link>https://engineering-leadership-preview.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-preview.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>Delivering Live Virtual Classes in Microsoft Teams and Mural</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/</link>
				<pubDate>Sun, 21 Jun 2020 21:40:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/</guid>
				<description>Delivering live virtual classes using Microsoft Teams and Mural offers strong security, flexibility, and features that support self-organising teams and foster a safe, collaborative learning environment. Running a tech check before classes saves time and sets expectations, while Teams enables students to manage their own breakout sessions and resources, promoting autonomy and engagement. For best results, set up Teams in advance and use Mural to create structured, interactive exercises that mirror in-person collaboration.</description>
			</item>
			<item>
				<title>Getting Started with Objectives &amp; Key Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-objectives-key-results/</link>
				<pubDate>Mon, 18 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</link>
				<pubDate>Wed, 11 Jun 2025 15:30:44 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/</guid>
				<description>The FBI&amp;rsquo;s Sentinel project failed after years and massive spending using a traditional waterfall approach, delivering nothing. Switching to a small, focused Agile team produced a working product in a year at a fraction of the cost. Consider adopting iterative methods to avoid wasted time and resources and deliver real value sooner.</description>
			</item>
			<item>
				<title>You can’t deliver change through memos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</link>
				<pubDate>Sat, 31 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</guid>
				<description>Change cannot be achieved through memos or top-down mandates; real progress happens when everyone is trained together and understands the reasons behind new approaches. Broad-based training helps people identify problems and suggest improvements, making change more effective and sustainable. To drive meaningful change, involve all stakeholders in learning and improvement, not just managers or specialists.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>Unlocking the Power of Assumptions in Product Development: Why the PPDV Course is a Game-Changer</title>
				<link>https://engineering-leadership-preview.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-preview.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>How to Achieve Predictability in Business through Agile Principles</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</link>
				<pubDate>Mon, 13 Feb 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</guid>
				<description>Scrum does not directly acquire or retain customers, but it helps teams deliver value quickly and adapt based on customer feedback, which can lead to competitive advantage. Its main strengths are making problems and opportunities visible, enabling rapid execution, and supporting a culture of innovation, but leaders and teams must still identify what customers need and how to deliver it. To succeed, focus on building strong teams, understanding market value, and using Scrum to consistently deliver and validate valuable features.</description>
			</item>
			<item>
				<title>Why are recessions a great time for organizations to evaluate the opportunity of agile?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Quality enablement with Visual Studio 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</link>
				<pubDate>Wed, 15 May 2013 03:13:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</guid>
				<description>Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations in Alameda, California</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</link>
				<pubDate>Fri, 26 Oct 2012 16:30:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</guid>
				<description>Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles in the development process.</description>
			</item>
			<item>
				<title>What&#39;s in a burndown?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</link>
				<pubDate>Wed, 28 Mar 2012 03:52:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</guid>
				<description>Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.</description>
			</item>
			<item>
				<title>My first Scrum team in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</link>
				<pubDate>Sun, 03 Apr 2011 21:44:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</guid>
				<description>A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.</description>
			</item>
			<item>
				<title>US Department of Defence and the History of Waterfall Delivery</title>
				<link>https://engineering-leadership-preview.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-preview.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>Transforming Training: How Immersive Learning and DevOps Drive Real Value in Organisations</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Scrum is not an engineering process</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</link>
				<pubDate>Wed, 21 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-an-engineering-process/</guid>
				<description>Scrum is a framework for fostering collaboration across the whole organisation, not just an engineering process for developers. True agility happens when everyone, regardless of role, understands and participates in Scrum, which helps break down silos and exposes issues that slow delivery. To achieve real change, ensure your entire team is aligned and involved in the conversation about how value is delivered.</description>
			</item>
			<item>
				<title>Navigating the Complex World of Azure DevOps Data Migration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-complex-world-of-azure-devops-data-migration/</link>
				<pubDate>Wed, 31 Jul 2024 12:00:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-complex-world-of-azure-devops-data-migration/</guid>
				<description>Migrating to Azure DevOps is complex, especially with legacy systems, but careful planning and attention to detail can prevent most issues. Key steps include importing legacy data before upgrades, aligning user identities to avoid workflow disruptions, cleaning up databases to meet size limits, and strictly following Microsoft’s backup procedures. Development managers should prioritize preparation and sequencing to ensure a smooth migration and minimize risks.</description>
			</item>
			<item>
				<title>The Evolution of Product Management in the Agile Era</title>
				<link>https://engineering-leadership-preview.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-preview.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>Continuous Adaptation: The Key to Success in a Dynamic Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/continuous-adaptation-the-key-to-success-in-a-dynamic-market/</link>
				<pubDate>Fri, 19 Jan 2024 06:08:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/continuous-adaptation-the-key-to-success-in-a-dynamic-market/</guid>
				<description>Success in today’s fast-changing market depends on a business’s ability to adapt quickly and continuously, guided by flexible principles rather than rigid rules. Companies that empower teams, encourage innovation, and stay agile are better positioned to outperform competitors, maintain productivity during disruptions, and deliver greater customer value. Development managers should foster a culture of adaptability and regularly review business practices to ensure ongoing relevance and competitiveness.</description>
			</item>
			<item>
				<title>What more needs to happen before traditional organisations consider Agile?</title>
				<link>https://engineering-leadership-preview.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-preview.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>OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/okr-guide/</link>
				<pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>How Does Your Consulting Experience Manifest in the Training Environment?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-your-consulting-experience-manifest-in-the-training-environment/</link>
				<pubDate>Wed, 21 Jun 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-your-consulting-experience-manifest-in-the-training-environment/</guid>
				<description>Training is most effective when led by someone with real consulting experience, as it brings practical, relatable examples that bridge the gap between theory and real-world challenges. Sharing authentic stories from consulting helps teams engage, learn, and apply concepts like Agile and Scrum more effectively. Consider choosing training programs led by experienced consultants to ensure your teams gain actionable insights they can use immediately.</description>
			</item>
			<item>
				<title>In WIP, less is more.  Why?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-wip-less-is-more-why/</link>
				<pubDate>Tue, 09 May 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Product Goal is an Intermediate Strategic Goal</title>
				<link>https://engineering-leadership-preview.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-preview.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>Why Embracing Automation is Essential for Reducing Human Error in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/</link>
				<pubDate>Wed, 18 Dec 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/</guid>
				<description>Automation is essential in software development because it reduces human error, speeds up feedback, and creates more reliable processes. Relying on manual steps leads to costly mistakes and unsustainable workloads, while automation enables faster, higher-quality releases and happier customers. Development managers should prioritise automating repetitive tasks and rearchitecting processes that cannot be automated to improve quality and efficiency.</description>
			</item>
			<item>
				<title>What would be an example of a great agile consulting outcome for a client?</title>
				<link>https://engineering-leadership-preview.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-preview.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>Human and AI Agency in Adaptive Systems: Strategy Before Optimisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/human-and-ai-agency-in-adaptive-systems-strategy-before-optimisation/</link>
				<pubDate>Mon, 30 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/human-and-ai-agency-in-adaptive-systems-strategy-before-optimisation/</guid>
				<description>Human decision-making is essential for setting strategy, purpose, and adapting to change, while AI should be used for tactical optimisation within clear human-defined boundaries. Over-relying on AI for adaptation leads to fragile systems, loss of accountability, and strategic obsolescence. Development managers should ensure humans remain responsible for strategic direction and adaptation, using AI only to optimise within those parameters.</description>
			</item>
			<item>
				<title>Unlocking Agile Mastery: How the Minecraft Case Study Transforms Training and Team Dynamics</title>
				<link>https://engineering-leadership-preview.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-preview.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>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.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-preview.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>Navigating the Balance: How Lean Governance Can Boost Agility and Innovation in Your Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-balance-how-lean-governance-can-boost-agility-and-innovation-in-your-organisation/</link>
				<pubDate>Sun, 09 Feb 2025 22:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-balance-how-lean-governance-can-boost-agility-and-innovation-in-your-organisation/</guid>
				<description>Excessive or siloed governance can slow down your organisation and stifle innovation, often leading to unnecessary processes that do not add value. Focusing on lean governance by regularly reviewing policies, integrating compliance into your tools, and eliminating waste helps maintain agility and efficiency. Review your current governance practices and remove or streamline anything that does not directly support compliance or business value.</description>
			</item>
			<item>
				<title>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</link>
				<pubDate>Thu, 15 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</guid>
				<description>Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions.</description>
			</item>
			<item>
				<title>Navigating the Future with a Fine-Tuned Product Backlog</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking Agile Mastery: Why Spaced Learning Outshines Traditional Courses</title>
				<link>https://engineering-leadership-preview.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-preview.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>Scaling Smart: How to Build Sustainable Growth Without the Chaos</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</link>
				<pubDate>Wed, 08 May 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</guid>
				<description>Traditional two-day Scrum training is ineffective for lasting change because participants retain little and struggle to apply what they learn. Immersive learning, with shorter sessions spread over time, hands-on assignments, and ongoing feedback, leads to better retention, practical application, and continuous improvement. Development managers should consider adopting immersive training formats to drive real, sustainable transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</link>
				<pubDate>Wed, 30 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</guid>
				<description>Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs.</description>
			</item>
			<item>
				<title>Can organisations run an Applying Professional Scrum workshop? How would that help them?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</link>
				<pubDate>Wed, 29 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>What is a common mistake made by rookie agile consultants?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-common-mistake-made-by-rookie-agile-consultants/</link>
				<pubDate>Fri, 17 Feb 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-common-mistake-made-by-rookie-agile-consultants/</guid>
				<description>Rookie agile consultants often make the mistake of rigidly applying frameworks like Scrum without understanding or addressing the unique needs and goals of each team, believing that simply following the rules will guarantee success. This dogmatic approach overlooks the importance of context, empiricism, and helping teams understand the purpose behind agile practices. Development managers should ensure agile adoption is tailored to their team&amp;rsquo;s specific challenges and objectives, focusing on continuous learning and adaptation rather than just process compliance.</description>
			</item>
			<item>
				<title>Most companies still get Product Ownership wrong</title>
				<link>https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</guid>
				<description>Many companies misunderstand the Product Owner role, treating it as simple backlog management or assigning it to any business analyst, which leads to weak products and misaligned teams. Effective Product Owners are strategic leaders who own the vision, make tough decisions, and use evidence to guide development. Development managers should ensure they are hiring or empowering true Product Owners with the right skills and authority, not just filling a position.</description>
			</item>
			<item>
				<title>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</link>
				<pubDate>Mon, 24 Feb 2025 07:26:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</guid>
				<description>The idea of a &amp;ldquo;junior Scrum Master&amp;rdquo; is misleading because the role demands significant experience, technical knowledge, and the ability to navigate complex team and organisational dynamics. Assigning this responsibility to inexperienced team members undermines both individual growth and team effectiveness. Development managers should ensure that Scrum Masters are chosen based on proven competence and relevant experience, not as entry-level positions.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Key to Agile Success</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.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>Transform Your Agile Training: The Power of Immersive Learning for Lasting Impact</title>
				<link>https://engineering-leadership-preview.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-preview.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>Solution: Testing Web Services with MSTest on Team Foundation Build Services 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/</link>
				<pubDate>Thu, 04 Mar 2010 13:15:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/</guid>
				<description>Explains how to configure MSTest for automated testing of web services on Team Foundation Build Services 2010, including handling dynamic server ports and build environments.</description>
			</item>
			<item>
				<title>From Control to Empowerment: Embracing Agile Leadership in a Complex World</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-control-to-empowerment-embracing-agile-leadership-in-a-complex-world/</link>
				<pubDate>Wed, 09 Aug 2023 13:43:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-control-to-empowerment-embracing-agile-leadership-in-a-complex-world/</guid>
				<description>Traditional management works well for predictable problems but falls short in today’s complex, fast-changing environment. Agile leadership empowers teams, encourages collaboration, and fosters innovation by shifting focus from control to enabling people. Development managers should move from directing every detail to creating environments where teams can adapt and thrive.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</link>
				<pubDate>Thu, 01 Aug 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</guid>
				<description>Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive.</description>
			</item>
			<item>
				<title>The Evolution of Agile Learning: Insights from Scrum.org&#39;s Webinar</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-evolution-of-agile-learning-insights-from-scrum-org&#39;s-webinar/</link>
				<pubDate>Thu, 14 Dec 2023 14:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-evolution-of-agile-learning-insights-from-scrum-org&#39;s-webinar/</guid>
				<description>Immersive learning, which combines incremental classroom sessions, real-world assignments, and facilitated reflection over several weeks, is proving far more effective than traditional short-term training for Agile and Scrum. This approach leads to better knowledge retention, practical application, and lasting change in participants’ skills and mindsets. Development managers should consider shifting from traditional workshops to immersive programs to achieve meaningful improvements in team performance and learning outcomes.</description>
			</item>
			<item>
				<title>How will the immersive learning experience help coach people on the job?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>The market isn’t slowing down for anyone</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</link>
				<pubDate>Mon, 26 Feb 2024 14:06:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</guid>
				<description>Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow.</description>
			</item>
			<item>
				<title>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</link>
				<pubDate>Wed, 03 Apr 2024 17:21:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</guid>
				<description>Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team&amp;rsquo;s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team&amp;rsquo;s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results.</description>
			</item>
			<item>
				<title>Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>How do you select the most valuable items for the sprint backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</link>
				<pubDate>Tue, 30 May 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</guid>
				<description>Selecting the most valuable items for the sprint backlog requires input from business, product, and engineering perspectives, not just following the product backlog order. It is a collaborative process where the team and stakeholders align on priorities to ensure each sprint delivers real value. Development managers should facilitate open discussions to balance strategic goals and technical needs when planning sprints.</description>
			</item>
			<item>
				<title>Why should I use Visual Studio ALM</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/</link>
				<pubDate>Wed, 07 Jan 2015 15:39:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/</guid>
				<description>Visual Studio ALM offers a comprehensive set of features beyond just source control and build, covering requirements, project, change, quality, feedback, defect, release, and analytics management in one integrated platform. Replacing it with tools like Git and Jenkins means losing most of this functionality and facing significant integration and maintenance challenges. Development managers should carefully assess what capabilities they need and consider the long-term effort required to replicate Visual Studio ALM’s end-to-end support before switching tools.</description>
			</item>
			<item>
				<title>Migrating source from Perforce to Git on VSO</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</link>
				<pubDate>Wed, 20 Aug 2014 14:06:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</guid>
				<description>Step-by-step guide to migrating source code from Perforce to Git on VSO, covering repository setup, dependency management, build processes, and key migration tips.</description>
			</item>
			<item>
				<title>Searching for self-organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/searching-for-self-organisation/</link>
				<pubDate>Wed, 31 Jul 2013 09:38:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/searching-for-self-organisation/</guid>
				<description>Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and consistency for effective collaboration.</description>
			</item>
			<item>
				<title>Virtual Labs in the modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/virtual-labs-in-the-modern-application-lifecycle/</link>
				<pubDate>Sat, 22 Sep 2012 05:22:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/virtual-labs-in-the-modern-application-lifecycle/</guid>
				<description>Explores how virtual labs help development and operations teams manage, test, and automate complex modern application environments using virtualisation technologies.</description>
			</item>
			<item>
				<title>Full-fidelity history and data migration are mutually exclusive</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/</link>
				<pubDate>Tue, 29 May 2012 01:24:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/</guid>
				<description>Explains why preserving complete historical data and accurate dates is often incompatible with data migration, especially for compliance and traceability in regulated industries.</description>
			</item>
			<item>
				<title>Scrum is hard to adopt and disruptive to your organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</link>
				<pubDate>Thu, 22 Sep 2011 01:17:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</guid>
				<description>Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful organisational change and Agile adoption.</description>
			</item>
			<item>
				<title>Why you need to tag your build servers in TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-you-need-to-tag-your-build-servers-in-tfs/</link>
				<pubDate>Mon, 14 Jun 2010 18:11:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-you-need-to-tag-your-build-servers-in-tfs/</guid>
				<description>Tagging build servers in TFS helps manage dependencies, assign builds to suitable agents, and streamline workflows across teams and regions for reliable automation.</description>
			</item>
			<item>
				<title>How much of an impact can a strong, skilled product owner have?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</link>
				<pubDate>Tue, 16 May 2017 10:40:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</guid>
				<description>For agile software teams using TFS or VSTS, choose the Scrum process template to minimize friction and avoid legacy constraints found in the Agile and CMMI templates. The Scrum template is lightweight, flexible, and easier to customize for your team&amp;rsquo;s needs, while the other templates enforce outdated practices and create unnecessary barriers. Start with the Scrum template and tailor it as needed to support your workflow and adoption.</description>
			</item>
			<item>
				<title>3 Core Practices of Kanban: Improving a Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</link>
				<pubDate>Wed, 28 Feb 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</guid>
				<description>Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Pride</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/</link>
				<pubDate>Fri, 13 Oct 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>What is the difference between resource efficiency and flow efficiency?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-difference-between-resource-efficiency-and-flow-efficiency/</link>
				<pubDate>Thu, 09 Mar 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-difference-between-resource-efficiency-and-flow-efficiency/</guid>
				<description>Resource efficiency focuses on maximizing how much each team member produces, while flow efficiency looks at how smoothly work moves through the entire process. Overemphasizing resource efficiency can lead to burnout and bottlenecks, but balancing both approaches helps create a healthier, more productive workflow. Review your current processes to ensure you are not just keeping people busy but also delivering value efficiently across the system.</description>
			</item>
			<item>
				<title>Access denied for orchestration plan on Build</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</link>
				<pubDate>Wed, 16 Dec 2015 14:18:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</guid>
				<description>When setting up a TFS build agent for a high-volume customer, a permissions error blocked builds because the &amp;ldquo;Project Collection Build Service&amp;rdquo; lacked write access to the orchestration plan. The issue is tied to permission inheritance and a known bug in TFS 2015 RTM, and can be fixed by ensuring both &amp;ldquo;Project Build Service&amp;rdquo; and &amp;ldquo;Project Collection Build Service&amp;rdquo; have inherited permissions on build definitions via Visual Studio. Development managers should verify these permissions to avoid similar build failures and streamline onboarding to new build systems.</description>
			</item>
			<item>
				<title>TFS Build reports Licencies.licx: unable to load type</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-build-reports-licencies-licx-unable-to-load-type/</link>
				<pubDate>Thu, 23 Oct 2014 15:09:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-build-reports-licencies-licx-unable-to-load-type/</guid>
				<description>A build error caused by mismatched component versions in the licenses.licx file blocked successful automated builds, even though local builds worked due to developers having multiple versions installed. The issue was traced to inconsistent component versions between developer machines and the build server, highlighting the risks of unmanaged dependencies. To avoid similar problems, regularly clean up or reimage developer workstations and prioritize setting up automated builds to catch these issues early.</description>
			</item>
			<item>
				<title>Engaging with complexity - Team Foundation Server Edition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/</link>
				<pubDate>Mon, 01 Jul 2013 17:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/</guid>
				<description>Detailed walkthrough of a complex Team Foundation Server migration, covering remediation, hardware moves, upgrades, user management, and validation in large enterprise environments.</description>
			</item>
			<item>
				<title>Syncing many Dynamics AX instances to a single TFS 2010 Team Project</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/</link>
				<pubDate>Fri, 08 Oct 2010 16:20:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/</guid>
				<description>Explains how to configure multiple Dynamics AX instances to sync with a single TFS 2010 Team Project, streamlining source control and work item management for many clients.</description>
			</item>
			<item>
				<title>Too many organisations hide behind excuses:&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/</link>
				<pubDate>Sat, 07 Jun 2025 15:30:25 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>The Ghosts of Agile Past: Why Burndown Charts Might Be Holding You Back</title>
				<link>https://engineering-leadership-preview.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-preview.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>How to Overcome Agile Banditry: A Product Owner’s Journey</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Creating a WIT Adapter for the TFS Integration Platform for a source with no history</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/</link>
				<pubDate>Thu, 02 Jun 2011 11:25:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/</guid>
				<description>Explains how to build a TFS Integration Platform Work Item Tracking (WIT) adapter for a source system without history, covering versioning, field mapping, and error handling.</description>
			</item>
			<item>
				<title>Why do you trust Russell to deliver the PSPO course for NKD Agility?</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>Unlocking the Power of Immersive Learning in Agile</title>
				<link>https://engineering-leadership-preview.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-preview.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>Reserve an Agent for a special build in Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</link>
				<pubDate>Thu, 04 Apr 2013 01:37:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</guid>
				<description>Explains how to reserve a build agent in Team Foundation Server 2012 using custom activities, agent tagging, and workflow changes to ensure reliable, isolated build execution.</description>
			</item>
			<item>
				<title>Upgrading TFS 2010 to TFS 2012 with VSS Migration and Process Template consolidation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/</link>
				<pubDate>Sat, 30 Jun 2012 02:38:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/</guid>
				<description>Step-by-step guide to upgrading TFS 2010 to TFS 2012, migrating VSS data, consolidating process templates, and resolving common issues during team project integration.</description>
			</item>
			<item>
				<title>Upgrading from TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SF 2010 with SfTSv3</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/</link>
				<pubDate>Thu, 30 Jun 2011 15:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/</guid>
				<description>Step-by-step guide to upgrading TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SharePoint 2010, including process template migration and data handling.</description>
			</item>
			<item>
				<title>Rethinking Budgeting: How to Break Free from Traditional Constraints and Maximise Value</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Real Scope of a Product Owner: Beyond the Backlog</title>
				<link>https://engineering-leadership-preview.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-preview.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 Kanban: A Tool for Transparency and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</link>
				<pubDate>Mon, 24 Jun 2024 06:48:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</guid>
				<description>Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements.</description>
			</item>
			<item>
				<title>Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</link>
				<pubDate>Thu, 25 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</guid>
				<description>Evidence-based management helps leaders make better decisions by focusing on meaningful metrics that drive real business value, such as current and unrealised value, time to market, and ability to innovate. Regularly reviewing and tailoring these metrics to your organisation enables data-driven strategies and a clear competitive advantage. Consider adopting this approach to move beyond gut feelings and ensure your team delivers measurable results.</description>
			</item>
			<item>
				<title>Why Most Companies Fail at Adopting Agility Beyond IT</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-companies-fail-at-adopting-agility-beyond-it/</link>
				<pubDate>Thu, 27 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-companies-fail-at-adopting-agility-beyond-it/</guid>
				<description>Most companies fail to adopt agility beyond IT because the real barriers are organisational, such as rigid hierarchies, inflexible budgeting, and outdated performance reviews. Scrum Masters need to focus on driving broader organisational change, not just team-level practices. Development managers should address systemic blockers and rethink how work is funded and measured to enable true agility.</description>
			</item>
			<item>
				<title>Navigating the Unknown: How to Fund Your Product Like a Venture Capitalist</title>
				<link>https://engineering-leadership-preview.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-preview.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>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Hiring a Product Owner? Avoid copying job specs from the internet</title>
				<link>https://engineering-leadership-preview.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-preview.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>Why Limiting Work in Progress is Key to Success in Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</link>
				<pubDate>Mon, 22 Jul 2024 06:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</guid>
				<description>Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable.</description>
			</item>
			<item>
				<title>Mastering Cloud Migration: Overcoming the Fear of Incomplete Data Transfers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-cloud-migration-overcoming-the-fear-of-incomplete-data-transfers/</link>
				<pubDate>Thu, 07 Nov 2024 05:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-cloud-migration-overcoming-the-fear-of-incomplete-data-transfers/</guid>
				<description>Concerns about incomplete data transfers during cloud migration are often overstated; with proper planning, use of Microsoft’s migration tools, and clear communication about limitations, data loss is highly unlikely. Key steps include assessing your data, understanding cloud constraints like attachment size, and engaging Microsoft support for complex cases. To ensure a smooth migration, involve stakeholders early, plan for contingencies, and address potential issues before starting the move.</description>
			</item>
			<item>
				<title>The Importance of Product Backlog Management in Today&#39;s Agile Landscape</title>
				<link>https://engineering-leadership-preview.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-preview.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>A great Product Owner drives product strategy, not just manages the backlog</title>
				<link>https://engineering-leadership-preview.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-preview.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-preview.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-preview.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>The Strategic Imperative: Empowering Teams with Vision, Goals, and Direction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</link>
				<pubDate>Thu, 08 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</guid>
				<description>Many teams lack clarity on their organization’s vision, goals, and value, leading to inefficiency and misaligned efforts. To address this, leaders should clearly communicate strategic direction, empower teams with autonomy through intent-based leadership, and move beyond rigid procedures to foster engagement and continuous improvement. Ensure everyone understands how their work contributes to broader objectives so teams can make informed decisions and drive meaningful results.</description>
			</item>
			<item>
				<title>Unlocking Agile’s Core: Questioning to Create Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</link>
				<pubDate>Tue, 23 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</guid>
				<description>Agile success depends on fostering a culture where everyone questions existing processes, seeks continuous improvement, and adapts quickly to change. Scrum helps teams identify inefficiencies and encourages regular reflection, while leadership must empower all employees to challenge the status quo and act on feedback. To stay ahead of competitors, create open forums for discussion, reward initiative, and ensure that improvement is a shared, ongoing effort across the organization.</description>
			</item>
			<item>
				<title>Can you really commit to delivering work?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</link>
				<pubDate>Sat, 26 Nov 2011 20:24:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</guid>
				<description>Explores why Scrum shifted from &amp;ldquo;commitment&amp;rdquo; to &amp;ldquo;forecasting&amp;rdquo; work delivery, highlighting the risks of overpromising and the benefits of transparency in Agile teams.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</link>
				<pubDate>Mon, 15 Mar 2010 13:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</guid>
				<description>Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning in Agile: Overcoming Cognitive Bias</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</link>
				<pubDate>Mon, 05 Feb 2024 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</guid>
				<description>Immersive learning is essential for Agile teams because it exposes knowledge gaps and helps overcome overconfidence, leading to real skill growth. By focusing on hands-on practice, continuous feedback, and regular reflection, teams can drive ongoing improvement and avoid common pitfalls. Development managers should encourage immersive, practical learning environments to ensure their teams keep evolving and truly master Agile principles.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Insights from the New Scrum.org Course</title>
				<link>https://engineering-leadership-preview.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-preview.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>Understanding Product Discovery: Why It Matters More Than Ever</title>
				<link>https://engineering-leadership-preview.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-preview.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>What is the most valuable thing you have learned through training people?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</link>
				<pubDate>Tue, 07 Feb 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</guid>
				<description>The most valuable lesson from training people worldwide is that teams everywhere face the same core challenges when adopting agile and Scrum, regardless of culture or location. Shared experiences in training help participants realize their problems are not unique, which builds confidence and accelerates learning. Development managers should leverage global perspectives and proven Scrum practices to address common issues and drive improvement in their teams.</description>
			</item>
			<item>
				<title>Rethinking Software Estimation: Embrace Probabilistic Forecasting for Agile Success</title>
				<link>https://engineering-leadership-preview.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-preview.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 Effective Product Development: How a Hypothesis-Driven Approach Transforms User Experience</title>
				<link>https://engineering-leadership-preview.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-preview.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>When should I use Areas in TFS instead of Team Projects in Team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/</link>
				<pubDate>Tue, 09 Mar 2010 12:27:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/</guid>
				<description>Explains when to use Areas versus Team Projects in TFS 2010, comparing benefits, drawbacks, and best practices for managing multiple projects and process templates.</description>
			</item>
			<item>
				<title>Embracing Change: Why Agile Evolution is the Key to Thriving in a Rapidly Shifting World</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-change-why-agile-evolution-is-the-key-to-thriving-in-a-rapidly-shifting-world/</link>
				<pubDate>Wed, 22 Jul 2020 10:08:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-change-why-agile-evolution-is-the-key-to-thriving-in-a-rapidly-shifting-world/</guid>
				<description>Agility is not a one-time transformation but an ongoing process of experimentation and adaptation, essential for surviving in today’s rapidly changing business environment. Traditional management practices from the industrial era are no longer effective; leaders must foster continuous learning, embrace failure, and evolve their organisations iteratively. To stay competitive, development managers should prioritise experimentation and empower teams to adapt quickly rather than relying on outdated processes.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps Migration: Expert Insights for a Seamless Transition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-expert-insights-for-a-seamless-transition/</link>
				<pubDate>Fri, 08 Nov 2024 05:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-expert-insights-for-a-seamless-transition/</guid>
				<description>Migrating to Azure DevOps is complex and often a one-time event, so most teams lack the necessary in-house expertise. Key challenges include database validation, unexpected data issues, and the need for deep tool knowledge, making external experts or targeted training highly valuable. To ensure a smooth and successful migration, consider bringing in specialists or upskilling your team with expert support.</description>
			</item>
			<item>
				<title>Navigating the TFS to Azure DevOps Migration: Overcoming Compatibility Concerns with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-tfs-to-azure-devops-migration-overcoming-compatibility-concerns-with-confidence/</link>
				<pubDate>Wed, 06 Nov 2024 05:45:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-tfs-to-azure-devops-migration-overcoming-compatibility-concerns-with-confidence/</guid>
				<description>Migrating from TFS on-premises to Azure DevOps is generally straightforward, with most compatibility concerns affecting older on-prem versions rather than the cloud. Key considerations include planning for the loss of unsupported customisations, ensuring code security during the transition, and evaluating how existing extensions will work in Azure DevOps. To ensure a smooth migration, assess your current setup, identify potential gaps, and proactively address customisation needs.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps Migration: Navigating Challenges, Solutions, and Best Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-navigating-challenges-solutions-and-best-practices/</link>
				<pubDate>Wed, 31 Jul 2024 09:25:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-navigating-challenges-solutions-and-best-practices/</guid>
				<description>Migrating to Azure DevOps can streamline development, reduce costs, and improve scalability, but it comes with challenges like complex legacy systems and team resistance. Success depends on thorough planning, clear communication, extensive testing, and adaptability throughout the process. Development managers should assess their current environment, involve stakeholders, and consider expert support to ensure a smooth and effective migration.</description>
			</item>
			<item>
				<title>Rethinking &#39;User Stories&#39;: A Call for Clarity in Product Backlog Management</title>
				<link>https://engineering-leadership-preview.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-preview.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>Upgrading your process template from MSF for Agile 4 to Visual Studio Scrum 2.x</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/</link>
				<pubDate>Mon, 22 Apr 2013 17:37:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/</guid>
				<description>Step-by-step guide to safely upgrade from MSF for Agile 4 to Visual Studio Scrum 2.x process templates in TFS, including handling customisations and preserving work items.</description>
			</item>
			<item>
				<title>Solution - SEO permanent redirects for old URL’s?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/</link>
				<pubDate>Mon, 04 Jan 2010 02:34:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/</guid>
				<description>Explains how to set up SEO-friendly permanent redirects for old URLs to new ones in ASP.NET, covering best practices and code examples for preserving search rankings.</description>
			</item>
			<item>
				<title>The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility</title>
				<link>https://engineering-leadership-preview.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-preview.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 Taylorism, and why Waterfall is just the tip of the iceberg!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/</link>
				<pubDate>Mon, 18 Jan 2021 14:02:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/</guid>
				<description>Traditional management practices like Waterfall are just symptoms of deeper, outdated Tayloristic approaches that treat people as replaceable cogs, stifle innovation, and create disengaged teams. These practices persist through rigid hierarchies, siloed departments, best practices, and incentive systems that work against autonomy, mastery, and purpose. To improve outcomes and employee engagement, development managers should move toward cross-functional teams, empower those closest to the work to define practices, and focus on intrinsic motivators rather than outdated control mechanisms.</description>
			</item>
			<item>
				<title>Ethos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/ethos/</link>
				<pubDate>Tue, 13 May 2025 10:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Sprint Review</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</link>
				<pubDate>Sun, 11 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/</guid>
				<description>The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product&amp;rsquo;s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product&amp;rsquo;s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation.</description>
			</item>
			<item>
				<title>Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Site Reliability Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</guid>
				<description>Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks.</description>
			</item>
			<item>
				<title>Service Level Expectation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/service-level-expectation/</link>
				<pubDate>Mon, 05 May 2025 09:46:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>Liberating Structures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/liberating-structures/</link>
				<pubDate>Mon, 14 Apr 2025 14:50:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/agnostic-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:49:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</guid>
				<description>Agnostic Agile is a movement that advocates for a flexible and context-driven approach to agility, emphasising the importance of principles over rigid frameworks. Originating from the need for adaptability in various methodologies, it encourages teams to tailor their practices based on specific requirements rather than conforming to a single ideology. This pragmatic approach allows practitioners to integrate diverse methodologies such as Scrum, Kanban, Lean, and Extreme Programming, fostering an environment that values critical thinking and professionalism. By prioritising value delivery, Agnostic Agile equips teams to respond effectively to evolving circumstances, ensuring predictable and sustainable value generation. This adaptability is essential in today&amp;rsquo;s dynamic environments, where the capacity to pivot and innovate can significantly influence an organisation&amp;rsquo;s success. Furthermore, Agnostic Agile promotes ethical practices by avoiding brand loyalty to specific frameworks, thereby nurturing a culture of continuous improvement and learning. This mindset empowers teams to experiment and refine their processes, ultimately supporting a long-term, systemic approach to agility that enhances organisational resilience and effectiveness. As such, Agnostic Agile is a crucial concept in contemporary product development and delivery, providing valuable insights for teams striving to thrive in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Current Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/time-to-market/</link>
				<pubDate>Thu, 10 Apr 2025 14:20:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/accountability/</link>
				<pubDate>Thu, 10 Apr 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/accountability/</guid>
				<description>Accountability is a structural concept that delineates who is answerable for outcomes within a work system, distinguishing it from task-level responsibility and decision-making authority. In the context of Scrum, accountability is embodied by three roles: the Product Owner, the Scrum Master, and the Developers, each clarifying their responsibility for value, the work system, and the delivery of completed increments. This framework is crucial in Agile, Scrum, and DevOps environments, where self-management, decentralised control, and transparency are vital for success. Without clear accountability, organisations risk falling into patterns of unclear ownership, blame diffusion, and command-and-control management. It is important to note that accountability is distinct from responsibility, which pertains to task execution, and authority, which involves decision-making power; individuals can possess authority without accountability or responsibility without ownership of outcomes. By establishing clear accountabilities, organisations can facilitate inspection and adaptation, enabling data-driven decision-making, identifying delivery bottlenecks, and enhancing overall flow and value delivery. Ultimately, accountability serves as a defined structural mechanism that fosters clarity, alignment, and effective delivery in complex work systems.</description>
			</item>
			<item>
				<title>Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/product-development/</link>
				<pubDate>Wed, 09 Apr 2025 14:47:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Capability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/capability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/concepts/framework/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/concepts/method/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>Observability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/observability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/concepts/practice/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>Agentic Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-agility/</link>
				<pubDate>Mon, 07 Apr 2025 12:39:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-agility/</guid>
				<description>Agentic Agility is the capacity, human or AI, to take intentional, adaptive action within socio-technical environments to improve outcomes and align with evolving goals. It is grounded in agency: the power to act with autonomy, accountability, and purpose. Without agency, Agile devolves into hollow rituals; with it, people and systems can deliberately shape value delivery. Agentic Agility manifests through human judgement and learning or AI-driven optimisation within constraints, enabling continuous evolution of both what is delivered and how it is delivered. It is the critical lever that sustains agility as a living, resilient capability rather than a hollow label.</description>
			</item>
			<item>
				<title>Test First Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/test-first-development/</link>
				<pubDate>Tue, 25 Mar 2025 07:40:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</link>
				<pubDate>Fri, 21 Mar 2025 14:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/evidence-based-management/</link>
				<pubDate>Fri, 21 Mar 2025 14:44:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Continuous Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/</link>
				<pubDate>Fri, 21 Mar 2025 13:37:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</guid>
				<description>Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation&amp;rsquo;s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation&amp;rsquo;s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of &amp;ldquo;Kaizen,&amp;rdquo; which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value.</description>
			</item>
			<item>
				<title>Agile Product Operating Model</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-operating-model/</link>
				<pubDate>Fri, 21 Mar 2025 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Social Technologies</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/social-technologies/</link>
				<pubDate>Wed, 19 Mar 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/social-technologies/</guid>
				<description>Social technologies refer to foundational philosophies that enhance adaptability, emergent coordination, and collective intelligence in complex environments characterised by high variance. Unlike traditional methodologies that prescribe specific processes, social technologies provide a framework for decision-making that emphasises continuous learning, self-management, and decentralised authority. This approach allows organisations to navigate uncertainty with intention rather than relying on rigid procedures. Key principles include self-organisation, which promotes decentralised structures over hierarchical control; empirical inquiry, which prioritises iterative learning and experimentation; and collective intelligence, which recognises work as a social process driven by shared understanding. The importance of these philosophies lies in their ability to foster fluidity and resilience within organisations, enabling them to adapt to change and innovate effectively. By cultivating a social technology ethos, embracing epistemic humility, fostering emergent order, promoting participatory governance, and committing to continuous sense-making, organisations can transform their approach to complexity. This shift not only enhances collaboration and value creation but also positions adaptability as an intrinsic aspect of organisational culture, ultimately driving continuous progress in product development and operational effectiveness.</description>
			</item>
			<item>
				<title>Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</link>
				<pubDate>Tue, 04 Mar 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/scrum/</guid>
				<description>Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum&amp;rsquo;s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum&amp;rsquo;s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment.</description>
			</item>
			<item>
				<title>Acceptance Test Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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 Planning Tools</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/agile-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Asynchronous Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/asynchronous-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Azure Boards</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-boards/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Backlog Refinement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/backlog-refinement/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/behaviour-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Change Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/change-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/change-management/</guid>
				<description>Change Management is a structured approach aimed at guiding individuals, teams, and organisations through the transition from their current state to a desired future state. Originating from the need to effectively implement new processes, technologies, and mindsets, it plays a critical role in ensuring that changes are not only executed but also embraced by all stakeholders, leading to sustainable improvements in performance and value delivery. By prioritising the human aspects of change, this methodology helps teams navigate the complexities of organisational dynamics, thereby reducing resistance and enhancing engagement. Recognising that change is an ongoing journey rather than a one-off event, effective change management provides the necessary support and reinforcement to empower teams to respond to market demands and internal challenges with agility. This approach aligns closely with Lean and Agile principles, fostering a culture of continuous improvement and learning through experimentation and adaptation. Such a long-term perspective is vital for building resilience and nurturing a culture that thrives on innovation and collaboration, ultimately driving organisational success and growth.</description>
			</item>
			<item>
				<title>Coaching</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/coaching/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/coaching/</guid>
				<description>Coaching is a practice aimed at unlocking the potential of teams and leaders through guidance rather than directives, fostering an environment conducive to skill development, enhanced decision-making, and a mindset of continuous improvement. Originating from methodologies in agile, lean, and DevOps, coaching is vital for empowering teams to adapt to changing circumstances and deliver value in a predictable and sustainable manner. By prioritising the long-term development of individuals and teams, coaching cultivates a culture of learning and experimentation, promoting self-organisation and accountability that enables collaborative problem-solving. This systemic approach not only improves team performance but also aligns with organisational goals, ensuring that product and service delivery effectively meets customer needs. Unlike mentoring, which often involves knowledge transfer, coaching emphasises the coachee&amp;rsquo;s self-discovery and growth, focusing on asking the right questions to facilitate insights and actionable outcomes. This distinction is essential for building resilience and adaptability, traits that are increasingly important in fast-paced development environments. Additionally, by fostering psychological safety, coaching encourages open communication and trust, which are critical components of high-performing teams.</description>
			</item>
			<item>
				<title>Collaboration Tools</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/collaboration-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/continuous-integration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Cross Functional Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Cycle Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
			<item>
				<title>Decision Making</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/decision-making/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/decision-making/</guid>
				<description>Decision making is the process of applying structured, evidence-based approaches to make informed business choices that contribute to organisational success. This practice is essential as it enables teams to systematically evaluate options, relying on data, analysis, and collective insights rather than intuition alone. By fostering a culture of informed decision making, organisations can enhance their capacity to deliver value in a predictable and sustainable manner. Effective decision making incorporates various methodologies, including Lean and Agile principles, which promote iterative learning and adaptability to change, thereby minimising the risk of costly errors. Additionally, decision making is a systemic process that is shaped by organisational culture, team dynamics, and strategic objectives. By emphasising evidence-based choices, organisations can develop a mindset of continuous improvement, allowing decisions to be revisited and refined based on outcomes and feedback. This long-term perspective not only boosts operational efficiency but also aligns teams towards shared goals, driving innovation and competitive advantage. Ultimately, the ability to make sound decisions consistently is fundamental to organisational agility and resilience, ensuring that teams can remain responsive and effective in a rapidly changing environment.</description>
			</item>
			<item>
				<title>Deployment Frequency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/deployment-strategies/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Empirical Process Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/empirical-process-control/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Estimation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/estimation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/experimentation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/forecasting/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Lean Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lean-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/lean-product-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/lean-startup/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/lean-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Mentoring</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/mentoring/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Pragmatic Thinking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/pragmatic-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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 Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</guid>
				<description>The Product Owner is a key accountability within the Scrum framework, tasked with maximising the value of the product produced by the Scrum Team. This role encompasses more than just managing the product backlog; it involves making strategic decisions that align the product vision with customer needs and business objectives. The importance of the Product Owner lies in their responsibility for outcomes rather than merely tasks, as they prioritise features that balance immediate requirements with long-term goals. By optimising the product backlog and adapting to stakeholder feedback and market changes, the Product Owner significantly influences the product&amp;rsquo;s success and the team&amp;rsquo;s effectiveness. They foster collaboration between stakeholders and the development team, ensuring transparency and alignment across the organisation, which enhances decision-making and workflow efficiency. This accountability is crucial for a value-driven approach to product development, as the Product Owner must navigate competing priorities and ensure the product delivers measurable business value. Their strategic decision-making role is distinct from that of the Scrum Master or Development Team, as they continuously assess the product&amp;rsquo;s value and make evidence-based decisions to guide its evolution. By embedding this accountability within the organisational culture, the Product Owner helps maintain alignment with broader strategic goals, ultimately contributing to the consistency of value delivery and the successful completion of product iterations.</description>
			</item>
			<item>
				<title>Product Validation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-validation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Psychological Safety</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/psychological-safety/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Remote Working</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/remote-working/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Self Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/self-organisation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/software-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Troubleshooting</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/troubleshooting/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/troubleshooting/</guid>
				<description>Troubleshooting is the systematic process of identifying and resolving issues within software, hardware, and systems, which is essential for maintaining and optimising functionality. This practice is vital for organisations that seek to deliver value in a predictable and sustainable manner, as it directly influences the reliability and performance of their products and services. By effectively diagnosing problems, teams can reduce downtime, improve user satisfaction, and ensure a consistent workflow, which is particularly important in agile and DevOps environments. Furthermore, troubleshooting promotes a culture of continuous improvement, allowing teams to learn from failures and adapt their processes, thereby enhancing long-term resilience through the integration of knowledge and practices that prevent future issues. It also encourages collaboration among cross-functional teams, as diverse perspectives can lead to more effective solutions. Importantly, troubleshooting is not just a reactive strategy; it is a fundamental component of the development lifecycle that aligns with agile principles by fostering transparency and accountability. By prioritising troubleshooting, organisations can remain responsive to change, ultimately improving their capacity to innovate and consistently deliver value to customers, distinguishing high-performing teams in the fast-paced development landscape.</description>
			</item>
			<item>
				<title>Value Stream Mapping</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-mapping/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/working-agreements/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/working-software/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/agile-product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/application-lifecycle-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Flow Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/flow-efficiency/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/categories/kanban/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/kanban/</guid>
				<description>Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments.</description>
			</item>
			<item>
				<title>Lean</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/lean/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/metrics-and-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Product Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Value Stream Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Agentic Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/</link>
				<pubDate>Tue, 21 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>
	</channel>
</rss>
