<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Social Technologies on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/social-technologies/</link>
		<description>Recent content in Social Technologies 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/social-technologies/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>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>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>Release planning and predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</guid>
				<description>The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications.</description>
			</item>
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>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>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>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>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>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>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>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>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>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>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>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>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>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>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>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>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>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>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>Breaking the Silence: How to Combat the Hidden Dangers in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-the-silence-how-to-combat-the-hidden-dangers-in-agile-teams/</link>
				<pubDate>Fri, 10 Nov 2023 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-the-silence-how-to-combat-the-hidden-dangers-in-agile-teams/</guid>
				<description>Silence in Agile teams can lead to poor communication, lack of accountability, and misleading commitments, which undermine value delivery, erode trust, and stall growth. Managers should actively foster open communication, model vulnerability, and set clear expectations to prevent these issues. Prioritising honest dialogue and celebrating those who speak up will help teams deliver better results and maintain a healthy, agile culture.</description>
			</item>
			<item>
				<title>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>Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</link>
				<pubDate>Thu, 27 Jul 2017 18:16:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</guid>
				<description>Great Calm improved team alignment and agility by investing in Scrum training led by a trainer with real engineering experience, which fostered open dialogue and practical learning. The training is expected to enhance communication, align teams with business goals, and empower them to own their processes. Development managers should consider similar real-world-focused training to drive meaningful change and continuous improvement in their teams.</description>
			</item>
			<item>
				<title>Beware the Fake Agilists: How to Protect Your Team from the Agile Apocalypse</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beware-the-fake-agilists-how-to-protect-your-team-from-the-agile-apocalypse/</link>
				<pubDate>Tue, 07 Nov 2023 07:36:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beware-the-fake-agilists-how-to-protect-your-team-from-the-agile-apocalypse/</guid>
				<description>Relying on leaders with only Agile certifications but no real software development experience can harm team trust, stifle growth, and lead to ineffective processes. To protect your teams, prioritize practical experience over credentials, encourage ongoing learning, and focus on delivering value rather than just following procedures. Ensure Agile leadership is grounded in genuine expertise to maintain team effectiveness and resilience.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Boss to Empowering Facilitator</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/</guid>
				<description>The Scrum Master should not act as a boss or micromanager but as a facilitator who empowers the team to self-organise and take ownership of their work. Key points include avoiding micromanagement, focusing on support and facilitation rather than control, and promoting collaboration and continuous learning. Development managers should ensure Scrum Masters adopt a coaching mindset to help teams thrive and deliver better results.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Transformative Power of Teaching the &#34;Why&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</guid>
				<description>Helping teams understand the reasons behind Agile practices is key to real engagement and lasting change. When team members grasp the value and purpose of what they do, they collaborate better, adapt more easily, and drive continuous improvement. Development managers should focus on explaining the &amp;ldquo;why&amp;rdquo; behind processes to empower teams and boost performance.</description>
			</item>
			<item>
				<title>Story Points: A Ghost of Agile Past</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</link>
				<pubDate>Fri, 29 Dec 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</guid>
				<description>Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance.</description>
			</item>
			<item>
				<title>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>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>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>Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</link>
				<pubDate>Wed, 20 Nov 2024 08:02:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</guid>
				<description>A team increased their annual feature delivery from 25 to 150 by breaking down work into smaller experiments, enabling faster feedback, reduced risk, and continuous learning without increasing headcount. This approach allowed them to quickly identify and focus on features that mattered most to customers, leading to better products. Development managers should consider adopting small, frequent experiments to drive both speed and quality in feature delivery.</description>
			</item>
			<item>
				<title>Transforming Chaos into Collaboration: How a Common Framework Can Revolutionise Your Team&#39;s Dynamics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team&#39;s-dynamics/</link>
				<pubDate>Fri, 28 Jul 2017 11:55:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team&#39;s-dynamics/</guid>
				<description>Introducing a common framework and structured backlog helped transform a chaotic team environment into one marked by better collaboration, clearer communication, and increased trust. Teams benefited from a shared language, improved confidence, and more effective problem-solving, while regular feedback channels boosted morale and engagement. Development managers should consider adopting structured frameworks and open communication practices to drive positive change and sustain team momentum.</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 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>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>let-us be blunt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</guid>
				<description>Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability.</description>
			</item>
			<item>
				<title>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>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>You can not implement Agile or Scrum successfully by decree</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/</link>
				<pubDate>Tue, 13 May 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/</guid>
				<description>Agile and Scrum cannot be made effective just by issuing mandates or using tools; their success depends on a culture of trust, openness, and willingness to improve. If your team fears blame or resists change, process changes alone will not help. Focus on building a supportive culture before trying to improve processes.</description>
			</item>
			<item>
				<title>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>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>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>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>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>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>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>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</guid>
				<description>Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback.</description>
			</item>
			<item>
				<title>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>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>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>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>The Future of Scrum Training: Immersive Learning for Lasting Change</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</link>
				<pubDate>Thu, 23 Nov 2023 08:30:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/</guid>
				<description>Immersive learning is more effective than traditional Scrum training because it provides ongoing support, real-time problem solving, and peer collaboration over several weeks, helping participants apply new skills in real situations. This approach leads to gradual, sustainable change and builds confidence through shared learning and continuous improvement. Development managers should consider immersive learning to achieve lasting transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</link>
				<pubDate>Tue, 24 Oct 2023 06:50:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-1/</guid>
				<description>Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars.</description>
			</item>
			<item>
				<title>How does the APS course help people apply scrum effectively?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</link>
				<pubDate>Wed, 18 Jan 2023 08:57:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/</guid>
				<description>The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption.</description>
			</item>
			<item>
				<title>The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-management-guide/</link>
				<pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-management-guide/</guid>
				<description>Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and continuous experimentation.</description>
			</item>
			<item>
				<title>You want speed, adaptability, resilience</title>
				<link>https://engineering-leadership-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>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>“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>Empowering Leadership: Driving Cultural Change for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-leadership-driving-cultural-change-for-agile-success/</link>
				<pubDate>Fri, 07 Feb 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-leadership-driving-cultural-change-for-agile-success/</guid>
				<description>Leadership is crucial for enabling agile success by setting a clear vision, investing in automation, supporting architectural improvements, fostering continuous learning, and breaking down silos. These actions help teams align with organisational goals, deliver more reliably, and adapt to change. Development managers should prioritise these areas to create a culture that supports frequent, high-quality delivery and ongoing improvement.</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>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>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>Training: A Bridge to Knowledge and Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/training-a-bridge-to-knowledge-and-growth/</link>
				<pubDate>Fri, 27 Oct 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/training-a-bridge-to-knowledge-and-growth/</guid>
				<description>Investing in training and continuous learning is key to team growth and long-term success, helping teams stay relevant and engaged while demonstrating organizational commitment. Leaders should focus on creating a supportive environment that encourages experimentation, celebrates small wins, and addresses systemic barriers to learning. Prioritize ongoing development and adapt to new technologies to boost morale, performance, and retention.</description>
			</item>
			<item>
				<title>7 harbingers of the Agile apocalypse- War</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-war/</link>
				<pubDate>Thu, 19 Oct 2023 13:00:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-war/</guid>
				<description>Unchecked conflict in agile teams can escalate from healthy debate to destructive infighting, undermining collaboration and progress. Leaders must foster open communication, empathy, and clear conflict resolution processes to keep disagreements constructive and aligned with shared goals. Proactively managing conflict is essential to prevent team dysfunction and support ongoing innovation and growth.</description>
			</item>
			<item>
				<title>Scaling Teams: How to Foster Innovation Without Falling into Bureaucracy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-teams-how-to-foster-innovation-without-falling-into-bureaucracy/</link>
				<pubDate>Thu, 27 Feb 2025 11:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-teams-how-to-foster-innovation-without-falling-into-bureaucracy/</guid>
				<description>Scaling teams does not automatically lead to more innovation; it often results in bureaucracy, slower decision-making, and communication issues. To avoid this, focus on empowering teams, streamlining processes, and improving communication so growth enhances agility and innovation rather than stifling it. Development managers should reassess their scaling strategies to prioritize adaptability and team ownership for better outcomes.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-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>Create your own path to Organisational Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/</link>
				<pubDate>Thu, 11 Jan 2018 13:28:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/</guid>
				<description>A one-size-fits-all agile framework rarely works because every organisation’s path to agility is unique; instead, you should define a clear vision, form a cross-functional change team, and use an incremental, evidence-based approach to improvement. Broad, consistent training across all levels ensures everyone understands and supports the change, while involving stakeholders in identifying and prioritising impediments helps create a relevant organisational change backlog. To succeed, secure executive buy-in, empower teams to drive change, and focus on continuous, measurable improvements tailored to your context.</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>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>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>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>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>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>When is an APS course appropriate for a scrum team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</link>
				<pubDate>Thu, 12 Oct 2023 08:32:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/</guid>
				<description>An APS course is valuable for Scrum teams that want to deepen their understanding of core Scrum principles and shed ineffective practices that may have accumulated over time. It helps teams focus on delivering a working product each iteration and provides practical exercises, like the Barnacle Exercise, to identify and remove process inefficiencies. Consider APS if your team needs to realign with authentic Scrum practices and drive meaningful agile transformation.</description>
			</item>
			<item>
				<title>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>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>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>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>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>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</link>
				<pubDate>Mon, 11 Jan 2021 14:36:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</guid>
				<description>The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.</description>
			</item>
			<item>
				<title>No Estimates and is it advisable for a Scrum Team to adopt it?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/</link>
				<pubDate>Thu, 22 Aug 2019 12:55:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/</guid>
				<description>Estimation is valuable mainly for the team discussions it generates, not the numbers themselves. New Scrum Teams benefit from using Story Points and Velocity, but as they mature, they should shift to flow-based metrics like Cycle Time and Throughput and consider dropping traditional estimation. Teams should regularly review and adapt their process, moving toward simpler sizing and continuous improvement as they gain experience.</description>
			</item>
			<item>
				<title>What does a poor scrum team look, act and feel like?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-does-a-poor-scrum-team-look-act-and-feel-like/</link>
				<pubDate>Fri, 27 Jan 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-does-a-poor-scrum-team-look-act-and-feel-like/</guid>
				<description>Poor scrum teams are marked by autocratic leadership, dysfunctional product ownership, lack of trust, and absence of transparency, which lead to low morale and failure to deliver value. High-performing teams are rare because most organizations create barriers that prevent true collaboration and growth. To improve outcomes, focus on removing organizational obstacles and fostering an environment where teams can develop trust, openness, and shared ownership.</description>
			</item>
			<item>
				<title>Transforming Management into Agile Leadership: The Power of Virtual Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-management-into-agile-leadership-the-power-of-virtual-training/</link>
				<pubDate>Sat, 25 Apr 2020 02:29:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-management-into-agile-leadership-the-power-of-virtual-training/</guid>
				<description>Virtual agile leadership training offers significant benefits, including fostering true leadership over traditional management, encouraging team self-organisation, and focusing on value delivery. Small, diverse virtual classes enable deeper engagement, richer learning, and cost-effective, flexible participation using effective technology. Development managers should consider virtual training to upskill teams, broaden perspectives, and support continuous learning in an evolving agile landscape.</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>What is your perspective on collocation?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-your-perspective-on-collocation/</link>
				<pubDate>Mon, 21 Oct 2019 13:05:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-your-perspective-on-collocation/</guid>
				<description>Collocation, where all team members work together in the same space, is not required for Scrum but is strongly recommended, especially for new teams, as it improves communication, focus, and team ownership. While remote work is possible with the right technology, it often requires extra effort to replicate the benefits of in-person interaction. If collocation is not feasible, managers should support teams with tools and practices to minimize communication challenges and continuously improve team effectiveness.</description>
			</item>
			<item>
				<title>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>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>Breaking the Silence: How to Combat Communication Gaps in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/</link>
				<pubDate>Thu, 02 Nov 2023 11:30:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/</guid>
				<description>Communication gaps in Agile teams can lead to stagnation, loss of trust, and failure to deliver value. Silence often shows up as avoiding tough conversations, ignoring misalignment, withholding feedback, or making false promises. Development managers should actively foster open dialogue, model transparent communication, and create safe channels for feedback to keep teams aligned and effective.</description>
			</item>
			<item>
				<title>Nexus Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>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>The Synergy Between Product Management and Product Development in Agile Environments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</link>
				<pubDate>Thu, 25 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</guid>
				<description>Product Management and Product Development must work closely together in agile environments to deliver products that meet current and future market needs. Product Management sets the vision and strategy, while Product Development brings these ideas to life through innovation, quality, and fast delivery, with both functions relying on continuous feedback and improvement. Development managers should ensure strong collaboration and feedback loops between these teams to maximize product value and long-term success.</description>
			</item>
			<item>
				<title>How Immersive Learning Transforms Aspiring Agile Leaders</title>
				<link>https://engineering-leadership-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>The Power of Community: Becoming an Awesome Agile Coach</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-community-becoming-an-awesome-agile-coach/</link>
				<pubDate>Thu, 16 Nov 2023 11:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-community-becoming-an-awesome-agile-coach/</guid>
				<description>To be an effective Agile coach, it is essential to engage with a diverse community that challenges your thinking and provides honest feedback, rather than staying in a comfortable echo chamber. Growth comes from seeking out different perspectives, embracing critique, and continuously evolving your approach, which ultimately leads to delivering greater value to your teams and customers. Development managers should encourage their coaches to actively participate in varied Agile communities and prioritize learning and feedback to drive continuous improvement.</description>
			</item>
			<item>
				<title>Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness</title>
				<link>https://engineering-leadership-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>Unlocking Sustainable Growth: Why Leadership is the Key to Successful Scaling</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-sustainable-growth-why-leadership-is-the-key-to-successful-scaling/</link>
				<pubDate>Mon, 24 Feb 2025 10:12:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-sustainable-growth-why-leadership-is-the-key-to-successful-scaling/</guid>
				<description>Successful scaling in software development depends more on effective leadership than on technical solutions. Empowering teams, removing bottlenecks, and decentralising decision-making are key to sustainable growth. Development managers should focus on shaping leadership behaviours to create an environment where teams can scale effectively.</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>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>Scrum is made up of Influencers, Entrepreneurs, and Makers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-made-up-of-influencers-entrepreneurs-and-makers/</link>
				<pubDate>Mon, 01 Mar 2021 14:02:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-made-up-of-influencers-entrepreneurs-and-makers/</guid>
				<description>Scrum teams need a balance of three key roles: Influencers who lead and shape the environment, Entrepreneurs who define and communicate the product vision, and Makers who build the product. Each role has its own growth path and is essential for delivering high-value products. Development managers should ensure all three tracks are present and balanced in their teams to maximize success.</description>
			</item>
			<item>
				<title>Why 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>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 think Agile is evolving since its inception in 2001?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</link>
				<pubDate>Wed, 15 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</guid>
				<description>Agile has evolved since 2001, but many organizations still rely on top-down management rather than empowering teams to make decisions. The next major shift will be moving beyond just adopting frameworks like Scrum to building true agile capabilities across leadership, partners, and teams, focusing on adaptability and customer value. Development managers should revisit agile principles and work to remove barriers that prevent teams from responding quickly to change.</description>
			</item>
			<item>
				<title>What&#39;s the best way to work around multiple PO?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-the-best-way-to-work-around-multiple-po/</link>
				<pubDate>Mon, 16 Sep 2019 17:57:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-the-best-way-to-work-around-multiple-po/</guid>
				<description>If multiple people are acting as Product Owners but are not providing clear direction or attending key meetings, your team lacks true ownership of the product backlog and value delivery. This leads to wasted effort on features that may not matter, with industry data showing up to 65 percent of time spent on the wrong work. Raise this issue with management and ensure someone is clearly accountable for prioritizing and validating work, even if it means temporarily assigning the role until a suitable Product Owner is found.</description>
			</item>
			<item>
				<title>Kanban Guide for Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</guid>
				<description>Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery.</description>
			</item>
			<item>
				<title>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>What is Sprint Planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</link>
				<pubDate>Wed, 24 May 2023 14:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/</guid>
				<description>Sprint planning is a team meeting to align on what will be accomplished in the next sprint, ensuring everyone understands the goals and priorities, including new features, technical debt, and unexpected work. It provides clarity, flexibility, and a shared sense of direction, whether you use Scrum or Kanban. Make sure your team uses sprint planning to regularly evaluate priorities and maintain alignment for better outcomes.</description>
			</item>
			<item>
				<title>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>Unlocking Trust in Scrum: The Power of Openness and Transparency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</link>
				<pubDate>Fri, 28 Apr 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/</guid>
				<description>Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early.</description>
			</item>
			<item>
				<title>How will a PSM II course challenge your assumptions the most?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-will-a-psm-ii-course-challenge-your-assumptions-the-most/</link>
				<pubDate>Mon, 03 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-will-a-psm-ii-course-challenge-your-assumptions-the-most/</guid>
				<description>The PSM II course challenges common misconceptions about the Scrum Master role, showing that it is much more than being a Jira admin or a problem solver; instead, it focuses on empowering teams to be self-sufficient and highlights the value of subtle, behind-the-scenes leadership. The course helps Scrum Masters evolve from basic task facilitators to advanced guides who foster team autonomy and sustainable practices. Development managers should consider this course to deepen their understanding of effective Scrum leadership and drive stronger team performance.</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>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>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>Why Most Transformations Fail Without Honest Conversations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/</link>
				<pubDate>Thu, 19 Jun 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/</guid>
				<description>Most transformation efforts fail because teams avoid honest conversations about real issues. Creating space for open dialogue leads to genuine improvement and transparency, which are essential for true agility. Development managers should ensure their teams regularly discuss tough topics to drive meaningful change.</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>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>How do you incorporate a Design Sprint in Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</link>
				<pubDate>Fri, 16 Aug 2019 12:35:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</guid>
				<description>Design Sprints should not be treated as separate or special sprints in Scrum; instead, design and UX work should be integrated into regular sprints as part of the team&amp;rsquo;s ongoing activities or handled during backlog refinement for future work. All team members should collaborate on these tasks, leveraging individual skills without creating silos or specialist-only phases. Development managers should ensure design activities are visible, collaborative, and aligned with sprint goals, using communities of practice to share knowledge across teams.</description>
			</item>
			<item>
				<title>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>Unlocking Organisational Value: The Transformative Power of Engagement in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-organisational-value-the-transformative-power-of-engagement-in-agile-teams/</link>
				<pubDate>Thu, 28 Sep 2023 10:27:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-organisational-value-the-transformative-power-of-engagement-in-agile-teams/</guid>
				<description>Organisations deliver the most value when they focus on engaging their teams, not just managing them. Empowering people through decentralised decision-making, inclusivity, and clear principles leads to higher morale, innovation, and better results. Development managers should prioritise creating an environment where everyone feels trusted, aligned with the vision, and motivated to contribute.</description>
			</item>
			<item>
				<title>Embrace Uniqueness: Why Creating Your Own Scaling Practices Leads to Business Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/</link>
				<pubDate>Wed, 21 Jun 2023 15:34:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/</guid>
				<description>Relying on generic scaling frameworks can dilute what makes your organization successful, so it is better to develop your own scaling practices tailored to your unique culture, challenges, and goals. This approach preserves your competitive edge, increases adaptability, and fosters team ownership and engagement. Learn from others but create solutions that fit your context to achieve sustainable growth.</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>What is the most common mistake in sprint planning?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</link>
				<pubDate>Thu, 25 May 2023 14:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/</guid>
				<description>The most common mistake in sprint planning is failing to define a clear and tangible sprint goal, which is essential for guiding the team&amp;rsquo;s immediate work and connecting it to the broader product vision. A well-defined sprint goal provides focus, enables actionable stakeholder feedback, and helps the team understand and meet expectations. Development managers should ensure every sprint has a concrete goal that can be evaluated at the sprint review to drive progress and alignment.</description>
			</item>
			<item>
				<title>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>Introducing Kanban for Professional Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</link>
				<pubDate>Mon, 26 Feb 2018 15:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/</guid>
				<description>A new Professional Scrum with Kanban class and guide now enable Scrum teams to integrate Kanban practices like workflow visualization, limiting work in progress, and flow-based metrics without changing Scrum itself. This approach helps teams focus on value delivery and can replace traditional metrics like velocity with more actionable measures such as throughput and cycle time. Development managers should consider reviewing the Kanban Guide for Scrum Teams and exploring the training to enhance their teams&amp;rsquo; effectiveness.</description>
			</item>
			<item>
				<title>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>What are the barriers that prevent developers from fully accepting a Product Owner as the final decision maker?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-are-the-barriers-that-prevent-developers-from-fully-accepting-a-product-owner-as-the-final-decision-maker/</link>
				<pubDate>Tue, 03 Oct 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-are-the-barriers-that-prevent-developers-from-fully-accepting-a-product-owner-as-the-final-decision-maker/</guid>
				<description>Developers may not fully accept the Product Owner as the final decision maker when stakeholders undermine the Product Owner’s authority, send mixed messages, or fail to consistently support their decisions. This leads to confusion, lack of trust, and developers second-guessing decisions. To address this, ensure stakeholders back the Product Owner publicly, document agreements, and foster open communication to build trust and accountability.</description>
			</item>
			<item>
				<title>The Urgent Call for Agile Organisational Transformation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-urgent-call-for-agile-organisational-transformation/</link>
				<pubDate>Thu, 29 Jun 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-urgent-call-for-agile-organisational-transformation/</guid>
				<description>Traditional hierarchical structures are holding back organisations from adapting to today’s fast-changing markets, leading to slow responses and missed opportunities. Superficial agile transformations fail because they do not address deep-rooted command-and-control habits, causing apathy and repeated failure. To stay competitive, leaders should drive genuine organisational change by adopting decentralised, network-based models and commit to ongoing organisational refactoring and hygiene.</description>
			</item>
			<item>
				<title>The Power of Humility in Agile: A Core Virtue for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/</link>
				<pubDate>Tue, 12 Dec 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/</guid>
				<description>Humility is crucial for Agile teams because it enables better collaboration, trust, and openness to feedback, leading to stronger products and happier teams. Recognizing that not all ideas are right, listening to others, and being willing to change course based on data and feedback are key to success. Development managers should foster a culture where team members check their egos, seek diverse perspectives, and use data thoughtfully to continuously improve.</description>
			</item>
			<item>
				<title>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>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>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>Why Immersive Learning Keeps Scrum Students Excited and Engaged</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</link>
				<pubDate>Thu, 01 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/</guid>
				<description>Immersive learning keeps Scrum students engaged by making each session a hands-on journey of discovery, allowing them to apply new concepts in real time and reflect on their experiences. Spreading content over multiple sessions helps teams assimilate knowledge, experiment safely, and continuously improve through feedback. Development managers should break training into manageable pieces, encourage experimentation, and foster regular feedback to maintain excitement and drive ongoing growth.</description>
			</item>
			<item>
				<title>5 tools that Scrum Masters love. Part 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</link>
				<pubDate>Thu, 14 Sep 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/</guid>
				<description>Liberating structures are a set of frameworks that help Scrum Masters run more engaging and effective meetings by matching specific techniques to clear objectives. Using these tools can boost team participation, break down communication barriers, and drive better outcomes. Consider adopting liberating structures to turn routine meetings into productive sessions that support team growth and innovation.</description>
			</item>
			<item>
				<title>Why did you choose the Scrum.Org track rather than the Scrum Alliance track?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-did-you-choose-the-scrum-org-track-rather-than-the-scrum-alliance-track/</link>
				<pubDate>Fri, 24 Feb 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-did-you-choose-the-scrum-org-track-rather-than-the-scrum-alliance-track/</guid>
				<description>The author chose Scrum.Org over Scrum Alliance due to its strong professionalism, integrity, and community focus, as well as its fair certification policies that avoid recurring fees and restrictive progression paths. Scrum.Org encourages continuous improvement and knowledge sharing among trainers, which benefits both individuals and organizations. Development managers should consider Scrum.Org for its flexible, value-driven approach to Scrum training and certification.</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>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>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>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>Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</link>
				<pubDate>Tue, 27 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</guid>
				<description>Defining and visualising your workflow in Kanban creates shared understanding, clarity, and alignment among team members, which leads to greater efficiency. Establishing clear rules for task selection, workflow stages, and work in progress is essential for a stable and productive system. Take time to document and visualise your process so everyone knows how work flows and can contribute effectively.</description>
			</item>
			<item>
				<title>Is Your Engineering Culture Ready to Scale with Your Technology?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-engineering-culture-ready-to-scale-with-your-technology/</link>
				<pubDate>Thu, 20 Feb 2025 07:33:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-engineering-culture-ready-to-scale-with-your-technology/</guid>
				<description>Scaling technology is easy compared to scaling engineering culture, which is often overlooked but critical for sustainable growth. If your culture does not evolve, issues like poor collaboration, superficial DevOps practices, and lack of continuous learning can undermine progress, and more tools alone will not fix this. Development managers should focus on fostering genuine collaboration, integrating DevOps as a mindset, and making continuous learning part of daily work to ensure culture keeps pace with technology.</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>Mindset Versus Philosophy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/podcasts/mindset-versus-philosophy/</link>
				<pubDate>Thu, 22 Feb 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/podcasts/mindset-versus-philosophy/</guid>
				<description>Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is crucial for transparency and effective communication in Agile environments. They emphasize that the words teams choose directly impact understanding and outcomes. Development managers should ensure their teams are clear and intentional with language to improve collaboration and results.</description>
			</item>
			<item>
				<title>Introduction to Agility’s Ghosts: Shedding Dogma and Embracing Pragmatism</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/introduction-to-agility-s-ghosts-shedding-dogma-and-embracing-pragmatism/</link>
				<pubDate>Thu, 28 Dec 2023 08:40:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/introduction-to-agility-s-ghosts-shedding-dogma-and-embracing-pragmatism/</guid>
				<description>Rigid adherence to Agile rules can harm teams and stifle progress; true agility means adapting processes to fit the team’s needs and focusing on delivering value. Flexibility and pragmatism are essential for creating inclusive, effective environments, while dogmatic approaches undermine collaboration and innovation. Development managers should prioritize outcomes and continuous improvement over strict rule-following to support team success.</description>
			</item>
			<item>
				<title>The Importance of Evaluating Direction: Are You Heading the Right Way?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</link>
				<pubDate>Sat, 20 Jan 2024 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/</guid>
				<description>Regularly evaluating your direction at every level, developer, product owner, and organization, is essential to avoid wasted effort and ensure you are building the right things for your users. Key insights include aligning work with the product vision, listening to feedback, and being willing to pivot based on data rather than sticking to outdated plans. Make time for honest retrospectives and be ready to change course when needed to achieve better outcomes.</description>
			</item>
			<item>
				<title>Why &#39;Definition of Done&#39; is Crucial for Success in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-&#39;definition-of-done&#39;-is-crucial-for-success-in-scrum/</link>
				<pubDate>Tue, 14 Nov 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-&#39;definition-of-done&#39;-is-crucial-for-success-in-scrum/</guid>
				<description>The Definition of Done sets clear quality standards for all work, ensuring every deliverable meets your organization&amp;rsquo;s expectations regardless of the specific feature or project. It aligns teams, reduces defects, and protects your brand by making sure nothing is released before it is truly ready. Regularly review and adapt your Definition of Done with your team to maintain high quality and customer satisfaction.</description>
			</item>
			<item>
				<title>Empathy in Agile: Building Trust and Stronger Relationships for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/</link>
				<pubDate>Tue, 12 Dec 2023 11:00:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/</guid>
				<description>Empathy, modesty, and respect are essential for building trust and strong relationships in agile teams, leadership, and with customers, leading to better collaboration and outcomes. Avoiding assumptions and seeking diverse perspectives through open questions and feedback helps prevent bias and supports continuous improvement. Development managers should prioritise empathy and active listening to create a culture where everyone feels valued and engaged.</description>
			</item>
			<item>
				<title>Mastering the Art of Product Ownership: The Power of Marketing Your Vision</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-product-ownership-the-power-of-marketing-your-vision/</link>
				<pubDate>Fri, 15 Dec 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-product-ownership-the-power-of-marketing-your-vision/</guid>
				<description>Product Owners need to actively market their product vision to engage teams, stakeholders, and customers, not just manage backlogs. Consistent, emotionally resonant communication boosts participation in Sprint Reviews, improves feedback, and aligns everyone around shared goals. Development managers should encourage Product Owners to treat vision-sharing as an ongoing marketing effort to drive engagement and maximize product value.</description>
			</item>
			<item>
				<title>Online is the new co-located</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/online-is-the-new-co-located/</link>
				<pubDate>Mon, 16 Nov 2020 15:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/online-is-the-new-co-located/</guid>
				<description>With modern video technology and fast internet, online meetings can now provide the same level of non-verbal communication as being in the same room, so keeping cameras on is essential for team transparency and engagement. Development managers should encourage camera use during online events to maximize communication and adapt interactions, but also respect occasional needs for cameras off. If team members cannot use video reliably, consider in-person participation instead.</description>
			</item>
			<item>
				<title>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>Adaptive Operating Model</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/adaptive-operating-model/</link>
				<pubDate>Fri, 16 Jan 2026 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/adaptive-operating-model/</guid>
				<description>An adaptive operating model is an organisational structure designed to enable value delivery in environments characterised by uncertainty, complexity, and ongoing change. Unlike traditional models that rely on prediction, control, and centralised authority, the adaptive operating model is built around principles of learning, rapid feedback, and decentralised decision-making. Its core features include organising work around outcomes rather than tasks or projects, distributing decision rights to those closest to emerging information, embedding explicit learning loops for continuous adjustment, maintaining stable teams and roles while allowing flexible execution, and implementing governance that supports flow and transparency rather than rigid compliance. This model serves as the foundational structure for product-centric organisations and underpins specialised approaches such as product operating models and agile product operating models, which apply adaptive principles specifically to product delivery. The adaptive operating model is not a set of delivery practices, a process framework, or a superficial change initiative; rather, it fundamentally redefines how work is coordinated, how decisions are made, and how value is discovered within an organisation. Organisations adopt this model when they face rapidly evolving customer needs, technological uncertainty, high coordination costs, bottlenecks from centralised control, and when the speed of learning is more critical than adherence to plans. In such contexts, adaptability becomes essential for survival, making the adaptive operating model particularly valuable in agile, DevOps, product development, and modern organisational design, where empiricism, accountability, and the ability to respond to change are paramount.</description>
			</item>
			<item>
				<title>Objective Key Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/objective-key-results/</link>
				<pubDate>Tue, 03 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/objective-key-results/</guid>
				<description>Objective &amp;amp; Key Results (OKR) are a structured method for translating strategic goals into measurable outcomes, enabling clarity, alignment, and accountability within teams and organizations. Originating from John Doerr&amp;rsquo;s &amp;ldquo;Measure What Matters,&amp;rdquo; this approach defines an Objective as a meaningful, directional goal, and Key Results as specific, measurable indicators of progress toward that goal. Rather than tracking tasks or individual efforts, Objective Key Results emphasize outcomes and evidence of actual progress. Their value lies in creating a transparent system that encourages teams to focus on critical priorities, align their efforts clearly, regularly inspect progress, and adapt accordingly. Properly implemented, Objective Key Results foster a culture of accountability and continuous improvement, pushing teams beyond comfort zones to achieve meaningful results. In agile, DevOps, product development, and organizational design contexts, Objective Key Results serve as a foundational practice for ensuring strategic alignment, outcome-driven decision-making, and iterative learning.</description>
			</item>
			<item>
				<title>Ethos</title>
				<link>https://engineering-leadership-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>Increment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</guid>
				<description>Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices.</description>
			</item>
			<item>
				<title>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>Definition of Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</guid>
				<description>The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability.</description>
			</item>
			<item>
				<title>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>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>Cell Structure Design</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cell-structure-design/</link>
				<pubDate>Thu, 10 Apr 2025 14:48:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cell-structure-design/</guid>
				<description>Cell Structure Design is an organisational model that redefines traditional hierarchies by establishing a decentralised network of autonomous units, referred to as cells. Each cell is granted end-to-end responsibility, enabling rapid responses to customer needs and market fluctuations. This model aligns with the principles of the Beta Codex, promoting accountability and continuous adaptation through dynamic coordination rather than a command-and-control approach. Grounded in complexity theory, Cell Structure Design acknowledges the unpredictable nature of modern business environments, where adaptability is essential. By fostering transparency and collaboration both within and between cells, this structure enhances communication and accelerates decision-making, allowing teams to deliver value in a predictable and sustainable manner. The independent yet cohesive operation of cells facilitates ongoing innovation and process improvement, contributing to long-term organisational success. This systemic design not only boosts operational efficiency but also nurtures a culture of empowerment and engagement, which is vital for thriving in today’s fast-paced business landscape. Ultimately, the focus on value creation and responsiveness equips organisations to effectively navigate complexity, ensuring their competitiveness and relevance in the market.</description>
			</item>
			<item>
				<title>Company as a Product</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/company-as-a-product/</link>
				<pubDate>Thu, 10 Apr 2025 14:47:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/company-as-a-product/</guid>
				<description>Company as a Product (CaaP) is an organisational strategy that conceptualises the entire company as a dynamic product, evolving continuously based on customer feedback and measurable outcomes. Originating from the principles of agile and product development, this approach emphasises the alignment of all organisational components, people, processes, and systems, towards delivering customer value. CaaP fosters a culture of cross-functional collaboration and experimentation, enabling teams to respond swiftly to market changes and customer needs. This strategy represents a significant shift from traditional hierarchical structures to a more fluid and responsive organisational model, encouraging leaders to view their company&amp;rsquo;s capabilities as adaptable. By promoting a mindset of continuous improvement, CaaP ensures that every aspect of the organisation is open to refinement and innovation, which is crucial for maintaining competitiveness and relevance in a rapidly changing environment. Ultimately, by treating the organisation as a product, CaaP facilitates predictable and sustainable value delivery, establishing a resilient framework that supports long-term success and adaptability.</description>
			</item>
			<item>
				<title>Open Space Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/open-space-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:45:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/open-space-agile/</guid>
				<description>Open Space Agile is a progressive methodology for enhancing organisational agility, rooted in the principles of Open Space Technology. Developed by Daniel Mezick and the Open Leadership Network, this approach enables self-organisation and collaborative engagement among large groups, allowing all members of an organisation to actively influence the transformation process. By creating an environment characterised by psychological safety and shared ownership, Open Space Agile promotes authentic dialogue and collective decision-making, moving away from conventional top-down management styles. This method is particularly beneficial in complex settings where adaptability is essential, as it aligns with Agile principles by encouraging practices that emerge from the actual needs of teams rather than rigid plans. Teams are empowered to set their own priorities and actions, which enhances their capacity to deliver value in a predictable and sustainable manner. Furthermore, Open Space Agile not only supports immediate collaboration but also fosters a culture of continuous improvement and innovation, making it an integral aspect of contemporary organisational design. By valuing the insights of those closest to the work, it transforms the process of change into a shared journey towards increased agility and responsiveness.</description>
			</item>
			<item>
				<title>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>Scaling</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scaling/</link>
				<pubDate>Wed, 09 Apr 2025 13:53:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scaling/</guid>
				<description>Scaling refers to the capacity of an organisation to effectively coordinate multiple teams in the delivery of complex products while maintaining agility. This concept originates from the need to align efforts, optimise workflow, and enhance value delivery across the enterprise. It is particularly important in the contexts of agile methodologies and DevOps, as it allows organisations to respond swiftly to market changes without compromising on quality or speed. By implementing lean principles and adaptive product structures, scaling promotes a cohesive approach to product development, enabling teams to operate autonomously while remaining aligned with broader business objectives. This alignment is crucial for maximising efficiency and minimising waste, thereby leveraging the organisation&amp;rsquo;s collective capabilities. Furthermore, scaling fosters a culture of continuous improvement, where feedback loops and collaboration are integral to the development process. By prioritising these aspects, organisations can achieve sustainable growth and deliver value consistently, enhancing their competitive advantage in a rapidly changing environment. Ultimately, scaling is not just about increasing size but about establishing a robust framework that supports innovation and responsiveness throughout the organisation.</description>
			</item>
			<item>
				<title>Capability</title>
				<link>https://engineering-leadership-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>Model</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/model/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/model/</guid>
				<description>A model is a conceptual representation that aids teams in understanding and analysing complex systems or problems by simplifying intricate dynamics into more manageable forms. This simplification enhances clarity, enabling teams to visualise relationships, processes, and outcomes, which in turn fosters effective communication and collaboration through a shared framework for discussing challenges and opportunities. Models are particularly valuable in Agile, Lean, and DevOps environments, where rapid change and adaptability are essential. They serve as foundational tools for decision-making and systems thinking, distinguishing themselves from frameworks or methodologies by focusing on the underlying dynamics rather than structured approaches. For example, the Cynefin Framework assists teams in identifying problem complexity, while the Three Ways of DevOps model optimises software delivery through visualising flow and enabling feedback loops. By providing insight into the structural relationships that govern a system, models empower organisations to navigate complexity confidently, make informed decisions, align with organisational goals, and enhance agility and resilience. Ultimately, effective use of models allows teams to optimise their responses to challenges, ensure consistent value delivery, and drive sustainable organisational growth.</description>
			</item>
			<item>
				<title>Philosophy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/philosophy/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/philosophy/</guid>
				<description>The Philosophy category encompasses the foundational beliefs that underpin methodologies such as Agile, DevOps, and Lean, focusing on the rationale behind their effectiveness and the principles that guide decision-making and organisational behaviour. It delves into the reasons why these methodologies work, offering insights into how teams and organisations should conceptualise work, value, and collaboration. By exploring key principles like Agile values, Lean efficiency, and the culture of DevOps, alongside concepts from complexity theory and evidence-based decision-making, this category highlights the importance of understanding the underlying purpose of practices that drive systemic change within organisations. Unlike methods and frameworks that prescribe specific actions, philosophy provides a lens through which to interpret these actions, fostering a mindset that prioritises collaboration, adaptability, and transparency. This philosophical approach is crucial for organisations aiming to navigate complexity, enhance continuous improvement, and achieve long-term success, as it shapes how teams deliver value and respond to change. By embracing these philosophical foundations, organisations can cultivate an environment conducive to innovation and effective collaboration.</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>Principle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/principle/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/principle/</guid>
				<description>A principle is a fundamental, actionable belief or guiding rule that shapes decision-making and behaviour within an organisation, serving as a framework for action that aligns teams with broader organisational goals and values. Originating from the need for clarity in dynamic environments, principles are not abstract ideals but practical guides that help teams navigate complexity and uncertainty. For instance, the principle of Empiricism promotes decision-making based on evidence and experience, while Self-Management empowers teams to organise themselves and make autonomous decisions. Unlike values, which express an organisation&amp;rsquo;s core beliefs, principles directly influence behaviour and execution, as seen in the Continuous Improvement principle that encourages ongoing reflection and enhancement of processes. Principles also differ from tenets, as they are not rigid doctrines but adaptable guidelines that foster flexibility and resilience, exemplified by the principle of Adaptability. Their long-term value lies in their systemic nature, providing a stable foundation for decision-making across all organisational levels. By embedding principles into the organisational culture, teams can ensure alignment, drive continuous improvement, and effectively respond to challenges, ultimately delivering sustainable value to customers and fostering a culture of learning and innovation.</description>
			</item>
			<item>
				<title>Tenet</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/tenet/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/tenet/</guid>
				<description>A tenet is a specific, actionable guiding rule or doctrine that reinforces a larger philosophy within an organisation, distinguishing itself from values and principles by providing prescriptive direction for team behaviour in specific situations. Originating from frameworks like Kanban and Agile, tenets such as &amp;ldquo;Flow efficiency over resource efficiency&amp;rdquo; and &amp;ldquo;decentralised decision-making&amp;rdquo; translate overarching philosophies into concrete actions, thereby enhancing operational efficiency and responsiveness. Their importance lies in their ability to create a consistent organisational culture, guiding decision-making and behaviour across teams while remaining stable amidst changing practices. By embedding tenets into daily operations, organisations can align actions with broader philosophical frameworks, fostering a culture of continuous improvement and learning, which is essential for sustainable success in dynamic environments. Tenets serve as the foundation for collective behaviour, ensuring that teams work cohesively towards shared goals, ultimately driving adaptability and effectiveness in product development and organisational design.</description>
			</item>
			<item>
				<title>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>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>Artifact</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</link>
				<pubDate>Fri, 21 Mar 2025 13:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</guid>
				<description>An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change.</description>
			</item>
			<item>
				<title>Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</guid>
				<description>Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation&amp;rsquo;s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation&amp;rsquo;s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of &amp;ldquo;Kaizen,&amp;rdquo; which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value.</description>
			</item>
			<item>
				<title>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>DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/devops/</link>
				<pubDate>Thu, 20 Mar 2025 11:04:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/devops/</guid>
				<description>DevOps is a philosophy that integrates people, processes, and technology to facilitate continuous value delivery in software development. Originating from the need to bridge the gap between development and operations, it emphasises collaboration and automation to enhance the quality and speed of software delivery. The core principles of DevOps prioritise flow efficiency over mere resource utilisation, advocate for rapid feedback loops to align with customer needs, and promote automation to minimise errors and delays. Additionally, it fosters shared accountability among developers, operations, and security teams, ensuring collective responsibility for product quality. DevOps encourages a culture of continuous improvement, where teams are committed to experimentation and adaptation. In practice, organisations embracing DevOps focus on eliminating silos, integrating quality and security measures early in the development process, leveraging data for informed decision-making, and automating as many processes as possible. This approach is crucial in agile and DevOps environments as it enables organisations to deliver software more reliably and efficiently, ultimately enhancing their ability to respond to market demands and customer expectations. DevOps is viewed not as a final goal but as an ongoing journey towards improved software delivery.</description>
			</item>
			<item>
				<title>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>Agile Frameworks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</guid>
				<description>Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape.</description>
			</item>
			<item>
				<title>Agile Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-leadership/</guid>
				<description>Agile Leadership refers to the practice of guiding teams and organisations through change by creating an environment that emphasises adaptability, empowerment, and continuous improvement. Originating from agile methodologies, this leadership style moves beyond traditional management by enabling teams to self-organise, collaborate on decision-making, and swiftly respond to market changes. Its significance lies in fostering a culture that encourages experimentation and learning, which is essential for teams to innovate and deliver value consistently. Agile Leaders exemplify transparency and trust, establishing psychological safety that allows team members to express their ideas and concerns freely. They align organisational goals with team objectives, ensuring a unified focus on outcomes. By utilising frameworks like Scrum and Kanban, Agile Leaders enhance workflows, collaboration, and overall performance. This approach is not just about project management; it represents a transformation in organisational mindset, embedding agility as a fundamental value. Ultimately, Agile Leadership is a long-term commitment to cultivating a resilient organisational culture capable of adapting to change, thereby driving sustained success and value delivery in a fast-paced environment.</description>
			</item>
			<item>
				<title>Agile Philosophy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-philosophy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-philosophy/</guid>
				<description>Agile philosophy is a mindset that emphasises flexibility, collaboration, and a focus on customer needs in the realm of product development. Originating from the desire to improve traditional project management approaches, it serves as a foundational ethos that guides teams beyond specific methodologies like Scrum or Kanban. This philosophy is vital as it promotes incremental and iterative value delivery, enabling organisations to swiftly adapt to evolving market conditions and customer feedback. By fostering a culture of continuous improvement and learning, Agile philosophy allows teams to refine their processes over time, ensuring ongoing effectiveness and relevance. It encourages cross-functional collaboration, dismantling silos and fostering shared ownership of outcomes, which enhances team dynamics and aligns organisational objectives with customer expectations. Furthermore, Agile philosophy nurtures an environment conducive to experimentation and innovation, empowering teams to make data-driven decisions that lead to superior products and services. Its emphasis on adaptability and responsiveness distinguishes Agile philosophy from other frameworks, making it an essential component in achieving organisational excellence and resilience.</description>
			</item>
			<item>
				<title>Agile Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</guid>
				<description>Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development.</description>
			</item>
			<item>
				<title>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>Agile Transformation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-transformation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-transformation/</guid>
				<description>Agile Transformation refers to the comprehensive process of altering an organisation&amp;rsquo;s culture, mindset, and operational practices to adopt Agile principles and methodologies. Originating from the need for more adaptive and responsive work environments, this transformation is essential for enabling teams to deliver value in a predictable and sustainable manner. By emphasising collaboration, customer feedback, and iterative development, organisations can significantly improve their capacity for innovation and responsiveness to market changes. Agile Transformation is a long-term commitment that requires systemic changes across all organisational levels, evolving processes, structures, and behaviours to foster continuous improvement and learning. It empowers teams to self-organise, make informed decisions, and take ownership of their work, which enhances motivation and performance. Unlike specific Agile Frameworks or leadership roles that focus on particular methodologies, Agile Transformation adopts a holistic approach that integrates diverse practices and principles throughout the organisation. This creates an ecosystem that supports agility, aligning every team member with the organisation&amp;rsquo;s strategic goals and values. By embedding Agile thinking into the organisational culture, companies can achieve greater resilience, improve customer satisfaction, and drive sustainable growth through a dedication to delivering high-quality products and services.</description>
			</item>
			<item>
				<title>Agile Values and Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-values-and-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-values-and-principles/</guid>
				<description>Agile Values and Principles are fundamental guidelines that underpin effective Agile practices, serving as a framework for teams to consistently and sustainably deliver value. Originating from the Agile Manifesto, these values prioritise human interactions and collaboration over rigid processes and tools, fostering an environment where customer feedback and adaptability are central. Their importance lies in their ability to enable organisations to respond swiftly to change, ensuring that products remain relevant and aligned with customer needs. By promoting a culture of continuous improvement, Agile encourages teams to regularly assess their processes and outcomes, which enhances efficiency and drives innovation. This systemic approach builds organisational resilience, equipping teams to navigate the complexities and uncertainties of modern product development. By embedding these values into the organisational culture, teams gain the autonomy to self-organise and make informed decisions, maintaining a focus on high-quality outcomes. Ultimately, embracing Agile Values and Principles transcends a mere tactical adjustment; it acts as a strategic enabler that transforms operational dynamics, fostering a mindset oriented towards long-term success and value creation, thereby driving meaningful change and sustainable growth across the organisation.</description>
			</item>
			<item>
				<title>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>Beta Codex</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/beta-codex/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/beta-codex/</guid>
				<description>Beta Codex is a transformative framework for organisational design that promotes decentralised, adaptive, and human-centric structures, moving beyond traditional hierarchical models. Originating from the need for organisations to become more agile and responsive, this concept empowers teams to make decisions autonomously, embedding agility into the organisational culture rather than treating it as a set of practices. The significance of Beta Codex lies in its ability to enhance innovation and responsiveness to change, which are critical in today&amp;rsquo;s rapidly evolving market. By decentralising decision-making, organisations can respond more swiftly to customer needs, fostering collaboration and transparency that dismantle silos and create a unified purpose among team members. This approach cultivates resilience and adaptability, essential for success in complex environments. Furthermore, Beta Codex aligns with Lean and Agile principles, emphasising continuous value delivery and prioritising human interactions, trust, and psychological safety. By unlocking the potential of teams, organisations can achieve sustained performance and innovation, while also improving operational efficiency and fostering a culture of continuous improvement, ensuring they remain competitive and relevant in an ever-changing landscape.</description>
			</item>
			<item>
				<title>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 Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-learning/</guid>
				<description>Continuous Learning is the practice of nurturing a growth mindset and facilitating knowledge sharing within teams to achieve ongoing improvement. Originating from the need to adapt to rapidly changing environments, this concept underscores the significance of learning from both successes and failures to enhance skills, processes, and products. It is crucial in agile and DevOps contexts, as it enables teams to respond swiftly to challenges, ensuring consistent and sustainable value delivery. By embedding continuous learning into an organisation&amp;rsquo;s culture, teams become more resilient and innovative, fostering an environment that encourages experimentation and reflection. This approach not only refines practices and boosts performance but also integrates insights from diverse sources to inform strategic decision-making. Unlike Continuous Improvement, which focuses on incremental changes, Continuous Learning adopts a broader perspective, enhancing individual competencies and strengthening team dynamics. It promotes active knowledge sharing, leading to collective intelligence that drives superior outcomes. Continuous Learning is a long-term commitment rather than a one-off initiative, essential for organisations to remain competitive and relevant in a fast-evolving landscape. By prioritising this practice, organisations can cultivate a culture of excellence that enhances value delivery and customer satisfaction across all operations.</description>
			</item>
			<item>
				<title>Cross Functional Teams</title>
				<link>https://engineering-leadership-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>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>Evidence Based Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-leadership/</guid>
				<description>Evidence Based Leadership is a strategic methodology that leverages empirical data to guide decision-making and enhance organisational performance. Originating from the need for accountability and transparency in leadership, this approach enables leaders to make informed choices that align with both organisational goals and team requirements. By focusing on measurable outcomes and real-time feedback, leaders can discern effective practices and areas for improvement, fostering a more adaptive organisational culture. This methodology is particularly valuable in agile and DevOps environments, where the ability to respond swiftly to market changes and customer demands is critical. Evidence Based Leadership encourages continuous learning and adaptation, promoting a long-term perspective that prioritises systemic enhancements to performance and resilience. By embedding data-driven insights into leadership practices, organisations can create a culture of experimentation and innovation, empowering teams to test ideas and learn from their outcomes. This not only boosts team motivation and engagement but also ensures a stronger alignment between strategic objectives and operational execution, ultimately leading to improved results and value delivery.</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>Frequent Releases</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/</guid>
				<description>Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape.</description>
			</item>
			<item>
				<title>Large Scale Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/large-scale-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/large-scale-agility/</guid>
				<description>Large Scale Agility is the implementation of agile principles and practices throughout entire organisations, moving beyond individual teams to cultivate a culture of adaptability, collaboration, and continuous improvement. Originating from the need for enterprises to respond quickly to market dynamics and customer demands, this approach ensures that value delivery remains both predictable and sustainable. By adopting agile methodologies at scale, organisations can dismantle silos, improve cross-functional collaboration, and align strategic objectives with operational execution. This concept prioritises systemic change, focusing on the organisation as a cohesive unit rather than isolated teams, and encourages the use of frameworks like the Scaled Agile Framework (SAFe) or Large Scale Scrum (LeSS) to provide structured methods for scaling agile practices. The holistic perspective of Large Scale Agility enhances transparency, decision-making, and a shared understanding of goals across all organisational levels. The long-term advantages include increased capacity for innovation, improved employee engagement, and stronger alignment between business and technology. By creating an environment conducive to experimentation, learning, and adaptation, organisations can better navigate the complexities of a rapidly changing landscape, ultimately achieving sustained competitive advantage through agility at scale.</description>
			</item>
			<item>
				<title>Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/leadership/</guid>
				<description>Leadership is a fundamental aspect of organisational agility, acting as the catalyst for accountability and the continuous delivery of value. It originates from the need to navigate complex transformations within teams, promoting an atmosphere where innovation and collaboration are essential. Effective leadership goes beyond traditional management; it involves nurturing a culture that welcomes change and fosters adaptive thinking. In Agile, Lean, and DevOps contexts, leadership focuses on empowering individuals rather than merely directing tasks, facilitating decision-making that allows teams to swiftly adapt to shifting demands and customer needs. This systemic approach to leadership has far-reaching implications, affecting not only immediate results but also the long-term sustainability of the organisation. By emphasising the development of leadership capabilities, organisations can establish a robust foundation for success, ensuring that teams are well-equipped to deliver consistent value in a dynamic environment. This leadership model is crucial for creating a space where innovation and collaboration can thrive, ultimately propelling the organisation towards its goals.</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 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>Organisational Culture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-culture/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-culture/</guid>
				<description>Organisational culture refers to the collective values, beliefs, and behaviours that define how teams function within an organisation. It originates from the shared experiences and practices of employees and plays a crucial role in shaping decision-making processes, collaboration, and the agility of teams. A robust organisational culture is vital as it cultivates an environment conducive to innovation, enabling teams to swiftly adapt to changes and challenges. This adaptability is essential for delivering consistent and sustainable value, fostering a mindset of continuous improvement and learning. The long-term effects of organisational culture are significant, establishing a foundation of trust and psychological safety that encourages team members to express ideas and concerns openly. Such an environment enhances problem-solving capabilities and collaboration, which are critical in agile and DevOps methodologies. Unlike specific frameworks, organisational culture is an overarching element that influences every facet of an organisation, affecting strategy execution and team interactions. By prioritising a positive organisational culture, companies can improve their capacity for innovation and adaptability, thereby facilitating successful transformations and achieving strategic objectives. This cultural alignment serves not just as a backdrop but as a dynamic force that drives teams towards excellence and resilience in a constantly changing landscape.</description>
			</item>
			<item>
				<title>Organisational Physics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-physics/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-physics/</guid>
				<description>Organisational Physics is a conceptual model that applies systems thinking to understand and influence the dynamics within an organisation. It originates from the need to comprehend how various elements, including people, processes, and technology, interact and affect overall organisational behaviour and performance. This model is crucial in agile, DevOps, and product development contexts as it enables teams to recognise patterns and feedback loops, thereby identifying systemic issues and areas for improvement. By providing a framework for understanding the forces at play, Organisational Physics facilitates more effective decision-making, change management, and innovation. It empowers organisations to become more adaptable and resilient, allowing them to respond to challenges while maintaining a focus on value delivery. Rather than merely managing specific methodologies, this approach offers a holistic perspective on the underlying dynamics that drive performance, fostering a culture of continuous improvement. In an era of rapid change, Organisational Physics serves as a foundation for leaders to align their strategies with the realities of their operational environments, ultimately enhancing decision-making processes and contributing to long-term organisational success.</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>Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/professional-scrum/</guid>
				<description>Professional Scrum is a disciplined approach to the Scrum framework that emphasises empiricism, technical excellence, and the continuous delivery of value. Originating from the principles of Scrum, it prioritises the intentional and accountable ways in which individuals, teams, and organisations operate, rather than merely adhering to prescribed rituals or frameworks. This methodology underscores the importance of transparency, the definition of &amp;lsquo;Done&amp;rsquo;, and the necessity of empirical practices, positioning Product Owners as strategic leaders, Scrum Masters as catalysts for change, and Developers as skilled engineers. By embracing complexity as a dynamic to respond to rather than a challenge to control, Professional Scrum encourages rapid learning, frequent delivery, and ongoing improvement. Its significance lies in its ability to infuse professionalism, responsibility, and rigor into the process of complex product delivery, making it a valuable framework for organisations seeking to enhance their agility, foster collaboration, and achieve sustainable success in product development.</description>
			</item>
			<item>
				<title>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>Scrum Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-team/</guid>
				<description>A Scrum Team is a fundamental component of the Scrum framework, tasked with delivering value through iterative and incremental work. Comprising a Scrum Master, Product Owner, and Developers, the team operates collaboratively towards a unified Product Goal. Characterised by its self-managing and cross-functional nature, the Scrum Team eschews sub-teams and hierarchies, holding collective accountability for producing a usable Increment at the end of each Sprint. While individual members may have specific roles, the team&amp;rsquo;s shared responsibility encompasses all facets of product delivery, including stakeholder engagement, development, validation, and release. This structure empowers the Scrum Team to autonomously manage its work, making it a vital element in agile methodologies, DevOps practices, and effective organisational design. Understanding the dynamics and responsibilities of the Scrum Team is crucial for navigating complex and adaptive environments, as it highlights the importance of collaboration and accountability in achieving successful product outcomes.</description>
			</item>
			<item>
				<title>Scrum Values</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-values/</guid>
				<description>The Scrum Values are fundamental principles that form the backbone of the Scrum framework, consisting of commitment, courage, focus, openness, and respect. Originating from the need to create a structured yet flexible approach to project management, these values are essential for fostering a collaborative and high-performing team environment. Their importance lies in their ability to enhance a team&amp;rsquo;s capacity to deliver value consistently and sustainably, as they promote a culture of trust and accountability. Commitment drives team members to pursue their goals diligently, while courage encourages them to take risks and express concerns. Focus helps streamline efforts towards critical tasks, boosting productivity and efficiency. Openness facilitates transparent communication and collaboration, leading to effective problem-solving, and respect nurtures a supportive environment that values diverse perspectives, fostering innovation. The long-term benefits of integrating Scrum Values into daily practices are significant, enabling teams to effectively navigate complexities and adapt to evolving circumstances. By embedding these values within their organisational culture, companies can cultivate resilience, prioritise continuous improvement, and align their activities with overarching goals, ensuring that value delivery remains central to their product development and delivery processes.</description>
			</item>
			<item>
				<title>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>Sensemaking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/sensemaking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/sensemaking/</guid>
				<description>Sensemaking is the process by which organisations interpret complex information and situations to make informed decisions, involving data gathering, pattern recognition, and insight derivation. This capability is particularly valuable in environments marked by rapid change and uncertainty, as it enables teams to respond effectively to challenges and opportunities. By cultivating a culture of sensemaking, organisations can enhance their ability to deliver value in a predictable and sustainable manner, as teams become skilled at understanding customer needs, market dynamics, and internal capabilities, thereby aligning their efforts with strategic objectives. Unlike methodologies such as Agile Planning or Continuous Improvement, which focus on specific practices, sensemaking serves as a foundational framework that supports these initiatives by ensuring decisions are informed by a comprehensive understanding of the context. This long-term, enabling nature of sensemaking is essential for organisational agility, fostering continuous learning and innovation at all levels. By integrating sensemaking into daily operations, teams can better anticipate challenges and seize opportunities, ultimately improving their performance and adaptability in a complex landscape.</description>
			</item>
			<item>
				<title>Team Collaboration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/team-collaboration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/team-collaboration/</guid>
				<description>Team collaboration is the practice of enhancing teamwork, communication, and shared ownership among team members to achieve high performance. Originating from the need for effective interaction within teams, it is crucial for enabling organisations to deliver value in a predictable and sustainable manner. By fostering a culture of openness and trust, team collaboration empowers individuals to contribute their ideas and skills, thereby enhancing problem-solving capabilities and accelerating decision-making. This collaborative approach helps break down silos, facilitating the free flow of knowledge and expertise across functions, which in turn improves efficiency and adaptability in response to changing requirements and customer feedback. The long-term advantages of strong collaboration include increased innovation, higher employee engagement, and improved overall performance, aligning teams more closely with organisational goals and customer needs. Furthermore, the use of effective collaboration tools and practices is essential in agile, lean, and DevOps environments, supporting seamless communication and coordination. Ultimately, team collaboration serves as a foundational element that drives continuous improvement and value delivery, making it vital for modern product development and organisational success.</description>
			</item>
			<item>
				<title>Team Motivation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/team-motivation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/team-motivation/</guid>
				<description>Team motivation refers to the intrinsic drive that encourages individuals within a team to engage fully, take ownership of their responsibilities, and pursue high performance. It originates from the need to create an environment where team members feel valued and inspired, which is particularly important in agile, lean, and DevOps frameworks. Prioritising motivation leads to enhanced collaboration, innovation, and adaptability, enabling teams to respond effectively to changing circumstances. Motivated teams are capable of delivering value consistently and sustainably, as their commitment results in high-quality outputs and timely delivery. This focus on motivation fosters a culture of continuous improvement, encouraging team members to learn from experiences and experiment with new ideas. Furthermore, team motivation is a long-term investment that aligns individual aspirations with organisational goals, creating a shared sense of purpose that drives collective success. This alignment not only enhances team resilience and adaptability but also establishes a robust feedback loop, where motivated teams actively seek and respond to customer feedback, thereby improving their capacity to deliver value in a competitive landscape.</description>
			</item>
			<item>
				<title>Transparency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/transparency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/transparency/</guid>
				<description>Transparency is the practice of fostering openness and visibility within agile processes, which is essential for building trust and accountability among team members. Originating from agile methodologies, transparency enables teams to share information freely, allowing all members to grasp project status, challenges, and progress. This clarity is vital for effective collaboration, empowering individuals to make informed decisions and contribute significantly to team objectives. By promoting transparency, organisations can more easily identify bottlenecks and inefficiencies, facilitating continuous improvement and creating a culture that values feedback and adaptability. This openness not only enhances team dynamics but also aligns efforts towards common goals, ensuring that all members work together to deliver value in a predictable and sustainable manner. Furthermore, transparency supports a long-term approach to organisational health by cultivating an environment of psychological safety, where team members feel secure in expressing concerns and proposing innovations without fear of retribution. This ultimately results in a more resilient organisation, capable of navigating the complexities and uncertainties inherent in product development. By embedding transparency into daily operations, teams can improve their performance and achieve meaningful outcomes that resonate with stakeholders and customers.</description>
			</item>
			<item>
				<title>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>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>Enterprise Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/enterprise-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/enterprise-agility/</guid>
				<description>Enterprise Agility is the capacity of an organisation to swiftly and effectively adapt to changes in the market and customer demands, extending agile principles beyond individual teams to encompass the entire enterprise. This concept is vital as it cultivates a culture of adaptability, allowing organisations to pivot quickly in response to new information or shifting priorities. By integrating agility into the organisational structure, processes, and culture, teams can deliver value in a predictable and sustainable manner, ensuring alignment with customer needs. Enterprise Agility focuses on long-term systemic change rather than temporary solutions, fostering a mindset that prioritises continuous improvement and learning across all levels. It promotes cross-functional collaboration, dismantling silos that can impede responsiveness, thereby enhancing operational efficiency and creating an environment conducive to innovation. By emphasising agility at the enterprise level, organisations are better equipped to navigate complexity and uncertainty, leading to improved customer satisfaction and business outcomes. This proactive approach ensures that agility transcends mere practices, becoming a fundamental organisational capability that drives sustained success.</description>
			</item>
			<item>
				<title>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>One Engineering System</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/one-engineering-system/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/one-engineering-system/</guid>
				<description>The One Engineering System (1ES) is a strategic framework designed to unify engineering tools and practices across various teams, aiming to reduce friction, enhance collaboration, and ensure consistency at scale. Originating from the need to streamline workflows in software development, 1ES focuses on establishing a shared engineering backbone that allows teams to operate more efficiently by eliminating the chaos associated with disparate toolchains and ad hoc processes. This approach is crucial in agile and DevOps environments, as it promotes a common set of engineering standards that facilitate planning, coding, testing, deployment, and production support. By reducing cognitive overhead and simplifying integration, 1ES enables teams to deliver high-quality outcomes more reliably. Importantly, the framework emphasises that tools should adapt to the teams&amp;rsquo; workflows rather than impose rigid structures, allowing for flexibility and coherence rather than uniformity. Successful implementation of 1ES necessitates investment in team enablement, including guidance, training, and support, to ensure effective adoption. When executed properly, 1ES fosters scalable engineering excellence, characterised by clear communication, consistent processes, and a resilient development lifecycle across the organisation.</description>
			</item>
			<item>
				<title>Organisational Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/organisational-agility/</guid>
				<description>Organisational Agility is the ability of an organisation to rapidly adjust to changes in the market, customer needs, and new opportunities. This concept is essential for enabling teams to deliver consistent and sustainable value, allowing them to effectively navigate both challenges and opportunities. By promoting a culture of flexibility and responsiveness, organisations can improve their capacity for innovation and maintain a competitive advantage. Organisational Agility transcends quick fixes or temporary adjustments; it represents a long-term, systemic approach that weaves agility into the organisation&amp;rsquo;s core. This requires aligning processes, structures, and mindsets to foster continuous improvement and learning, facilitating cohesive team operations, breaking down silos, and enhancing collaboration across functions, which are critical for effective decision-making and value delivery. Additionally, it encourages a proactive approach to change, enabling organisations to anticipate market shifts rather than simply reacting to them. This forward-thinking perspective is crucial for sustaining growth and resilience in a constantly changing environment. By embedding agility into their fundamental operations, organisations can create a culture that not only accepts change but thrives on it, ultimately leading to improved performance and greater customer satisfaction.</description>
			</item>
			<item>
				<title>Sociotechnical Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/sociotechnical-systems/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/sociotechnical-systems/</guid>
				<description>Sociotechnical systems encompass the complex interactions between social and technical components within an organisation, particularly relevant to software delivery and team performance. This concept highlights that technology is not an isolated entity; rather, it is intricately linked to the organisational culture, structures, and processes. Understanding this duality allows teams to recognise how their workflows, communication styles, and tools impact overall effectiveness. The importance of sociotechnical systems lies in their capacity to create environments where teams can deliver value in a predictable and sustainable manner. When social factors, such as collaboration, trust, and motivation, are harmonised with technical capabilities, including tools and processes, organisations can enhance efficiency and foster innovation. This alignment equips teams to swiftly adapt to evolving market demands and customer expectations, thereby improving agility. Furthermore, sociotechnical systems advocate for a long-term, systemic approach to problem-solving, promoting continuous improvement and learning. By concentrating on the interplay between human and technological elements, organisations can establish resilient frameworks that facilitate ongoing adaptation and growth, ensuring optimal utilisation of both human and technical resources to drive value creation. This comprehensive perspective is crucial for navigating the complexities of contemporary product development and achieving sustained success in a competitive environment.</description>
			</item>
			<item>
				<title>Systems Thinking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/systems-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/systems-thinking/</guid>
				<description>Systems Thinking is a holistic methodology that helps organisations comprehend and manage complexity by perceiving systems as interconnected entities rather than as separate components. Originating from various disciplines, this approach is utilised to enhance decision-making and facilitate sustainable change within organisations. Its significance lies in fostering a culture of collaboration and shared understanding, enabling teams to foresee the repercussions of their actions throughout the entire system. By recognising interdependencies, organisations can pinpoint leverage points that yield substantial improvements in performance and value delivery. Systems Thinking aligns with Agile, Lean, and DevOps principles by promoting continuous learning and adaptation, allowing teams to respond effectively to feedback and changing requirements. Integrating Systems Thinking into organisational practices not only bolsters innovation and consistent value delivery but also establishes a resilient framework that supports long-term success. This comprehensive perspective aids in problem-solving and nurtures an environment conducive to team growth, ultimately leading to more effective and sustainable outcomes.</description>
			</item>
			<item>
				<title>Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/value-delivery/</guid>
				<description>Value Delivery is a systematic approach aimed at providing consistent and meaningful outcomes to customers through iterative and incremental processes. Originating from methodologies such as Lean and Agile, it is used in product development to ensure that efforts are aligned with customer needs, allowing for every release to contribute tangible benefits. This concept is vital as it enables teams to deliver value predictably and sustainably, fostering a culture of continuous improvement and responsiveness to change. By prioritising value delivery, organisations can significantly enhance customer satisfaction and loyalty, as products are more likely to meet expectations. It promotes cross-functional collaboration, encouraging teams to work together to identify and eliminate waste, optimise workflows, and streamline processes. Value Delivery encompasses the entire lifecycle of product development, from initial discovery to delivery and beyond, ensuring that teams can adapt to evolving market demands and customer feedback. This long-term focus ultimately leads to sustained organisational success and resilience in a competitive landscape, as embedding value delivery into the organisational culture creates a robust framework that supports innovation and drives continuous value creation for customers and stakeholders alike.</description>
			</item>
			<item>
				<title>Collective Intelligence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/collective-intelligence/</link>
				<pubDate>Thu, 23 Jan 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/collective-intelligence/</guid>
				<description>Collective Intelligence represents the enhanced problem-solving and innovation capabilities that emerge when humans with agency effectively collaborate with AI agents as team members. This concept goes beyond traditional human collaboration to encompass human-AI partnerships where both parties contribute complementary strengths, human creativity, judgment, and contextual understanding combined with AI processing power, pattern recognition, and consistent execution. Unlike passive tool usage, Collective Intelligence requires humans to have genuine agency and AI systems to operate with designed autonomy within appropriate constraints. The resulting synergy enables teams to navigate complex socio-technical environments, make more informed decisions, and deliver superior outcomes that neither humans nor AI could achieve independently. This form of agentic agility is essential for modern product development, where the volume and complexity of information, rapid change cycles, and need for continuous adaptation exceed purely human cognitive capabilities. By cultivating Collective Intelligence, organisations can harness the full potential of human-AI collaboration, transforming how value is created and delivered in digital product development.</description>
			</item>
	</channel>
</rss>
