<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Software Development on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/software-development/</link>
		<description>Recent content in Software Development 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/software-development/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Telling People What to Do Is Not Leadership. It’s a Failure of System Design</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</link>
				<pubDate>Mon, 04 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</guid>
				<description>Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work.</description>
			</item>
			<item>
				<title>Stop Building Silos. Start Building Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</link>
				<pubDate>Mon, 07 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</guid>
				<description>Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system.</description>
			</item>
			<item>
				<title>Don’t Manage Dependencies, Remove Them</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</link>
				<pubDate>Mon, 29 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</guid>
				<description>Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy.</description>
			</item>
			<item>
				<title>Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</link>
				<pubDate>Mon, 15 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</guid>
				<description>The phrase “flow of value” is often misused in software development, as value is only confirmed when customers validate it, not just when work is completed. Teams should focus on validating outcomes quickly, breaking work into small, testable increments, and using data to cut features that do not deliver real value. To truly optimise value, ensure every item has a clear hypothesis, measure time to feedback, and prioritise learning over simply moving work through the system.</description>
			</item>
			<item>
				<title>Is Agile Really Just a Mindset?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</link>
				<pubDate>Mon, 11 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</guid>
				<description>Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change.</description>
			</item>
			<item>
				<title>Why Topic Branches Drive High-Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</link>
				<pubDate>Mon, 14 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</guid>
				<description>Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality.</description>
			</item>
			<item>
				<title>Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</link>
				<pubDate>Wed, 14 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</guid>
				<description>When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility.</description>
			</item>
			<item>
				<title>Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</link>
				<pubDate>Mon, 15 Sep 2025 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</guid>
				<description>Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies.</description>
			</item>
			<item>
				<title>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</link>
				<pubDate>Mon, 22 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</guid>
				<description>Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control.</description>
			</item>
			<item>
				<title>The Definition of Done is a Commitment to Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</link>
				<pubDate>Mon, 26 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</guid>
				<description>Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value.</description>
			</item>
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Velocity isn’t how many story points a team burns down</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</link>
				<pubDate>Mon, 10 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</guid>
				<description>Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness.</description>
			</item>
			<item>
				<title>Stop Hiding Behind Complexity and Start Delivering Continuously</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</link>
				<pubDate>Mon, 24 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</guid>
				<description>Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery.</description>
			</item>
			<item>
				<title>Scrum Masters are not glorified meeting schedulers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/</link>
				<pubDate>Sun, 09 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/</guid>
				<description>Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility.</description>
			</item>
			<item>
				<title>Should You Use One Project to Rule Them All in Azure DevOps?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</link>
				<pubDate>Mon, 25 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</guid>
				<description>Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and delivery.</description>
			</item>
			<item>
				<title>Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</link>
				<pubDate>Wed, 07 May 2025 11:46:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/</guid>
				<description>Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact.</description>
			</item>
			<item>
				<title>Release planning and predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</link>
				<pubDate>Wed, 21 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</guid>
				<description>Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence.</description>
			</item>
			<item>
				<title>There no such thing as &#34;good&#34; technical debt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/</link>
				<pubDate>Sat, 19 Apr 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/</guid>
				<description>Technical debt is always harmful and should not be considered acceptable; it slows onboarding, increases errors, and creates inefficiency. It accumulates quickly and can suddenly halt delivery, as seen in Microsoft&amp;rsquo;s experience before they overhauled their processes and addressed their debt. Development managers should prioritize identifying and reducing technical debt now rather than accepting it as normal.</description>
			</item>
			<item>
				<title>Engineering can fix technical debt, but leadership has to invest in it</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</link>
				<pubDate>Mon, 03 Mar 2025 16:30:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</guid>
				<description>Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements.</description>
			</item>
			<item>
				<title>There Is No Such Thing as a &#34;Junior&#34; Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/</guid>
				<description>The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications.</description>
			</item>
			<item>
				<title>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/</link>
				<pubDate>Mon, 04 Aug 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/</guid>
				<description>Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization.</description>
			</item>
			<item>
				<title>Scrum Teams don’t set the bar for quality, they meet it</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/</link>
				<pubDate>Thu, 03 Apr 2025 15:30:01 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/</guid>
				<description>Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict, non-negotiable measure of what is releasable. Weakening or fluctuating the DoD increases risk and technical debt, undermining quality and predictability. Development managers should ensure their teams consistently strengthen the DoD over time rather than lowering it to deliver more features.</description>
			</item>
			<item>
				<title>Testing in Production Maximises Quality and Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</link>
				<pubDate>Thu, 13 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</guid>
				<description>Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness.</description>
			</item>
			<item>
				<title>Definition of Done - Objective vs Subjective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</link>
				<pubDate>Thu, 19 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</guid>
				<description>Technical debt is the cost of future rework from prioritising speed over good design, and it is distinct from poor quality, which often causes bigger productivity losses. Long release cycles and mislabeling poor quality as technical debt can lead to unsustainable practices and higher costs. Development managers should set clear quality standards, encourage regular refactoring, and adopt continuous improvement to reduce technical debt, improve efficiency, and deliver better products.</description>
			</item>
			<item>
				<title>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Are We Still Pretending Coding Was the Bottleneck?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</link>
				<pubDate>Mon, 01 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</guid>
				<description>AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output.</description>
			</item>
			<item>
				<title>Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</link>
				<pubDate>Mon, 21 Jul 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</guid>
				<description>Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</link>
				<pubDate>Wed, 16 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</guid>
				<description>Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage.</description>
			</item>
			<item>
				<title>Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</link>
				<pubDate>Wed, 02 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</guid>
				<description>Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality.</description>
			</item>
			<item>
				<title>Resilience is Part of the Product, Not an Afterthought</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/</link>
				<pubDate>Mon, 09 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/</guid>
				<description>Resilience must be designed into your product from the start, not added later or left to individual heroics. Building resilience means engineering for failure containment, rapid recovery, and continuous improvement, using tools like telemetry, feature flags, and safe deployment practices. Make resilience a core part of your development process and culture, treating it as a critical feature to avoid costly outages and business risks.</description>
			</item>
			<item>
				<title>Delivery is the only Measure of Progress in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</link>
				<pubDate>Mon, 03 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</guid>
				<description>Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration.</description>
			</item>
			<item>
				<title>Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/</link>
				<pubDate>Sat, 30 Nov 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/</guid>
				<description>Prioritising quality from the start is essential to protect your brand and build customer trust, and this requires empowering engineering teams to take ownership, address technical debt openly, and integrate practices like continuous integration, user experience, and security early in development. Fostering a culture of transparency, collaboration, and continuous improvement leads to better products and stronger technical leadership. Invest in your teams’ skills and encourage shared responsibility for quality to drive lasting value for your customers and organisation.</description>
			</item>
			<item>
				<title>The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</link>
				<pubDate>Wed, 21 Aug 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</guid>
				<description>DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results.</description>
			</item>
			<item>
				<title>Stop Testing Quality In: How Shifting Left Builds Better Software, Faster</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</link>
				<pubDate>Mon, 18 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</guid>
				<description>Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</link>
				<pubDate>Wed, 18 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</guid>
				<description>A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility.</description>
			</item>
			<item>
				<title>Do More Staging Environments Really Reduce Deployment Risk</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</link>
				<pubDate>Wed, 26 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</guid>
				<description>Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates.</description>
			</item>
			<item>
				<title>Every delay increases the risk of failure</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</link>
				<pubDate>Mon, 10 Feb 2025 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</guid>
				<description>Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release.</description>
			</item>
			<item>
				<title>Stop Promoting Branches</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/</link>
				<pubDate>Thu, 06 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/</guid>
				<description>Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster.</description>
			</item>
			<item>
				<title>The Power of Technical Excellence in Agile Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</link>
				<pubDate>Thu, 27 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</guid>
				<description>Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive.</description>
			</item>
			<item>
				<title>Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</link>
				<pubDate>Wed, 09 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</guid>
				<description>Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success.</description>
			</item>
			<item>
				<title>How to Build for Business Resilience and Continuity</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</link>
				<pubDate>Mon, 26 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</guid>
				<description>Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement.</description>
			</item>
			<item>
				<title>Building a culture of Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/</link>
				<pubDate>Fri, 22 Nov 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/</guid>
				<description>A culture of quality cannot be built by one person; it requires everyone in the organization to demonstrate and model technical excellence and leadership. Focusing only on revenue, as seen in Boeing&amp;rsquo;s decline, undermines quality and can lead to dangerous outcomes, while a strong culture of quality leads to better, safer products. Development managers should prioritize building and reinforcing engineering excellence and technical leadership across teams, using frameworks and tools as enablers rather than solutions.</description>
			</item>
			<item>
				<title>Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</link>
				<pubDate>Thu, 04 Jun 2020 02:05:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</guid>
				<description>The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust.</description>
			</item>
			<item>
				<title>Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/</link>
				<pubDate>Mon, 08 Sep 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/</guid>
				<description>Big Bang rewrites of legacy systems usually fail due to high costs, delays, and unchanged team mindsets, while incremental in-place improvements deliver ongoing value and reduce risk. Sustainable change comes from building a culture of continuous improvement and engineering excellence, where teams refactor and modernise systems piece by piece. Development managers should focus on fostering this culture and invest in gradual, disciplined transformation rather than risky all-at-once rewrites.</description>
			</item>
			<item>
				<title>How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</link>
				<pubDate>Wed, 25 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</guid>
				<description>You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready.</description>
			</item>
			<item>
				<title>Scrum doesn’t stop you from optimising flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it.</description>
			</item>
			<item>
				<title>Technical debt isn’t just messy code</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</link>
				<pubDate>Thu, 13 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</guid>
				<description>Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines.</description>
			</item>
			<item>
				<title>Transforming Chaos into Clarity: How Optimising Systems Fuels Engineering Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</link>
				<pubDate>Mon, 16 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</guid>
				<description>Unmanaged chaos in software delivery leads to poor quality, technical debt, and wasted resources. Optimising systems and processes, as shown by Microsoft’s transformation of their DevOps team, enables faster delivery, higher productivity, and better products by reducing technical debt and improving testing practices. Development managers should prioritise system optimisation and technical leadership to empower teams and drive sustainable engineering excellence.</description>
			</item>
			<item>
				<title>A better way than staggered iterations for delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</link>
				<pubDate>Thu, 10 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</guid>
				<description>Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality.</description>
			</item>
			<item>
				<title>Without Delivery, There Is No Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/</link>
				<pubDate>Mon, 10 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/</guid>
				<description>Value in software is only realised when products are delivered to users, so frequent releases are essential to validate assumptions, gather feedback, and adapt quickly. Delaying delivery increases costs, risks, and missed opportunities, while research shows that teams releasing often are more successful and resilient. Development managers should prioritise short feedback loops and empower teams to release working software regularly to maximise value and minimise waste.</description>
			</item>
			<item>
				<title>Why Handoffs Are Killing Your Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</link>
				<pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</guid>
				<description>Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness.</description>
			</item>
			<item>
				<title>Detecting Agile BS: Lessons from the Department of Defense</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/</link>
				<pubDate>Fri, 02 Aug 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/</guid>
				<description>Adopting Agile development practices is not enough if the rest of your organization remains slow and bureaucratic; true agility requires continuous delivery, high product quality, and minimal manual or bureaucratic steps across the entire process. Use the Department of Defense&amp;rsquo;s six-question test to assess your real agility, and focus on automating testing, streamlining deployment, and building quality in from the start. Regularly review and improve your processes to eliminate bottlenecks and ensure your whole ecosystem supports rapid, reliable delivery.</description>
			</item>
			<item>
				<title>Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</link>
				<pubDate>Mon, 11 Aug 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</guid>
				<description>Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible.</description>
			</item>
			<item>
				<title>Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</link>
				<pubDate>Wed, 04 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</guid>
				<description>Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software.</description>
			</item>
			<item>
				<title>Mastering Sustainable Scaling: Overcoming Product Development Challenges with Naked Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</link>
				<pubDate>Fri, 28 Feb 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</guid>
				<description>Scaling product development is complex and requires more than just adding people; it demands clear priorities, strong leadership, and systems designed for growth. Naked Agility helps organisations address common scaling challenges like alignment, technical debt, and slow feedback by eliminating bottlenecks, using data-driven decisions, and tailoring strategies to each team&amp;rsquo;s needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth.</description>
			</item>
			<item>
				<title>Scaling Smart: How to Tackle Technical Debt for Sustainable Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</link>
				<pubDate>Tue, 25 Feb 2025 06:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</guid>
				<description>Unchecked technical debt slows development, increases bugs, and reduces team productivity, making scaling risky and inefficient. Addressing weak points through sustainable architecture, automated testing, and continuous integration enables faster feedback, more reliable releases, and confident growth. Development managers should prioritize managing technical debt and automation to support sustainable scaling and maintain innovation.</description>
			</item>
			<item>
				<title>Technical debt cripples business agility and slows engineers down</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/</link>
				<pubDate>Tue, 06 May 2025 15:30:42 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/</guid>
				<description>Technical debt severely limits business agility and slows down engineering teams, making it harder to respond to market opportunities and innovate. This is a real risk seen in major companies and happens when technical debt is ignored. To stay competitive, focus on shortening feedback loops, automating processes, increasing transparency, and actively managing technical debt rather than accepting it.</description>
			</item>
			<item>
				<title>If teams struggle with quality or delivery, the problem is often the system</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/</link>
				<pubDate>Wed, 02 Apr 2025 15:30:05 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/</guid>
				<description>When teams face issues with quality or delivery, the root cause is often the broader system, not just the team itself. Consistent quality requires clear engineering standards, automation, and strong leadership support, not just team-level efforts. Leaders should ensure these foundations are in place rather than simply demanding results.</description>
			</item>
			<item>
				<title>The Hidden Costs of Supporting Multiple Versions in Production</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/</link>
				<pubDate>Thu, 06 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/</guid>
				<description>Supporting multiple versions in production drains engineering resources through increased context-switching, merge conflicts, and bug risks. Back-porting fixes and maintaining separate branches for each customer make things worse, leading to instability and technical debt. To avoid these problems, teams should simplify and standardise their branching strategy.</description>
			</item>
			<item>
				<title>The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</link>
				<pubDate>Tue, 19 Nov 2024 09:58:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</guid>
				<description>Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success.</description>
			</item>
			<item>
				<title>Why Most Scrum Masters Are Failing and What They Should Know</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</link>
				<pubDate>Thu, 05 Sep 2024 11:14:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/</guid>
				<description>Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</link>
				<pubDate>Mon, 03 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</guid>
				<description>Measuring individual cycle time in Kanban misleads teams by focusing on personal speed instead of system flow, which ignores real bottlenecks and encourages counterproductive behaviors. To improve delivery, track system-wide metrics like lead time, work in progress, process cycle efficiency, and blockers, then address constraints at the process level. Development managers should shift measurement and improvement efforts from individuals to the overall workflow to achieve better outcomes.</description>
			</item>
			<item>
				<title>Professional Scrum teams build software that works</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</link>
				<pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/</guid>
				<description>Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization&amp;rsquo;s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training.</description>
			</item>
			<item>
				<title>Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</link>
				<pubDate>Wed, 11 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</guid>
				<description>Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn.</description>
			</item>
			<item>
				<title>Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</link>
				<pubDate>Wed, 28 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</guid>
				<description>Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline.</description>
			</item>
			<item>
				<title>The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</link>
				<pubDate>Thu, 01 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/</guid>
				<description>Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change.</description>
			</item>
			<item>
				<title>Navigating the Unpredictability of Software Development: Embrace Agile for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/</link>
				<pubDate>Mon, 02 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/</guid>
				<description>Software development is inherently unpredictable, often leading to missed deadlines and budget overruns, but this can be managed by focusing on strong technical leadership and engineering excellence. Relying on a single best practice is a mistake; instead, adopting Agile principles like iterative development, continuous delivery, feedback, and testing helps teams adapt and deliver value. Development managers should foster these capabilities to navigate complexity and drive better project outcomes.</description>
			</item>
			<item>
				<title>Can the Definition of Done change per Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</link>
				<pubDate>Mon, 14 Oct 2019 13:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/</guid>
				<description>The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint.</description>
			</item>
			<item>
				<title>Why Organisations Believe Their Software Is Too Complex for CD</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</link>
				<pubDate>Mon, 24 Feb 2025 10:51:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</guid>
				<description>Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity.</description>
			</item>
			<item>
				<title>Mastering Technical Debt: Strategies to Transform Challenges into Opportunities for Your Development Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</link>
				<pubDate>Thu, 28 Nov 2024 06:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</guid>
				<description>Technical debt results from choosing quick fixes over robust solutions, leading to future costs and risks that can hinder your team&amp;rsquo;s productivity. Proactively paying down technical debt, as shown by the Azure DevOps team&amp;rsquo;s shift to agile practices, can dramatically increase feature delivery and product quality. Make refactoring, short feedback loops, and a focus on quality part of your regular process to unlock long-term gains and sustainable success.</description>
			</item>
			<item>
				<title>NKD Agility: Your partner in developing engineering excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/</link>
				<pubDate>Sat, 23 Nov 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/</guid>
				<description>NKD Agility helps organizations build engineering excellence and technical leadership by shifting key practices like testing, security, and architecture closer to development teams and actively addressing technical debt. This approach reduces the high costs of poor-quality products and supports a culture of quality and value creation. Development managers looking to improve software quality and team capability can partner with NKD Agility for modern engineering practices and support.</description>
			</item>
			<item>
				<title>Empowering Development Teams: Cultivating an Agile Mindset for Lasting Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-development-teams-cultivating-an-agile-mindset-for-lasting-quality/</link>
				<pubDate>Tue, 07 Apr 2020 20:33:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-development-teams-cultivating-an-agile-mindset-for-lasting-quality/</guid>
				<description>Development teams often struggle with agile adoption due to a lack of intrinsic motivation and engagement with quality and customer feedback. Leadership must create an environment that fosters autonomy, mastery, and purpose, while bridging the gap between technical skills and mindset through practices like retrospectives, code reviews, and continuous feedback. Focus on building a culture that values quality and empowerment to achieve lasting agile transformation.</description>
			</item>
			<item>
				<title>Avoid the pick-n-mix branching anti-pattern</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</link>
				<pubDate>Mon, 14 Jul 2014 15:35:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</guid>
				<description>Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability.</description>
			</item>
			<item>
				<title>DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/</link>
				<pubDate>Mon, 02 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/</guid>
				<description>DevOps enables organisations to modernise legacy systems without starting from scratch by introducing automation, continuous integration and deployment, and observability, which make change safer and more routine. These practices reduce bottlenecks, lower the cost of change, and help teams deliver improvements continuously. Development managers should focus on identifying friction points and adopting DevOps practices to make ongoing system improvements achievable and sustainable.</description>
			</item>
			<item>
				<title>Rethinking Dev-Test-Staging-Production Pipelines for Safety</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</link>
				<pubDate>Fri, 21 Feb 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</guid>
				<description>Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency.</description>
			</item>
			<item>
				<title>Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</link>
				<pubDate>Wed, 22 Jan 2025 14:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</guid>
				<description>Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps: Avoiding Common Pitfalls for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/</link>
				<pubDate>Tue, 09 Apr 2024 08:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/</guid>
				<description>Many teams misuse Azure DevOps by creating flat work item hierarchies, using custom work item types that do not fit agile practices, neglecting traceability, and overcomplicating processes, which reduces the platform’s effectiveness. Sticking to intended structures and keeping processes simple helps teams stay agile and productive. Review your team’s use of Azure DevOps to ensure alignment with agile principles and avoid these common pitfalls.</description>
			</item>
			<item>
				<title>Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/</link>
				<pubDate>Mon, 28 Jul 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/</guid>
				<description>Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</link>
				<pubDate>Sat, 15 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</guid>
				<description>Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals.</description>
			</item>
			<item>
				<title>Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</link>
				<pubDate>Mon, 25 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</guid>
				<description>Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible.</description>
			</item>
			<item>
				<title>Evolving Engineering Practices to Improve Sprint Workflow in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/</link>
				<pubDate>Thu, 29 May 2025 15:30:45 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/</guid>
				<description>To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress.</description>
			</item>
			<item>
				<title>Why Tracking Individual Cycle Time Distorts Team Behaviour</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</link>
				<pubDate>Wed, 12 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</guid>
				<description>Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead.</description>
			</item>
			<item>
				<title>The Scrum Master is accountable for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>Where Agile Went Wrong: Understanding the Competence Crisis</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/</link>
				<pubDate>Mon, 14 Oct 2024 07:00:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/</guid>
				<description>Agile has struggled because its founders assumed widespread competence and commitment to continuous learning, but most organizations lack enough skilled practitioners, especially in key roles like Scrum Master. This competence gap is worsened by low hiring standards and overreliance on basic certifications, leading to ineffective teams and missed opportunities for improvement. Development managers should prioritize hiring and promoting individuals with proven learning habits, deep contextual understanding, and advanced expertise to build high-performing Agile teams.</description>
			</item>
			<item>
				<title>DevOps: Elevating Your Organization’s Performance Through Bespoke Solutions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/</link>
				<pubDate>Fri, 16 Aug 2024 07:18:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/</guid>
				<description>Tailoring DevOps to your organization’s unique needs starts with assessing your current state, streamlining processes, and choosing the right tools, which leads to higher quality and more frequent software deliveries. Key actions include conducting solo interviews to uncover real issues, automating and rationalizing tools, and empowering teams with end-to-end ownership while ensuring compliance does not block DevOps practices. Start with small, controlled deployments and strategic timing to minimize risk and maximize efficiency.</description>
			</item>
			<item>
				<title>Empowering Teams for Success: The Key to Thriving Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/</link>
				<pubDate>Tue, 07 May 2024 11:02:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/</guid>
				<description>Successful product development depends on empowered, engaged, and happy teams who understand the value of their work and are trusted to make decisions. Key drivers include fostering collaboration, providing continuous feedback, investing in skills development, and enabling direct customer engagement. Development managers should focus on creating an environment where team members feel valued and supported, as this leads to higher quality products and greater innovation.</description>
			</item>
			<item>
				<title>If a client hasn&#39;t considered DevOps consulting as part of their Agile Consulting needs, why should they?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn&#39;t-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/</link>
				<pubDate>Mon, 21 Aug 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn&#39;t-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/</guid>
				<description>Relying on Agile alone limits your team&amp;rsquo;s ability to deliver quality software quickly and efficiently; integrating DevOps consulting breaks down silos, accelerates time to market, and embeds quality from the start. DevOps is more than tools, it is a culture shift that harmonizes development and operations, enabling continuous improvement and resilient deployments. To maximize Agile&amp;rsquo;s benefits, development managers should invest in DevOps consulting to create a truly high-performing, adaptable software delivery process.</description>
			</item>
			<item>
				<title>Toyota &#34;andon&#34; cord lets any worker stop production to fix defects</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</link>
				<pubDate>Mon, 12 May 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/</guid>
				<description>Giving teams tools like Scrum events or defect reporting only works if you also create a culture where people feel safe to speak up and address problems. Without psychological safety and genuine empowerment, process changes alone will not lead to real improvement. Development managers should focus on building trust and openness so teams feel comfortable raising issues.</description>
			</item>
			<item>
				<title>Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</link>
				<pubDate>Tue, 27 Jun 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</guid>
				<description>In the first 90 days, a Scrum team can move from limited delivery to continuous delivery by focusing on frequent releases, clarifying business value, integrating user feedback, and empowering team members to take ownership. Success depends on organisational support and team readiness. Managers should prioritise building a delivery culture and enabling the team to sustain progress independently.</description>
			</item>
			<item>
				<title>I do continuous deliver, why should I Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</guid>
				<description>Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible.</description>
			</item>
			<item>
				<title>Legacy Systems Aren’t the Enemy, Friction Is: How to Unblock Innovation and Accelerate Agile Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/legacy-systems-aren-t-the-enemy-friction-is-how-to-unblock-innovation-and-accelerate-agile-delivery/</link>
				<pubDate>Mon, 14 Jul 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/legacy-systems-aren-t-the-enemy-friction-is-how-to-unblock-innovation-and-accelerate-agile-delivery/</guid>
				<description>Legacy systems are only a problem when they create friction that slows delivery, increases fragility, and blocks innovation. The real issue is not system age but lack of ongoing maintenance and improvement, which leads to bottlenecks for both engineers and management. To accelerate agile delivery, focus on identifying and removing friction points, prioritising continuous improvement, and communicating the value of these efforts to the business.</description>
			</item>
			<item>
				<title>Why Engineering Teams Use Staging Environments for Risk Reduction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/</link>
				<pubDate>Fri, 14 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/</guid>
				<description>Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead.</description>
			</item>
			<item>
				<title>Getting started with a modern source control system and DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/</link>
				<pubDate>Mon, 13 Jul 2020 18:41:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/</guid>
				<description>Modern source control systems are essential for managing not just code but the entire software development lifecycle, supporting DevOps practices and providing critical metadata for process visibility. Key practices include always using source control, automating release pipelines, minimizing branches with feature flags, moving to Git, and ensuring regular feedback and testing. To stay competitive, development managers should ensure all code is in source control, automate releases, and adopt integrated platforms like VSTS that support any technology and enable continuous delivery.</description>
			</item>
			<item>
				<title>The Insufficiency of Scrum is a fallacy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</link>
				<pubDate>Sat, 23 Mar 2013 17:37:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</guid>
				<description>Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes.</description>
			</item>
			<item>
				<title>The Sprint is a container for Planning and not necessarily for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</link>
				<pubDate>Tue, 29 Nov 2011 04:36:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</guid>
				<description>Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality.</description>
			</item>
			<item>
				<title>Executives want predictability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</link>
				<pubDate>Mon, 31 Mar 2025 15:30:08 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</guid>
				<description>If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating &amp;ldquo;Done&amp;rdquo; as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments.</description>
			</item>
			<item>
				<title>Why Scrum Masters Need Technical Expertise to Guide Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/</link>
				<pubDate>Fri, 28 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/</guid>
				<description>Scrum Masters are most effective when they have hands-on experience and technical understanding relevant to their team&amp;rsquo;s work, such as development practices or domain-specific knowledge. This expertise helps them guide teams toward improvement without doing the work themselves. Development managers should ensure Scrum Masters have sufficient technical background to enable, not just facilitate, their teams.</description>
			</item>
			<item>
				<title>Why Slow Processes Impact Developer Productivity and Performance</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/</link>
				<pubDate>Fri, 14 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/</guid>
				<description>Developer performance issues are often caused by slow or broken processes, not individual shortcomings. Focusing on improving systems like training, reviews, and team handoffs leads to better results than blaming people. To boost productivity, address process bottlenecks rather than targeting individuals.</description>
			</item>
			<item>
				<title>Shifting Left. Quality from the Start</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/</link>
				<pubDate>Wed, 20 Nov 2024 07:00:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/</guid>
				<description>Automating code reviews and quality checks as early as possible in the development process reduces defects and speeds up delivery by minimizing manual bottlenecks. Manual code reviews should be a safety net, not the primary method for ensuring quality, and no code should reach the main branch without passing automated checks. Development managers should invest in robust automation for code validation to improve quality and accelerate value delivery.</description>
			</item>
			<item>
				<title>The Competence Crisis in Scrum Master Roles: A Call for Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</link>
				<pubDate>Wed, 16 Oct 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/</guid>
				<description>There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Estimating Better in an Overloaded System Is a Poor Man’s Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</link>
				<pubDate>Mon, 08 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</guid>
				<description>Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning.</description>
			</item>
			<item>
				<title>Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/</link>
				<pubDate>Fri, 27 Jun 2025 06:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/</guid>
				<description>Focusing on real agility and DevOps means building adaptable teams and resilient systems, not just adopting the latest tools or trends. Key outcomes include smoother delivery, better feedback, and teams that can handle change without disruption. Prioritise embedding adaptability into your culture and processes so your teams can lead rather than react to change.</description>
			</item>
			<item>
				<title>Stop Writing Business Logic in Stored Procedures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/</link>
				<pubDate>Mon, 23 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/</guid>
				<description>Stop adding business logic to stored procedures and refactor existing logic into application code as you make changes, rather than rewriting everything at once. Keeping business logic in stored procedures makes testing, deployment, version control, scalability, and maintainability much harder, increasing technical debt and risk. Adopt a gradual, pay-as-you-go approach to modernize your codebase, improve engineering practices, and enable faster, more reliable delivery.</description>
			</item>
			<item>
				<title>Technical Debt Management for Long-Term Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</link>
				<pubDate>Thu, 21 Nov 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</guid>
				<description>Technical debt results from choosing quick fixes over long-term solutions and can be both intentional and unintentional, eventually limiting your team&amp;rsquo;s ability to deliver value. The Azure DevOps team dramatically increased their feature delivery by prioritizing and paying down technical debt, showing that addressing it leads to faster delivery and higher product quality. Development managers should actively identify and pay back technical debt to maximize long-term productivity and value.</description>
			</item>
			<item>
				<title>Bridging the Gap: Understanding the True Meaning of &#34;Done&#34; in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/</link>
				<pubDate>Thu, 07 Dec 2023 11:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/</guid>
				<description>Many Agile teams misunderstand what &amp;ldquo;done&amp;rdquo; really means, leading to gaps in quality and unmet expectations. Clearly defining &amp;ldquo;done&amp;rdquo; with input from both leadership and the team ensures consistent quality, reduces rework, and builds trust with stakeholders. Development managers should regularly review and refine their team&amp;rsquo;s definition of done to align with evolving business needs and maintain high standards.</description>
			</item>
			<item>
				<title>Embrace Simplicity: How to Transform Complexity into Continuous Delivery Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/</link>
				<pubDate>Thu, 27 Feb 2025 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/</guid>
				<description>Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success.</description>
			</item>
			<item>
				<title>Best Branching Strategies for Development Teams Explained</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/</link>
				<pubDate>Tue, 25 Feb 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/</guid>
				<description>Using separate branches for each environment increases complexity and slows feedback, making it harder to deliver value quickly. Teams should use branches to manage work in progress and rely on feature flags and progressive rollouts to control what users see. Review your current branching approach and consider simplifying it to speed up delivery and reduce risk.</description>
			</item>
			<item>
				<title>The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</link>
				<pubDate>Mon, 21 Oct 2024 05:32:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/</guid>
				<description>Scrum Masters need deep knowledge of both agile practices and the technical work of their teams to drive real improvement in product delivery. Without this competence, teams stagnate and fail to deliver business value, while skilled Scrum Masters elevate team capabilities and outcomes. Development managers should ensure their Scrum Masters have practical expertise, not just facilitation skills, to maximize team impact.</description>
			</item>
			<item>
				<title>Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</link>
				<pubDate>Mon, 08 Jan 2024 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</guid>
				<description>Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting.</description>
			</item>
			<item>
				<title>Unlocking Rapid Delivery: Overcoming Common DevOps Challenges for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</link>
				<pubDate>Fri, 21 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</guid>
				<description>Many teams struggle to deliver products quickly due to slow feedback loops, limited automation, and resistance to change. Key improvements include automating processes, engaging compliance teams early to challenge assumptions, and fostering a culture open to experimentation. Development managers should review their delivery pipelines for bottlenecks and actively involve stakeholders to enable faster, more agile releases.</description>
			</item>
			<item>
				<title>Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/</link>
				<pubDate>Wed, 13 May 2020 05:03:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/</guid>
				<description>Story points often create confusion and unpredictability, so focusing on throughput and cycle time gives teams clearer insights and better delivery. Slightly larger teams with diverse roles can handle complex work and maintain quality more effectively. Embracing emergent architecture helps teams stay flexible and competitive, so consider shifting your metrics and team structures to support adaptability and faster value delivery.</description>
			</item>
			<item>
				<title>Why Azure DevOps Wins for Governance, Security, and Scale, Right Out of the Box</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/</link>
				<pubDate>Mon, 01 Sep 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/</guid>
				<description>Azure DevOps provides integrated governance, security, compliance, and scalability out of the box, eliminating the need for complex tool setups and manual integration. Its seamless traceability, audit trails, and ability to handle thousands of users make it ideal for large-scale, secure software development. Development managers should consider Azure DevOps to reduce operational friction and focus on delivering value rather than managing disparate tools.</description>
			</item>
			<item>
				<title>Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/</link>
				<pubDate>Thu, 08 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/</guid>
				<description>Aiming for a resilient, fast, and fault-tolerant token counting system, the author replaced fragile server restarts with a batch-wide server lifecycle, added retry logic for transient failures, and implemented a local fallback to ensure uninterrupted processing. These changes improved reliability, reduced downtime, and provided clear logs for troubleshooting. Development managers should focus on building systems that handle real-world failures gracefully, prioritize flow, and include observability and fallback mechanisms from the start.</description>
			</item>
			<item>
				<title>I’ll never understand teams that manage bugs instead of fixing them</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/</link>
				<pubDate>Thu, 01 May 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/</guid>
				<description>Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate.</description>
			</item>
			<item>
				<title>Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</link>
				<pubDate>Wed, 23 Apr 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/</guid>
				<description>When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement.</description>
			</item>
			<item>
				<title>A changing Definition of Done undermines quality and predictability in teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/</link>
				<pubDate>Fri, 04 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/</guid>
				<description>Frequently changing the Definition of Done makes it hard for teams to deliver predictable results and maintain quality. The Definition of Done should only evolve to raise standards, not lower them. To improve predictability and quality, keep your Definition of Done consistent and ensure it is followed.</description>
			</item>
			<item>
				<title>Rethinking Continuous Delivery: Why Best Practices Don&#39;t Exist in Complex Environments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don&#39;t-exist-in-complex-environments/</link>
				<pubDate>Thu, 23 Jan 2025 06:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don&#39;t-exist-in-complex-environments/</guid>
				<description>There are no universal best practices for continuous delivery in complex environments; instead, teams should adopt flexible, situation-specific approaches. Key strategies include audience-based delivery for rapid feedback, testing in production to validate real-world performance, and a commitment to quickly finding and fixing issues. Development managers should focus on continuous improvement and adaptability rather than rigid processes.</description>
			</item>
			<item>
				<title>Code Reviews for Quality Assurance</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/code-reviews-for-quality-assurance/</link>
				<pubDate>Wed, 27 Nov 2024 06:00:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/code-reviews-for-quality-assurance/</guid>
				<description>Automating code validation before pull requests speeds up delivery, catches defects earlier, and ensures consistent quality, allowing manual reviews to focus on architecture and business alignment instead of minor issues. Development managers should invest in automated testing, static analysis, and security checks, making pull requests mandatory and using manual reviews strategically. This approach reduces bottlenecks and helps teams deliver high-quality software faster.</description>
			</item>
			<item>
				<title>Deciphering the Enigma of Story Points Across Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</link>
				<pubDate>Thu, 21 Sep 2023 08:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</guid>
				<description>Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes.</description>
			</item>
			<item>
				<title>Hiring a Professional Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</link>
				<pubDate>Mon, 15 Mar 2021 14:11:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-scrum-master/</guid>
				<description>Hiring a Scrum Master is challenging and requires someone who can lead, coach, and support both the team and organization to improve effectiveness and adopt Scrum practices. Key requirements include strong leadership, facilitation, and communication skills, a servant leadership mindset, and relevant certifications, with technical or business domain knowledge as a plus. Focus on candidates who can foster a safe, collaborative environment and drive continuous improvement for reliable product delivery.</description>
			</item>
			<item>
				<title>Navigating the Shift: Key Strategies for a Successful Transition to Microservices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-shift-key-strategies-for-a-successful-transition-to-microservices/</link>
				<pubDate>Mon, 21 Apr 2025 06:00:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-shift-key-strategies-for-a-successful-transition-to-microservices/</guid>
				<description>Transitioning from monolithic systems to microservices can improve flexibility and delivery speed, but success depends on clear business goals, careful planning to avoid unnecessary complexity, and an iterative approach that considers both technical and team dynamics. Focus on strategic decomposition and ensure each service is independently deployable and maintainable. Take time to assess your needs and plan the transition step by step to achieve real business value.</description>
			</item>
			<item>
				<title>If every release feels high-risk, you lack a true Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</link>
				<pubDate>Sat, 05 Apr 2025 15:30:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</guid>
				<description>If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team&amp;rsquo;s process to make releases predictable and low-stress.</description>
			</item>
			<item>
				<title>Special Sprints: Agile Banditry or Risk Management?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</link>
				<pubDate>Thu, 04 Jan 2024 11:09:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</guid>
				<description>Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk.</description>
			</item>
			<item>
				<title>let-us do the maths</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/</link>
				<pubDate>Wed, 30 Apr 2025 15:30:52 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/</guid>
				<description>Slow release cycles mean customer needs go unmet and competitors gain an edge. Microsoft’s shift from a two-year delivery cycle to three-week sprints allowed them to deliver features in days, improving customer satisfaction and competitiveness. Accelerate your delivery process to stay relevant and meet customer demands faster.</description>
			</item>
			<item>
				<title>Hiring an Agile Coach: What to Look For in Both Technical and Leadership Engagement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/hiring-an-agile-coach-what-to-look-for-in-both-technical-and-leadership-engagement/</link>
				<pubDate>Tue, 21 Nov 2023 11:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/hiring-an-agile-coach-what-to-look-for-in-both-technical-and-leadership-engagement/</guid>
				<description>When hiring an Agile coach, prioritize candidates who can engage deeply with both technical teams and leadership, as this is key to a successful Agile transformation. Look for strong technical understanding relevant to your industry, business acumen to connect Agile practices to strategic goals, and excellent communication skills to influence at all levels. Choose a coach who fits your culture and can bridge gaps across the organization to drive real business outcomes.</description>
			</item>
			<item>
				<title>Cloud Migration Without the Mayhem: How to Move Legacy Systems Safely and Set Your Teams Up for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/</link>
				<pubDate>Mon, 05 May 2025 06:00:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/</guid>
				<description>Cloud migration works best when approached gradually, using a hybrid model to reduce risk and avoid simply moving existing problems to the cloud. Success depends on understanding both your technology and how your teams work, aligning people and processes, and focusing on long-term maintainability. Treat migration as an ongoing journey, not a rushed project, and invest in shared understanding and continuous improvement to ensure a smooth transition.</description>
			</item>
			<item>
				<title>There a common belief that rollback is the ultimate safety net</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/</link>
				<pubDate>Thu, 13 Feb 2025 15:53:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/</guid>
				<description>Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes.</description>
			</item>
			<item>
				<title>The Importance of Visualizing Your Work in a Kanban Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</link>
				<pubDate>Thu, 07 Mar 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/</guid>
				<description>Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process.</description>
			</item>
			<item>
				<title>Stop Chasing the Hottest Tech Stack: Why Context-Driven Choices Win Every Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-the-hottest-tech-stack-why-context-driven-choices-win-every-time/</link>
				<pubDate>Fri, 06 Jun 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-the-hottest-tech-stack-why-context-driven-choices-win-every-time/</guid>
				<description>Choosing technology based on trends rather than your team’s needs often leads to wasted effort and complexity. Focus on your business goals, team maturity, and constraints to shape a tech strategy that truly fits. Prioritise what delivers value for your context instead of chasing the latest tools.</description>
			</item>
			<item>
				<title>Why compromising on software quality is a leadership decision</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/</link>
				<pubDate>Tue, 01 Apr 2025 15:30:02 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/</guid>
				<description>Compromising on software quality is a leadership decision, not a team one, and lowering standards to meet deadlines carries business risks that should be explicitly approved by leadership. A clear Definition of Done helps maintain consistent quality, and any decision to reduce it should be transparent and deliberate. Development managers should ensure quality expectations are set and upheld at the leadership level, not left to teams under delivery pressure.</description>
			</item>
			<item>
				<title>Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</link>
				<pubDate>Thu, 04 Jan 2024 12:14:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/</guid>
				<description>Relying on special Sprints like Sprint Zero or bug fix Sprints undermines true Agile practices by encouraging risky behavior, diluting focus, and creating a false sense of security. Teams should instead prioritize delivering a usable product at the end of every Sprint, foster accountability, and integrate quality assurance into regular work. Development managers should avoid safety nets and focus on continuous improvement and value delivery each Sprint.</description>
			</item>
			<item>
				<title>Why do you trust Joanna to deliver Scrum.Org classes for NKD Agility?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-do-you-trust-joanna-to-deliver-scrum-org-classes-for-nkd-agility/</link>
				<pubDate>Tue, 22 Aug 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-do-you-trust-joanna-to-deliver-scrum-org-classes-for-nkd-agility/</guid>
				<description>Joanna delivers Scrum.Org classes that combine deep technical expertise with clear, practical Agile training, making complex concepts easy to understand and apply. Her sessions focus on real-world problem-solving, continuous improvement, and effective leadership, helping teams and individuals level up their Agile skills. Development managers should consider her training to boost team performance and confidently navigate Agile transformation.</description>
			</item>
			<item>
				<title>Are technical skills required to be a Scrum Master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</link>
				<pubDate>Sun, 01 Sep 2019 15:37:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/</guid>
				<description>Technical skills are not strictly required to be a Scrum Master, but having a solid understanding of technical, business, and organizational contexts makes a Scrum Master much more effective. Mastery in these areas helps Scrum Masters better support their teams, guide Product Owners, and drive meaningful organizational change. Development managers should ensure their Scrum Masters are equipped with broad contextual knowledge to maximize team and business value.</description>
			</item>
			<item>
				<title>Modernising Legacy Systems: How to Tackle Security Risks Without Breaking Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/</link>
				<pubDate>Mon, 12 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/</guid>
				<description>Modernising legacy systems is essential for security, but rushing the process can create new risks; instead, map your workflows, embed security throughout development, empower teams, and focus on maintainability and compliance. Treat security as an ongoing mindset, not a one-time task, and continuously adapt as threats evolve. Start by assessing how work and security practices flow in your organisation before making changes.</description>
			</item>
			<item>
				<title>The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 16:30:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</guid>
				<description>Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings.</description>
			</item>
			<item>
				<title>Transforming Technical Debt: Unlocking Innovation and Value Through Quality Product Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/</link>
				<pubDate>Thu, 21 Nov 2024 17:01:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/</guid>
				<description>Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to persist leads to higher maintenance costs, slower delivery, and lower team morale, while prioritising high-quality product delivery enables greater agility, consistent value, and innovation. Development managers should regularly assess and address technical debt, foster a culture of quality, and communicate its impact to stakeholders to unlock their teams’ full potential.</description>
			</item>
			<item>
				<title>The Power of Kaizen: Continuous Improvement in Scrum and Beyond</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</link>
				<pubDate>Sun, 25 Aug 2024 22:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/</guid>
				<description>Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum.</description>
			</item>
			<item>
				<title>How important is DevOps in continuous delivery of value to customers?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</link>
				<pubDate>Mon, 20 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</guid>
				<description>DevOps is essential for delivering value to customers because it enables teams to quickly and effectively turn ideas into working software, closely aligning with agile principles. Both DevOps and agile focus on rapid feedback, continuous improvement, and adapting to customer needs, making them deeply interconnected. Development managers should ensure their teams integrate DevOps practices to accelerate delivery, validate value, and reduce risk.</description>
			</item>
			<item>
				<title>Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</link>
				<pubDate>Fri, 17 Apr 2020 18:57:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</guid>
				<description>To succeed with Agile transformation, focus on empowering teams through servant leadership, prioritising valuable product outcomes over feature lists, and fostering continuous improvement to manage technical debt. Enable product owners to drive value, build cross-functional teams, and measure results by customer impact rather than activity. Start with small changes to build momentum and consider expert support if needed.</description>
			</item>
			<item>
				<title>You are doing Scrum but the Scrum Master tells the team what to do!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</link>
				<pubDate>Tue, 13 Sep 2011 20:40:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/</guid>
				<description>Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</link>
				<pubDate>Mon, 16 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</guid>
				<description>DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues.</description>
			</item>
			<item>
				<title>Pragmatism crushes Dogma in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</link>
				<pubDate>Thu, 21 Mar 2024 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/</guid>
				<description>Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively.</description>
			</item>
			<item>
				<title>Mastering Agile: 3 Essential Strategies to Boost Your Team&#39;s Sprint Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</link>
				<pubDate>Thu, 16 Nov 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team&#39;s-sprint-success/</guid>
				<description>To improve your team&amp;rsquo;s Sprint outcomes, clearly define what &amp;ldquo;done&amp;rdquo; means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place.</description>
			</item>
			<item>
				<title>Unlocking the Power of Sprint Planning: Transform Your Agile Approach for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/</link>
				<pubDate>Thu, 29 Jun 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/</guid>
				<description>Effective Sprint planning can transform your team&amp;rsquo;s Agile approach by building shared understanding, enabling hands-on practice with real-time coaching, and fostering continuous improvement through feedback. As teams gain confidence, they should adapt Sprint planning to fit their unique needs and culture. Consider structured workshops with flexible delivery to empower your team to run impactful Sprint planning sessions independently.</description>
			</item>
			<item>
				<title>Unlocking the True Potential of Scrum: Why Professionalism Matters in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</link>
				<pubDate>Thu, 20 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/</guid>
				<description>Many software teams fall short of Scrum’s true potential because organizations prioritize speed over professionalism, leading to shortcuts and unprofessional practices. Achieving real value with Scrum requires a commitment to transparency, production-ready increments each iteration, and honest assessment of current capabilities, often revealing significant gaps. Development managers should focus on fostering a professional work ethic and closing these gaps to unlock Scrum’s full benefits.</description>
			</item>
			<item>
				<title>Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</link>
				<pubDate>Thu, 27 Jul 2017 18:16:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/</guid>
				<description>Great Calm improved team alignment and agility by investing in Scrum training led by a trainer with real engineering experience, which fostered open dialogue and practical learning. The training is expected to enhance communication, align teams with business goals, and empower them to own their processes. Development managers should consider similar real-world-focused training to drive meaningful change and continuous improvement in their teams.</description>
			</item>
			<item>
				<title>Why Using a Blocked Column in Azure DevOps Is a Mistake</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/</link>
				<pubDate>Thu, 20 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/</guid>
				<description>Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving.</description>
			</item>
			<item>
				<title>Hiring an Agile Coach: What You Need to Know</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/hiring-an-agile-coach-what-you-need-to-know/</link>
				<pubDate>Wed, 22 Nov 2023 11:00:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/hiring-an-agile-coach-what-you-need-to-know/</guid>
				<description>When hiring an Agile coach, look for someone who can teach, mentor, and inspire your teams, not just coach them. The right coach will help teams deeply understand Agile practices, foster growth and accountability, and motivate continuous improvement, leading to better alignment, autonomy, and engagement. Prioritize candidates with hands-on experience, strong communication skills, and a good cultural fit to maximize the impact on your organization.</description>
			</item>
			<item>
				<title>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>Deploying Windows OS Directly to Production: Then vs Now</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</link>
				<pubDate>Sat, 22 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</guid>
				<description>Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness.</description>
			</item>
			<item>
				<title>Unmasking Agile: How to Spot Genuine Practices Amidst the Myths</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unmasking-agile-how-to-spot-genuine-practices-amidst-the-myths/</link>
				<pubDate>Wed, 18 Mar 2020 13:56:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unmasking-agile-how-to-spot-genuine-practices-amidst-the-myths/</guid>
				<description>Most organizations claim to be agile, but few actually follow core practices like short iterations, ordered backlogs, and regular retrospectives, which limits their ability to deliver value and improve. Cultural resistance and outdated management styles are major barriers to genuine agility. Development managers should honestly assess their teams against key agile principles and take action to remove obstacles, empower teams, and focus on rapid feedback and continuous improvement.</description>
			</item>
			<item>
				<title>Branch promotion is a relic of slow, manual software delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</link>
				<pubDate>Sat, 08 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</guid>
				<description>Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery.</description>
			</item>
			<item>
				<title>Frequent releases are not just a technical strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</link>
				<pubDate>Fri, 07 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</guid>
				<description>Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback.</description>
			</item>
			<item>
				<title>Transform Your Software Architecture: The Game-Changing Impact of TDD and Pair Programming</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/</link>
				<pubDate>Tue, 19 Nov 2024 16:55:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/</guid>
				<description>Test-driven development and pair programming lead to cleaner, more maintainable software architectures by focusing on essential functionality and fostering collaboration. While pair programming may seem slower at first, it improves code quality, reduces costly bugs, and enhances team skills, resulting in long-term productivity gains. Development managers should consider adopting these practices to build more resilient and scalable systems that align with business goals.</description>
			</item>
			<item>
				<title>The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</link>
				<pubDate>Tue, 22 Oct 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</guid>
				<description>Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress.</description>
			</item>
			<item>
				<title>Are there any Scrum courses that teach you how to scale Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/are-there-any-scrum-courses-that-teach-you-how-to-scale-scrum/</link>
				<pubDate>Wed, 18 Oct 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/are-there-any-scrum-courses-that-teach-you-how-to-scale-scrum/</guid>
				<description>There is no single course that teaches you exactly how to scale Scrum, but courses like Scaled Professional Scrum from Scrum.org provide tools and techniques to help you build a scaling framework tailored to your organization. Key to success are starting small, focusing on dependency management and alignment, and iterating based on feedback. Development managers should invest in team education, select relevant practices, and foster a culture of collaboration and continuous improvement to scale Scrum effectively.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</link>
				<pubDate>Mon, 22 May 2023 14:00:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/</guid>
				<description>A Scrum Master is essential for team effectiveness because they guide teams by understanding business needs, technical practices like DevOps, and organisational change. Without this role, teams often struggle to deliver value quickly and improve continuously. Development managers should ensure their teams have access to a skilled Scrum Master or equivalent expertise to maximize productivity and quality.</description>
			</item>
			<item>
				<title>Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</link>
				<pubDate>Thu, 04 Jun 2020 05:33:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/</guid>
				<description>Focus on team productivity rather than just feature count, and ensure everyone understands the difference between Definition of Done, which sets quality standards, and acceptance criteria, which specify requirements for each item. Use backlog refinement to address unknowns instead of relying on spikes, and plan sprint capacity to accommodate some ad hoc work while maintaining transparency and continuous improvement. Review your team’s approach to these areas to improve delivery and reduce disruptions.</description>
			</item>
			<item>
				<title>From Firefighting to Focus: How CTOs Can Lead with Clarity Instead of Chasing the Next Big Thing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-firefighting-to-focus-how-ctos-can-lead-with-clarity-instead-of-chasing-the-next-big-thing/</link>
				<pubDate>Fri, 23 May 2025 06:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-firefighting-to-focus-how-ctos-can-lead-with-clarity-instead-of-chasing-the-next-big-thing/</guid>
				<description>CTOs should stop chasing every new technology and instead focus on making their systems and decision-making processes visible to identify real improvement opportunities. Effective leadership means building a clear, context-driven strategy and fostering sustainable innovation by investing in team learning and system evolution. Take action by stepping back from survival mode, clarifying how work happens, and leading with intention for long-term value.</description>
			</item>
			<item>
				<title>Understanding Blocked Columns and Stalled Work in Project Boards</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/</link>
				<pubDate>Tue, 04 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/</guid>
				<description>Using a separate &amp;ldquo;Blocked&amp;rdquo; column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible.</description>
			</item>
			<item>
				<title>Too many teams overcomplicate their branching strategies</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</link>
				<pubDate>Thu, 06 Feb 2025 09:38:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</guid>
				<description>Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability.</description>
			</item>
			<item>
				<title>The Common Challenges of Adopting DevOps Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</link>
				<pubDate>Tue, 20 Aug 2024 08:04:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</guid>
				<description>Adopting DevOps brings challenges like managing new types of risk and avoiding setbacks, especially as teams shift from long, structured cycles to rapid, continuous delivery. Success depends on quickly closing feedback loops, acting on real-world data from production, and adapting processes to maintain quality and flexibility. Development managers should focus on integrating feedback into daily workflows and using modern tools to manage risk without slowing down delivery.</description>
			</item>
			<item>
				<title>Is Your Project Ecosystem Truly Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</link>
				<pubDate>Wed, 31 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</guid>
				<description>Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile.</description>
			</item>
			<item>
				<title>Why Are a Scrum Team Better Served by an Agile Consultant than a Professional Coach?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-a-scrum-team-better-served-by-an-agile-consultant-than-a-professional-coach/</link>
				<pubDate>Mon, 26 Jun 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-a-scrum-team-better-served-by-an-agile-consultant-than-a-professional-coach/</guid>
				<description>Scrum teams benefit more from Agile consultants than professional coaches because consultants provide the technical and practical guidance teams often lack, especially in the early stages. Teams need help understanding what they do not know and how to apply effective engineering practices, not just support in finding their own solutions. Development managers should consider bringing in Agile consultants to build foundational knowledge and accelerate team capability.</description>
			</item>
			<item>
				<title>Big Scrum: All you need and not enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</link>
				<pubDate>Wed, 01 Jul 2015 16:33:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/</guid>
				<description>Scaling Scrum requires truly professional teams who embody agile values and strong engineering practices, not just following processes superficially. Off-the-shelf frameworks do not fit every organization, so adapting Scrum to your unique context is essential. Focus on building skilled teams, fostering effective communication, and adopting only the practices that support your specific scaling needs.</description>
			</item>
			<item>
				<title>We hear self-managing teams so often it become a cliché</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</link>
				<pubDate>Fri, 09 May 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/</guid>
				<description>Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction.</description>
			</item>
			<item>
				<title>Building the wrong thing is worse than fixing a bug</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</link>
				<pubDate>Mon, 14 Apr 2025 15:30:31 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</guid>
				<description>Most features built by software teams do not deliver value, with 65 percent considered waste. Shortening feedback loops through frequent reviews and real user input helps teams focus on what matters and avoid building the wrong things. Act now to get faster, actionable feedback and prevent wasted time and resources.</description>
			</item>
			<item>
				<title>We don’t have time for automation, but manual testing slows releases and quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/</link>
				<pubDate>Mon, 07 Apr 2025 15:30:01 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/</guid>
				<description>Relying on manual testing slows releases, overwhelms testers, and lets bugs slip through, making it impossible to keep up with rapid changes. Automation is essential for maintaining both speed and quality in software development. Teams should prioritize moving to automated testing to avoid bottlenecks and improve release reliability.</description>
			</item>
			<item>
				<title>Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</link>
				<pubDate>Tue, 14 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</guid>
				<description>Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement.</description>
			</item>
			<item>
				<title>Unlocking Code Quality: The Transformative Power of Frequent Deployments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</link>
				<pubDate>Mon, 13 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</guid>
				<description>Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance.</description>
			</item>
			<item>
				<title>From Chaos to Clarity: My Journey Through DevOps and the Three Key Challenges to Overcome</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</link>
				<pubDate>Thu, 04 Apr 2024 11:34:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</guid>
				<description>The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster.</description>
			</item>
			<item>
				<title>Rethinking Sprint Planning: Why Burndown Charts Are Agile Banditry and What to Do Instead</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/</link>
				<pubDate>Tue, 09 Jan 2024 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, which is ineffective given the high uncertainty and frequent changes in software development. Instead, start each Sprint with only enough planning to begin work, then reassess and adjust daily to stay flexible and focused on delivering value. Shift your team’s approach to minimal, just-in-time planning to reduce overhead and respond better to change.</description>
			</item>
			<item>
				<title>The Pitfalls of Routine Agile Questions: Avoiding the Ghosts of Agile Past</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</link>
				<pubDate>Wed, 03 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</guid>
				<description>Focusing daily meetings on routine status questions leads to disengagement and distracts from delivering real value. Instead, teams should use these meetings to track progress toward sprint goals, manage aging tasks before they become bottlenecks, and adapt ceremonies to support value delivery and continuous improvement. Review your Agile practices and shift the focus from individual updates to team outcomes for better results.</description>
			</item>
			<item>
				<title>Getting started with a Definition of Done (DoD)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</link>
				<pubDate>Mon, 14 Dec 2020 13:03:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/</guid>
				<description>A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what &amp;ldquo;done&amp;rdquo; means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product.</description>
			</item>
			<item>
				<title>Metrics that matter with evidence-based management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</link>
				<pubDate>Tue, 25 Feb 2014 13:29:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</guid>
				<description>Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement.</description>
			</item>
			<item>
				<title>Building a release pipeline with Release Management with Visual Studio 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</link>
				<pubDate>Tue, 18 Feb 2014 16:30:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</guid>
				<description>Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices.</description>
			</item>
			<item>
				<title>Quality enablement to achieve predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</link>
				<pubDate>Wed, 24 Jul 2013 09:46:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</guid>
				<description>Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance.</description>
			</item>
			<item>
				<title>If software is not delivered, it is not valuable</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</link>
				<pubDate>Sat, 01 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</guid>
				<description>Undelivered software provides no value, and long development cycles increase risk, cost, and missed opportunities. Research shows that teams releasing software frequently are more successful and efficient. To maximize value and learning, prioritize frequent delivery to users.</description>
			</item>
			<item>
				<title>A two-day Scrum Master certification doesn’t make you a Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</link>
				<pubDate>Thu, 27 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/</guid>
				<description>A two-day Scrum Master certification alone is not enough to prepare someone for the real challenges of leading Scrum Teams and delivering value. Effective Scrum Masters have hands-on experience, understand code quality and DevOps, and have navigated real-world obstacles. Companies should prioritize hiring or developing Scrum Masters with proven experience rather than relying solely on certifications.</description>
			</item>
			<item>
				<title>Transforming Waste into Value: How to Boost ROI with Agile Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</link>
				<pubDate>Tue, 17 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</guid>
				<description>Most organisations lose significant value due to waste and lack of focus on engineering excellence, with metrics showing that only a small fraction of development investment results in features customers actually use. Key insights include low innovation rates, poor feature usage, and lagging version adoption, all of which drastically reduce ROI. Development managers should measure and act on innovation and usage metrics, close feedback loops, and focus on delivering value rather than just reducing costs.</description>
			</item>
			<item>
				<title>The Evolution of My Journey with Azure DevOps: Lessons and Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/</link>
				<pubDate>Wed, 31 Jul 2024 09:21:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/</guid>
				<description>Azure DevOps has evolved from TFS to a powerful, flexible platform that can transform team workflows, but successful adoption and migration require careful planning and sometimes custom solutions. Key lessons include the importance of assessing your environment, choosing the right migration tools, and leveraging expert guidance for complex needs. Development managers should ensure their teams are trained and consider consulting support to maximize the benefits and scalability of Azure DevOps.</description>
			</item>
			<item>
				<title>Mastering Caman Strategy: How to Leverage Azure DevOps for Effective Visualisation in Hybrid Work Environments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/</link>
				<pubDate>Fri, 29 Mar 2024 16:42:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/</guid>
				<description>Using Azure DevOps to implement a Caman strategy helps hybrid teams visualise and manage work more effectively by establishing shared workflow rules, customising boards and columns, and tracking key metrics like lead and cycle time. Involving the whole team in defining and refining these rules improves transparency and reduces local optimisations that can harm overall flow. Development managers should ensure their teams collaborate on workflow setup in Azure DevOps and regularly review it to optimise efficiency and clarity.</description>
			</item>
			<item>
				<title>Mastering Scrum: Essential Insights for New Teams from a Scrum Master&#39;s Journey</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</link>
				<pubDate>Tue, 28 Nov 2023 11:00:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-master&#39;s-journey/</guid>
				<description>New Scrum teams succeed when they deeply understand Scrum principles, empiricism, and core values, which the Scrum Master should actively teach and reinforce. Practical workshops, real-world examples, and a focus on continuous learning help teams build trust, adapt to change, and improve over time. Development managers should ensure their teams have ongoing support and a safe environment to foster growth and agility.</description>
			</item>
			<item>
				<title>Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</link>
				<pubDate>Thu, 27 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</guid>
				<description>If teams do not deliver a usable product at the end of each iteration, trust with stakeholders erodes, technical debt grows, adaptability slows, and expectations become misaligned. This also leads to lower team morale and a lack of feedback, making it hard to improve or stay on track. To avoid these issues, ensure every iteration results in a usable product so you maintain trust, alignment, and the ability to adapt quickly.</description>
			</item>
			<item>
				<title>Stop normalizing unprofessional behaviour in the name of agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/</link>
				<pubDate>Mon, 19 Apr 2021 14:04:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/</guid>
				<description>Unprofessional behavior should not be excused as part of agile practices, as true agility requires professionalism, discipline, and competence. Failing to deliver usable increments, lacking team understanding of goals, and rigid processes undermine agility and can lead to serious consequences. Development managers should actively address and correct unprofessional behaviors to ensure ethical, effective, and sustainable agile delivery.</description>
			</item>
			<item>
				<title>Staging Environments Do Not Prevent Production Failures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</link>
				<pubDate>Fri, 28 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</guid>
				<description>Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems.</description>
			</item>
			<item>
				<title>Every unreleased feature is a cost</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</link>
				<pubDate>Wed, 05 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</guid>
				<description>Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team&amp;rsquo;s efforts translate into actual value.</description>
			</item>
			<item>
				<title>Maximising Product Value: The Power of Hypothesis-Driven Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</link>
				<pubDate>Wed, 11 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</guid>
				<description>Focusing on hypothesis-driven engineering helps teams maximise product value by testing ideas with small experiments, measuring outcomes, and quickly adapting based on real customer feedback. The Azure DevOps team’s experience showed that even costly initiatives can provide critical learning, allowing resources to be redirected before larger losses occur. Development managers should encourage rapid experimentation and validation at all levels to ensure investments deliver real value and support agility.</description>
			</item>
			<item>
				<title>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>Biggest contribution from a Product Owner that you know of</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/biggest-contribution-from-a-product-owner-that-you-know-of/</link>
				<pubDate>Tue, 13 Jun 2023 11:32:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/biggest-contribution-from-a-product-owner-that-you-know-of/</guid>
				<description>Brian Harry and Aaron Bjork at Microsoft transformed product development by shifting from slow, two-year release cycles to rapid, three-week feedback loops, driving a major cultural and process shift toward Agile across the organization. Their leadership and collaboration, supported by executive buy-in, embedded sustainable Agile practices and set a new industry standard for balancing scale with agility. Development managers should recognize the impact that visionary Product Owners can have in driving both process and cultural change, and prioritize empowering such leaders within their teams.</description>
			</item>
			<item>
				<title>Big Scrum: Are you doing mechanical Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</link>
				<pubDate>Wed, 24 Jun 2015 13:43:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/</guid>
				<description>Many organizations adopt Scrum hoping for rapid productivity gains but are disappointed when they only follow the motions without embracing its core values and technical excellence. True effectiveness and faster delivery come from practicing Professional Scrum, which means living the principles and focusing on quality, not just the framework. Development managers should ensure their teams go beyond mechanical Scrum and invest in building a professional culture to achieve real results.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</link>
				<pubDate>Fri, 25 Oct 2024 07:02:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/</guid>
				<description>Many Scrum Masters misunderstand their true responsibilities, focusing on tools and rituals instead of the core principles and accountabilities defined by Scrum. Effective Scrum Masters balance support for the team, Product Owner, and organisation, acting as coaches and mentors rather than process enforcers. Development managers should ensure Scrum Masters are competent in Scrum’s philosophies and adapt practices to fit their context, not just follow common routines.</description>
			</item>
			<item>
				<title>Empowering Your Team: Why Quick Fixes in Agile and DevOps Are a Myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-your-team-why-quick-fixes-in-agile-and-devops-are-a-myth/</link>
				<pubDate>Thu, 09 May 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-your-team-why-quick-fixes-in-agile-and-devops-are-a-myth/</guid>
				<description>There are no quick fixes for Agile or DevOps transformation; relying on external parties or contractors to deliver ready-made solutions does not build lasting capability. Sustainable change comes from empowering your own team through learning, collaboration, and continuous improvement, with consultants serving as guides rather than doers. Invest in developing your people and culture to achieve real, long-term agility.</description>
			</item>
			<item>
				<title>You can&#39;t stop the signal! But you can ignore it!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</link>
				<pubDate>Wed, 17 Apr 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</guid>
				<description>Agile and Scrum frameworks highlight problems in team processes, but many organizations ignore these signals due to cultural barriers like fear of repercussions and resistance to change. Simply adopting these frameworks is not enough; their effectiveness depends on a culture that encourages transparency, feedback, and continuous improvement. Development managers should focus on building an environment where raising and addressing issues is supported and valued to fully realize the benefits of Agile and Scrum.</description>
			</item>
			<item>
				<title>Scrum is like communism, it doesn&#39;t work. Myth 3</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-3/</link>
				<pubDate>Wed, 25 Oct 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn&#39;t-work-myth-3/</guid>
				<description>Scrum does not inherently lead to micromanagement; this misconception arises when organizations misapply Scrum by imposing top-down control instead of empowering teams. True Scrum gives developers autonomy over their work, encourages open collaboration, and relies on trust and technical expertise. Development managers should focus on enabling team decision-making and fostering a culture of trust to realize the full benefits of Agile.</description>
			</item>
			<item>
				<title>Can you align DevOps and Software Engineering Teams Through Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-you-align-devops-and-software-engineering-teams-through-scrum/</link>
				<pubDate>Fri, 16 Jun 2023 14:30:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-you-align-devops-and-software-engineering-teams-through-scrum/</guid>
				<description>Scrum can effectively align DevOps and software engineering teams by promoting transparency, regular delivery of usable products, and continuous feedback. Achieving this alignment requires discipline and integrating DevOps practices into Scrum workflows. Development managers should focus on embedding these practices to drive better collaboration and higher-quality outcomes.</description>
			</item>
			<item>
				<title>Unlocking Value in DevOps: My Role as a Consultant in Driving Change and Overcoming Bottlenecks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</link>
				<pubDate>Tue, 02 May 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</guid>
				<description>As a DevOps consultant, my main focus is helping teams rethink how they deliver value by identifying and addressing both technical and process bottlenecks, such as slow builds or approval delays. I do this by asking targeted questions and encouraging teams to examine their workflows, which leads to continuous improvement and better customer outcomes. Development managers should regularly review their processes to spot and resolve the biggest sources of delay.</description>
			</item>
			<item>
				<title>Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</link>
				<pubDate>Fri, 28 Apr 2023 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</guid>
				<description>Focusing on Scrum rituals instead of its core principles, empiricism, transparency, and delivering value, can hinder true agile success. Overemphasis on mechanics leads to misplaced priorities, reduced creativity, and lower team engagement. Development managers should encourage open dialogue, support experimentation, and regularly assess whether practices are truly delivering value, adapting or discarding those that do not.</description>
			</item>
			<item>
				<title>If your backlog is not refined then you are doing it wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</link>
				<pubDate>Thu, 17 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/</guid>
				<description>If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints.</description>
			</item>
			<item>
				<title>Embracing Process Improvement: How Understanding Scrum Transformed a Developer&#39;s Mindset</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</link>
				<pubDate>Thu, 27 Jul 2017 19:14:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</guid>
				<description>Understanding and embracing Scrum processes can transform developer mindsets, leading to better collaboration, higher quality product delivery, and more empowered teams. Taking time to learn and refine processes is essential for sustainable success, not just individual productivity. Development managers should encourage their teams to invest in process improvement to drive long-term value and team growth.</description>
			</item>
			<item>
				<title>Constructing a framework for the TFS Automation Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/constructing-a-framework-for-the-tfs-automation-platform/</link>
				<pubDate>Sun, 12 Jun 2011 04:44:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/constructing-a-framework-for-the-tfs-automation-platform/</guid>
				<description>Outlines the structure and components of a framework for the TFS Automation Platform, detailing its architecture, plugin management, and development approach.</description>
			</item>
			<item>
				<title>Guidance - Branching for each Sprint</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-branching-for-each-sprint/</link>
				<pubDate>Thu, 08 Apr 2010 16:34:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-branching-for-each-sprint/</guid>
				<description>Explains how using a separate version control branch for each sprint in Scrum improves code stability, release management, and team collaboration over using labels.</description>
			</item>
			<item>
				<title>Navigating the Legacy System Labyrinth: Strategies for Modernisation Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-legacy-system-labyrinth-strategies-for-modernisation-success/</link>
				<pubDate>Mon, 07 Apr 2025 06:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-legacy-system-labyrinth-strategies-for-modernisation-success/</guid>
				<description>Modernising legacy systems is complex because they are deeply tied to business processes, compliance, and fragile integrations, making change risky and disruptive. Security vulnerabilities and lack of scalability add to the challenge, so a clear strategy focused on incremental improvements and strategic replacements is essential. Development managers should assess their systems holistically and pursue manageable, stepwise changes to enable long-term organisational success.</description>
			</item>
			<item>
				<title>Too many Scrum Masters believe they don’t need technical skills</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/</link>
				<pubDate>Mon, 24 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/</guid>
				<description>Scrum Masters need relevant technical and domain knowledge to effectively support their teams, not just certifications. Without understanding the specific challenges and practices of their team&amp;rsquo;s work, they cannot truly enable success. Development managers should ensure Scrum Masters have or develop the necessary expertise to make a meaningful impact.</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>Live Site Culture &amp; Site Reliability Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</link>
				<pubDate>Wed, 17 Jun 2020 13:23:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</guid>
				<description>To stay competitive in a fast-changing market, teams must adopt DevOps and continuous delivery, shifting from infrequent releases to deploying updates daily. This requires faster feedback, shared responsibility for quality and operations, and new ways of working, as shown by Microsoft&amp;rsquo;s Azure DevOps team. Development managers should consider evolving their team structures and practices to support rapid, customer-focused delivery.</description>
			</item>
			<item>
				<title>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>Most teams don’t fail because they lack frameworks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</link>
				<pubDate>Mon, 05 May 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</guid>
				<description>Teams usually fail not because they lack frameworks like Agile or Scrum, but because they ignore the feedback these frameworks reveal. The real challenge is creating a culture where teams feel safe and empowered to act on what they learn. Development managers should focus on listening to feedback and enabling teams to address issues, which leads to better performance and competitive advantage.</description>
			</item>
			<item>
				<title>Here the dirty secret behind many agile transformations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</link>
				<pubDate>Fri, 02 May 2025 15:30:32 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/</guid>
				<description>Many agile transformations fail because organizations maintain tight control over how work is done while claiming to empower teams. True agility requires leadership to set clear goals and priorities but let teams decide how to achieve them. To foster commitment and improvement, review where your processes still dictate the how and shift toward real team autonomy.</description>
			</item>
			<item>
				<title>Empowering Teams to Maximize Value and Return on Investment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</link>
				<pubDate>Wed, 24 Jul 2024 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</guid>
				<description>Empowering teams to adapt their own processes is essential for maximizing value and return on investment in Agile environments. Teams that have autonomy, leadership support, and a culture of continuous improvement consistently outperform those forced to follow rigid, standardized processes. Development managers should trust teams to tailor their workflows, provide the necessary tools and support, and focus on outcomes rather than strict process adherence.</description>
			</item>
			<item>
				<title>How effectively does an APS prepare a team to do a solid, professional Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</link>
				<pubDate>Sat, 12 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/</guid>
				<description>The Applied Professional Scrum (APS) course helps teams focus on delivering a working product every iteration and sheds unhelpful habits that slow progress. Through practical exercises like the &amp;ldquo;Barnacle Exercise,&amp;rdquo; teams identify and remove outdated practices, leading to more effective Scrum adoption. Development managers should consider APS to build teams that consistently deliver value and embody true Scrum principles.</description>
			</item>
			<item>
				<title>Release Management with Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</link>
				<pubDate>Wed, 24 Apr 2013 17:38:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</guid>
				<description>Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality.</description>
			</item>
			<item>
				<title>Professional Scrum Developer (.NET) Training in London</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</link>
				<pubDate>Fri, 18 Jun 2010 15:53:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/</guid>
				<description>Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies.</description>
			</item>
			<item>
				<title>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>Too much refinement wastes time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-much-refinement-wastes-time/</link>
				<pubDate>Tue, 29 Apr 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-much-refinement-wastes-time/</guid>
				<description>Too much backlog refinement wastes time, while too little causes confusion and delays. Aim for just enough detail so developers can start work confidently without needing constant clarification. If Sprint Planning is about making commitments rather than figuring things out, your refinement process is working well.</description>
			</item>
			<item>
				<title>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</link>
				<pubDate>Wed, 05 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</guid>
				<description>Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</link>
				<pubDate>Fri, 13 Sep 2024 07:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</guid>
				<description>Evidence-based management in Scrum focuses on four key value areas, current value, unrealized value, ability to innovate, and time to market, to guide data-driven decisions and balance innovation with stability. Tracking metrics in these areas helps teams improve customer satisfaction, identify growth opportunities, manage technical debt, and speed up delivery. Development managers should start measuring these areas to align teams with evidence-based management and drive sustainable product success.</description>
			</item>
			<item>
				<title>Overcoming the Plague of Rigidity: Embracing True Agility in Your Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/</link>
				<pubDate>Wed, 08 Nov 2023 11:00:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/</guid>
				<description>Rigidly sticking to tools and processes can cause teams to stagnate, resist change, and miss out on innovation. True agility comes from regularly reassessing practices, encouraging experimentation, and focusing on outcomes rather than methods. Development managers should foster a culture of continuous improvement and adaptability to keep their teams responsive and effective.</description>
			</item>
			<item>
				<title>Decoding Scrum Team Work: Balancing Sprint and Refinement Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</link>
				<pubDate>Thu, 14 Sep 2023 14:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/</guid>
				<description>Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: How Empirical Models Transform Project Outcomes</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</link>
				<pubDate>Wed, 12 Oct 2022 17:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</guid>
				<description>Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>Scaling Professional Scrum with Visual Studio Team Services</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scaling-professional-scrum-with-visual-studio-team-services/</link>
				<pubDate>Wed, 06 Jul 2016 12:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scaling-professional-scrum-with-visual-studio-team-services/</guid>
				<description>Visual Studio Team Services helps reduce friction and risks when scaling Scrum across multiple teams by providing robust automation and support for organizing work within a Nexus framework. Workshops and webcasts demonstrated how VSTS can be set up to manage many teams effectively, making it a strong choice for enterprise-scale Scrum. Development managers should consider VSTS when coordinating large, distributed Scrum teams to streamline processes and improve visibility.</description>
			</item>
			<item>
				<title>Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/</link>
				<pubDate>Thu, 29 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/</guid>
				<description>Upgrading legacy .NET projects to SDK-style makes your codebase easier to maintain, improves build and CI/CD integration, and prepares you for future .NET upgrades. Converting class libraries is straightforward and highly recommended, while web apps require more care and are best handled with the MSBuild.SDK.SystemWeb package if you want SDK-style; otherwise, you can leave them in the old format. Start by converting class libraries now to simplify your engineering system and reduce technical debt.</description>
			</item>
			<item>
				<title>How to Be an Effective Agile Coach: Agnosticism in Practice</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</link>
				<pubDate>Tue, 14 Nov 2023 11:00:50 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/</guid>
				<description>Effective Agile coaching means being flexible and not pushing one framework; instead, help teams understand core Agile, Lean, and Scrum principles so they can choose what works best for their context. Encourage experimentation, educate teams on different approaches, and support their decision-making process. Focus on enabling teams to own their process and continuously improve rather than prescribing solutions.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile Apocalypse - Plague</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-plague/</link>
				<pubDate>Fri, 20 Oct 2023 07:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-plague/</guid>
				<description>Many organizations are undermined by unqualified Agile coaches and Scrum Masters who lack real understanding and experience, leading to harmful practices, lost trust in Agile, and reduced team performance. Key issues include rigid rule enforcement, lack of inclusivity, and prioritizing process over people. To avoid these pitfalls, prioritize hiring experienced, continuously learning Agile leaders who embody true Agile values and focus on team empowerment and value delivery.</description>
			</item>
			<item>
				<title>How Much of An Impact can Scrum Have in a DevOps Environment?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-much-of-an-impact-can-scrum-have-in-a-devops-environment/</link>
				<pubDate>Thu, 15 Jun 2023 14:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-much-of-an-impact-can-scrum-have-in-a-devops-environment/</guid>
				<description>Combining Scrum and DevOps creates a powerful approach that boosts speed, collaboration, and product quality in software development. Scrum provides structure and problem-solving strategies, while DevOps brings automation and efficient delivery. Development managers should consider integrating both to maximize team performance and deliver better products faster.</description>
			</item>
			<item>
				<title>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</link>
				<pubDate>Thu, 08 May 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</guid>
				<description>Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives.</description>
			</item>
			<item>
				<title>Unlocking the True Power of Continuous Delivery: How Automation Transforms Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</link>
				<pubDate>Fri, 06 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</guid>
				<description>The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently.</description>
			</item>
			<item>
				<title>Security by Design Building Secure Software</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/</link>
				<pubDate>Tue, 26 Nov 2024 13:35:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/</guid>
				<description>Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation.</description>
			</item>
			<item>
				<title>Agile is Not New: A Journey Back to the Basics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/</link>
				<pubDate>Thu, 10 Oct 2024 15:48:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/</guid>
				<description>Agile is rooted in centuries-old practices focused on human connection and adaptability, but mass production and Taylorism shifted work toward efficiency at the cost of empathy and craftsmanship. The Agile movement aimed to restore these values, yet many organizations now face a competence gap, hiring for Agile roles without ensuring the necessary skills, which leads to disappointing results. Development managers should prioritize building real competence and continuous learning in their teams to realize Agile’s true benefits and prepare for a coming reset that emphasizes value, empathy, and adaptability over rigid processes.</description>
			</item>
			<item>
				<title>Detecting Agile BS: Lessons from the US Department of Defense</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</link>
				<pubDate>Fri, 28 Jun 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/</guid>
				<description>Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense&amp;rsquo;s &amp;ldquo;Detecting Agile BS&amp;rdquo; guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation.</description>
			</item>
			<item>
				<title>How long does it take to transition from project management to Kanban?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</link>
				<pubDate>Fri, 16 Feb 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</guid>
				<description>Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams.</description>
			</item>
			<item>
				<title>The Overlooked Virtue of Agility: Diligence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/</link>
				<pubDate>Thu, 07 Dec 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/</guid>
				<description>Diligence, or consistently following through on quality standards like the definition of done, is often overlooked in Agile teams but is essential for reliable delivery and long-term success. Without diligence, teams risk inconsistent quality and increased rework, while a strong focus on it leads to better products and faster delivery over time. Development managers should ensure the definition of done is clear, visible, and enforced, and foster a culture of accountability and perseverance to make diligence a team habit.</description>
			</item>
			<item>
				<title>Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</link>
				<pubDate>Mon, 13 Nov 2023 06:56:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/</guid>
				<description>A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk.</description>
			</item>
			<item>
				<title>Do you want to be an ALM Consultant?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-want-to-be-an-alm-consultant/</link>
				<pubDate>Fri, 14 Jan 2011 21:07:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-want-to-be-an-alm-consultant/</guid>
				<description>Role overview for an ALM Consultant at Northwest Cadence, focusing on software lifecycle management, training, consulting, and technical leadership using Microsoft technologies.</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>Detecting Agile BS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/</guid>
				<description>Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and critical evaluation questions.</description>
			</item>
			<item>
				<title>Stop Starting and Start Finishing: The Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</link>
				<pubDate>Wed, 31 Jan 2024 14:26:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</guid>
				<description>Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Chaos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-chaos/</link>
				<pubDate>Mon, 23 Oct 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-chaos/</guid>
				<description>Chaos in agile transformations often arises from unclear product vision and poor communication, leading to misalignment and confusion. To overcome this, development managers should establish a clear strategic direction, break it down into actionable goals, and reinforce it through ongoing communication and feedback. Focus on principles that empower teams and ensure everyone understands how their work contributes to shared objectives.</description>
			</item>
			<item>
				<title>Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</link>
				<pubDate>Fri, 20 Oct 2023 16:01:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</guid>
				<description>Many teams claim to be Agile but stall due to issues like not delivering working software each Sprint, lacking clear goals, ignoring user feedback, slow deployments, rigid requirements, and resistance to process change. These signs indicate a lack of true agility and hinder progress. Development managers should honestly assess their teams for these problems and take action to empower teams, streamline feedback and deployment, and adapt processes as needed.</description>
			</item>
			<item>
				<title>7 harbingers of the Agile apocalypse - Judgement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</link>
				<pubDate>Fri, 20 Oct 2023 11:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</guid>
				<description>Rigid, judgmental application of Agile frameworks stifles creativity and innovation, turning teams into rule-followers instead of problem-solvers. True agility comes from empowering teams with autonomy, transparency, and principles rather than enforcing one-size-fits-all rules. Development managers should focus on fostering a culture of openness and continuous learning, allowing teams to adapt practices to their unique needs.</description>
			</item>
			<item>
				<title>Quotes: Less is More. True or False?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</link>
				<pubDate>Sat, 14 Oct 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</guid>
				<description>Focusing on fewer, high-value tasks rather than trying to do everything leads to better productivity and higher quality in Agile teams. Regularly refining the backlog and planning sprints around essential work helps eliminate waste and ensures efforts align with project goals. Development managers should encourage teams to prioritize what matters most to maximize results.</description>
			</item>
			<item>
				<title>From Unused Gym Memberships to Agile Implementation The Parallels of Misapplied Investments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/</link>
				<pubDate>Thu, 03 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/</guid>
				<description>Adopting agile methods is like buying a gym membership; real benefits come only with consistent, committed practice rather than superficial adoption. Key to success are breaking down goals, fostering cross-functional teams, and maintaining quality instead of just following rituals. Development managers should focus on genuine agile implementation and ongoing improvement to avoid wasted investment and missed opportunities.</description>
			</item>
			<item>
				<title>How Usable Working Products Are Your Ultimate Weapon Against Risks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</link>
				<pubDate>Thu, 20 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</guid>
				<description>Continuously delivering a usable working product is the most effective way to reduce risk in Agile development. Focus on releasing functional increments, fixing bugs quickly, automating tests, and keeping documentation lean to stay responsive to market needs. Prioritise regular feedback from users and stakeholders to ensure you are building what truly adds value.</description>
			</item>
			<item>
				<title>How does a Scrum team decide on a Sprint goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</guid>
				<description>A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable.</description>
			</item>
			<item>
				<title>Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</link>
				<pubDate>Tue, 23 Aug 2022 16:53:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/</guid>
				<description>The Scaled Professional Scrum course helps teams address common challenges in scaling Scrum, such as managing cross-team dependencies, maintaining self-management, and ensuring transparency. Through hands-on, interactive sessions, participants gain practical techniques and tools to structure and manage large agile projects effectively. Development managers looking to scale Scrum without unnecessary overhead should consider this course to equip their teams with proven practices and ongoing support.</description>
			</item>
			<item>
				<title>Evidence-based Management: Gathering the metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</link>
				<pubDate>Wed, 30 Dec 2020 14:02:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</guid>
				<description>Evidence-based Management helps software organizations focus on delivering real value by tracking metrics in three areas: current value, time to market, and ability to innovate. Traditional measures like on-time and on-budget delivery miss customer value, so organizations should gather and regularly review these agile-focused metrics to guide improvement. Start collecting baseline data now and reassess quarterly to track progress and demonstrate the impact of agile investments.</description>
			</item>
			<item>
				<title>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>Professional Scrum Courses for 2016 in Oslo, Norway</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-courses-for-2016-in-oslo-norway/</link>
				<pubDate>Wed, 06 Jan 2016 16:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-courses-for-2016-in-oslo-norway/</guid>
				<description>Recent Professional Scrum Master and Developer courses in Norway have been highly successful, attracting participants from top companies and leading to additional sessions being scheduled in Oslo and Kongsberg. The Scrum Master course focuses on advanced skills for experienced practitioners, while the Developer course emphasizes practical DevOps and Agile practices using Microsoft tools. Development managers should consider enrolling their teams to enhance Scrum mastery and technical delivery capabilities.</description>
			</item>
			<item>
				<title>Continuous value delivery with modern business applications</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</link>
				<pubDate>Tue, 27 Nov 2012 23:00:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</guid>
				<description>Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates.</description>
			</item>
			<item>
				<title>The True Role of a Scrum Master Beyond Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</link>
				<pubDate>Tue, 25 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/</guid>
				<description>A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation.</description>
			</item>
			<item>
				<title>Mastering Agile: The Power of &#34;Just Enough and No More&#34; for Optimal Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/</link>
				<pubDate>Tue, 05 Dec 2023 11:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/</guid>
				<description>Applying the principle of &amp;ldquo;just enough and no more&amp;rdquo; across backlog management, team size, refinement, and planning helps teams stay focused, efficient, and adaptable. Prioritising value, embracing simplicity, and iterating regularly reduces wasted effort and maximises productivity. Development managers should encourage teams to do only what is necessary to deliver value and continuously improve.</description>
			</item>
			<item>
				<title>From Software Engineer to Scrum Trainer: How My Journey Shapes Effective DevOps Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-software-engineer-to-scrum-trainer-how-my-journey-shapes-effective-devops-training/</link>
				<pubDate>Fri, 20 Jan 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-software-engineer-to-scrum-trainer-how-my-journey-shapes-effective-devops-training/</guid>
				<description>The author’s journey from software engineer to Scrum trainer, including recognition as a Microsoft MVP and extensive DevOps consulting across multiple industries, shapes a practical and relatable training style. Key insights include the value of learning from both successes and failures, the motivational power of real-world stories, and the belief that any team can move toward continuous delivery. Development managers should consider leveraging trainers with hands-on experience to inspire teams and drive meaningful change.</description>
			</item>
			<item>
				<title>Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</link>
				<pubDate>Tue, 21 Jul 2020 18:00:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</guid>
				<description>Many teams claim to be agile but still operate with outdated management mindsets that stifle autonomy and engagement, leading to low adoption of core agile practices like short iterations and retrospectives. True agility requires transparency, regular feedback, and a focus on delivering value rather than just completing tasks. Development managers should assess whether their teams meet these criteria and actively foster a culture that supports genuine agile principles.</description>
			</item>
			<item>
				<title>The Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</guid>
				<description>A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems.</description>
			</item>
			<item>
				<title>The Importance of Delivering Working Software Every Iteration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</link>
				<pubDate>Wed, 26 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</guid>
				<description>Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort.</description>
			</item>
			<item>
				<title>How does a Scrum Master or Agile coach motivate a Scrum Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</link>
				<pubDate>Mon, 11 Sep 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/</guid>
				<description>Scrum Masters and Agile coaches play a key role in keeping teams motivated by aligning goals with stakeholder value, celebrating achievements, and fostering open communication. Teams lose motivation when goals are misaligned or stakeholder engagement is lacking, so it is important to set achievable objectives, involve stakeholders, and encourage autonomy and continuous learning. Regularly review team morale, connect work to its broader impact, and create feedback loops to maintain a resilient and high-performing team.</description>
			</item>
			<item>
				<title>Unlocking Agility: How EPS Immersive Learning Transforms Your Team&#39;s Performance</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agility-how-eps-immersive-learning-transforms-your-team&#39;s-performance/</link>
				<pubDate>Wed, 16 Aug 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agility-how-eps-immersive-learning-transforms-your-team&#39;s-performance/</guid>
				<description>The EPS immersive learning experience offers structured, ongoing coaching and feedback that helps teams improve agility and effectiveness with minimal time investment. Through iterative assignments, tailored feedback, and additional coaching, teams can continuously adapt and enhance their practices. To get the most value, managers should actively engage with the process and integrate learnings into daily work.</description>
			</item>
			<item>
				<title>What is your favourite DevOps consulting outcome?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/</link>
				<pubDate>Tue, 18 Apr 2023 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/</guid>
				<description>A fragmented, multi-billion-dollar software project with 80 to 90 teams across nine countries was transformed by unifying processes and source control onto Azure DevOps, greatly improving collaboration and efficiency. The key outcomes were simplification, system unification, and a shift toward a &amp;lsquo;One Engineering System&amp;rsquo; approach. Development managers should consider consolidating tools and processes to drive similar improvements in productivity and teamwork.</description>
			</item>
			<item>
				<title>What would you advise a scrum team to do in their first 4 weeks?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</link>
				<pubDate>Thu, 16 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/</guid>
				<description>In the first four weeks, a scrum team should focus on practicing scrum correctly, learning both what works and what does not, and experimenting to find the best fit for their context. Teams should document obstacles and improvements, address one key change per sprint, and use retrospectives to drive continuous improvement. This approach builds a strong foundation and helps make organizational issues visible for future action.</description>
			</item>
			<item>
				<title>Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</link>
				<pubDate>Sun, 14 Apr 2024 12:17:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/</guid>
				<description>Achieving true agility requires more than adopting Agile practices; organisations often fall into seven common traps such as seeking quick fixes, overloading backlogs, focusing on resource utilisation over value, lacking accountability, fostering blame, copying others blindly, and letting pride block learning. These behaviours hinder innovation, value delivery, and team effectiveness. Development managers should regularly assess and address these pitfalls, tailor Agile to their context, and foster a culture of continuous improvement and honest reflection.</description>
			</item>
			<item>
				<title>Why Every Scrum Master Needs an Immersive Training Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</link>
				<pubDate>Tue, 21 Nov 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/</guid>
				<description>Immersive training is essential for Scrum Masters who already have hands-on experience, as it deepens practical skills, sharpens leadership abilities, and drives better team outcomes. Unlike standard courses, immersive classes focus on real-world challenges, immediate feedback, and peer learning, helping Scrum Masters maximize team value and effectiveness. Development managers should encourage experienced Scrum Masters to pursue immersive training to foster continuous improvement and stronger team leadership.</description>
			</item>
			<item>
				<title>Quotes: &#34;I estimate that 75% of those organisations using Scrum will not succeed in getting the benefits that they hope for from it.&#34; - Ken Schwaber</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</link>
				<pubDate>Fri, 06 Oct 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/</guid>
				<description>Most organisations using Scrum do not achieve the benefits they expect because they focus on team-level practices instead of making broader organisational changes. Success requires adopting an agile mindset across the whole company, securing management support, and continuously improving processes. Development managers should drive holistic transformation beyond just the development team to increase the chances of real Scrum success.</description>
			</item>
			<item>
				<title>Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</link>
				<pubDate>Mon, 06 Mar 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/</guid>
				<description>Many Scrum Masters focus too much on administrative tasks like Jira management instead of empowering their teams and supporting the Product Owner and organization. The Advanced PSM course highlights the importance of enabling team accountability, facilitating value delivery, and addressing organizational barriers. Development managers should encourage Scrum Masters to move beyond admin work and focus on building team capability and organizational agility.</description>
			</item>
			<item>
				<title>What is the hardest part of working with a brand-new scrum team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</link>
				<pubDate>Fri, 03 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/</guid>
				<description>The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement.</description>
			</item>
			<item>
				<title>Professional Scrum is for everyone in your organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</link>
				<pubDate>Tue, 16 Jan 2018 13:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/</guid>
				<description>Scrum works best when everyone in the organisation is involved, not just the development teams, as this breaks down old management habits and empowers people at all levels to contribute to value delivery. Training all staff together surfaces misconceptions, encourages open discussion, and creates a shared understanding that drives real change. To maximise the benefits, managers should ensure broad participation in Scrum training and use the resulting organisational change backlog to remove barriers to effective software delivery.</description>
			</item>
			<item>
				<title>Not all surprises in product development are true unknowns</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/</link>
				<pubDate>Mon, 28 Apr 2025 15:30:55 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/</guid>
				<description>Many surprises in product development are due to poor backlog management rather than true unknowns. Regularly reviewing and categorizing past surprises helps teams improve their backlog and anticipate issues. Development managers should ensure their teams use backlog refinement to build foresight and reduce avoidable disruptions.</description>
			</item>
			<item>
				<title>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>Challenging Misconceptions About Behaviour in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</link>
				<pubDate>Thu, 13 Feb 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/</guid>
				<description>Agile is often misused to justify poor planning and lack of accountability, but true agility demands more discipline, professionalism, and clear alignment with the product vision. Teams that fail to deliver usable increments or start work without sufficient understanding are not practicing real Agile. Development managers should ensure their teams uphold high standards and address unprofessional behavior rather than excusing it as Agile.</description>
			</item>
			<item>
				<title>Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/</link>
				<pubDate>Tue, 13 Feb 2024 15:44:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/</guid>
				<description>Using Blocked columns on Kanban boards hides the true status of work, encourages team disengagement, and leads to stale tasks and inflated work-in-progress limits. Instead, teams should tag blocked items within their current workflow stage and provide clear context, which maintains transparency and accountability. Managers should avoid Blocked columns and use tags or annotations to highlight issues without disrupting the flow or losing critical information.</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>Story Points &amp; Velocity are a sign of an unsuccessful team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</link>
				<pubDate>Mon, 04 Jan 2021 14:20:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</guid>
				<description>Story points and velocity are not required by Scrum and relying on them long-term signals a team&amp;rsquo;s lack of maturity and adaptability. While they can help new teams start conversations and build shared understanding, they do not provide real predictability or confidence in delivery. Development managers should focus on transparency, concrete data, and metrics like cycle time to build true confidence and improve predictability for stakeholders.</description>
			</item>
			<item>
				<title>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>Who broke the build?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/who-broke-the-build/</link>
				<pubDate>Mon, 29 Mar 2010 18:47:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/who-broke-the-build/</guid>
				<description>Explains the importance of passing builds, common causes of build failures, how to identify issues and responsible users, and best practices for build ownership.</description>
			</item>
			<item>
				<title>let-us be blunt, if a Scrum Team isn’t delivering, is it effective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</link>
				<pubDate>Fri, 07 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</guid>
				<description>A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness.</description>
			</item>
			<item>
				<title>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>Sprint Review #1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: Embrace Continuous Forecasting and Transform Your Training Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/</link>
				<pubDate>Thu, 21 May 2020 05:26:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/</guid>
				<description>Continuous forecasting in Agile, supported by metrics and tools like Monte Carlo simulations, enables teams to plan flexibly and adapt quickly rather than committing to a full sprint plan upfront. Virtual training with interactive tools and follow-up sessions has improved learning and engagement. Development managers should consider adopting continuous forecasting and leveraging available training resources to enhance team performance and responsiveness.</description>
			</item>
			<item>
				<title>Great Scrum Masters and Product Owners don’t micromanage</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</link>
				<pubDate>Sun, 23 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/</guid>
				<description>Effective Scrum Masters and Product Owners avoid micromanaging by providing clear direction, supporting team autonomy, and ensuring accountability. Teams perform best when they understand the vision and operate within a structured framework that balances freedom with alignment. Leaders should focus on removing obstacles and maintaining this balance to enable true agility; consider how your organization supports both autonomy and structure.</description>
			</item>
			<item>
				<title>Hiring a Scrum Master is hard</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</link>
				<pubDate>Sun, 16 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/</guid>
				<description>Hiring a Scrum Master is challenging because many organizations misunderstand the role and focus on the wrong qualifications. A strong Scrum Master needs deep knowledge of Scrum, the ability to drive team effectiveness, and enough technical understanding to support your teams and foster change. Look for candidates who demonstrate commitment, challenge assumptions, and coach teams to deliver real value, not just those with certifications or project management backgrounds.</description>
			</item>
			<item>
				<title>Transform Your Leadership: The Power of Evidence-Based Management in Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/</link>
				<pubDate>Wed, 29 Nov 2023 11:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/</guid>
				<description>Evidence-based management helps Agile leaders make better decisions by using data on team performance, customer satisfaction, and product quality, leading to continuous improvement and stronger collaboration. Real-world examples show that adopting EBM can improve delivery times, morale, and outcomes. Development managers should invest in EBM training, encourage data-driven practices, and support experimentation to drive team success.</description>
			</item>
			<item>
				<title>Redefining the Scrum Master: From Misconceptions to Empowering Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</link>
				<pubDate>Fri, 12 May 2023 14:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/</guid>
				<description>The Scrum Master role is often misunderstood as tool administration or problem-solving, but its true value lies in empowering teams to self-organize and operate independently. Key insights include fostering team autonomy, guiding rather than controlling, and committing to continuous learning. Development managers should support Scrum Masters in becoming facilitators who enable teams to thrive without constant oversight.</description>
			</item>
			<item>
				<title>ALM Consulting in Scotland, UK, Scandinavia &amp;amp; Europe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/alm-consulting-in-scotland-uk-scandinavia-amp-europe/</link>
				<pubDate>Mon, 11 Nov 2013 15:08:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/alm-consulting-in-scotland-uk-scandinavia-amp-europe/</guid>
				<description>Provides ALM consulting, training, and assessments across Scotland, UK, and Europe, specialising in lean-agile, TFS, Visual Studio, Scrum, and process improvement.</description>
			</item>
			<item>
				<title>Presenting Visual Studio ALM and upgrading TFS 2010 to TFS 2012 in production – Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/presenting-visual-studio-alm-and-upgrading-tfs-2010-to-tfs-2012-in-production-%E2%80%93-done/</link>
				<pubDate>Sun, 10 Jun 2012 19:03:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/presenting-visual-studio-alm-and-upgrading-tfs-2010-to-tfs-2012-in-production-%E2%80%93-done/</guid>
				<description>Covers presenting Visual Studio ALM features and the process of upgrading from TFS 2010 to TFS 2012, including benefits, challenges, and key considerations for organisations.</description>
			</item>
			<item>
				<title>A change for the better #3 - SSW to Northwest Cadence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-change-for-the-better-3/</link>
				<pubDate>Tue, 07 Sep 2010 09:58:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-change-for-the-better-3/</guid>
				<description>Reflects on lessons learned at SSW in software process, technology, and communication, and details a career move to an ALM consultant role at Northwest Cadence in Seattle.</description>
			</item>
			<item>
				<title>“Teams are self-managing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</link>
				<pubDate>Fri, 21 Mar 2025 16:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/teams-are-self-managing/</guid>
				<description>Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance.</description>
			</item>
			<item>
				<title>Ditch the Agile Bandit Mentality: How to Prioritise Value Over Estimates for Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/</link>
				<pubDate>Fri, 05 Jan 2024 11:00:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/</guid>
				<description>Focusing on estimates instead of value delivery can harm team morale and undermine Agile principles. Shifting attention to outcomes, fostering psychological safety, and using metrics that reflect real customer impact lead to better products and a more engaged team. Development managers should prioritise value and team well-being over tracking estimates to achieve lasting success.</description>
			</item>
			<item>
				<title>Mastering Complexity in Scrum: Transform Your Team with Agile Product Strategy Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/</link>
				<pubDate>Wed, 15 Nov 2023 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/</guid>
				<description>Understanding and managing complexity is essential for Scrum teams to plan and execute effectively, especially as unpredictability increases. Emphasizing transparency, inspection, and adaptation helps teams navigate complex work, improve processes, and foster continuous improvement. Consider investing in training or discussions that deepen your team&amp;rsquo;s grasp of these principles to boost effectiveness.</description>
			</item>
			<item>
				<title>You are doing it wrong if you are not using test first</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</link>
				<pubDate>Mon, 07 Dec 2020 12:00:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</guid>
				<description>Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices.</description>
			</item>
			<item>
				<title>Taming the Chaos Factor: How to Align Your Agile Teams for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/</link>
				<pubDate>Thu, 09 Nov 2023 10:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/</guid>
				<description>Chaos in Agile teams often results from unclear goals, poor communication, and lack of alignment, leading to disjointed work, low morale, and ineffective decisions. To address this, set clear objectives, ensure open communication, and align teams with the organisation’s vision. Focus on fostering collaboration and regularly reinforcing shared goals to create a more productive and unified environment.</description>
			</item>
			<item>
				<title>Combatting the Agile Apocalypse: How to Overcome the Famine of Feedback and Engagement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</link>
				<pubDate>Wed, 08 Nov 2023 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</guid>
				<description>A lack of feedback and engagement from stakeholders, especially the product owner, leads to disengaged teams, poor product alignment, and increased risk of failure. Regular feedback sessions, open communication, and early stakeholder involvement are essential to keep teams motivated and ensure products meet business needs. Development managers should prioritise active stakeholder participation to maintain team morale and deliver better outcomes.</description>
			</item>
			<item>
				<title>7 Deadly Sins of Agile: Greed</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</link>
				<pubDate>Wed, 11 Oct 2023 12:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</guid>
				<description>Focusing on resource utilisation over value in Agile leads to busywork, burnout, and reduced innovation, undermining true productivity. Teams should prioritise delivering customer value, balance workloads, and foster open communication and trust to enable creativity and continuous improvement. Development managers should shift from maximising activity to nurturing a value-driven, healthy Agile culture that supports learning and adaptation.</description>
			</item>
			<item>
				<title>Why is Satya Nadella a better example of agile leadership than Steve Jobs?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</link>
				<pubDate>Wed, 01 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</guid>
				<description>Satya Nadella is a stronger example of agile leadership than Steve Jobs because he built a culture of innovation and empowered teams across Microsoft, rather than centralizing decision-making and innovation in one person. Nadella decentralized authority, focused on meaningful metrics that drive customer value, and fostered continuous improvement and collaboration throughout the organization. Development managers should consider enabling team autonomy and aligning incentives with customer outcomes to drive sustainable innovation.</description>
			</item>
			<item>
				<title>There is no &#34;do agile&#34; there is only &#34;be agile&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-do-agile-there-is-only-be-agile/</link>
				<pubDate>Sun, 01 Sep 2013 22:31:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-do-agile-there-is-only-be-agile/</guid>
				<description>Explores the difference between adopting agile practices superficially and truly embracing agile values, highlighting the need for deep organisational change and continuous learning.</description>
			</item>
			<item>
				<title>Testing in the modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/</link>
				<pubDate>Tue, 25 Sep 2012 02:00:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/</guid>
				<description>Explores challenges and solutions for manual testing in agile software development, focusing on tracking, automation, actionable bugs, and integrated test management tools.</description>
			</item>
			<item>
				<title>Balance of Leadership and Control in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</link>
				<pubDate>Mon, 17 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/</guid>
				<description>Scrum Masters and Product Owners are expected to deliver results, so they need both influence and enough authority to remove obstacles, enforce alignment, and ensure accountability. Too much control stifles team autonomy, but too little makes teams ineffective; the right balance depends on the organisation and situation. Development managers should empower these roles with the authority needed to drive change while maintaining team ownership and continuous improvement.</description>
			</item>
			<item>
				<title>Unlocking Continuous Delivery: How Feature Flags Transform Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</link>
				<pubDate>Thu, 16 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</guid>
				<description>Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs.</description>
			</item>
			<item>
				<title>Unlocking the Future of Software Development: Why Automation is Your Key to Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</link>
				<pubDate>Wed, 15 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</guid>
				<description>Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability.</description>
			</item>
			<item>
				<title>What is the Sprint Review workshop and how will it help organisations?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</link>
				<pubDate>Fri, 30 Jun 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</guid>
				<description>The Sprint Review workshop helps teams align product development with stakeholder needs, adapt to market changes, and drive continuous improvement. It offers practical guidance on running effective reviews, boosting stakeholder engagement, and turning feedback into actionable improvements. Development managers should consider this workshop to enhance team performance and ensure products deliver real value.</description>
			</item>
			<item>
				<title>How Hard is it to Transition from Being a Developer to a Scrum developer?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-hard-is-it-to-transition-from-being-a-developer-to-a-scrum-developer/</link>
				<pubDate>Thu, 22 Jun 2023 11:00:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-hard-is-it-to-transition-from-being-a-developer-to-a-scrum-developer/</guid>
				<description>Transitioning from a traditional developer role to a Scrum developer is challenging but rewarding, requiring a shift to continuous delivery, testing, and improvement, along with strong engineering practices. Success depends on embracing ongoing learning and aligning coding with Agile principles. Development managers should support their teams with training and opportunities to practice Scrum to ensure high-quality, sustainable product delivery.</description>
			</item>
			<item>
				<title>Should the Scrum Master always remove impediments?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/should-the-scrum-master-always-remove-impediments/</link>
				<pubDate>Mon, 23 Sep 2019 18:49:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/should-the-scrum-master-always-remove-impediments/</guid>
				<description>The Scrum Master is responsible for removing impediments, but should only step in when the team cannot resolve the issue themselves. Their focus should be on enabling the team to handle similar problems independently in the future, building self-sufficiency. Development managers should encourage Scrum Masters to coach teams rather than always solving problems for them.</description>
			</item>
			<item>
				<title>Professional Scrum Training for the Ghana Police Service</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</link>
				<pubDate>Mon, 30 Oct 2017 19:26:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/</guid>
				<description>The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>Scrum doesn&#39;t solve problems, it reveals them. How, and why is that valuable?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</link>
				<pubDate>Wed, 27 Sep 2023 07:00:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn&#39;t-solve-problems-it-reveals-them-how-and-why-is-that-valuable/</guid>
				<description>Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation.</description>
			</item>
			<item>
				<title>Why did so many of the early agile transformations fail?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-did-so-many-of-the-early-agile-transformations-fail/</link>
				<pubDate>Mon, 06 Feb 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-did-so-many-of-the-early-agile-transformations-fail/</guid>
				<description>Many agile transformations fail because decisions are made top-down without involving the teams who do the actual work, leading to poor fit and lack of buy-in. Teams have the best understanding of their environment and should be included in selecting and shaping agile solutions to ensure success. To improve outcomes, involve your teams in decision-making from the start rather than imposing off-the-shelf frameworks.</description>
			</item>
			<item>
				<title>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>NDC London: Second Look, Team Foundation Server &amp;amp; VSO</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/</link>
				<pubDate>Wed, 15 Oct 2014 14:49:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/</guid>
				<description>The speaker will present a demo-heavy session at NDC London to showcase major improvements in Team Foundation Server and Visual Studio Online since 2012, targeting developers who previously found TFS lacking. Key insights include end-to-end demonstrations of new features for agile project management, coding, testing, release, and monitoring, with scenarios covering both new features and bug fixes. Development managers should consider revisiting TFS/VSO for .NET projects and can provide feedback on which features or scenarios they want prioritized in the session.</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>Quotes: You can&#39;t connect the dots looking forward; you can only connect them looking backwards. Steve Jobs</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-you-can&#39;t-connect-the-dots-looking-forward-you-can-only-connect-them-looking-backwards-steve-jobs/</link>
				<pubDate>Fri, 13 Oct 2023 11:00:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-you-can&#39;t-connect-the-dots-looking-forward-you-can-only-connect-them-looking-backwards-steve-jobs/</guid>
				<description>Steve Jobs’ idea that you can only connect the dots looking backward highlights the value of learning from past experiences in Agile environments. Development managers should regularly reflect on previous outcomes, use data to inform decisions, and remain flexible to adapt strategies as new information emerges. Encourage your teams to balance lessons from the past with ongoing validation and iterative improvement to stay effective in a changing landscape.</description>
			</item>
			<item>
				<title>Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management</title>
				<link>https://engineering-leadership-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>What is the best application of Scrum in the world?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-best-application-of-scrum-in-the-world/</link>
				<pubDate>Fri, 26 May 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-best-application-of-scrum-in-the-world/</guid>
				<description>Microsoft&amp;rsquo;s Azure DevOps team successfully transitioned from waterfall to Scrum, dramatically reducing build times from over 20 hours to just 3.5 minutes and delivering a product that better meets customer needs. This highlights how effective Scrum can be when applied well, especially in overcoming technical debt and improving efficiency. Development managers should consider how adopting Scrum could drive similar improvements in their own teams.</description>
			</item>
			<item>
				<title>DOD has made it illegal to do waterfall</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</link>
				<pubDate>Tue, 01 May 2018 01:02:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</guid>
				<description>The US Department of Defense has updated its procurement rules to require agile, iterative development instead of traditional waterfall methods, following high-profile failures like the FBI’s Sentinel project. Agile approaches have proven to deliver higher success rates, lower costs, and reduced risk, and these changes are now influencing government and vendor practices across the US and UK. Development managers working with government clients should adopt agile methods to align with new regulations and improve project outcomes.</description>
			</item>
			<item>
				<title>My journey into Professional Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</link>
				<pubDate>Wed, 04 Feb 2015 10:53:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/</guid>
				<description>Professional Scrum has been key to my success in software development and consulting, showing that most team challenges are cultural rather than technical. Building professional, adaptable individuals and teams leads to greater business agility and consistent delivery of valuable software. Avoid one-size-fits-all approaches to scaling Scrum; instead, tailor frameworks and practices to your organisation’s unique culture and needs.</description>
			</item>
			<item>
				<title>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: The Critical Role of User Feedback in Requirement Changes</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/</link>
				<pubDate>Fri, 19 Jul 2024 06:45:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/</guid>
				<description>Empowering teams to change requirements based on real user feedback is essential for true agility, yet many organizations are held back by rigid contracts, complex change processes, and lack of team autonomy. Teams must be able to quickly adapt, discard outdated features, and act on feedback to keep products relevant and valuable. Development managers should streamline change processes, build flexibility into contracts, and foster a culture of trust so teams can respond rapidly to evolving business needs.</description>
			</item>
			<item>
				<title>Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</link>
				<pubDate>Mon, 06 May 2024 14:12:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/</guid>
				<description>Many common beliefs about Scrum, such as it being just meetings, requiring story points, encouraging micromanagement, lacking planning, or having no governance, are misconceptions that hinder its effectiveness. Scrum events are purposeful, story points are optional, teams should self-organise, planning is integral, and governance is flexible to business needs. Development managers should challenge these myths to help teams fully benefit from Agile and deliver greater value.</description>
			</item>
			<item>
				<title>Redefining Agile’s Core: Beyond Rituals and Procedures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</link>
				<pubDate>Mon, 22 Jan 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</guid>
				<description>Agile is not about following rituals or procedures but about delivering value and adapting to change to maximize business outcomes. Teams that focus only on rituals risk losing sight of continuous improvement and ownership, while over-automation can miss the need for human judgment in complex situations. Development managers should prioritize outcomes, encourage critical thinking about processes, and adapt Agile practices to their unique context rather than just checking boxes.</description>
			</item>
			<item>
				<title>The Pitfalls of Agile Burndowns: Stop Being Agile Bandits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</link>
				<pubDate>Tue, 09 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, false confidence, and wasted effort, as most plans quickly become outdated and only a fraction of features are actually used. Instead, focus on minimal, just-in-time planning and continuous flow to adapt quickly, reduce overhead, and deliver real value. Encourage your teams to plan only what is needed for the next day, adjust daily, and prioritize delivering value over maintaining detailed charts.</description>
			</item>
			<item>
				<title>How do you decide whether to pivot or stay the course? (Nokia story)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-decide-whether-to-pivot-or-stay-the-course-nokia-story/</link>
				<pubDate>Wed, 13 Sep 2023 13:59:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-decide-whether-to-pivot-or-stay-the-course-nokia-story/</guid>
				<description>Product owners must confidently make pivotal decisions, often with incomplete information, by balancing data, instinct, and alignment with long-term goals. Success depends on staying connected with teams and stakeholders, monitoring market trends, and fostering a culture of continuous learning and adaptability. To lead effectively, embrace change, value feedback, and be prepared to pivot or persevere based on evidence rather than sunk costs.</description>
			</item>
			<item>
				<title>Unlocking the True Power of Agile: Embracing Change and Collaboration for Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-agile-embracing-change-and-collaboration-for-team-success/</link>
				<pubDate>Thu, 13 Jul 2023 07:38:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-agile-embracing-change-and-collaboration-for-team-success/</guid>
				<description>Agile works best when teams focus on collaboration, embrace change, and prioritize delivering real value to customers rather than rigidly following processes. Regular reflection, empowering team members, and experimenting with new approaches help teams adapt and improve. Development managers should foster a growth mindset and lead by example to create an environment where teams can thrive and continuously deliver better results.</description>
			</item>
			<item>
				<title>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</link>
				<pubDate>Fri, 26 May 2023 14:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</guid>
				<description>Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes.</description>
			</item>
			<item>
				<title>Is a scrum master an agile micromanager?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</link>
				<pubDate>Tue, 25 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/</guid>
				<description>A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail.</description>
			</item>
			<item>
				<title>Why Teams Claim Self-Management to Avoid Alignment Discussions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</link>
				<pubDate>Tue, 18 Mar 2025 16:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/</guid>
				<description>Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability.</description>
			</item>
			<item>
				<title>The Importance of Evidence-Based Management in Agile Environments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</link>
				<pubDate>Mon, 22 Jan 2024 11:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</guid>
				<description>Evidence-based management helps Agile teams make smarter decisions by tracking key metrics like value delivered, time to market, and ability to innovate, ensuring changes actually lead to improvement. Without data, teams risk wasting time and resources on ineffective changes, but with regular measurement and analysis, they can adapt quickly and foster continuous improvement. Start by identifying and tracking a few important metrics, involve your team, and use the insights to guide your next steps.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Key Strategies for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/</link>
				<pubDate>Thu, 30 Nov 2023 11:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/</guid>
				<description>Effective product backlog management is crucial for Agile success; prioritising tasks, limiting work in progress, and holding regular refinement sessions help teams stay focused and deliver more value. Engaging stakeholders and using visual tools can further improve clarity and alignment. Development managers should regularly review their backlog practices to ensure they are working on the most valuable items and maintaining a manageable, focused backlog.</description>
			</item>
			<item>
				<title>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>Why the Scrum Master’s True Power Lies in Influence, Not Authority</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/</link>
				<pubDate>Fri, 15 Sep 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/</guid>
				<description>The Scrum Master’s effectiveness comes from their ability to influence and build trust within the team, not from formal authority. By consistently providing value and fostering a collaborative environment, they help teams thrive and drive continuous improvement. Development managers should focus on supporting Scrum Masters in developing their leadership and relationship-building skills rather than granting them traditional authority.</description>
			</item>
			<item>
				<title>Why Agile Success Lies in Principles, Not Tools: A Shift in Focus</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-lies-in-principles-not-tools-a-shift-in-focus/</link>
				<pubDate>Wed, 03 May 2023 07:00:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-lies-in-principles-not-tools-a-shift-in-focus/</guid>
				<description>Focusing on Agile principles rather than tools leads to better decision-making, consistency, and long-term team success. Overreliance on tools can create rigid, ineffective processes, while principles support adaptability and collaboration. Development managers should reflect on whether their teams are prioritising principles and consider shifting their focus to foster continuous improvement.</description>
			</item>
			<item>
				<title>Would you hire a Junior CISO? A Junior Financial Director</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/</link>
				<pubDate>Mon, 17 Feb 2025 10:06:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/</guid>
				<description>Hiring a junior Scrum Master is risky because the role requires proven expertise in technical, business, and organisational areas from the start, similar to senior roles like CISO or Financial Director. Scrum Masters must lead teams and drive change, not learn on the job. Only hire experienced Scrum Masters to ensure your team&amp;rsquo;s success and true agility.</description>
			</item>
			<item>
				<title>Daily Scrum Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/</guid>
				<description>Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals.</description>
			</item>
			<item>
				<title>Understanding the True Role of a Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</link>
				<pubDate>Tue, 28 Nov 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/</guid>
				<description>The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</link>
				<pubDate>Mon, 23 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</guid>
				<description>Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions.</description>
			</item>
			<item>
				<title>The High of Release</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/</link>
				<pubDate>Sat, 05 Dec 2015 14:49:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/</guid>
				<description>Microsoft’s new web-based Release Management tools let teams build flexible, integrated release pipelines in VSTS or TFS without being locked into specific deployment tools. The focus is on orchestration and integration, allowing you to use your preferred technologies like Chef, Puppet, Docker, or PowerShell. These tools are now in public preview, so consider evaluating them to streamline your release process and support cloud or on-premises deployments.</description>
			</item>
			<item>
				<title>Create a Release Management pipeline for Professional Developers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</link>
				<pubDate>Thu, 04 Dec 2014 12:15:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</guid>
				<description>This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles.</description>
			</item>
			<item>
				<title>Avoid the Bug as Task anti-pattern in Azure DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</link>
				<pubDate>Wed, 06 Aug 2014 14:46:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/</guid>
				<description>Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers guidance for agile teams to avoid it.</description>
			</item>
			<item>
				<title>Does your company culture resemble Survivor?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/</link>
				<pubDate>Wed, 10 Jul 2013 19:37:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/</guid>
				<description>Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering teamwork in software development.</description>
			</item>
			<item>
				<title>Guidance: A Branching strategy for Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/</link>
				<pubDate>Wed, 14 Apr 2010 20:11:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/</guid>
				<description>Explains an effective branching strategy for Scrum teams, covering best practices, common pitfalls, and step-by-step guidance for managing code, releases, and bug fixes.</description>
			</item>
			<item>
				<title>What should you do if your Sprint Review delivers harsh, scathing feedback?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</link>
				<pubDate>Fri, 08 Sep 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</guid>
				<description>Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Unlocking the Scrum Master&#39;s Potential: Embracing Broader Responsibilities for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-scrum-master&#39;s-potential-embracing-broader-responsibilities-for-agile-success/</guid>
				<description>Scrum Masters have a broader responsibility beyond supporting their teams; they also need to engage with the Product Owner and the wider organisation to remove obstacles and drive agility. Encouraging Scrum Masters to question outdated processes and model collaborative behaviours can lead to meaningful organisational change. Development managers should empower Scrum Masters to challenge the status quo and support their growth in these expanded roles.</description>
			</item>
			<item>
				<title>Scrum Master Effectiveness Begins with Consistent Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</link>
				<pubDate>Thu, 06 Mar 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/</guid>
				<description>Scrum Master effectiveness depends on ensuring teams deliver something every sprint, as delivery enables feedback and improvement. Without delivery, there is no basis for learning or adding value. Development managers should prioritize consistent delivery as the foundation for team effectiveness and continuous improvement.</description>
			</item>
			<item>
				<title>Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</link>
				<pubDate>Wed, 17 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</guid>
				<description>Empowering teams to update or delete requirements based on user feedback is essential for true agility and delivering maximum value. Regularly engaging with the product team, keeping the backlog dynamic, and being willing to pivot or remove features ensures your product stays relevant and user-focused. Review your processes to make sure your teams have the authority and support to make these changes.</description>
			</item>
			<item>
				<title>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>What my father taught me about Evidence-based Management (34 years before it was invented!)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</guid>
				<description>Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in both business and software contexts.</description>
			</item>
			<item>
				<title>Mastering Agile in a Distributed World: Tools and Strategies for Effective Team Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-in-a-distributed-world-tools-and-strategies-for-effective-team-management/</link>
				<pubDate>Fri, 10 Apr 2020 18:35:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-in-a-distributed-world-tools-and-strategies-for-effective-team-management/</guid>
				<description>Managing distributed Agile teams is effective when you choose tools that fit your team’s needs, such as GitHub for open-source, Microsoft Planner for simple task management, or Azure DevOps for comprehensive Agile support. Success depends on adapting practices, experimenting with tools, and maintaining regular feedback loops. Encourage continuous learning and collaboration to keep improving team performance.</description>
			</item>
			<item>
				<title>Scaling Agility: Navigating the Dragons of Change in the Future of Work</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/</link>
				<pubDate>Wed, 25 Mar 2020 16:17:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/</guid>
				<description>Scaling agility is about more than just expanding frameworks like Scrum or Nexus; it requires focusing on core practices, using meaningful metrics, and adapting to new ways of working such as virtual training. Key insights include the importance of revisiting Scrum fundamentals, tailoring metrics to your context, and leveraging technology for effective remote collaboration. Development managers should prioritize continuous learning, experiment with virtual tools, and stay open to sharing experiences to navigate the challenges of scaling in today’s changing work environment.</description>
			</item>
			<item>
				<title>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>TFS for cross team and cross business line work item tracking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/</link>
				<pubDate>Tue, 04 Mar 2014 16:34:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/</guid>
				<description>Explains how to use a single Team Project and Team Field in TFS to streamline cross-team work item tracking, reporting, and collaboration across business lines.</description>
			</item>
			<item>
				<title>Design Sprints in Scrum: Common Questions and Practical Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</link>
				<pubDate>Wed, 04 Jun 2025 15:31:05 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/</guid>
				<description>There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.</description>
			</item>
			<item>
				<title>Scrum Myth Debunked: Unfinished Work is Allowed in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</link>
				<pubDate>Sat, 24 May 2025 15:30:17 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/</guid>
				<description>Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries.</description>
			</item>
			<item>
				<title>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</link>
				<pubDate>Wed, 26 Mar 2025 16:30:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</guid>
				<description>Product Owners should be empowered as strategic leaders who drive product vision and business value, not just manage backlogs. Scrum Masters play a key role in coaching Product Owners to use customer insights and data for better decisions. Development managers should ensure Product Owners have the authority and support to lead effectively, rather than treating them as task managers.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: The Essential Knowledge Every Coach Needs</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</link>
				<pubDate>Wed, 15 Nov 2023 11:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/</guid>
				<description>Effective Agile coaching relies on a deep understanding of both frameworks like Scrum, Kanban, and Lean, and the principles behind them, along with strong technical knowledge. Continuous learning, community engagement, and practical experimentation are key to improving coaching skills and supporting teams. Development managers should prioritize ongoing education and active involvement to help their teams succeed with Agile.</description>
			</item>
			<item>
				<title>What 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>What will you learn on the professional scrum master course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</link>
				<pubDate>Thu, 19 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/</guid>
				<description>The Professional Scrum Master course teaches the theory and practical skills needed to be an effective scrum master, focusing on serving developers, product owners, and the organization to maximize team value. Participants learn through real-world examples, discussions, and case studies about empiricism, delivering working increments each sprint, and overcoming common challenges. Development managers should consider this course to strengthen their teams&amp;rsquo; ability to deliver value and navigate complexity.</description>
			</item>
			<item>
				<title>Navigating DevOps: Crafting Unique Solutions for Unique Organizations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-devops-crafting-unique-solutions-for-unique-organizations/</link>
				<pubDate>Fri, 23 Aug 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-devops-crafting-unique-solutions-for-unique-organizations/</guid>
				<description>DevOps success depends on tailoring solutions to your organization’s unique context rather than following a one-size-fits-all approach. Bringing in external experts can provide valuable new perspectives and help spark innovation, while long-term commitment to continuous improvement and adaptation is essential. Focus on developing a flexible DevOps philosophy, regularly refine your practices, and seek outside help when needed to sustain progress.</description>
			</item>
			<item>
				<title>Maximizing Transparency and Improvement in Software Engineering with Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</link>
				<pubDate>Mon, 29 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</guid>
				<description>Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement.</description>
			</item>
			<item>
				<title>Does Your Team Truly Understand Your Product Vision and Goals?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</link>
				<pubDate>Fri, 12 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</guid>
				<description>Many teams lack a true understanding of the product vision and strategic goals, which leads to misaligned decisions and reduced value for customers. Regularly communicating and reinforcing these goals helps team members see how their work contributes to the bigger picture, improving collaboration and decision-making. Development managers should frequently check team alignment and use practical strategies like workshops, visual roadmaps, and leadership engagement to ensure everyone is working toward shared objectives.</description>
			</item>
			<item>
				<title>If you could teach just one thing about Scrum, what would it be?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</link>
				<pubDate>Mon, 27 Feb 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/</guid>
				<description>The most important thing to teach about Scrum is the principle of empiricism, which means making work transparent, inspecting progress frequently, and adapting based on what is learned. This approach helps teams navigate complex, uncertain environments where traditional project management falls short. Focus on building your team&amp;rsquo;s ability to learn and adapt quickly, as Scrum reveals problems but does not solve them for you.</description>
			</item>
			<item>
				<title>Is ALM a useful term?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/is-alm-a-useful-term/</link>
				<pubDate>Sat, 25 Feb 2012 03:41:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/is-alm-a-useful-term/</guid>
				<description>Explores whether Application Lifecycle Management (ALM) is a useful term, its role in agile software delivery, and differences in adoption across organisations and regions.</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>From Developer to Agile Advocate: How My Journey Unveiled the Power of Scrum and DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-developer-to-agile-advocate-how-my-journey-unveiled-the-power-of-scrum-and-devops/</link>
				<pubDate>Thu, 02 Mar 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-developer-to-agile-advocate-how-my-journey-unveiled-the-power-of-scrum-and-devops/</guid>
				<description>The author describes moving from traditional project management to Agile, highlighting that real change comes from rethinking processes and focusing on people rather than just adopting new tools. Key insights include the importance of simplifying workflows, avoiding unnecessary bureaucracy, and empowering teams through Agile and Scrum principles. Development managers should focus on enabling team autonomy and streamlining processes to unlock better results.</description>
			</item>
			<item>
				<title>How would you help organizations pitch the opportunity of agile internally?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</link>
				<pubDate>Wed, 08 Feb 2023 07:15:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</guid>
				<description>To successfully pitch agile internally, tailor your message to leadership by focusing on business outcomes they care about, such as reduced costs, faster time to market, and improved customer satisfaction, using clear metrics and financial examples. When engaging teams, use a consultative approach that involves them in problem-solving and framework selection to build buy-in and reduce resistance. The key action is to align agile benefits with stakeholder priorities and measure progress with relevant data to make a compelling, evidence-based case.</description>
			</item>
			<item>
				<title>Unlocking Your Potential: Transformative Training for Aspiring Scrum Masters</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-your-potential-transformative-training-for-aspiring-scrum-masters/</link>
				<pubDate>Wed, 27 Jul 2022 18:45:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-your-potential-transformative-training-for-aspiring-scrum-masters/</guid>
				<description>Effective Scrum Master training combines interactive workshops, supplementary learning, and ongoing community support to build deep understanding and practical skills. Participants benefit from hands-on activities, access to assessments, and regular engagement with peers and trainers, which helps them apply Scrum principles in real-world settings. Investing in such training empowers Scrum Masters to foster collaboration and continuous improvement, so consider supporting your team’s development through similar opportunities.</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>Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</link>
				<pubDate>Mon, 13 Mar 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</guid>
				<description>A great Scrum Master is defined by their fit with the team and their ability to build trust, which is best achieved when teams help select their own Scrum Master. Beyond supporting the team, the most effective Scrum Masters build relationships across the organisation to identify and address broader obstacles, empowering others to drive change. Development managers should involve teams in Scrum Master selection and support their efforts to connect with stakeholders for greater organisational impact.</description>
			</item>
			<item>
				<title>Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</link>
				<pubDate>Tue, 18 Oct 2022 16:13:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/</guid>
				<description>Scrum is a flexible framework that helps teams deliver value through transparency, clear roles, and structured events, all grounded in trust and five core values. Key elements include defined accountabilities, essential artifacts for decision-making, and regular events to inspect and adapt work. To get the most from Scrum, focus on building trust, maintaining transparency, and continuously improving team processes.</description>
			</item>
			<item>
				<title>Nexus Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</link>
				<pubDate>Fri, 27 Oct 2023 14:30:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/</guid>
				<description>Ineffective Product Owners, whether due to lack of skills or organisational constraints, can hinder team performance and product success. Development managers should support Product Owners through relationship-building, organisational education, and open dialogue, while ensuring the team continues to deliver quality work. Take action by fostering collaboration and advocating for clear role expectations to help Product Owners and teams succeed.</description>
			</item>
			<item>
				<title>Is Your Scrum Master Struggling? Discover When to Choose an Agile Process Simulation Workshop</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</link>
				<pubDate>Wed, 05 Apr 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/</guid>
				<description>If your Scrum Master is struggling with the team, first assess whether the issue is with their approach or deeper team dynamics. An Agile Process Simulation workshop can help by engaging the team in open dialogue and tailored learning, empowering them to decide if Scrum fits their needs. Prioritize collaboration and self-discovery over imposing solutions to achieve better team outcomes.</description>
			</item>
			<item>
				<title>The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</link>
				<pubDate>Fri, 31 Mar 2023 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/</guid>
				<description>The difference between a new and professional Scrum Master is less about labels and more about embracing accountability and a mindset focused on team effectiveness and value creation. Regardless of experience, a Scrum Master should guide the team, remove obstacles, and drive continuous improvement rather than micromanage. Development managers should support Scrum Masters in adopting a professional approach that prioritises team impact and organisational value.</description>
			</item>
			<item>
				<title>Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</link>
				<pubDate>Mon, 09 Jan 2023 12:36:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/</guid>
				<description>Teaching Scrum through hands-on experience, including using Minecraft, helps participants move from initial chaos to a clear understanding of Scrum’s value. Students first experience confusion similar to real project starts, then learn to apply Scrum principles, leading to practical insights and improved teamwork. Development managers should consider experiential learning to help teams internalise agile practices and appreciate their real-world benefits.</description>
			</item>
			<item>
				<title>Maximising Value from Applying Professional Scrum Training</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</link>
				<pubDate>Mon, 09 Jun 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/</guid>
				<description>The main benefit of Professional Scrum training is not just learning Scrum, but creating a clear list of organisational obstacles that slow delivery. When teams are empowered to identify these issues and leadership commits to addressing them, real transformation can begin. Development managers should ensure their teams have a change backlog and actively work with leadership to remove barriers.</description>
			</item>
			<item>
				<title>At the end of the day, Kanban is about improving flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/</link>
				<pubDate>Mon, 03 Mar 2025 15:46:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/</guid>
				<description>Kanban focuses on improving workflow by removing constraints and bottlenecks, not by pushing people to work harder or longer. Key to better delivery is reducing work in progress and identifying blockers to increase efficiency. Managers should identify and address the biggest constraint in their current workflow to see meaningful improvements.</description>
			</item>
			<item>
				<title>Mastering the Art of Scaling Agile: Strategies to Maintain Agility Across Multiple Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/</link>
				<pubDate>Wed, 26 Feb 2025 06:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/</guid>
				<description>Scaling agile across multiple teams introduces complexity and risks slowing down delivery, so it is crucial to choose a scaling approach that fits your organisation’s unique context. Key to success are mapping dependencies, proactively addressing communication pitfalls, and maintaining speed in delivering value as you grow. Consider a tailored, hands-on strategy to preserve agility and empower your teams as you scale.</description>
			</item>
			<item>
				<title>Git Flow should have died years ago</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/</link>
				<pubDate>Sun, 09 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/</guid>
				<description>Git Flow is outdated and causes unnecessary delays and complications for modern software teams. Long-lived branches and complex merges slow down delivery and increase risk. Switch to simpler workflows like GitHub Flow or Release Flow to speed up development and focus on delivering value.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps Migration Tools: Your Ultimate Guide to Seamless Migrations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-tools-your-ultimate-guide-to-seamless-migrations/</link>
				<pubDate>Thu, 17 Oct 2019 19:16:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-tools-your-ultimate-guide-to-seamless-migrations/</guid>
				<description>Azure DevOps Migration Tools enable experienced teams to move work items and related data between environments efficiently, supporting features like syncing changes during migration and extensive customization. For best results, set up a dedicated environment, migrate open work items first, use date-based queries for updates, and monitor API performance. Engage with the active open-source community for support and improvements to ensure a smooth migration.</description>
			</item>
			<item>
				<title>Detecting agile theatre with real delivery signals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/</link>
				<pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/</guid>
				<description>Agile is measured by delivery, feedback, and decision-making authority in the hands of teams, not by visible ceremonies or tooling.</description>
			</item>
			<item>
				<title>Resilience is not a department</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/resilience-is-not-a-department/</link>
				<pubDate>Sat, 17 May 2025 15:30:21 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/resilience-is-not-a-department/</guid>
				<description>Resilience must be built into your product from the start, not treated as a separate concern or afterthought. Focusing only on performance, cost, or speed can lead to fragile systems that fail in real-world conditions. Make sure your disaster recovery plans are tested under real scenarios, not just documented, to avoid turning your product into a liability.</description>
			</item>
			<item>
				<title>Scrum Masters: Why Influence Alone May Not Be Enough</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</link>
				<pubDate>Thu, 20 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/</guid>
				<description>Relying only on influence limits a Scrum Master&amp;rsquo;s ability to drive real change, especially when teams or leaders resist Agile practices. Sustainable agility needs Scrum Masters who can enforce the framework, remove obstacles, and hold teams accountable, not just suggest improvements. Development managers should ensure Scrum Masters have enough authority to lead effectively, not just influence.</description>
			</item>
			<item>
				<title>How Do You Know How Long It Takes to Deliver Value?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</link>
				<pubDate>Fri, 26 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</guid>
				<description>Measuring and improving Time to Market is essential for delivering value quickly and staying competitive. Key metrics like lead time, cycle time, time to pivot, time to learn, and time to fix help teams identify bottlenecks and make better decisions. Focus on streamlining processes, automating tasks, gathering fast feedback, and building cross-functional teams to reduce delivery times and ensure you are delivering what customers need most.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Essential Skills for Product Owners</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</link>
				<pubDate>Mon, 18 Dec 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</guid>
				<description>Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently.</description>
			</item>
			<item>
				<title>Taming the Chaos: How to Align Your Agile Team for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</link>
				<pubDate>Fri, 03 Nov 2023 05:11:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</guid>
				<description>Chaos in Agile teams is usually caused by unclear goals, lack of direction, and poor communication, which leads to inefficiency and confusion. Aligning teams through clear goals, regular check-ins, open communication, and visualising progress increases motivation, collaboration, and productivity. Development managers should prioritise establishing and communicating shared objectives to reduce chaos and drive team success.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Gluttony</title>
				<link>https://engineering-leadership-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>Say-Do Metrics: Avoiding Agile Banditry in Your Organization</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</link>
				<pubDate>Fri, 05 Jan 2024 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</guid>
				<description>Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change.</description>
			</item>
			<item>
				<title>DevOps Demystified: Why It&#39;s More Than Just Tools and How to Embrace Its True Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/devops-demystified-why-it&#39;s-more-than-just-tools-and-how-to-embrace-its-true-value/</link>
				<pubDate>Wed, 07 Jun 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/devops-demystified-why-it&#39;s-more-than-just-tools-and-how-to-embrace-its-true-value/</guid>
				<description>DevOps is not just about tools like Azure DevOps but is a broader idea focused on improving engineering systems through collaboration, agility, and continuous improvement. Shifting your team&amp;rsquo;s mindset from tool selection to embracing DevOps principles will lead to better performance and product quality. Focus on how DevOps concepts can enhance your processes rather than relying solely on specific tools.</description>
			</item>
			<item>
				<title>Why is Scrum so easy to understand but incredibly hard to master?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</link>
				<pubDate>Tue, 28 Feb 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/</guid>
				<description>Scrum is challenging to master because true understanding and effective implementation require deep cultural change, transparency, and alignment with agile values, not just following the framework. Many teams struggle due to legacy mindsets, lack of comprehension, and misaligned organizational structures, leading to superficial adoption and missed opportunities for value creation. Development managers should focus on fostering a culture of transparency, learning, and value-driven collaboration to realize Scrum’s full benefits.</description>
			</item>
			<item>
				<title>Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</link>
				<pubDate>Fri, 07 Oct 2022 10:41:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</guid>
				<description>Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs.</description>
			</item>
			<item>
				<title>How do you think Agile is evolving since its inception in 2001?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</link>
				<pubDate>Wed, 15 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/</guid>
				<description>Agile has evolved since 2001, but many organizations still rely on top-down management rather than empowering teams to make decisions. The next major shift will be moving beyond just adopting frameworks like Scrum to building true agile capabilities across leadership, partners, and teams, focusing on adaptability and customer value. Development managers should revisit agile principles and work to remove barriers that prevent teams from responding quickly to change.</description>
			</item>
			<item>
				<title>Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</link>
				<pubDate>Wed, 18 Nov 2020 16:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/</guid>
				<description>The 2020 update to the Scrum Guide simplifies language and reduces prescriptive rules, emphasizing that Scrum Teams are self-managing and collectively accountable for delivering value each Sprint. Key changes include clear commitments for Product Goal, Sprint Goal, and Definition of Done, as well as a focus on cross-functional teams and improved Sprint Planning. Development managers should review the new guide to align their teams with these streamlined practices.</description>
			</item>
			<item>
				<title>How do you handle conflict in a Scrum Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</link>
				<pubDate>Mon, 07 Oct 2019 16:32:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/</guid>
				<description>When conflict arises in a Scrum Team, first encourage the team to resolve it themselves and use facilitation techniques that ensure everyone is heard, such as structured group discussions. The Scrum Master should coach team members and escalate only if necessary, involving HR or considering team changes as a last resort. Focus on building conflict resolution skills within the team and iteratively adapt your approach to find the best solution.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</link>
				<pubDate>Mon, 29 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</guid>
				<description>Evidence-Based Management (EBM) helps product owners make better decisions by tracking key metrics like current value, unrealized value, ability to innovate, and time to market, ensuring teams focus on delivering the right value efficiently. Using EBM enables you to identify when to pivot, align stakeholders, and engage your team in the product’s success. Consider adopting EBM practices or training, such as the PAL-EBM course, to maximize value delivery and team effectiveness.</description>
			</item>
			<item>
				<title>The Key to Being an Effective Agile Coach: Understanding the Team’s Context</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-being-an-effective-agile-coach-understanding-the-team-s-context/</link>
				<pubDate>Fri, 17 Nov 2023 11:00:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-being-an-effective-agile-coach-understanding-the-team-s-context/</guid>
				<description>Effective Agile coaching requires understanding your team&amp;rsquo;s specific work and context, not just Agile frameworks. Coaches with domain experience or those who actively learn about their team&amp;rsquo;s challenges can offer more relevant, practical advice and build trust. Development managers should ensure their coaches engage deeply with teams&amp;rsquo; day-to-day realities to maximize impact.</description>
			</item>
			<item>
				<title>Combatting Famine in Agile: How to Foster Stakeholder Engagement and Boost Team Morale</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-famine-in-agile-how-to-foster-stakeholder-engagement-and-boost-team-morale/</link>
				<pubDate>Tue, 31 Oct 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-famine-in-agile-how-to-foster-stakeholder-engagement-and-boost-team-morale/</guid>
				<description>A lack of stakeholder feedback in Agile leads to disengagement, low team morale, and misalignment with business goals. Regular check-ins, fostering a feedback culture, involving the product owner, and visualizing progress help keep stakeholders engaged and teams motivated. Development managers should prioritize active stakeholder involvement to ensure team purpose and deliver better results.</description>
			</item>
			<item>
				<title>What should be top of mind when a Scrum team prepare for a Sprint review?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</link>
				<pubDate>Mon, 04 Sep 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</guid>
				<description>To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency.</description>
			</item>
			<item>
				<title>Best Scrum advice you ever received?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</link>
				<pubDate>Mon, 05 Jun 2023 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/</guid>
				<description>The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team&amp;rsquo;s unique context. Flexibility and continuous improvement are more important than strict adherence to the framework, so use Scrum as a guide and modify it as needed to maximize value and innovation. Encourage your teams to experiment and iterate, focusing on what works best for your organization.</description>
			</item>
			<item>
				<title>Finding the problem on a partially succeeded build on Team Foundation Build Services 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/finding-the-problem-on-a-partially-succeeded-build-on-team-foundation-build-services-2010/</link>
				<pubDate>Thu, 04 Mar 2010 17:48:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/finding-the-problem-on-a-partially-succeeded-build-on-team-foundation-build-services-2010/</guid>
				<description>Learn how to diagnose and resolve partially succeeded builds in Team Foundation Build Services 2010 by tracing test failures, identifying code issues, and managing bugs.</description>
			</item>
			<item>
				<title>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>Branch Policies for TFVC</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/</link>
				<pubDate>Wed, 13 Jan 2016 15:49:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/</guid>
				<description>A new branch policy tool for TFVC allows you to apply policies like branch locks, code reviews, and work item requirements across multiple branches using simple patterns, making policy management much easier for large, complex codebases. This approach avoids cumbersome path-based setups and helps ensure key quality steps are not missed without overburdening developers. You can try the tool, provide feedback, or contribute to its development on GitHub.</description>
			</item>
			<item>
				<title>David thought he already knew Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</link>
				<pubDate>Mon, 26 May 2025 15:30:28 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/david-thought-he-already-knew-scrum/</guid>
				<description>Even experienced teams often fall into old habits and misunderstand Scrum, leading to ineffective practices that only look agile on the surface. Regularly revisiting the fundamentals and purpose of Scrum helps prevent complacency and ensures real improvement. Consider challenging your team&amp;rsquo;s understanding of Scrum to maintain true agility and drive meaningful change.</description>
			</item>
			<item>
				<title>Turning User Feedback into Actionable Work: A Guide to Maximizing Product Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/</link>
				<pubDate>Wed, 10 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/</guid>
				<description>Turning user feedback into actionable work quickly is essential for delivering real product value and staying truly agile. Teams that engage users regularly, prioritize feedback effectively, and integrate it into each Sprint see higher satisfaction and better business results. Review feedback weekly, involve stakeholders, and empower your team to act fast so your product evolves in line with user needs.</description>
			</item>
			<item>
				<title>Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/</link>
				<pubDate>Thu, 13 Jul 2023 07:41:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/</guid>
				<description>This Scrum Master training focuses on immediate real-world application, building a supportive peer community, and flexible learning to help participants address actual workplace challenges as they learn. The program’s structure allows for ongoing feedback and shared problem-solving, which boosts confidence and competence. Development managers should consider this approach to accelerate team growth and foster lasting professional networks.</description>
			</item>
			<item>
				<title>Why is DevOps such a Critical Element of Software Engineering?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-devops-such-a-critical-element-of-software-engineering/</link>
				<pubDate>Wed, 14 Jun 2023 14:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-devops-such-a-critical-element-of-software-engineering/</guid>
				<description>DevOps is essential in software engineering because it connects development and operations, enabling faster and more reliable delivery of value to customers. It acts as the glue that speeds up product releases and strengthens feedback loops, helping teams innovate and improve continuously. Development managers should consider adopting DevOps practices to accelerate delivery and enhance product quality.</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>Open-source with VSTS or TFS and Github for better DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</link>
				<pubDate>Tue, 10 May 2016 16:19:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</guid>
				<description>You can use VSTS or TFS for full DevOps and agile capabilities while keeping your open-source code on Github by setting up automated two-way synchronization between the platforms. This approach lets you manage private work and processes in VSTS, then publish selected branches to Github for public access and contributions. Set up automated builds in VSTS to sync code in both directions, using personal tokens for authentication, so you get the best of both tools without extra manual effort.</description>
			</item>
			<item>
				<title>Manifesto for Agile Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</guid>
				<description>Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement.</description>
			</item>
			<item>
				<title>Reasons to do an APS Course in 60 Seconds</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/reasons-to-do-an-aps-course-in-60-seconds/</link>
				<pubDate>Mon, 10 Jul 2023 14:30:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/reasons-to-do-an-aps-course-in-60-seconds/</guid>
				<description>An APS (Agile Professional Scrum) course helps teams new to Scrum get started effectively and provides experienced teams with a valuable refresher to ensure they are applying Scrum correctly. It aligns everyone on best practices and clarifies what professional Scrum should look like in your organisation. Consider enrolling your team to boost their Scrum skills and improve how you deliver software.</description>
			</item>
			<item>
				<title>How do you know if you&#39;ve got a great Sprint Goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-if-you&#39;ve-got-a-great-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 11:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-if-you&#39;ve-got-a-great-sprint-goal/</guid>
				<description>A great sprint goal excites and energizes both the team and stakeholders, sparking curiosity and engagement. If your team feels genuinely enthusiastic and eager to start, your sprint goal is likely effective. Aim to craft sprint goals that inspire interest and conversation, not just list tasks.</description>
			</item>
			<item>
				<title>Worst agile advice you&#39;ve ever heard?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/worst-agile-advice-you&#39;ve-ever-heard/</link>
				<pubDate>Tue, 09 May 2023 09:30:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/worst-agile-advice-you&#39;ve-ever-heard/</guid>
				<description>Rigid rules like requiring everyone to stand during daily meetings go against Agile’s core values of flexibility and respect for individuals. Teams should adapt processes to fit their unique needs and prioritize inclusivity and human-centric practices. Development managers should focus on outcomes and team well-being rather than enforcing one-size-fits-all routines.</description>
			</item>
			<item>
				<title>The new normal of the modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-new-normal-of-the-modern-application-lifecycle/</link>
				<pubDate>Wed, 10 Oct 2012 17:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-new-normal-of-the-modern-application-lifecycle/</guid>
				<description>Explores how rapid technological change, consumer expectations, and agile practices are reshaping software development, IT roles, and business relevance in the digital era.</description>
			</item>
			<item>
				<title>Guidance: How to layout you files for an Ideal Solution</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-how-to-layout-you-files-for-an-ideal-solution/</link>
				<pubDate>Mon, 17 May 2010 11:08:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/guidance-how-to-layout-you-files-for-an-ideal-solution/</guid>
				<description>Learn best practices for organising solution and project files in version control, including folder structure, naming conventions, and branching for maintainable code.</description>
			</item>
			<item>
				<title>The Myth of Knowing Everything Upfront in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</link>
				<pubDate>Mon, 16 Jun 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</guid>
				<description>You cannot know everything upfront in software development, so focus on continuous discovery and adapt as you learn. Scrum supports this by encouraging just enough planning and design to move forward, then delivering and learning from real use. Prioritise delivery and feedback over excessive upfront design to create more value.</description>
			</item>
			<item>
				<title>Agile and Scrum are often misunderstood</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</link>
				<pubDate>Sun, 04 May 2025 15:30:30 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/</guid>
				<description>Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team&amp;rsquo;s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance.</description>
			</item>
			<item>
				<title>Lack of Authority Blocks Progress on Critical Projects</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</link>
				<pubDate>Sun, 16 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/</guid>
				<description>Scrum Masters need real authority to remove obstacles and drive project success, but many are blocked by bureaucracy and lack of support. Without empowerment, they cannot be held accountable for outcomes and become ineffective. Development managers should ensure Scrum Masters have the authority to act if they expect meaningful results.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps Migration: A Step-by-Step Guide for Seamless Project Transfers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-a-step-by-step-guide-for-seamless-project-transfers/</link>
				<pubDate>Thu, 16 Nov 2023 12:47:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-a-step-by-step-guide-for-seamless-project-transfers/</guid>
				<description>Migrating projects in Azure DevOps can be straightforward if you use the right tools, carefully configure your migration files, and address common issues like field mapping and iteration paths. Key steps include installing migration tools, preparing configuration files, ensuring required fields are present, and matching Git repo names between source and target. Prepare thoroughly, follow the outlined steps, and seek expert help if needed to ensure a smooth migration.</description>
			</item>
			<item>
				<title>Unlocking Team Potential: The Essential Role of Digital Whiteboards in Agile Collaboration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-digital-whiteboards-in-agile-collaboration/</link>
				<pubDate>Tue, 19 Sep 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-digital-whiteboards-in-agile-collaboration/</guid>
				<description>Digital whiteboards are essential for effective team collaboration, especially in remote or hybrid agile environments, as they boost engagement, visual communication, and flexibility. Choosing the right tool, setting clear objectives, encouraging participation, and keeping sessions organised are key to maximising their value. Development managers should adopt and actively leverage digital whiteboards to enhance team alignment and productivity.</description>
			</item>
			<item>
				<title>What is a sprint goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-goal/</link>
				<pubDate>Wed, 31 May 2023 11:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-goal/</guid>
				<description>A sprint goal is a clear, tactical objective that guides the Scrum team’s work during each sprint, connecting daily efforts to the broader product vision. It provides a concrete focus for the team, enables actionable stakeholder feedback at sprint reviews, and helps maintain alignment and motivation. Development managers should ensure each sprint has a well-defined, tangible goal to drive progress and gather meaningful feedback.</description>
			</item>
			<item>
				<title>Why Copying Scaled Agile Frameworks Fails in Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>Transforming Scope Creep into Success: Embrace Agility and Deliver Value in a Changing Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</link>
				<pubDate>Wed, 04 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</guid>
				<description>Scope creep is often a sign that traditional fixed-scope approaches are failing in today’s fast-changing market. Focusing on delivering customer value, embracing flexible planning, and actively seeking feedback helps teams adapt and succeed. Development managers should shift from rigid scope management to Agile practices that prioritize value and responsiveness to change.</description>
			</item>
			<item>
				<title>The Fallacy of Equating Agility with Speed: What Agile Really Means</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</link>
				<pubDate>Thu, 11 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</guid>
				<description>Agile is not about working faster but about focusing on delivering the most valuable outcomes by prioritizing, experimenting, and adapting based on real customer needs. Speed alone can lead to building the wrong product, while Agile helps teams avoid wasted effort by eliminating unnecessary work and bureaucracy. Development managers should ensure their teams use Agile to maximize value, not just to increase velocity.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Use vanity metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</link>
				<pubDate>Thu, 29 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</guid>
				<description>Relying on vanity metrics like story points and velocity can undermine your Kanban strategy, as they do not provide actionable insights. Instead, focus on key metrics such as work in progress, cycle time, throughput, and work item age to identify bottlenecks, optimize flow, and improve predictability. Use data from your workflow tools to drive continuous improvement and make informed decisions for better team performance.</description>
			</item>
			<item>
				<title>Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</link>
				<pubDate>Wed, 25 Oct 2023 13:30:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/</guid>
				<description>Effective planning is essential for Agile and Scrum teams, not something to skip; key Scrum events like sprint planning, backlog refinement, and daily standups all revolve around planning. The goal is to find the right balance, plan enough to provide direction and coordination, especially in large teams, but avoid over-planning that wastes resources. Development managers should ensure their teams have clear goals, roadmaps, and themes to align efforts and adapt as needed.</description>
			</item>
			<item>
				<title>Rethinking Product Backlog: Navigating Through the Weeds of Complexity</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/</link>
				<pubDate>Thu, 17 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/</guid>
				<description>Relying on rigid hierarchies in the Product Backlog can hinder transparency and adaptability in complex product development. Instead, focus on a flat backlog that highlights valuable, deliverable items, supports team autonomy, and leverages emergent practices over fixed best practices. Empower your teams to structure the backlog in ways that foster learning, innovation, and resilience in changing environments.</description>
			</item>
			<item>
				<title>Why do you think the PSU course has become so popular for product development?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-do-you-think-the-psu-course-has-become-so-popular-for-product-development/</link>
				<pubDate>Tue, 21 Feb 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-do-you-think-the-psu-course-has-become-so-popular-for-product-development/</guid>
				<description>The PSU course is popular because it fills a major gap in Scrum by teaching teams how to integrate user experience and design thinking into product development, not just how to execute work. It helps teams prioritize and validate the most valuable work, ensuring they build the right products for the right users rather than just delivering features efficiently. Development managers should consider this course to improve decision-making and deliver products that truly meet customer needs.</description>
			</item>
			<item>
				<title>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>Unlocking Agile Success: Your Guide to the Professional Scrum Foundations Class and PSM I Assessment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-your-guide-to-the-professional-scrum-foundations-class-and-psm-i-assessment/</link>
				<pubDate>Thu, 28 May 2020 05:34:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-your-guide-to-the-professional-scrum-foundations-class-and-psm-i-assessment/</guid>
				<description>The Professional Scrum Foundations class offers hands-on, team-based learning to build practical Scrum skills and prepare for the PSM I assessment, with a focus on clear roles, transparency, and empirical process control. Participants who take the assessment soon after the class and use provided resources are more likely to succeed. Investing in this training can improve team collaboration and Agile adoption across your organisation.</description>
			</item>
			<item>
				<title>You can&#39;t stack rank hierarchical work items?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stack-rank-hierarchical-work-items/</link>
				<pubDate>Fri, 02 Mar 2012 00:41:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stack-rank-hierarchical-work-items/</guid>
				<description>Explains why stack ranking hierarchical work items is challenging in agile software development, highlighting issues with ordering, parent-child links, and best practices.</description>
			</item>
			<item>
				<title>Are you doing Scrum? Really?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</link>
				<pubDate>Sat, 19 Nov 2011 16:41:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-you-doing-scrum-really/</guid>
				<description>Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if they are truly following Scrum.</description>
			</item>
			<item>
				<title>The future of software development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-future-of-software-development/</link>
				<pubDate>Sat, 14 Jul 2007 19:03:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-future-of-software-development/</guid>
				<description>Explores how software factories, web services, and specialised development teams can speed up software delivery, improve adaptability, and meet fast-changing business needs.</description>
			</item>
			<item>
				<title>You can’t deliver change through memos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</link>
				<pubDate>Sat, 31 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/</guid>
				<description>Change cannot be achieved through memos or top-down mandates; real progress happens when everyone is trained together and understands the reasons behind new approaches. Broad-based training helps people identify problems and suggest improvements, making change more effective and sustainable. To drive meaningful change, involve all stakeholders in learning and improvement, not just managers or specialists.</description>
			</item>
			<item>
				<title>Kanban Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</link>
				<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</guid>
				<description>Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>In high competition markets, how does scrum product development help acquire and retain customers?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</link>
				<pubDate>Mon, 13 Feb 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</guid>
				<description>Scrum does not directly acquire or retain customers, but it helps teams deliver value quickly and adapt based on customer feedback, which can lead to competitive advantage. Its main strengths are making problems and opportunities visible, enabling rapid execution, and supporting a culture of innovation, but leaders and teams must still identify what customers need and how to deliver it. To succeed, focus on building strong teams, understanding market value, and using Scrum to consistently deliver and validate valuable features.</description>
			</item>
			<item>
				<title>Why are recessions a great time for organizations to evaluate the opportunity of agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</link>
				<pubDate>Thu, 09 Feb 2023 07:15:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</guid>
				<description>Recessions are an ideal time for organizations to consider agile because uncertainty highlights the need to adapt quickly, focus on customer value, and empower teams to make decisions. Agile enables rapid learning, continuous improvement, and faster response to market changes compared to traditional management. Development managers should pilot agile practices in small, iterative cycles to test their impact and build on what works.</description>
			</item>
			<item>
				<title>Why does Agile focus on values and principles rather than a prescribed set of steps?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-does-agile-focus-on-values-and-principles-rather-than-a-prescribed-set-of-steps/</link>
				<pubDate>Mon, 23 Jan 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-does-agile-focus-on-values-and-principles-rather-than-a-prescribed-set-of-steps/</guid>
				<description>Agile focuses on values and principles instead of fixed steps because software development is complex work with unpredictable challenges, so no set process can guarantee success. Teams must adapt, experiment, and continuously learn, using values like commitment, courage, focus, openness, and respect as guides. Development managers should foster a culture that supports flexibility and ongoing improvement rather than relying on rigid procedures.</description>
			</item>
			<item>
				<title>How do you make a good Forecast?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</link>
				<pubDate>Mon, 09 Sep 2019 11:20:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</guid>
				<description>To make better forecasts in agile projects, shift from using metrics like story points and velocity to flow-based metrics such as cycle time, throughput, and work in process, which improve predictability by encouraging smaller, more manageable work items. For budgeting and staffing, calculate team costs per sprint and extrapolate for annual needs, moving from project-based to team-based budgeting. Involve stakeholders early in this transition to address concerns and ensure smoother adoption.</description>
			</item>
			<item>
				<title>How do you incorporate a Design Sprint in Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</link>
				<pubDate>Fri, 16 Aug 2019 12:35:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/</guid>
				<description>Design Sprints should not be treated as separate or special sprints in Scrum; instead, design and UX work should be integrated into regular sprints as part of the team&amp;rsquo;s ongoing activities or handled during backlog refinement for future work. All team members should collaborate on these tasks, leveraging individual skills without creating silos or specialist-only phases. Development managers should ensure design activities are visible, collaborative, and aligned with sprint goals, using communities of practice to share knowledge across teams.</description>
			</item>
			<item>
				<title>Professional Scrum in Immingham, UK</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-in-immingham-uk/</link>
				<pubDate>Wed, 11 Dec 2013 09:34:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-in-immingham-uk/</guid>
				<description>Summary of a multi-team Professional Scrum training at DFDS Seaways in Immingham, UK, highlighting co-located learning, cross-team collaboration, and agile best practices.</description>
			</item>
			<item>
				<title>Quality enablement with Visual Studio 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</link>
				<pubDate>Wed, 15 May 2013 03:13:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</guid>
				<description>Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations in Alameda, California</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</link>
				<pubDate>Fri, 26 Oct 2012 16:30:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/</guid>
				<description>Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles in the development process.</description>
			</item>
			<item>
				<title>What&#39;s in a burndown?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</link>
				<pubDate>Wed, 28 Mar 2012 03:52:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-in-a-burndown/</guid>
				<description>Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations in Salt Lake City, Utah</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-salt-lake-city-utah/</link>
				<pubDate>Mon, 26 Mar 2012 03:56:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-salt-lake-city-utah/</guid>
				<description>Covers hands-on experiences teaching the Professional Scrum Foundations course in Salt Lake City, highlighting teamwork, agile practices, and real-world Scrum challenges.</description>
			</item>
			<item>
				<title>My first Scrum team in the wild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</link>
				<pubDate>Sun, 03 Apr 2011 21:44:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/</guid>
				<description>A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.</description>
			</item>
			<item>
				<title>US Department of Defence and the History of Waterfall Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/</link>
				<pubDate>Sun, 08 Jun 2025 15:30:25 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/</guid>
				<description>The US Department of Defence has moved away from traditional waterfall delivery and now requires lean-agile approaches in its procurement rules, recognizing that agility is essential for complex, high-stakes projects. This shift is now mandated, not just recommended, showing that even large, regulated organizations can make the change. Development managers should reconsider stage-gate processes and focus on enabling real agility rather than clinging to outdated controls.</description>
			</item>
			<item>
				<title>What are 3 key takeaways for a scrum team after attending an APS immersive learning experience course?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-are-3-key-takeaways-for-a-scrum-team-after-attending-an-aps-immersive-learning-experience-course/</link>
				<pubDate>Mon, 14 Aug 2023 07:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-are-3-key-takeaways-for-a-scrum-team-after-attending-an-aps-immersive-learning-experience-course/</guid>
				<description>The APS immersive course helps Scrum teams deeply understand core principles, apply them to real-world challenges, and distinguish essential Scrum practices from unnecessary add-ons. It provides practical, actionable insights for overcoming early implementation hurdles. Teams are encouraged to revisit and refine their Scrum approach for greater effectiveness.</description>
			</item>
			<item>
				<title>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>Navigating the Complex World of Azure DevOps Data Migration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-complex-world-of-azure-devops-data-migration/</link>
				<pubDate>Wed, 31 Jul 2024 12:00:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-complex-world-of-azure-devops-data-migration/</guid>
				<description>Migrating to Azure DevOps is complex, especially with legacy systems, but careful planning and attention to detail can prevent most issues. Key steps include importing legacy data before upgrades, aligning user identities to avoid workflow disruptions, cleaning up databases to meet size limits, and strictly following Microsoft’s backup procedures. Development managers should prioritize preparation and sequencing to ensure a smooth migration and minimize risks.</description>
			</item>
			<item>
				<title>The Evolution of Product Management in the Agile Era</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</link>
				<pubDate>Thu, 18 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</guid>
				<description>Agile product management replaces long release cycles with short, frequent delivery, enabling faster feedback, reduced risk, and more responsive adaptation to customer needs. Building quality in from the start and using practices like continuous integration and a clear definition of done minimizes defects and waste. Development managers should focus on shorter cycles, continuous feedback, and embedding quality throughout the process to stay competitive and maximize business value.</description>
			</item>
			<item>
				<title>What more needs to happen before traditional organisations consider Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-more-needs-to-happen-before-traditional-organisations-consider-agile/</link>
				<pubDate>Thu, 06 Jul 2023 07:08:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-more-needs-to-happen-before-traditional-organisations-consider-agile/</guid>
				<description>Traditional organisations must go beyond surface-level Agile adoption and commit to deep cultural change if they want to stay competitive, attract top talent, and respond quickly to market shifts. True Agile transformation requires honest readiness assessment, willingness to dismantle old structures, and embracing the discomfort of change. Leaders should act now to drive genuine, organisation-wide agility or risk falling behind more adaptive competitors.</description>
			</item>
			<item>
				<title>How does a Scrum team estimate what can be delivered in a Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-estimate-what-can-be-delivered-in-a-sprint/</link>
				<pubDate>Thu, 01 Jun 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-estimate-what-can-be-delivered-in-a-sprint/</guid>
				<description>Scrum teams do not precisely estimate what can be delivered in a Sprint; instead, they focus on understanding the size and complexity of backlog items to make informed guesses. This approach acknowledges the unpredictability of creative work and the high level of uncertainty in software development. Managers should allow flexibility in Sprint goals and use estimation tools to foster shared understanding rather than to set rigid deadlines.</description>
			</item>
			<item>
				<title>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>Why Embracing Automation is Essential for Reducing Human Error in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/</link>
				<pubDate>Wed, 18 Dec 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/</guid>
				<description>Automation is essential in software development because it reduces human error, speeds up feedback, and creates more reliable processes. Relying on manual steps leads to costly mistakes and unsustainable workloads, while automation enables faster, higher-quality releases and happier customers. Development managers should prioritise automating repetitive tasks and rearchitecting processes that cannot be automated to improve quality and efficiency.</description>
			</item>
			<item>
				<title>Before You Call Yourself an Agile Coach: The Importance of Real Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/</link>
				<pubDate>Mon, 13 Nov 2023 11:00:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/</guid>
				<description>To be an effective Agile coach, you need real hands-on experience working with teams to build products, not just theoretical knowledge. Practical involvement helps you understand team dynamics, earn credibility, and offer advice that resonates with teams. If you aspire to coach, seek opportunities to join or volunteer with Agile teams so you can build the trust and insight needed to guide others successfully.</description>
			</item>
			<item>
				<title>Quotes: Don&#39;t scale Scrum! Pragmatic or defeatist?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</link>
				<pubDate>Mon, 09 Oct 2023 14:30:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-don&#39;t-scale-scrum-pragmatic-or-defeatist/</guid>
				<description>The idea that Scrum cannot be scaled is a misconception; frameworks like Nexus show that Scrum can be effectively scaled to deliver greater value. Key recommendations include understanding Nexus, starting with a single team, and scaling thoughtfully while adapting as you go. Development managers should explore scaling options rather than dismissing them, as successful scaling is both possible and beneficial.</description>
			</item>
			<item>
				<title>Standard Environments for Automated Deployment and Testing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/</link>
				<pubDate>Sun, 17 Mar 2013 06:23:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/</guid>
				<description>Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines.</description>
			</item>
			<item>
				<title>Automated Testing in a modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/</link>
				<pubDate>Tue, 25 Sep 2012 04:33:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/</guid>
				<description>Explains the role of automated testing in modern software development, covering types, integration, benefits, challenges, and tools for maintaining code quality.</description>
			</item>
			<item>
				<title>Momentum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/momentum/</link>
				<pubDate>Tue, 16 May 2023 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/momentum/</guid>
				<description>Momentum in product delivery means not just moving quickly but ensuring everyone is aligned and moving in the same direction, which is essential for achieving shared goals. Teams with strong momentum can inspire and pull others along, making a real difference between stagnation and progress. To build and sustain this momentum, consider investing in Agile and Scrum training or coaching to foster collaboration and continuous improvement.</description>
			</item>
			<item>
				<title>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</guid>
				<description>Hiring a professional Product Owner is increasingly valued, with companies seeking external candidates who bring fresh perspectives and strong business understanding. The Product Owner is accountable for maximizing product value by setting vision, managing stakeholders, collaborating with teams, making key decisions, and using evidence-based approaches to drive outcomes. Ensure candidates have both certification and practical experience, but remember that while responsibilities can be delegated, ultimate accountability always remains with the Product Owner.</description>
			</item>
			<item>
				<title>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</link>
				<pubDate>Thu, 15 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</guid>
				<description>Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions.</description>
			</item>
			<item>
				<title>Navigating the Future with a Fine-Tuned Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</link>
				<pubDate>Thu, 10 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</guid>
				<description>A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery.</description>
			</item>
			<item>
				<title>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>Transforming Training: The Power of Immersive Learning in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</link>
				<pubDate>Wed, 08 May 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</guid>
				<description>Traditional two-day Scrum training is ineffective for lasting change because participants retain little and struggle to apply what they learn. Immersive learning, with shorter sessions spread over time, hands-on assignments, and ongoing feedback, leads to better retention, practical application, and continuous improvement. Development managers should consider adopting immersive training formats to drive real, sustainable transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</link>
				<pubDate>Mon, 06 May 2024 13:29:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</guid>
				<description>Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes.</description>
			</item>
			<item>
				<title>The Key to a Kanban Strategy: Understanding WIP Limits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</link>
				<pubDate>Wed, 06 Mar 2024 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</guid>
				<description>Setting work-in-progress (WIP) limits is essential for an effective Kanban strategy because it prevents overload, exposes bottlenecks, and improves workflow. The optimal WIP limit for each stage should be found through experimentation and regular adjustment, aiming for a balance that maximizes flow without causing idle time or bottlenecks. Start small, monitor results, and adjust limits as needed to boost team productivity and collaboration.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</link>
				<pubDate>Wed, 30 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</guid>
				<description>Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs.</description>
			</item>
			<item>
				<title>What Does a Poor Product Backlog Look Like?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-does-a-poor-product-backlog-look-like/</link>
				<pubDate>Mon, 19 Jun 2023 13:01:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-does-a-poor-product-backlog-look-like/</guid>
				<description>A poor product backlog is disorganised, lacks clear priorities, and confuses both teams and stakeholders. A strong backlog is clearly ordered and understood by everyone, aligning team efforts with business goals. Review your backlog regularly to ensure clarity and shared understanding across your team.</description>
			</item>
			<item>
				<title>Can organisations run an Applying Professional Scrum workshop? How would that help them?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</link>
				<pubDate>Wed, 29 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>Most companies still get Product Ownership wrong</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</link>
				<pubDate>Thu, 17 Apr 2025 15:30:37 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/</guid>
				<description>Many companies misunderstand the Product Owner role, treating it as simple backlog management or assigning it to any business analyst, which leads to weak products and misaligned teams. Effective Product Owners are strategic leaders who own the vision, make tough decisions, and use evidence to guide development. Development managers should ensure they are hiring or empowering true Product Owners with the right skills and authority, not just filling a position.</description>
			</item>
			<item>
				<title>Overview of &#39;applying metrics for predictability&#39; Kanban course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</link>
				<pubDate>Tue, 20 Feb 2024 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</guid>
				<description>The &amp;ldquo;Applying Metrics for Predictability&amp;rdquo; Kanban course teaches teams how to use key Kanban metrics and probabilistic forecasting to improve delivery predictability, enabling more accurate planning and increased stakeholder trust. Participants learn to interpret data, identify bottlenecks, and make informed decisions that drive efficiency and consistent value delivery. Development managers whose teams struggle with predictability should consider this course to enhance forecasting and workflow reliability.</description>
			</item>
			<item>
				<title>In Scrum, we don’t do UX separately</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</link>
				<pubDate>Thu, 12 Jun 2025 15:30:39 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/</guid>
				<description>UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed.</description>
			</item>
			<item>
				<title>Why the Concept of a &#34;Junior Scrum Master&#34; is a Misguided Myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</link>
				<pubDate>Mon, 24 Feb 2025 07:26:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/</guid>
				<description>The idea of a &amp;ldquo;junior Scrum Master&amp;rdquo; is misleading because the role demands significant experience, technical knowledge, and the ability to navigate complex team and organisational dynamics. Assigning this responsibility to inexperienced team members undermines both individual growth and team effectiveness. Development managers should ensure that Scrum Masters are chosen based on proven competence and relevant experience, not as entry-level positions.</description>
			</item>
			<item>
				<title>Overcoming the Ghost of Agile Certifications</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overcoming-the-ghost-of-agile-certifications/</link>
				<pubDate>Tue, 02 Jan 2024 07:00:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overcoming-the-ghost-of-agile-certifications/</guid>
				<description>Agile certifications are often overvalued and can distract from real learning and practical experience; passing an exam does not make someone an expert or guarantee they can deliver value. True capability comes from hands-on work, team recognition, and continuous learning, not just credentials. Development managers should prioritize real-world skills and team impact over certifications when hiring or developing Agile professionals.</description>
			</item>
			<item>
				<title>Unlocking the Superpower of Software Development: How Shifting Left Transforms Quality Assurance</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</link>
				<pubDate>Fri, 22 Nov 2024 14:04:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</guid>
				<description>Shifting quality assurance to the start of the development process leads to higher product quality, faster delivery, and lower costs by catching issues early and fostering better collaboration. Teams that adopt this approach see improved morale and stakeholder confidence. To get started, educate your team, involve QA early, encourage collaboration, use automation, and focus on continuous improvement.</description>
			</item>
			<item>
				<title>The Definition of Done: Ensuring Quality without Compromising Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</link>
				<pubDate>Wed, 27 Sep 2023 09:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</guid>
				<description>The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team&amp;rsquo;s delivery.</description>
			</item>
			<item>
				<title>Transform Your Agile Training: The Power of Immersive Learning for Lasting Impact</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-agile-training-the-power-of-immersive-learning-for-lasting-impact/</link>
				<pubDate>Thu, 08 Jun 2023 07:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-agile-training-the-power-of-immersive-learning-for-lasting-impact/</guid>
				<description>Immersive learning in Agile training connects theory directly to participants&amp;rsquo; real work, leading to better retention and practical application compared to traditional classroom methods. Spreading sessions over time, using real assignments, and fostering peer feedback help teams apply new concepts and drive meaningful change in their organizations. Consider adopting this approach to make Agile training more relevant and impactful for your teams.</description>
			</item>
			<item>
				<title>The Sprint Goal is a commitment for the Sprint Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</link>
				<pubDate>Fri, 27 Nov 2020 13:09:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/</guid>
				<description>The Sprint Goal is a clear, single objective for each Sprint that guides the team’s focus and aligns their work toward the Product Goal. It is set during Sprint Planning, helps teams adapt their work as needed without losing sight of the main purpose, and should be specific to your business context. Ensure your Product Owner proposes a meaningful Sprint Goal for each Sprint to keep the team aligned and working toward valuable outcomes.</description>
			</item>
			<item>
				<title>Unit Testing against the Team Foundation Server 2012 API</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/</link>
				<pubDate>Mon, 02 Apr 2012 03:52:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/</guid>
				<description>Explains how to unit test applications against the Team Foundation Server 2012 API, focusing on handling authentication for automated and unattended test scenarios.</description>
			</item>
			<item>
				<title>Do you know the minimum builds to create on any branch?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-the-minimum-builds-to-create-on-any-branch/</link>
				<pubDate>Thu, 18 Mar 2010 14:51:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-the-minimum-builds-to-create-on-any-branch/</guid>
				<description>Explains the essential three build types, Gate, CI, and Nightly, needed per branch to ensure code quality, test coverage, and collaboration in team projects.</description>
			</item>
			<item>
				<title>Solution: Testing Web Services with MSTest on Team Foundation Build Services 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/</link>
				<pubDate>Thu, 04 Mar 2010 13:15:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/</guid>
				<description>Explains how to configure MSTest for automated testing of web services on Team Foundation Build Services 2010, including handling dynamic server ports and build environments.</description>
			</item>
			<item>
				<title>Developer Day Scotland</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/developer-day-scotland/</link>
				<pubDate>Sun, 03 May 2009 21:42:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/developer-day-scotland/</guid>
				<description>Summary of sessions from a Glasgow developer event, covering refactoring, dynamic languages in .NET, MVVM for WPF, architecture, and ASP.NET 4.0 insights.</description>
			</item>
			<item>
				<title>Does test-driven development speed up development?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/does-test-driven-development-speed-up-development/</link>
				<pubDate>Mon, 15 Dec 2008 14:55:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/does-test-driven-development-speed-up-development/</guid>
				<description>Explores whether test-driven development (TDD) accelerates software delivery by reducing complexity, rework, and design flaws, and improving adaptability and productivity.</description>
			</item>
			<item>
				<title>Navigating Agile Learning: Embrace Change and Community in Uncertain Times</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-learning-embrace-change-and-community-in-uncertain-times/</link>
				<pubDate>Wed, 01 Apr 2020 16:26:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-learning-embrace-change-and-community-in-uncertain-times/</guid>
				<description>Adapting to remote work and uncertainty, agile learning now emphasizes flexibility in teaching, flow management to help teams handle remote challenges, and gamified tools for better engagement. Building a strong, interactive community and gathering feedback are key to effective virtual learning. Managers should support team adaptability and encourage participation in collaborative, skill-building opportunities.</description>
			</item>
			<item>
				<title>What is a product backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-backlog/</link>
				<pubDate>Thu, 18 May 2023 07:00:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-backlog/</guid>
				<description>A product backlog is a prioritized list of features or improvements that guides the development team and fosters collaboration. It should be flexible, clearly understood by everyone involved, and regularly pruned to stay lean and effective. Development managers should ensure their teams maintain a focused and well-understood backlog to maximize productivity and alignment.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</link>
				<pubDate>Thu, 01 Aug 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</guid>
				<description>Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive.</description>
			</item>
			<item>
				<title>What is Scrum?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-scrum/</link>
				<pubDate>Fri, 19 May 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-scrum/</guid>
				<description>Scrum is a framework that helps teams organize around shared goals and is especially effective for tackling complex, unpredictable work where you learn as you go. It is designed to help teams navigate tasks that are novel or constantly changing, making it ideal for software development environments. Consider exploring Scrum further to boost your team&amp;rsquo;s productivity and adaptability.</description>
			</item>
			<item>
				<title>#1 tip for a new Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</link>
				<pubDate>Wed, 17 May 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/</guid>
				<description>New Scrum Masters should start by thoroughly reading and understanding the Scrum Guide to grasp the fundamentals of Scrum, including its roles, events, and principles. This foundational knowledge is essential for effectively leading teams, coaching others, and running Agile projects successfully. Make it a priority to master the basics before moving on to more advanced concepts.</description>
			</item>
			<item>
				<title>Professional Scrum Foundations coming to Glasgow, Scotland in November 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-coming-to-glasgow-scotland-in-november-2013/</link>
				<pubDate>Wed, 04 Sep 2013 19:22:39 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-coming-to-glasgow-scotland-in-november-2013/</guid>
				<description>Professional Scrum training courses in Glasgow, Scotland, offer foundational and advanced Scrum skills for teams, Scrum Masters, and developers adopting agile practices.</description>
			</item>
			<item>
				<title>Working within a single Team Project with Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/working-within-a-single-team-project-with-team-foundation-server-2012/</link>
				<pubDate>Mon, 08 Apr 2013 00:53:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/working-within-a-single-team-project-with-team-foundation-server-2012/</guid>
				<description>Explains how to organise teams, products, and projects within a single Team Project in Team Foundation Server 2012, covering design, security, and workflow considerations.</description>
			</item>
			<item>
				<title>One Team Project to rule them all</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/one-team-project/</link>
				<pubDate>Sun, 15 Jul 2012 03:53:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/one-team-project/</guid>
				<description>Explains how to manage multiple teams and projects in Team Foundation Server using a single Team Project, with tips on Agile planning, backlogs, and process templates.</description>
			</item>
			<item>
				<title>3 core practices of Kanban. Actively managing work items in a workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</link>
				<pubDate>Mon, 26 Feb 2024 14:06:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/</guid>
				<description>Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow.</description>
			</item>
			<item>
				<title>FBI Launched Outdated Criminal Records System in 1995</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/</link>
				<pubDate>Fri, 06 Jun 2025 15:30:50 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/</guid>
				<description>The FBI launched a criminal records system in 1995 that was already outdated, and it remained in use for 15 years. Relying on big, infrequent releases means technology and user needs quickly outpace your delivery. To avoid delivering obsolete solutions, shift to frequent, incremental releases so you can keep up with changing requirements and user expectations.</description>
			</item>
			<item>
				<title>Transforming Technical Debt: Unlocking Opportunities for Innovation and Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</link>
				<pubDate>Wed, 20 Nov 2024 16:53:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</guid>
				<description>Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to accumulate slows delivery, increases maintenance costs, and lowers team morale, while proactively addressing it empowers teams, improves agility, and enhances value delivery. Make technical debt management a regular part of your workflow and educate stakeholders to unlock your team&amp;rsquo;s full potential.</description>
			</item>
			<item>
				<title>Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</link>
				<pubDate>Wed, 03 Apr 2024 17:21:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/</guid>
				<description>Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team&amp;rsquo;s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team&amp;rsquo;s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results.</description>
			</item>
			<item>
				<title>Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</link>
				<pubDate>Tue, 26 Mar 2024 10:56:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</guid>
				<description>Using a flat backlog instead of a hierarchical one makes it easier to prioritise work, adapt to changing needs, and focus on delivering value rather than just managing tasks. Flat structures avoid the inflexibility and complexity of parent-child relationships, allowing teams to use tags and flexible visualisations for context. Development managers should consider shifting to a flat backlog to improve agility and value delivery.</description>
			</item>
			<item>
				<title>Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team&#39;s Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</link>
				<pubDate>Mon, 08 Jan 2024 11:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</guid>
				<description>Relying on story points and velocity as performance metrics creates mistrust and pressure, undermining team collaboration and the core values of Agile. Instead, focus on objective measures like cycle time and throughput to better understand team efficiency and foster a healthier, more productive environment. Shift your metrics to support transparency and continuous improvement rather than arbitrary targets.</description>
			</item>
			<item>
				<title>Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</link>
				<pubDate>Wed, 21 Jun 2023 11:00:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/</guid>
				<description>The Scrum Master is not a manager or authority figure but a servant leader who facilitates team processes, removes obstacles, and encourages autonomy. Misconceptions like expecting status updates or report writing from the Scrum Master undermine team ownership and collaboration. Development managers should empower Scrum Masters to support teams rather than control them, fostering a culture of trust and shared responsibility.</description>
			</item>
			<item>
				<title>How do you select the most valuable items for the sprint backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</link>
				<pubDate>Tue, 30 May 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/</guid>
				<description>Selecting the most valuable items for the sprint backlog requires input from business, product, and engineering perspectives, not just following the product backlog order. It is a collaborative process where the team and stakeholders align on priorities to ensure each sprint delivers real value. Development managers should facilitate open discussions to balance strategic goals and technical needs when planning sprints.</description>
			</item>
			<item>
				<title>Create a Build vNext build definition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-build-vnext-build-definition/</link>
				<pubDate>Wed, 04 Mar 2015 17:37:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-build-vnext-build-definition/</guid>
				<description>Microsoft&amp;rsquo;s new Build vNext system for TFS and VSO is more modular and user-friendly, offering a wide range of out-of-the-box build and deployment tasks, improved configuration options, and better auditability of changes. It currently supports only Git repositories and continuous integration triggers, with plans for greater extensibility and additional features in the future. Development managers should consider evaluating Build vNext in test environments to prepare for its eventual adoption and to explore its enhanced flexibility and control.</description>
			</item>
			<item>
				<title>Configure a Build vNext Agent</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/configure-a-build-vnext-agent/</link>
				<pubDate>Wed, 14 Jan 2015 14:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/configure-a-build-vnext-agent/</guid>
				<description>Microsoft&amp;rsquo;s new modular build system for TFS and VSO, currently in early preview, replaces the old controller model with a more flexible pool and queue approach, simplifying agent management and permissions. Setting up a vNext Build Agent requires spinning up your own VM, installing Visual Studio 2013 or 2015, and configuring the agent via PowerShell. Development managers should prepare for a shift to this new system and consider early testing to understand its benefits and requirements.</description>
			</item>
			<item>
				<title>Why should I use Visual Studio ALM</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/</link>
				<pubDate>Wed, 07 Jan 2015 15:39:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/</guid>
				<description>Visual Studio ALM offers a comprehensive set of features beyond just source control and build, covering requirements, project, change, quality, feedback, defect, release, and analytics management in one integrated platform. Replacing it with tools like Git and Jenkins means losing most of this functionality and facing significant integration and maintenance challenges. Development managers should carefully assess what capabilities they need and consider the long-term effort required to replicate Visual Studio ALM’s end-to-end support before switching tools.</description>
			</item>
			<item>
				<title>Create a Standard Environment for Release Management in Azure</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/</link>
				<pubDate>Thu, 04 Dec 2014 11:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/</guid>
				<description>Setting up a standard release management environment in Azure is straightforward, cost-effective, and closely mirrors on-premises setups by using VMs, resource groups, and Application Insights for analytics. Using the old Azure portal gives better control over naming and resource organization, while Azure’s flexibility allows quick scaling and isolation for multiple environments. Development managers should consider scripting environment setup for repeatability and use Application Insights to track application usage and feedback.</description>
			</item>
			<item>
				<title>Migrating source from Perforce to Git on VSO</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</link>
				<pubDate>Wed, 20 Aug 2014 14:06:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</guid>
				<description>Step-by-step guide to migrating source code from Perforce to Git on VSO, covering repository setup, dependency management, build processes, and key migration tips.</description>
			</item>
			<item>
				<title>Execute Tests with Release Management for Visual Studio 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/</link>
				<pubDate>Mon, 27 Jan 2014 11:29:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/</guid>
				<description>Learn how to automate test execution during deployments using Release Management for Visual Studio 2013, including setup steps, environment tips, and common issues.</description>
			</item>
			<item>
				<title>Team Foundation Build 2012 Issue - The target CleanWorkspacePackageTempDir does not exist</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-build-2012-issue-the-target-cleanworkspacepackagetempdir-does-not-exist/</link>
				<pubDate>Sat, 20 Oct 2012 17:30:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-build-2012-issue-the-target-cleanworkspacepackagetempdir-does-not-exist/</guid>
				<description>Explains how to resolve the &amp;ldquo;CleanWorkspacePackageTempDir does not exist&amp;rdquo; build error in Team Foundation Build 2012 for upgraded ASP.NET MVC projects by updating project targets.</description>
			</item>
			<item>
				<title>Virtual Labs in the modern application lifecycle</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/virtual-labs-in-the-modern-application-lifecycle/</link>
				<pubDate>Sat, 22 Sep 2012 05:22:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/virtual-labs-in-the-modern-application-lifecycle/</guid>
				<description>Explores how virtual labs help development and operations teams manage, test, and automate complex modern application environments using virtualisation technologies.</description>
			</item>
			<item>
				<title>Full-fidelity history and data migration are mutually exclusive</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/</link>
				<pubDate>Tue, 29 May 2012 01:24:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/</guid>
				<description>Explains why preserving complete historical data and accurate dates is often incompatible with data migration, especially for compliance and traceability in regulated industries.</description>
			</item>
			<item>
				<title>Visual Studio 2010 Overview - Code Management and Build</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-code-management-and-build/</link>
				<pubDate>Tue, 31 Jan 2012 03:34:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-code-management-and-build/</guid>
				<description>Explains branching, merging, and build strategies in Visual Studio 2010, including integration with Team Foundation Server and new tools for code management and ALM.</description>
			</item>
			<item>
				<title>Scrum is hard to adopt and disruptive to your organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</link>
				<pubDate>Thu, 22 Sep 2011 01:17:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/</guid>
				<description>Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful organisational change and Agile adoption.</description>
			</item>
			<item>
				<title>Do you know about the Visual Studio 2010 Database Projects Guidance?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-database-projects-guidance/</link>
				<pubDate>Wed, 16 Feb 2011 12:40:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-database-projects-guidance/</guid>
				<description>Guidance on using Visual Studio 2010 Database Projects, covering project management, source control, deployment automation, integration, and database testing.</description>
			</item>
			<item>
				<title>How Visual Studio 2010 and Team Foundation Server enable Compliance</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/</link>
				<pubDate>Wed, 09 Feb 2011 22:04:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/</guid>
				<description>Explains how Visual Studio 2010 and Team Foundation Server support compliance by enabling traceability, audit trails, and linking code changes to requirements and tests.</description>
			</item>
			<item>
				<title>Why you need to tag your build servers in TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-you-need-to-tag-your-build-servers-in-tfs/</link>
				<pubDate>Mon, 14 Jun 2010 18:11:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-you-need-to-tag-your-build-servers-in-tfs/</guid>
				<description>Tagging build servers in TFS helps manage dependencies, assign builds to suitable agents, and streamline workflows across teams and regions for reliable automation.</description>
			</item>
			<item>
				<title>Log Elmah errors in Team Foundation Server</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/log-elmah-errors-in-team-foundation-server/</link>
				<pubDate>Sun, 26 Jul 2009 22:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/log-elmah-errors-in-team-foundation-server/</guid>
				<description>Explains how to log Elmah error reports as work items in Team Foundation Server, including attaching error logs, using templates, and retrieving error details.</description>
			</item>
			<item>
				<title>Mastering the Migration: Seamlessly Transitioning from TFS to Azure DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-migration-seamlessly-transitioning-from-tfs-to-azure-devops/</link>
				<pubDate>Wed, 31 Jul 2024 11:58:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-migration-seamlessly-transitioning-from-tfs-to-azure-devops/</guid>
				<description>Migrating from TFS to Azure DevOps can boost team collaboration, enable cloud capabilities, and provide continuous updates, but it requires careful planning to address compatibility issues and account alignment. Key steps include updating TFS, running validation tools, fixing issues, and thorough post-migration testing to avoid disruptions. To ensure a smooth transition, use the right migration tools and consider expert support for complex environments.</description>
			</item>
			<item>
				<title>Choosing a Process Template for your Team Project</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</link>
				<pubDate>Tue, 16 May 2017 10:40:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/</guid>
				<description>For agile software teams using TFS or VSTS, choose the Scrum process template to minimize friction and avoid legacy constraints found in the Agile and CMMI templates. The Scrum template is lightweight, flexible, and easier to customize for your team&amp;rsquo;s needs, while the other templates enforce outdated practices and create unnecessary barriers. Start with the Scrum template and tailor it as needed to support your workflow and adoption.</description>
			</item>
			<item>
				<title>3 Core Practices of Kanban: Improving a Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</link>
				<pubDate>Wed, 28 Feb 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/</guid>
				<description>Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Pride</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/</link>
				<pubDate>Fri, 13 Oct 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/</guid>
				<description>Excessive pride in Agile can lead teams to make decisions based on assumptions or ego rather than real customer value and data. To avoid wasted effort and missed opportunities, managers should ensure decisions are data-driven, learn from failures, and focus on meaningful metrics. Foster a culture of humility and continuous learning to keep teams aligned with business goals.</description>
			</item>
			<item>
				<title>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>Temperance in Agile: Why Less is More</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</link>
				<pubDate>Tue, 05 Dec 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</guid>
				<description>Focusing on just enough work and keeping your backlog, planning, and team size lean helps your team deliver more value and avoid waste or burnout. Prioritize only high-impact tasks, limit work in progress, and avoid over-refining or over-planning. Say no to non-essential work, balance short-term wins with long-term goals, and seek coaching if you struggle to maintain this balance.</description>
			</item>
			<item>
				<title>Access denied for orchestration plan on Build</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</link>
				<pubDate>Wed, 16 Dec 2015 14:18:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</guid>
				<description>When setting up a TFS build agent for a high-volume customer, a permissions error blocked builds because the &amp;ldquo;Project Collection Build Service&amp;rdquo; lacked write access to the orchestration plan. The issue is tied to permission inheritance and a known bug in TFS 2015 RTM, and can be fixed by ensuring both &amp;ldquo;Project Build Service&amp;rdquo; and &amp;ldquo;Project Collection Build Service&amp;rdquo; have inherited permissions on build definitions via Visual Studio. Development managers should verify these permissions to avoid similar build failures and streamline onboarding to new build systems.</description>
			</item>
			<item>
				<title>TFS Build reports Licencies.licx: unable to load type</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-build-reports-licencies-licx-unable-to-load-type/</link>
				<pubDate>Thu, 23 Oct 2014 15:09:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-build-reports-licencies-licx-unable-to-load-type/</guid>
				<description>A build error caused by mismatched component versions in the licenses.licx file blocked successful automated builds, even though local builds worked due to developers having multiple versions installed. The issue was traced to inconsistent component versions between developer machines and the build server, highlighting the risks of unmanaged dependencies. To avoid similar problems, regularly clean up or reimage developer workstations and prioritize setting up automated builds to catch these issues early.</description>
			</item>
			<item>
				<title>The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</link>
				<pubDate>Thu, 03 Jul 2025 05:22:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</guid>
				<description>The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together.</description>
			</item>
			<item>
				<title>In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</link>
				<pubDate>Mon, 30 Sep 2019 18:35:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/</guid>
				<description>When managing multiple Scrum teams in a Nexus, the Product Owner should focus on high-level vision and attend only the Nexus Sprint Planning, delegating detailed planning to designated Team Owners or Area Owners for each team. This approach reduces overload, maintains alignment with the product vision, and relies on strong communication and autonomy within teams. To implement this, assign a representative for each team to handle their Sprint Planning and ensure ongoing coordination with the Product Owner.</description>
			</item>
			<item>
				<title>Engaging with complexity - Team Foundation Server Edition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/</link>
				<pubDate>Mon, 01 Jul 2013 17:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/</guid>
				<description>Detailed walkthrough of a complex Team Foundation Server migration, covering remediation, hardware moves, upgrades, user management, and validation in large enterprise environments.</description>
			</item>
			<item>
				<title>Improvements in Visual Studio ALM from the ALM Summit</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/improvements-in-visual-studio-alm-from-the-alm-summit/</link>
				<pubDate>Fri, 08 Feb 2013 03:18:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/improvements-in-visual-studio-alm-from-the-alm-summit/</guid>
				<description>Highlights new Visual Studio ALM features from the ALM Summit, including Git support, web-based test management, Kanban swim lanes, and flexible work item tagging.</description>
			</item>
			<item>
				<title>In-Place upgrade of TFS 2008 to TFS 2010 with move to new domain</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/</link>
				<pubDate>Tue, 19 Apr 2011 17:57:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/</guid>
				<description>Step-by-step guide to upgrading Team Foundation Server 2008 to 2010, including in-place upgrade, build server update, and migrating to a new domain with key troubleshooting tips.</description>
			</item>
			<item>
				<title>Project of Projects with team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/project-of-projects-with-team-foundation-server-2010/</link>
				<pubDate>Tue, 04 Jan 2011 23:51:49 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/project-of-projects-with-team-foundation-server-2010/</guid>
				<description>Guidance on structuring projects in Team Foundation Server 2010 using Areas, Iterations, source code organisation, work item queries, and build naming for clarity and scalability.</description>
			</item>
			<item>
				<title>Syncing many Dynamics AX instances to a single TFS 2010 Team Project</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/</link>
				<pubDate>Fri, 08 Oct 2010 16:20:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/</guid>
				<description>Explains how to configure multiple Dynamics AX instances to sync with a single TFS 2010 Team Project, streamlining source control and work item management for many clients.</description>
			</item>
			<item>
				<title>How to deal with a stuck or infinitely queued build</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/</link>
				<pubDate>Thu, 09 Sep 2010 12:59:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/</guid>
				<description>Learn how to identify, troubleshoot, and resolve stuck or infinitely queued builds in Team Foundation Build, including tips for monitoring and restarting build services.</description>
			</item>
			<item>
				<title>Rangers shipped Visual Studio 2010 Database Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rangers-shipped-visual-studio-2010-database-guide/</link>
				<pubDate>Wed, 25 Aug 2010 14:04:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/rangers-shipped-visual-studio-2010-database-guide/</guid>
				<description>Comprehensive guidance and hands-on labs for managing, testing, and deploying Visual Studio 2010 Database projects, including source control and automation tips.</description>
			</item>
			<item>
				<title>TFS Event Handler in .NET 3.5 Part 1 - The Architecture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-1-the-architecture/</link>
				<pubDate>Tue, 21 Aug 2007 21:10:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-1-the-architecture/</guid>
				<description>Explains designing a resilient, scalable TFS event handler in .NET 3.5, focusing on system architecture using Visual Studio diagrams for planning and deployment.</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>Creating a WIT Adapter for the TFS Integration Platform for a source with no history</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/</link>
				<pubDate>Thu, 02 Jun 2011 11:25:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/</guid>
				<description>Explains how to build a TFS Integration Platform Work Item Tracking (WIT) adapter for a source system without history, covering versioning, field mapping, and error handling.</description>
			</item>
			<item>
				<title>Overview of Applying Professional Kanban course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</link>
				<pubDate>Wed, 21 Feb 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/</guid>
				<description>The Applying Professional Kanban course teaches how to integrate Kanban into any workflow to improve efficiency, identify bottlenecks, and drive continuous improvement using data and visualizations. Key outcomes include better workflow management, data-driven decision-making, and increased value delivery to stakeholders. Development managers should consider this course to optimize their team&amp;rsquo;s processes and deliver more value quickly.</description>
			</item>
			<item>
				<title>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>Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</link>
				<pubDate>Wed, 23 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</guid>
				<description>Kanban can be applied to any workflow to provide visibility into how work moves through your system, enabling teams to optimise delivery speed and manage capacity effectively. By using data analysis and probabilistic forecasting, such as Monte Carlo simulations, you can set realistic expectations with stakeholders and make more informed decisions. Consider adopting Kanban to improve transparency, predictability, and continuous improvement in your development processes.</description>
			</item>
			<item>
				<title>The benefits of Visual Studio Online for the Enterprise</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/</link>
				<pubDate>Mon, 26 Jan 2015 14:13:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/</guid>
				<description>Visual Studio Online offers enterprises always up-to-date tools, integrated build and release management, global access, and reduced infrastructure overhead, enabling greater agility and faster feature delivery. While some customisation and reporting features from TFS are still missing, Microsoft is actively addressing these gaps, and most teams can work around them using tags and new reporting options. Development managers should consider VSO to streamline operations, lower support costs, and keep pace with evolving business needs, provided they are ready for the cultural shift to cloud-based development.</description>
			</item>
			<item>
				<title>NDC London 2014: Why TFS no longer sucks and VSO is awesome</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-2014-why-tfs-no-longer-sucks-and-vso-is-awesome/</link>
				<pubDate>Wed, 10 Dec 2014 16:23:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-2014-why-tfs-no-longer-sucks-and-vso-is-awesome/</guid>
				<description>Team Foundation Server has significantly improved since 2012, and Visual Studio Online now offers a streamlined, cloud-based experience that eliminates many previous pain points. Recent demos showed that setup is fast, workflows are smoother, and release management is much easier, though some minor technical issues can still occur. Development managers should consider revisiting TFS and VSO for modern, efficient project and release management.</description>
			</item>
			<item>
				<title>Bug in the Visual Studio Git integration that results in a merge conflict</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/bug-in-the-visual-studio-git-integration-that-results-in-a-merge-conflict/</link>
				<pubDate>Thu, 09 Oct 2014 15:20:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/bug-in-the-visual-studio-git-integration-that-results-in-a-merge-conflict/</guid>
				<description>A bug in Visual Studio 2013.3&amp;rsquo;s Git integration causes merge conflicts when developers pull from a remote branch with local commits, even if there are no uncommitted changes. The issue disrupts teams migrating from older systems and can only be worked around by moving changes to a temporary branch and rolling back the local branch, or by adopting a workflow where all work is done on feature or hotfix branches. Installing Visual Studio 2013.4 CTP resolves the bug, so upgrading is recommended to avoid these conflicts and streamline development.</description>
			</item>
			<item>
				<title>Maven release prepare fails with detected changes in Jenkins</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/maven-release-prepare-fails-with-detected-changes-in-jenkins/</link>
				<pubDate>Wed, 09 Jul 2014 13:03:50 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/maven-release-prepare-fails-with-detected-changes-in-jenkins/</guid>
				<description>Explains how to fix Maven release prepare failures in Jenkins with TFS by using .tfignore files to exclude generated files like release.properties from source control.</description>
			</item>
			<item>
				<title>Mask password in Jenkins when calling TEE</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/mask-password-in-jenkins-when-calling-tee/</link>
				<pubDate>Wed, 21 May 2014 13:49:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/mask-password-in-jenkins-when-calling-tee/</guid>
				<description>Learn how to securely mask passwords in Jenkins logs when using Team Explorer Everywhere (TEE), preventing sensitive credentials from being exposed during build processes.</description>
			</item>
			<item>
				<title>Configuring Jenkins to talk to TFS 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-jenkins-to-talk-to-tfs-2013/</link>
				<pubDate>Wed, 07 May 2014 09:51:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-jenkins-to-talk-to-tfs-2013/</guid>
				<description>Guide to integrating Jenkins with TFS 2013 using the Team Foundation Server plugin, covering installation, configuration, and key differences from TF Build.</description>
			</item>
			<item>
				<title>Reserve an Agent for a special build in Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</link>
				<pubDate>Thu, 04 Apr 2013 01:37:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</guid>
				<description>Explains how to reserve a build agent in Team Foundation Server 2012 using custom activities, agent tagging, and workflow changes to ensure reliable, isolated build execution.</description>
			</item>
			<item>
				<title>Upgrading to Team Foundation Server 2012 Update 1 in production – DONE</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1-in-production-%E2%80%93-done/</link>
				<pubDate>Mon, 31 Dec 2012 18:47:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1-in-production-%E2%80%93-done/</guid>
				<description>Step-by-step guide to upgrading Team Foundation Server 2012 to Update 1, including prerequisites, backup, disk space, configuration, troubleshooting, and build server setup.</description>
			</item>
			<item>
				<title>Teams without areas using a team field in TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/teams-without-areas-using-a-team-field-in-tfs/</link>
				<pubDate>Wed, 19 Dec 2012 06:51:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/teams-without-areas-using-a-team-field-in-tfs/</guid>
				<description>Explains how to configure TFS to manage teams using a custom team field instead of area paths, enabling flexible team-product assignments and streamlined backlogs.</description>
			</item>
			<item>
				<title>TFS 2012 - Issue: Stuck builds in Team Foundation Build with no build number</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-stuck-builds-in-team-foundation-build-with-no-build-number/</link>
				<pubDate>Thu, 30 Aug 2012 05:40:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-stuck-builds-in-team-foundation-build-with-no-build-number/</guid>
				<description>Explains how to resolve stuck builds in TFS 2012 where no build number is assigned, caused by IIS multiple site bindings, with steps to fix via web.config settings.</description>
			</item>
			<item>
				<title>Deploy from Visual Studio 2012 to iOS, Windows Phone, Android and Windows</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/deploy-from-visual-studio-2012-to-ios-windows-phone-android-and-windows/</link>
				<pubDate>Fri, 03 Aug 2012 01:00:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/deploy-from-visual-studio-2012-to-ios-windows-phone-android-and-windows/</guid>
				<description>Learn how to use Visual Studio 2012 and C# to build and deploy a single codebase to iOS, Android, Windows, and more, with options for generic or platform-specific UIs.</description>
			</item>
			<item>
				<title>Migrating data from FogBugz to TFS 2012 using the TFS Integration Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-data-from-fogbugz-to-tfs-2012-using-the-tfs-integration-platform/</link>
				<pubDate>Tue, 17 Jul 2012 00:54:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-data-from-fogbugz-to-tfs-2012-using-the-tfs-integration-platform/</guid>
				<description>Step-by-step guide to migrating FogBugz data to TFS 2012 using a custom CSV adapter with the TFS Integration Platform, including setup, mapping, and import tips.</description>
			</item>
			<item>
				<title>Upgrading TFS 2010 to TFS 2012 with VSS Migration and Process Template consolidation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/</link>
				<pubDate>Sat, 30 Jun 2012 02:38:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/</guid>
				<description>Step-by-step guide to upgrading TFS 2010 to TFS 2012, migrating VSS data, consolidating process templates, and resolving common issues during team project integration.</description>
			</item>
			<item>
				<title>Scrum-damentals Webcast on 17th February 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-damentals-webcast-on-17th-february-2012/</link>
				<pubDate>Thu, 16 Feb 2012 22:56:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-damentals-webcast-on-17th-february-2012/</guid>
				<description>Explore common challenges in Scrum adoption, practical strategies for overcoming them, and proven practices to help teams implement Scrum more effectively.</description>
			</item>
			<item>
				<title>Product Owners are not a myth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/product-owners-are-not-a-myth/</link>
				<pubDate>Tue, 18 Oct 2011 01:56:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/product-owners-are-not-a-myth/</guid>
				<description>Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large product backlogs effectively.</description>
			</item>
			<item>
				<title>Are Scrum Masters agents for change?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-scrum-masters-agents-for-change/</link>
				<pubDate>Fri, 30 Sep 2011 22:59:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-scrum-masters-agents-for-change/</guid>
				<description>Explores the role of Scrum Masters in driving organisational change, effective Scrum adoption, and the importance of experience in leading successful agile transformations.</description>
			</item>
			<item>
				<title>Upgrading from TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SF 2010 with SfTSv3</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/</link>
				<pubDate>Thu, 30 Jun 2011 15:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/</guid>
				<description>Step-by-step guide to upgrading TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SharePoint 2010, including process template migration and data handling.</description>
			</item>
			<item>
				<title>A working Test Track Pro Adapter for the TFS Integration Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-working-test-track-pro-adapter-for-the-tfs-integration-platform/</link>
				<pubDate>Mon, 06 Jun 2011 14:23:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-working-test-track-pro-adapter-for-the-tfs-integration-platform/</guid>
				<description>Describes building a working Test Track Pro Adapter for the TFS Integration Platform, detailing code changes, conflict handling, and incremental work item migration.</description>
			</item>
			<item>
				<title>Test Track Pro and the case of the missing data</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/test-track-pro-and-the-case-of-the-missing-data/</link>
				<pubDate>Mon, 06 Jun 2011 05:24:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/test-track-pro-and-the-case-of-the-missing-data/</guid>
				<description>Explains issues with Test Track Pro data queries in TFS Integration, highlighting problems with date filters causing missing records and suggesting hourly filtering as a fix.</description>
			</item>
			<item>
				<title>Anatomy of an Automation for the Tfs Automation Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/anatomy-of-an-automation-for-the-tfs-automation-platform/</link>
				<pubDate>Wed, 01 Jun 2011 13:25:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/anatomy-of-an-automation-for-the-tfs-automation-platform/</guid>
				<description>Explains how to build, install, configure, and run automations for TFS, covering plugin deployment, activation, settings, UI integration, and job processing steps.</description>
			</item>
			<item>
				<title>How might we implement the Change Iteration Automation for the Tfs Automation Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-might-we-implement-the-change-iteration-automation-for-the-tfs-automation-platform/</link>
				<pubDate>Wed, 01 Jun 2011 06:09:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-might-we-implement-the-change-iteration-automation-for-the-tfs-automation-platform/</guid>
				<description>Explains automating the update of WIQL queries during sprint or iteration changes in the TFS Automation Platform, covering UI, configuration, and job execution details.</description>
			</item>
			<item>
				<title>SSW Brain Quest: Team Foundation Server and SharePoint 2010 (London)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/ssw-brain-quest-team-foundation-server-and-sharepoint-2010-london/</link>
				<pubDate>Fri, 02 Jul 2010 11:05:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/ssw-brain-quest-team-foundation-server-and-sharepoint-2010-london/</guid>
				<description>Full-day training covering new features and best practices in Visual Studio 2010, Team Foundation Server 2010, and SharePoint 2010 for project management and integration.</description>
			</item>
			<item>
				<title>Solution: Getting Silverlight to build on Team Foundation Build Services 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/solution-getting-silverlight-to-build-on-team-foundation-build-services-2010/</link>
				<pubDate>Wed, 03 Mar 2010 14:46:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/solution-getting-silverlight-to-build-on-team-foundation-build-services-2010/</guid>
				<description>Step-by-step guide to resolving build failures when compiling Silverlight 3 projects with Team Foundation Build Services 2010, including SDK, MSBuild, and code analysis fixes.</description>
			</item>
			<item>
				<title>Unity and ASP.NET</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/unity-and-asp-net/</link>
				<pubDate>Fri, 08 May 2009 17:31:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/unity-and-asp-net/</guid>
				<description>Explains how to use Unity for dependency injection in ASP.NET, enabling runtime component swapping without redeploying, with practical code and config examples.</description>
			</item>
			<item>
				<title>Fail a build if tests fail</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/fail-a-build-if-tests-fail/</link>
				<pubDate>Fri, 01 May 2009 11:11:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/fail-a-build-if-tests-fail/</guid>
				<description>Explains how to configure TFS 2008 builds to automatically fail if any tests fail by setting TreatTestFailureAsBuildFailure to true in the build project file.</description>
			</item>
			<item>
				<title>Mastering Kanban: A Simple Guide to Its Core Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</link>
				<pubDate>Mon, 01 Jul 2024 07:00:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</guid>
				<description>Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency.</description>
			</item>
			<item>
				<title>The Real Scope of a Product Owner: Beyond the Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</link>
				<pubDate>Mon, 27 Nov 2023 06:46:47 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/</guid>
				<description>The Product Owner role goes far beyond managing the backlog, requiring strategic decision-making, budget accountability, and proactive leadership to maximize product value and stay ahead of the market. Success depends on strong relationships, deep market understanding, and continuous learning, not just training. Development managers should ensure Product Owners have the authority, information, and support needed to drive product direction and deliver real business impact.</description>
			</item>
			<item>
				<title>Understanding the Power of Kanban in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</link>
				<pubDate>Mon, 05 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</guid>
				<description>Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery.</description>
			</item>
			<item>
				<title>Understanding Kanban: A Tool for Transparency and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</link>
				<pubDate>Mon, 24 Jun 2024 06:48:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</guid>
				<description>Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements.</description>
			</item>
			<item>
				<title>Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</link>
				<pubDate>Tue, 27 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/</guid>
				<description>Defining and visualising your workflow in Kanban creates shared understanding, clarity, and alignment among team members, which leads to greater efficiency. Establishing clear rules for task selection, workflow stages, and work in progress is essential for a stable and productive system. Take time to document and visualise your process so everyone knows how work flows and can contribute effectively.</description>
			</item>
			<item>
				<title>7 deadly sins of Agile: Envy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-envy/</link>
				<pubDate>Mon, 09 Oct 2023 11:17:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-envy/</guid>
				<description>Avoid copying Agile models like Spotify without considering your team&amp;rsquo;s unique context, as imitation and trend-driven decisions often lead to poor results. Instead, focus on adapting practices to fit your specific needs, encourage creativity and autonomy, and foster a positive, customer-focused culture. Assess new tools and methods carefully before adopting them to ensure they truly benefit your organization.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Sprint Planning Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/</guid>
				<description>Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders.</description>
			</item>
			<item>
				<title>Why Limiting Work in Progress is Key to Success in Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</link>
				<pubDate>Mon, 22 Jul 2024 06:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</guid>
				<description>Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable.</description>
			</item>
			<item>
				<title>Mastering the Agile Balance: Navigating Flexibility and Inflexibility for Project Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-agile-balance-navigating-flexibility-and-inflexibility-for-project-success/</link>
				<pubDate>Thu, 19 Sep 2024 11:05:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-agile-balance-navigating-flexibility-and-inflexibility-for-project-success/</guid>
				<description>Balancing flexibility and structure in agile is key to project success; while agile enables teams to adapt quickly and reallocate resources as needed, it can also create challenges with data quality and decision-making. Clear goals and regular context evaluation help teams decide when to be flexible or structured. Development managers should focus on aligning team adjustments with business objectives and ensure data integrity to support informed decisions.</description>
			</item>
			<item>
				<title>What is a product goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-goal/</link>
				<pubDate>Tue, 30 May 2023 11:00:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-product-goal/</guid>
				<description>A sprint goal is a specific, tactical objective that guides a Scrum team’s work during each sprint, connecting daily efforts to the broader product goal and vision. It provides a clear, tangible focus for the team and enables actionable stakeholder feedback at sprint reviews. Development managers should ensure every sprint has a well-defined goal to drive alignment, motivation, and meaningful progress.</description>
			</item>
			<item>
				<title>What&#39;s new in Visual Studio 2013 Team Foundation Server Preview</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-new-in-visual-studio-2013-team-foundation-server-preview/</link>
				<pubDate>Wed, 26 Jun 2013 16:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-new-in-visual-studio-2013-team-foundation-server-preview/</guid>
				<description>Highlights new features in Visual Studio 2013 Team Foundation Server, including agile portfolio management, enhanced team collaboration, and web-based test management.</description>
			</item>
			<item>
				<title>Unlocking Agile’s Core: Questioning to Create Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</link>
				<pubDate>Tue, 23 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/</guid>
				<description>Agile success depends on fostering a culture where everyone questions existing processes, seeks continuous improvement, and adapts quickly to change. Scrum helps teams identify inefficiencies and encourages regular reflection, while leadership must empower all employees to challenge the status quo and act on feedback. To stay ahead of competitors, create open forums for discussion, reward initiative, and ensure that improvement is a shared, ongoing effort across the organization.</description>
			</item>
			<item>
				<title>Migrating from Codeplex to Github</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-from-codeplex-to-github/</link>
				<pubDate>Wed, 02 Mar 2016 14:29:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-from-codeplex-to-github/</guid>
				<description>Migrating a Codeplex repository to GitHub is necessary due to declining support and features on Codeplex, but GitHub&amp;rsquo;s import tool is unreliable and does not handle folder selection or branches well. Using Git-TF with Chocolatey provides a more flexible and effective migration, allowing you to select specific folders and preserve history, though some manual steps are needed for wiki pages and other content. Development managers should use Git-TF for smoother migrations and plan for some manual adjustments, especially for documentation.</description>
			</item>
			<item>
				<title>Upcomming Scrum at Scale Workshop from Scrum.org</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upcomming-scrum-at-scale-workshop-from-scrum-org/</link>
				<pubDate>Wed, 22 Oct 2014 12:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upcomming-scrum-at-scale-workshop-from-scrum-org/</guid>
				<description>Scaling Scrum in large organizations is challenging mainly due to cultural resistance and lack of commitment to change. Scrum.org’s Scrum at Scale Workshop offers practical tools like the Agility Index and practices assessment to help you measure, guide, and sustain organizational change. Development managers leading agile transformation should consider this workshop to effectively drive and monitor enterprise-level agility.</description>
			</item>
			<item>
				<title>Can you really commit to delivering work?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</link>
				<pubDate>Sat, 26 Nov 2011 20:24:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/</guid>
				<description>Explores why Scrum shifted from &amp;ldquo;commitment&amp;rdquo; to &amp;ldquo;forecasting&amp;rdquo; work delivery, highlighting the risks of overpromising and the benefits of transparency in Agile teams.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 1 – The failed Sprint</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</link>
				<pubDate>Mon, 15 Mar 2010 13:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/</guid>
				<description>Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint.</description>
			</item>
			<item>
				<title>What is a Sprint Backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</link>
				<pubDate>Mon, 29 May 2023 12:01:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/</guid>
				<description>The Sprint Backlog is a combination of the Sprint Goal, selected tasks, and a clear plan for achieving them, providing transparency on current work and progress. It should balance goal-driven work with essential tasks like bug fixes, remain flexible to adapt to new needs during the Sprint, and set teams up for achievable success. Development managers should ensure Sprint Goals are realistic and use the Sprint Backlog to maintain focus while staying adaptable.</description>
			</item>
			<item>
				<title>Mastering Your Kanban Board: A Practical Guide to Visualising Workflows for Maximum Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/</link>
				<pubDate>Mon, 08 Jul 2024 06:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/</guid>
				<description>A clear and accurate Kanban board is essential for understanding and improving your team&amp;rsquo;s workflow. Map your actual process, adjust columns to reflect real work stages, and use visual cues to highlight priorities and bottlenecks. Regularly review and adapt your board to boost team collaboration, identify issues early, and drive continuous improvement.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning in Agile: Overcoming Cognitive Bias</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</link>
				<pubDate>Mon, 05 Feb 2024 07:00:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/</guid>
				<description>Immersive learning is essential for Agile teams because it exposes knowledge gaps and helps overcome overconfidence, leading to real skill growth. By focusing on hands-on practice, continuous feedback, and regular reflection, teams can drive ongoing improvement and avoid common pitfalls. Development managers should encourage immersive, practical learning environments to ensure their teams keep evolving and truly master Agile principles.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Insights from the New Scrum.org Course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/</link>
				<pubDate>Thu, 30 Nov 2023 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/</guid>
				<description>Scrum.org’s new Product Backlog Management course offers focused, practical training in backlog management, helping teams capture, prioritize, and break down work for better clarity and alignment. The compact 8-hour format teaches actionable techniques to minimize distractions, improve transparency, and ensure teams deliver high-value work that supports business goals. Development managers should consider this course to streamline their backlog processes and boost team efficiency.</description>
			</item>
			<item>
				<title>What is the most valuable thing you have learned through training people?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</link>
				<pubDate>Tue, 07 Feb 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/</guid>
				<description>The most valuable lesson from training people worldwide is that teams everywhere face the same core challenges when adopting agile and Scrum, regardless of culture or location. Shared experiences in training help participants realize their problems are not unique, which builds confidence and accelerates learning. Development managers should leverage global perspectives and proven Scrum practices to address common issues and drive improvement in their teams.</description>
			</item>
			<item>
				<title>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>Rethinking Software Estimation: Embrace Probabilistic Forecasting for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-software-estimation-embrace-probabilistic-forecasting-for-agile-success/</link>
				<pubDate>Thu, 05 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-software-estimation-embrace-probabilistic-forecasting-for-agile-success/</guid>
				<description>Traditional software estimation is often inaccurate and burdens teams, so shifting to probabilistic forecasting based on historical data provides more realistic delivery predictions and reduces pressure. Breaking work into smaller pieces and aiming for high confidence levels, such as 85 percent, helps teams adapt to uncertainty and improve outcomes. Development managers should move away from precise estimates and instead use probability-based forecasts to guide planning and decision-making.</description>
			</item>
			<item>
				<title>Mastering Data Migration: How to Minimise Downtime and Keep Your Engineers Productive</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-data-migration-how-to-minimise-downtime-and-keep-your-engineers-productive/</link>
				<pubDate>Tue, 05 Nov 2024 06:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-data-migration-how-to-minimise-downtime-and-keep-your-engineers-productive/</guid>
				<description>Data migration can be managed with minimal disruption if you plan thoroughly, use tools like Git to keep engineers productive during downtime, and schedule migrations strategically, such as over weekends. Dry runs and clear communication are essential to ensure everyone knows their tasks and to identify issues early. Invest time in preparation and involve experts when needed to keep your team working smoothly throughout the process.</description>
			</item>
			<item>
				<title>How does a Scrum team create a sprint goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</link>
				<pubDate>Thu, 01 Jun 2023 11:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/</guid>
				<description>A Scrum team creates a sprint goal by combining the product’s strategic direction, the product owner’s tactical priorities, and current engineering challenges to identify the most valuable next step. The team then selects backlog items that best align with this goal to deliver clear value to stakeholders. Encourage your teams to invest time in understanding context before setting sprint goals for better alignment and outcomes.</description>
			</item>
			<item>
				<title>How critical is a Product Owner in developing a great Product Backlog?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</link>
				<pubDate>Wed, 31 May 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/</guid>
				<description>A strong product owner is essential for creating and maintaining a focused, valuable product backlog that aligns with strategy and avoids becoming an unmanageable list of requests. The product owner is fully responsible for prioritizing and communicating the backlog, using discernment to filter out items that do not support the product vision. Development managers should ensure their product owners are empowered and proactive to keep teams focused on delivering real value.</description>
			</item>
			<item>
				<title>Unlocking Effective Product Development: How a Hypothesis-Driven Approach Transforms User Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</link>
				<pubDate>Mon, 10 Apr 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</guid>
				<description>A hypothesis-driven approach to product development helps teams make better decisions by focusing on user needs, testing ideas with small experiments, and measuring outcomes before committing to full features. Collaboration between design and engineering is essential to align daily decisions with long-term goals, and integrating these practices into continuous delivery ensures ongoing improvement. Development managers should encourage experimentation, cross-team collaboration, and data-driven feedback loops to build products that truly meet user needs.</description>
			</item>
			<item>
				<title>Professional Kanban Trainer for Applying Professional Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/professional-kanban-trainer-for-applying-professional-kanban/</link>
				<pubDate>Tue, 19 Jan 2021 14:49:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/professional-kanban-trainer-for-applying-professional-kanban/</guid>
				<description>The new Kanban Guide provides a clear, open framework for optimizing value flow in software teams, complementing Scrum and fostering collaboration between the two communities. Professional Kanban training now offers focused, in-depth learning on Kanban principles and practices, with certification and resources available independently of the course. Development managers can leverage these guides and training to improve workflow efficiency and team performance.</description>
			</item>
			<item>
				<title>Using the Build vNext capabilities and demands system</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/</link>
				<pubDate>Wed, 11 Mar 2015 14:10:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/</guid>
				<description>Build vNext in TFS 2015 introduces a capabilities and demands system that replaces the old agent tagging approach, making it easier to match build agents to specific build requirements. Agents now auto-detect many capabilities, and you can add custom ones like OS version to ensure builds run on suitable machines. This streamlines build configuration and targeting, so managers should explore Build vNext to improve build reliability and agent management.</description>
			</item>
			<item>
				<title>Configuring a DC in Azure for AAD integrated Release Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-dc-in-azure-for-aad-integrated-release-management/</link>
				<pubDate>Fri, 14 Nov 2014 15:24:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-dc-in-azure-for-aad-integrated-release-management/</guid>
				<description>Setting up a domain controller in Azure for Azure Active Directory integrated release management enables realistic cloud-based demos and infrastructure. The process involves creating a virtual machine, installing Active Directory and DNS roles, configuring a static IP, and promoting the VM to a domain controller, after which you can scale down resources to save costs. This approach provides a practical, cost-effective way to build and manage cloud-based environments for development and training; consider adopting similar steps for your own cloud infrastructure needs.</description>
			</item>
			<item>
				<title>Maven release perform tries to do a Get to a workspace sub folder in TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/maven-release-perform-tries-to-do-a-get-to-a-workspace-sub-folder-in-tfs/</link>
				<pubDate>Wed, 23 Jul 2014 14:26:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/maven-release-perform-tries-to-do-a-get-to-a-workspace-sub-folder-in-tfs/</guid>
				<description>Explains issues with Maven release perform in TFS workspaces, causes of build failures, and solutions for workspace mapping, concurrency, and label handling during migration.</description>
			</item>
			<item>
				<title>Should I upgrade to TFS 2013 Update 2?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/</link>
				<pubDate>Thu, 03 Apr 2014 19:26:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/</guid>
				<description>Covers new features and upgrade steps for Team Foundation Server 2013 Update 2, including improvements in backlog, test, release, and version management.</description>
			</item>
			<item>
				<title>PowerShell TFS 2013 API #2 - Adding to a GlobalList</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-2-adding-to-a-globallist/</link>
				<pubDate>Wed, 16 Oct 2013 10:30:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-2-adding-to-a-globallist/</guid>
				<description>Learn how to use PowerShell and the TFS 2013 API to automate adding items to a GlobalList by exporting, editing, and re-importing global lists as XML.</description>
			</item>
			<item>
				<title>Review: The Professional Scrum Masters Handbook</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/review-the-professional-scrum-masters-handbook/</link>
				<pubDate>Wed, 28 Aug 2013 10:41:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/review-the-professional-scrum-masters-handbook/</guid>
				<description>A critical review of The Professional Scrum Masters Handbook, highlighting its practical tips for new Scrum Masters and common Scrum misconceptions to avoid.</description>
			</item>
			<item>
				<title>Creating a custom Activity for Team Foundation Build</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-activity-for-team-foundation-build/</link>
				<pubDate>Mon, 22 Jul 2013 08:56:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-activity-for-team-foundation-build/</guid>
				<description>Learn how to create and integrate custom activities in Team Foundation Build, including class library setup, workflow design, argument handling, and build configuration.</description>
			</item>
			<item>
				<title>One Team Project Collection to rule them all - Consolidating Team Projects</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/one-team-project-collection-to-rule-them-all-consolidating-team-projects/</link>
				<pubDate>Thu, 12 Jul 2012 00:20:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/one-team-project-collection-to-rule-them-all-consolidating-team-projects/</guid>
				<description>Step-by-step guide to consolidating multiple Team Projects and Collections in TFS 2012 using the TFS Integration Platform, covering migration, mapping, and troubleshooting.</description>
			</item>
			<item>
				<title>Coffee Talk: Introduction to Scrum - webcast event this Friday!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</link>
				<pubDate>Tue, 16 Aug 2011 02:57:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/</guid>
				<description>Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking to improve team performance.</description>
			</item>
			<item>
				<title>Configuring a PowerShell Adapter for the TFS Integration Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-powershell-adapter-for-the-tfs-integration-platform/</link>
				<pubDate>Thu, 23 Jun 2011 03:58:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-powershell-adapter-for-the-tfs-integration-platform/</guid>
				<description>Explains how to set up and configure a PowerShell adapter in the TFS Integration Platform to automate source control migrations, with custom scripts for each change type.</description>
			</item>
			<item>
				<title>What is the Tfs Automation Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-the-tfs-automation-platform/</link>
				<pubDate>Tue, 31 May 2011 18:00:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-is-the-tfs-automation-platform/</guid>
				<description>A platform for automating Team Foundation Server tasks, enabling scheduled, event-driven, and on-demand workflows, with extensible package and Visual Studio integration.</description>
			</item>
			<item>
				<title>Scrum with Team Foundation Server 2010 Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-with-team-foundation-server-2010-done/</link>
				<pubDate>Sun, 09 May 2010 22:32:39 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-with-team-foundation-server-2010-done/</guid>
				<description>Explains how to use Scrum with Team Foundation Server 2010 for better project management, including practical tips, presentation slides, and real-world experiences.</description>
			</item>
			<item>
				<title>Even Scrum should have detailed Task descriptions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/even-scrum-should-have-detailed-task-descriptions/</link>
				<pubDate>Wed, 28 Apr 2010 19:25:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/even-scrum-should-have-detailed-task-descriptions/</guid>
				<description>Scrum tasks should include detailed descriptions so anyone can complete them, ensuring project continuity if team members are unavailable or leave unexpectedly.</description>
			</item>
			<item>
				<title>Do you have a contract between the Product Owner and the Team?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-have-a-contract-between-the-product-owner-and-the-team/</link>
				<pubDate>Wed, 14 Apr 2010 15:46:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/do-you-have-a-contract-between-the-product-owner-and-the-team/</guid>
				<description>Explains the benefits of a Sprint Contract in Scrum, clarifying roles and agreements between Product Owner and Team to improve collaboration and manage scope during each Sprint.</description>
			</item>
			<item>
				<title>Adventures in Scrum: Lesson 2 - For the record</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-2-for-the-record/</link>
				<pubDate>Mon, 15 Mar 2010 16:28:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-2-for-the-record/</guid>
				<description>Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, especially with proxy Product Owners.</description>
			</item>
			<item>
				<title>When should I use Areas in TFS instead of Team Projects in Team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/</link>
				<pubDate>Tue, 09 Mar 2010 12:27:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/</guid>
				<description>Explains when to use Areas versus Team Projects in TFS 2010, comparing benefits, drawbacks, and best practices for managing multiple projects and process templates.</description>
			</item>
			<item>
				<title>MVVM for Dummies</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/mvvm-for-dummies/</link>
				<pubDate>Fri, 05 Mar 2010 16:54:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/mvvm-for-dummies/</guid>
				<description>Explains the MVVM pattern in WPF and Silverlight, highlighting separation of concerns, code structure, and the roles of commanding, dependency injection, and design patterns.</description>
			</item>
			<item>
				<title>Updating the Command Line Parser</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/updating-the-command-line-parser/</link>
				<pubDate>Mon, 17 Aug 2009 01:11:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/updating-the-command-line-parser/</guid>
				<description>Explains how to enhance a .NET command line parser to support multiple and nested commands, custom switches, and delegate-based execution for flexible CLI applications.</description>
			</item>
			<item>
				<title>Wpf Drag &amp; Drop behaviour</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/wpf-drag-drop-behaviour/</link>
				<pubDate>Fri, 14 Aug 2009 04:16:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/wpf-drag-drop-behaviour/</guid>
				<description>Explains how to implement flexible drag and drop in WPF using MVVM, with customisable drop behaviour and bindable options for ItemsControls, including code examples.</description>
			</item>
			<item>
				<title>Branch madness!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/branch-madness/</link>
				<pubDate>Wed, 22 Oct 2008 14:44:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/branch-madness/</guid>
				<description>Describes a complex source control issue in TFS involving branch mismanagement, its impact on merging, and step-by-step actions taken to restore proper branch structure.</description>
			</item>
			<item>
				<title>Creating a managed service factory</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-managed-service-factory/</link>
				<pubDate>Tue, 19 Jun 2007 20:28:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-managed-service-factory/</guid>
				<description>Explains how to build a managed service factory to access and manage local or remote services across multiple servers, supporting flexible service discovery and integration.</description>
			</item>
			<item>
				<title>The Product Goal is a commitment for the Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</link>
				<pubDate>Mon, 23 Nov 2020 14:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</guid>
				<description>The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency.</description>
			</item>
			<item>
				<title>Mastering Azure DevOps Migration: Navigating Challenges, Solutions, and Best Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-navigating-challenges-solutions-and-best-practices/</link>
				<pubDate>Wed, 31 Jul 2024 09:25:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-migration-navigating-challenges-solutions-and-best-practices/</guid>
				<description>Migrating to Azure DevOps can streamline development, reduce costs, and improve scalability, but it comes with challenges like complex legacy systems and team resistance. Success depends on thorough planning, clear communication, extensive testing, and adaptability throughout the process. Development managers should assess their current environment, involve stakeholders, and consider expert support to ensure a smooth and effective migration.</description>
			</item>
			<item>
				<title>The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/</link>
				<pubDate>Tue, 17 Oct 2023 13:14:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/</guid>
				<description>The article draws parallels between the seven deadly sins of ancient Greece and common pitfalls in agile software development, highlighting issues like pride, envy, gluttony, lust, greed, sloth, and wrath as barriers to true agility. Key insights include the dangers of overconfidence, blind imitation, overloading backlogs, chasing quick fixes, prioritising short-term gains, lack of motivation, and blame culture. Development managers should regularly reflect on team behaviours, focus on genuine value delivery, and foster a culture of accountability and continuous improvement to avoid these traps.</description>
			</item>
			<item>
				<title>Rethinking &#39;User Stories&#39;: A Call for Clarity in Product Backlog Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-&#39;user-stories&#39;-a-call-for-clarity-in-product-backlog-management/</link>
				<pubDate>Thu, 31 Aug 2023 13:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-&#39;user-stories&#39;-a-call-for-clarity-in-product-backlog-management/</guid>
				<description>The author argues that using the term &amp;ldquo;User Stories&amp;rdquo; for all work items leads to confusion and unnecessary complexity, as not all tasks fit this format. Switching to a more generic term like &amp;ldquo;Product Backlog Item&amp;rdquo; allows teams to describe work more clearly and flexibly, improving communication and transparency. Development managers should consider updating their backlog terminology to better reflect the true nature of their work and support more effective product development.</description>
			</item>
			<item>
				<title>Install TFS 2015 today</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/install-tfs-2015-today/</link>
				<pubDate>Thu, 30 Apr 2015 05:50:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/install-tfs-2015-today/</guid>
				<description>If your team is still using TFS 2010 or earlier, you need to upgrade soon as support ends in July; TFS 2015 offers a streamlined installation, reduced setup time, and improved features, including a new build system. The Basic Server option makes it easy to get started with minimal configuration, and you can use SQL Express or your own SQL Server. Plan to upgrade to TFS 2015 now to ensure continued support and take advantage of the latest improvements.</description>
			</item>
			<item>
				<title>Upgrading to TFS 2015 in production - DONE</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-tfs-2015-in-production-done/</link>
				<pubDate>Wed, 29 Apr 2015 18:45:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-tfs-2015-in-production-done/</guid>
				<description>A production upgrade to TFS 2015 was completed smoothly for a customer with careful backups and preparation, despite some non-standard configurations. Key points include the need for sufficient disk space due to significant schema changes, ensuring all permissions and credentials are ready, and verifying backups before proceeding. With TFS 2010 support ending soon, managers should plan upgrades to TFS 2015 to benefit from new features and ongoing support.</description>
			</item>
			<item>
				<title>Unable to load task handler PowerShell for task VSBuild</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/unable-to-load-task-handler-powershell-for-task-vsbuild/</link>
				<pubDate>Wed, 18 Mar 2015 14:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/unable-to-load-task-handler-powershell-for-task-vsbuild/</guid>
				<description>When setting up TFS 2015&amp;rsquo;s vNext build system on Windows Server Technical Preview, you may encounter a &amp;ldquo;Unable to load task handler PowerShell for task VSBuild&amp;rdquo; error due to missing dependencies or blocked files. The issue is often caused by downloaded zip files being blocked by Windows, which prevents the build agent from working properly. To resolve this, ensure you unblock any downloaded zip files before extracting and configuring your build agent.</description>
			</item>
			<item>
				<title>Could not find mappings for all states defined in &#39;Test Suit&#39; work item type</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/could-not-find-mappings-for-all-states-defined-in-&#39;test-suit&#39;-work-item-type/</link>
				<pubDate>Tue, 11 Nov 2014 15:46:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/could-not-find-mappings-for-all-states-defined-in-&#39;test-suit&#39;-work-item-type/</guid>
				<description>After upgrading to TFS 2013.3, users may see errors related to state mappings in Test Suite work items, often due to case sensitivity issues in custom process templates, such as using &amp;ldquo;In process&amp;rdquo; instead of &amp;ldquo;In Process.&amp;rdquo; The problem can be fixed by correcting the state names to match the expected casing or by adding a custom process configuration override. This mainly affects older clients, so updating users to the latest version is also a recommended solution.</description>
			</item>
			<item>
				<title>Uncommitted changes messing up your sync in Git with Visual Studio</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/uncommitted-changes-messing-up-your-sync-in-git-with-visual-studio/</link>
				<pubDate>Thu, 16 Oct 2014 15:11:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/uncommitted-changes-messing-up-your-sync-in-git-with-visual-studio/</guid>
				<description>When moving from server-based to distributed version control like Git, you may encounter errors when pulling changes if you have uncommitted local changes. Unlike older systems, Git requires you to either commit or discard your changes before syncing, which helps prevent accidental code loss. Encourage your team to adapt to this workflow for safer and more reliable version control.</description>
			</item>
			<item>
				<title>Install of TFS 2013.3 with SharePoint 2013 on Windows Server 2012 R2 Update 1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/install-of-tfs-2013-3-with-sharepoint-2013-on-windows-server-2012-r2-update-1/</link>
				<pubDate>Tue, 30 Sep 2014 15:00:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/install-of-tfs-2013-3-with-sharepoint-2013-on-windows-server-2012-r2-update-1/</guid>
				<description>For a smooth TFS 2013.3 and SharePoint 2013 install on Windows Server 2012 R2, start with a clean, fully updated OS and avoid pre-installing SQL or TFS, as this often leads to extra rework. Key steps include using the advanced configuration for flexibility, ensuring all required service packs and features like full text search are present, and manually updating SharePoint to a supported version. To save time and avoid issues, always follow official documentation, use default options where possible, and rerun readiness checks after resolving errors.</description>
			</item>
			<item>
				<title>TFS Process Template migration script updated</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-process-template-migration-script-updated/</link>
				<pubDate>Wed, 11 Jun 2014 14:20:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-process-template-migration-script-updated/</guid>
				<description>Provides a step-by-step PowerShell script for migrating and updating TFS process templates, including customisations, work item types, categories, and configurations.</description>
			</item>
			<item>
				<title>Issue [ TFS 2013 ] Value cannot be null. Parameter name: key</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2013-value-cannot-be-null-parameter-name-key/</link>
				<pubDate>Wed, 23 Oct 2013 10:56:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2013-value-cannot-be-null-parameter-name-key/</guid>
				<description>Explains how a missing required Team Field in customised TFS 2013 work item templates causes &amp;ldquo;Value cannot be null&amp;rdquo; errors, and how to resolve it by making the field mandatory.</description>
			</item>
			<item>
				<title>PowerShell TFS 2013 API #1 - Get TfsCollection and TFS Services</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-1-get-tfscollection-and-tfs-services/</link>
				<pubDate>Wed, 02 Oct 2013 10:55:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-1-get-tfscollection-and-tfs-services/</guid>
				<description>Learn how to use PowerShell to connect to TFS 2013, import required assemblies, and access core TFS services like Work Item Store, Version Control, and project settings.</description>
			</item>
			<item>
				<title>Upgrading from the TFS 2013 Preview to TFS 2013 RC</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-the-tfs-2013-preview-to-tfs-2013-rc/</link>
				<pubDate>Mon, 09 Sep 2013 10:30:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-the-tfs-2013-preview-to-tfs-2013-rc/</guid>
				<description>Step-by-step guide to upgrading from TFS 2013 Preview to TFS 2013 RC, covering prerequisites, trial upgrades, installation, configuration, and best practices.</description>
			</item>
			<item>
				<title>What&#39;s new in Visual Studio 2013 and TFS 2013 RC</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-new-in-visual-studio-2013-and-tfs-2013-rc/</link>
				<pubDate>Mon, 09 Sep 2013 10:00:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what&#39;s-new-in-visual-studio-2013-and-tfs-2013-rc/</guid>
				<description>Overview of new features in Visual Studio 2013 and TFS 2013 RC, including Team Explorer updates, agile tools, test management, charting, and improved collaboration.</description>
			</item>
			<item>
				<title>Modelling Teams in Team Foundation Server 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/modelling-teams-in-team-foundation-server-2013/</link>
				<pubDate>Tue, 16 Jul 2013 08:57:50 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/modelling-teams-in-team-foundation-server-2013/</guid>
				<description>Guidance on structuring teams, areas, iterations, source control, and security in Team Foundation Server 2013 to support project management and reporting needs.</description>
			</item>
			<item>
				<title>Issue [ TFS 2013 ] You get TF400324 when connecting InRelease to TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2013-you-get-tf400324-when-connecting-inrelease-to-tfs/</link>
				<pubDate>Thu, 11 Jul 2013 17:02:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2013-you-get-tf400324-when-connecting-inrelease-to-tfs/</guid>
				<description>Explains how to resolve TF400324 errors when connecting InRelease 3 to TFS 2013, including correct URL usage and a supported PowerShell fix for collection paths.</description>
			</item>
			<item>
				<title>Create a Portfolio Backlog hierarchy in Team Foundation Server 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-portfolio-backlog-hierarchy-in-team-foundation-server-2013/</link>
				<pubDate>Mon, 08 Jul 2013 21:35:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-portfolio-backlog-hierarchy-in-team-foundation-server-2013/</guid>
				<description>Learn how to customise Team Foundation Server 2013 to add a multi-level Portfolio Backlog hierarchy by editing work item types, categories, and process configuration.</description>
			</item>
			<item>
				<title>Upgrading to Team Foundation Server 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2013/</link>
				<pubDate>Wed, 26 Jun 2013 16:35:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2013/</guid>
				<description>Step-by-step guide to upgrading to Team Foundation Server 2013, including backup, installation, configuration, validation, and estimated upgrade times for various scenarios.</description>
			</item>
			<item>
				<title>Issue [ TFS 2012.2 ] Detaching collection fails on SnapshotIdentities with object reference not set to an instance of an object</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2012-2-detaching-collection-fails-on-snapshotidentities-with-object-reference-not-set-to-an-instance-of-an-object/</link>
				<pubDate>Mon, 24 Jun 2013 09:35:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/issue-tfs-2012-2-detaching-collection-fails-on-snapshotidentities-with-object-reference-not-set-to-an-instance-of-an-object/</guid>
				<description>Explains how detaching a Team Project Collection in TFS 2012.x can fail due to orphaned identities, causing a NullReferenceException, and outlines steps for diagnosis and support.</description>
			</item>
			<item>
				<title>Restore TFS backups from SQL Enterprise to SQL Express</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/restore-tfs-backups-from-sql-enterprise-to-sql-express/</link>
				<pubDate>Mon, 27 May 2013 08:52:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/restore-tfs-backups-from-sql-enterprise-to-sql-express/</guid>
				<description>Explains how to resolve errors when restoring TFS backups from SQL Enterprise to SQL Express by removing unsupported data compression features from the database.</description>
			</item>
			<item>
				<title>Configure Test Plans for web access in TFS 2012.2</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/configure-test-plans-for-web-access-in-tfs-2012-2/</link>
				<pubDate>Fri, 10 May 2013 20:42:16 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/configure-test-plans-for-web-access-in-tfs-2012-2/</guid>
				<description>Explains how to configure Test Plans for web access in TFS 2012.2, focusing on Area Path, team field settings, visibility issues, and workarounds for team-based access.</description>
			</item>
			<item>
				<title>TFS2012.2 - Issue: Object not set to instance of object with TF400898, TF53010 &amp; TF30065</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs2012-2-issue-object-not-set-to-instance-of-object-with-tf400898-tf53010-tf30065/</link>
				<pubDate>Wed, 08 May 2013 17:51:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs2012-2-issue-object-not-set-to-instance-of-object-with-tf400898-tf53010-tf30065/</guid>
				<description>Explains causes and solutions for &amp;ldquo;Object reference not set to an instance of an object&amp;rdquo; errors (TF400898, TF53010, TF30065) in TFS 2012.2, fixed in Update 3.</description>
			</item>
			<item>
				<title>Upgrading your process template from MSF for Agile 4 to Visual Studio Scrum 2.x</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/</link>
				<pubDate>Mon, 22 Apr 2013 17:37:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/</guid>
				<description>Step-by-step guide to safely upgrade from MSF for Agile 4 to Visual Studio Scrum 2.x process templates in TFS, including handling customisations and preserving work items.</description>
			</item>
			<item>
				<title>TFS 2012 Issue: TF215097 an error occurred while initializing a build for build definition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-tf215097-an-error-occurred-while-initializing-a-build-for-build-definition/</link>
				<pubDate>Thu, 18 Apr 2013 17:35:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-tf215097-an-error-occurred-while-initializing-a-build-for-build-definition/</guid>
				<description>Explains the TF215097 error in TFS 2012 builds, its cause, missing custom assemblies, and how to resolve it by configuring the build controller to reference those assemblies.</description>
			</item>
			<item>
				<title>Migration from TF Service to TF Server with the TFS Integration Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migration-from-tf-service-to-tf-server-with-the-tfs-integration-platform/</link>
				<pubDate>Thu, 18 Apr 2013 03:28:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migration-from-tf-service-to-tf-server-with-the-tfs-integration-platform/</guid>
				<description>Guide to migrating data from Team Foundation Service to Team Foundation Server using the TFS Integration Platform, including user and work item mapping steps.</description>
			</item>
			<item>
				<title>Migrating source code with history to TFS 2012 with Git-Tf</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-code-with-history-to-tfs-2012-with-git-tf/</link>
				<pubDate>Tue, 19 Mar 2013 03:15:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-code-with-history-to-tfs-2012-with-git-tf/</guid>
				<description>Guide to migrating source code and preserving history from one Team Foundation Server (TFS) 2012 instance to another using Git-Tf and Git command-line tools.</description>
			</item>
			<item>
				<title>Quality Centre to Team Foundation Server in one complex step</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-centre-to-team-foundation-server-in-one-complex-step/</link>
				<pubDate>Wed, 05 Dec 2012 00:58:58 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-centre-to-team-foundation-server-in-one-complex-step/</guid>
				<description>Compares tools for migrating or synchronising data from HP Quality Centre to Team Foundation Server, outlining features, limitations, and best options for each approach.</description>
			</item>
			<item>
				<title>TFS 2012 Update 1 - TF255430: the database was partially upgraded during a failed upgrade</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-update-1-tf255430-the-database-was-partially-upgraded-during-a-failed-upgrade/</link>
				<pubDate>Mon, 03 Dec 2012 18:25:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-update-1-tf255430-the-database-was-partially-upgraded-during-a-failed-upgrade/</guid>
				<description>Explains how to resolve Team Foundation Server 2012 upgrade failures caused by partial database upgrades, SQL connectivity issues, and Analysis Services errors.</description>
			</item>
			<item>
				<title>TFS 2012 Agile Planning Tools Issue - nested tasks makes the parent task disappear</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-agile-planning-tools-issue-nested-tasks-makes-the-parent-task-disappear/</link>
				<pubDate>Sun, 14 Oct 2012 19:35:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-agile-planning-tools-issue-nested-tasks-makes-the-parent-task-disappear/</guid>
				<description>Explains why nesting tasks in TFS 2012 Agile Planning Tools causes parent tasks to disappear, and recommends using nested Product Backlog Items instead for proper visibility.</description>
			</item>
			<item>
				<title>Requirement management in the modern application lifecycle with TFS</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/requirement-management-in-the-modern-application-lifecycle/</link>
				<pubDate>Sun, 09 Sep 2012 17:51:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/requirement-management-in-the-modern-application-lifecycle/</guid>
				<description>Explains how Team Foundation Server supports requirement management in modern app development, including traceability, integration, and partner tools for agile and compliance needs.</description>
			</item>
			<item>
				<title>TFS Integration Tools - Issue: TF10141 No Files checked in as a result of a TFS check-in failure</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf10141-no-files-checked-in-as-a-result-of-a-tfs-check-in-failure/</link>
				<pubDate>Wed, 22 Aug 2012 01:25:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf10141-no-files-checked-in-as-a-result-of-a-tfs-check-in-failure/</guid>
				<description>Explains how to resolve TFS Integration Tools check-in failures (TF10141), covering conflict identification, manual resolution steps, and handling workspace issues.</description>
			</item>
			<item>
				<title>TFS Integration Tools - Issue: TF205022: The following path contains more than the allowed 259 characters</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf205022-the-following-path-contains-more-than-the-allowed-259-characters/</link>
				<pubDate>Mon, 20 Aug 2012 21:54:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf205022-the-following-path-contains-more-than-the-allowed-259-characters/</guid>
				<description>Explains how to resolve the TFS error caused by file paths exceeding 259 characters during migration, with steps to shorten paths and adjust workspace settings.</description>
			</item>
			<item>
				<title>TFS Integration Tools - Issue: TF14009: Cannot merge source into target because the target is underneath source</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf14009-cannot-merge-source-into-target-because-the-target-is-underneath-source/</link>
				<pubDate>Mon, 20 Aug 2012 18:19:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tf14009-cannot-merge-source-into-target-because-the-target-is-underneath-source/</guid>
				<description>Explains the TF14009 error in TFS when merging a source into a subfolder of itself, its causes during migration, and practical workarounds to resolve the issue.</description>
			</item>
			<item>
				<title>TFS 2012 - Issue: Manage Group Membership missing from admin after TFS 2008 to TFS 2012 Upgrade</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-manage-group-membership-missing-from-admin-after-tfs-2008-to-tfs-2012-upgrade/</link>
				<pubDate>Thu, 16 Aug 2012 21:46:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-manage-group-membership-missing-from-admin-after-tfs-2008-to-tfs-2012-upgrade/</guid>
				<description>Explains how to restore missing group membership management in TFS 2012 after upgrading from TFS 2008 by manually adding permissions using TFS Security commands.</description>
			</item>
			<item>
				<title>TFS Integration Tools - Issue: TFS WIT bypass-rule submission is enabled</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tfs-wit-bypass-rule-submission-is-enabled/</link>
				<pubDate>Thu, 09 Aug 2012 23:33:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-issue-tfs-wit-bypass-rule-submission-is-enabled/</guid>
				<description>Explains how to resolve TFS Integration Platform errors caused by missing permissions for bypass-rule submission by adding accounts to the Team Foundation Service Accounts group.</description>
			</item>
			<item>
				<title>Upgrading from TFS 2008 to TFS 2010 Overview</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-to-tfs-2010-overview/</link>
				<pubDate>Tue, 31 Jul 2012 18:35:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-to-tfs-2010-overview/</guid>
				<description>Guides the upgrade from TFS 2008 to TFS 2010, covering technical steps, process template migration, challenges, and best practices for a smooth transition.</description>
			</item>
			<item>
				<title>Installing TFS 2012 with Lab Management 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/installing-tfs-2012-with-lab-management-2012/</link>
				<pubDate>Wed, 20 Jun 2012 02:30:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/installing-tfs-2012-with-lab-management-2012/</guid>
				<description>Step-by-step guide to installing and configuring TFS 2012 with Lab Management, including SQL Server, SCVMM integration, troubleshooting, and environment setup tips.</description>
			</item>
			<item>
				<title>Process Template Upgrade #7 – Rename Work Items and Import new ones</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/process-template-upgrade-7-%E2%80%93-rename-work-items-and-import-new-ones/</link>
				<pubDate>Sat, 12 May 2012 00:25:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/process-template-upgrade-7-%E2%80%93-rename-work-items-and-import-new-ones/</guid>
				<description>Step-by-step guide to upgrading TFS process templates by renaming and importing work item types, preserving data, updating fields, categories, configs, and reports.</description>
			</item>
			<item>
				<title>Process Template Upgrade #3 - Destroy all Work Items and Import new ones</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/process-template-upgrade-3-destroy-all-work-items-and-import-new-ones/</link>
				<pubDate>Fri, 21 Oct 2011 17:42:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/process-template-upgrade-3-destroy-all-work-items-and-import-new-ones/</guid>
				<description>Step-by-step guide to upgrading a process template in TFS by deleting all existing work items, archiving queries and reports, and importing new template elements.</description>
			</item>
			<item>
				<title>Subversion to TFS 2010: The migration engine is unable to resolve a conflict where two changes have the same target item</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/subversion-to-tfs-2010-the-migration-engine-is-unable-to-resolve-a-conflict-where-two-changes-have-the-same-target-item/</link>
				<pubDate>Fri, 26 Aug 2011 18:18:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/subversion-to-tfs-2010-the-migration-engine-is-unable-to-resolve-a-conflict-where-two-changes-have-the-same-target-item/</guid>
				<description>Explains how to resolve case sensitivity conflicts when migrating from Subversion to TFS 2010, including tools and steps to handle duplicate target item errors.</description>
			</item>
			<item>
				<title>Upgrading your Process Template in Team Foundation Server</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-in-team-foundation-server/</link>
				<pubDate>Thu, 28 Jul 2011 22:00:39 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-your-process-template-in-team-foundation-server/</guid>
				<description>Explains methods for upgrading process templates in Team Foundation Server, comparing pros and cons of each approach, and highlighting risks, data integrity, and best practices.</description>
			</item>
			<item>
				<title>What do you do with a Work Item History Not Found Conflict Type Details</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-do-you-do-with-a-work-item-history-not-found-conflict-type-details/</link>
				<pubDate>Sat, 04 Jun 2011 00:50:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-do-you-do-with-a-work-item-history-not-found-conflict-type-details/</guid>
				<description>Explains how missing or non-consecutive work item revision history during TFS migrations causes conflicts, and details troubleshooting steps and unresolved backlog issues.</description>
			</item>
			<item>
				<title>What to do after a servicing fails on TFS 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-to-do-after-a-servicing-fails-on-tfs-2010/</link>
				<pubDate>Tue, 04 Jan 2011 16:10:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-to-do-after-a-servicing-fails-on-tfs-2010/</guid>
				<description>Guidance on troubleshooting failed servicing in TFS 2010, including schema version issues, recovery steps, and risks of database repair versus starting over.</description>
			</item>
			<item>
				<title>TFS 2010 Work Item Seed: TFS Work Item system.id at a predefined number</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2010-work-item-seed-tfs-work-item-system-id-at-a-predefined-number/</link>
				<pubDate>Wed, 20 Oct 2010 23:17:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2010-work-item-seed-tfs-work-item-system-id-at-a-predefined-number/</guid>
				<description>Explains how to use the TFS 2010 API to set the starting Work Item ID by programmatically creating and deleting items, avoiding ID conflicts with other systems.</description>
			</item>
			<item>
				<title>Team Foundation Server 2010 Event Handling with Subscribers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2010-event-handling-with-subscribers/</link>
				<pubDate>Thu, 16 Sep 2010 14:28:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2010-event-handling-with-subscribers/</guid>
				<description>Explains how to create and deploy server-side event subscribers in Team Foundation Server 2010 using the ISubscriber interface to handle and process TFS events.</description>
			</item>
			<item>
				<title>Active Directory Groups not Syncing with Team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/active-directory-groups-not-syncing-with-team-foundation-server-2010/</link>
				<pubDate>Wed, 07 Jul 2010 23:02:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/active-directory-groups-not-syncing-with-team-foundation-server-2010/</guid>
				<description>Explains why Active Directory groups may not sync with Team Foundation Server 2010, how to diagnose sync issues, and steps to resolve identity synchronisation problems.</description>
			</item>
			<item>
				<title>TFS Event Handler for Team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-for-team-foundation-server-2010/</link>
				<pubDate>Wed, 07 Jul 2010 11:20:44 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-for-team-foundation-server-2010/</guid>
				<description>Explains how to create and customise event handlers for Team Foundation Server 2010, covering supported events for version control, builds, work items, and test management.</description>
			</item>
			<item>
				<title>Changing the Team Project Collection of the Team Build Controller</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/changing-the-team-project-collection-of-the-team-build-controller/</link>
				<pubDate>Mon, 05 Jul 2010 16:57:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/changing-the-team-project-collection-of-the-team-build-controller/</guid>
				<description>Explains how to reconfigure a Team Build Controller in TFS 2010 to connect to a different Team Project Collection using the Administration Console and Build Service settings.</description>
			</item>
			<item>
				<title>Upgrading Team Foundation Server 2008 to 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-team-foundation-server-2008-to-2010/</link>
				<pubDate>Mon, 03 May 2010 13:04:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-team-foundation-server-2008-to-2010/</guid>
				<description>Step-by-step guide to upgrading Team Foundation Server 2008 to 2010, covering database backup, migration, verification, compatibility, and post-upgrade testing.</description>
			</item>
			<item>
				<title>Combining Scrum, TFS2010 and Email to keep everyone in the loop</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/combining-scrum-tfs2010-and-email-to-keep-everyone-in-the-loop/</link>
				<pubDate>Wed, 28 Apr 2010 16:21:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/combining-scrum-tfs2010-and-email-to-keep-everyone-in-the-loop/</guid>
				<description>Explains how to integrate Scrum, TFS 2010, and email to share task details, maintain history, and keep all stakeholders informed throughout project workflows.</description>
			</item>
			<item>
				<title>Upgrading from TFS 2010 RC to TFS 2010 RTM done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2010-rc-to-tfs-2010-rtm-done/</link>
				<pubDate>Mon, 12 Apr 2010 19:39:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2010-rc-to-tfs-2010-rtm-done/</guid>
				<description>Step-by-step guide to upgrading from TFS 2010 RC to RTM, including backup, uninstall, install, configuration, SharePoint and build server updates, and post-upgrade testing.</description>
			</item>
			<item>
				<title>Scrum for Team Foundation Server 2010</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-for-team-foundation-server-2010/</link>
				<pubDate>Fri, 09 Apr 2010 11:42:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/scrum-for-team-foundation-server-2010/</guid>
				<description>Learn how to implement Scrum practices using Team Foundation Server 2010 and Visual Studio ALM, including project planning, backlog management, and progress tracking.</description>
			</item>
			<item>
				<title>Solution - SEO permanent redirects for old URL’s?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/</link>
				<pubDate>Mon, 04 Jan 2010 02:34:55 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/</guid>
				<description>Explains how to set up SEO-friendly permanent redirects for old URLs to new ones in ASP.NET, covering best practices and code examples for preserving search rankings.</description>
			</item>
			<item>
				<title>Wpf Ninject Dojo: The Data Provider</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/wpf-ninject-dojo-the-data-provider/</link>
				<pubDate>Tue, 25 Aug 2009 14:43:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/wpf-ninject-dojo-the-data-provider/</guid>
				<description>Explains how to use a custom NinjectDataProvider in WPF to enable dependency injection for ViewModels, improving flexibility and design-time support in MVVM projects.</description>
			</item>
			<item>
				<title>Creating a Data Access layer using Unity</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-data-access-layer-using-unity/</link>
				<pubDate>Thu, 30 Jul 2009 04:57:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-data-access-layer-using-unity/</guid>
				<description>Learn how to build a flexible data access layer in .NET using Unity for dependency injection, interface mapping, and factory patterns with configuration support.</description>
			</item>
			<item>
				<title>My.Unity.Resolve(Of Ninja)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/my-unity-resolve-of-ninja/</link>
				<pubDate>Fri, 08 May 2009 14:17:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/my-unity-resolve-of-ninja/</guid>
				<description>Shows how to create a shared UnityContainer singleton in VB.NET using the “My” namespace, enabling dependency injection across WPF and ASP.NET applications.</description>
			</item>
			<item>
				<title>Reformat your CSS on the fly</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/reformat-your-css-on-the-fly/</link>
				<pubDate>Tue, 27 Jan 2009 16:50:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/reformat-your-css-on-the-fly/</guid>
				<description>Learn how to use a .NET HTTP handler to dynamically adjust CSS file paths, ensuring images and resources load correctly across different web application locations.</description>
			</item>
			<item>
				<title>Retrieving an identity from Team Foundation Server using only the display name</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/retrieving-an-identity-from-team-foundation-server-using-only-the-display-name/</link>
				<pubDate>Mon, 01 Dec 2008 17:30:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/retrieving-an-identity-from-team-foundation-server-using-only-the-display-name/</guid>
				<description>Explains how to retrieve a user or group identity from Team Foundation Server using only a display name, including handling Active Directory lookups and group assignments.</description>
			</item>
			<item>
				<title>Advice on using XamRibbon with Composite WPF</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/advice-on-using-xamribbon-with-composite-wpf/</link>
				<pubDate>Wed, 19 Nov 2008 17:03:42 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/advice-on-using-xamribbon-with-composite-wpf/</guid>
				<description>Provides guidance and code examples for integrating Infragistics XamRibbon with Composite WPF, including custom region adapters for dynamic tab and menu management.</description>
			</item>
			<item>
				<title>Sync extension for Lists/Collections or whatever</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sync-extension-for-lists-collections-or-whatever/</link>
				<pubDate>Mon, 13 Oct 2008 14:11:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sync-extension-for-lists-collections-or-whatever/</guid>
				<description>Explains how to synchronise two .NET collections by applying differences, with thread safety using locks, ensuring target lists match source lists efficiently.</description>
			</item>
			<item>
				<title>Creating a WPF Work Item Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wpf-work-item-control/</link>
				<pubDate>Fri, 19 Sep 2008 12:14:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wpf-work-item-control/</guid>
				<description>Learn how to build a custom WPF work item control for Visual Studio Team System, enabling WPF UI integration in work item forms using a generic wrapper and IWorkItemControl.</description>
			</item>
			<item>
				<title>IHandlerFactory</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/ihandlerfactory/</link>
				<pubDate>Tue, 05 Aug 2008 10:11:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/ihandlerfactory/</guid>
				<description>Explains how to use a custom IHttpHandler and handler factory in ASP.NET to redirect old URLs to a new site, preserving links and SEO with permanent redirects.</description>
			</item>
			<item>
				<title>TFS Event Handler in .NET 3.5 Part 2 - Handling Team Foundation Server Events</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-2-handling-team-foundation-server-events/</link>
				<pubDate>Fri, 07 Sep 2007 08:08:57 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-2-handling-team-foundation-server-events/</guid>
				<description>Guide to implementing a resilient Team Foundation Server event handler in .NET 3.5 using WCF, including service contracts, endpoints, configuration, and event parsing.</description>
			</item>
			<item>
				<title>Creating a custom proxy class</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-proxy-class/</link>
				<pubDate>Mon, 20 Aug 2007 17:20:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-proxy-class/</guid>
				<description>Learn how to build a custom proxy class in .NET 3.0 for duplex communication, enabling maintainable code and easy updates when service interfaces change.</description>
			</item>
			<item>
				<title>Creating your own Event Handler</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-your-own-event-handler/</link>
				<pubDate>Mon, 18 Jun 2007 23:12:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-your-own-event-handler/</guid>
				<description>Learn how to create custom event handlers for Team Foundation Server by inheriting from AEventHandler, implementing IsValid and Run methods, and handling event data securely.</description>
			</item>
			<item>
				<title>TFS Gotcha (Exception Handling)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-gotcha-exception-handling/</link>
				<pubDate>Wed, 30 May 2007 09:55:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/tfs-gotcha-exception-handling/</guid>
				<description>Explains how to handle non-serialisable Team Foundation Server exceptions in WCF by creating custom serialisable exceptions for reliable cross-service error handling.</description>
			</item>
			<item>
				<title>Creating WCF Service Host Programmatically</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/creating-wcf-service-host-programmatically/</link>
				<pubDate>Wed, 30 May 2007 00:23:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/creating-wcf-service-host-programmatically/</guid>
				<description>Explains how to programmatically create and configure a WCF Service Host in .NET, including base addresses, endpoints, bindings, and service behaviours for secure hosting.</description>
			</item>
			<item>
				<title>Adding ToolStripPanel UI Adapter Support to the Composite UI Application Block</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/adding-toolstrippanel-ui-adapter-support-to-the-composite-ui-application-block/</link>
				<pubDate>Thu, 22 Jun 2006 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/adding-toolstrippanel-ui-adapter-support-to-the-composite-ui-application-block/</guid>
				<description>Explains how to extend the Composite UI Application Block to support ToolStripPanel UI adapters, enabling dynamic ToolStrip integration and customisation in CAB applications.</description>
			</item>
			<item>
				<title>Calling an object method in a data trigger</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/calling-an-object-method-in-a-data-trigger/</link>
				<pubDate>Wed, 27 Aug 2008 11:16:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/calling-an-object-method-in-a-data-trigger/</guid>
				<description>Explains how to call an object method in a WPF DataTrigger, the limitations with extension methods, and common errors when binding methods in XAML templates.</description>
			</item>
			<item>
				<title>Installing Release Management Client for Visual Studio 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/installing-release-management-client-for-visual-studio-2013/</link>
				<pubDate>Fri, 10 Jan 2014 10:35:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/installing-release-management-client-for-visual-studio-2013/</guid>
				<description>Step-by-step guide to downloading, installing, and configuring the Release Management Client for Visual Studio 2013, including setup tips and troubleshooting advice.</description>
			</item>
			<item>
				<title>Agentic Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-engineering/</link>
				<pubDate>Tue, 22 Jul 2025 15:58:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-engineering/</guid>
				<description>Agentic Engineering is the deliberate design and practice of software development that maximises the agency of both humans and intelligent systems. It integrates engineering excellence, DevOps ethos, and ethical autonomy to create environments where decisions are decentralised, feedback is fast, and value delivery is continuous. It&amp;rsquo;s characterised by Developer Agency, Systemic Observability, DevOps-Infused Craft, Ethical AI Integration, and Feedback-Driven Adaptation. Agentic Engineering is not a job title, role, or method, it&amp;rsquo;s a philosophy of engineering in which the ability to act with clarity, intent, and impact is engineered into the way we build, learn, and evolve.</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>Site Reliability Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</guid>
				<description>Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks.</description>
			</item>
			<item>
				<title>Service Level Expectation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/service-level-expectation/</link>
				<pubDate>Mon, 05 May 2025 09:46:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/service-level-expectation/</guid>
				<description>A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team&amp;rsquo;s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team&amp;rsquo;s ability to deliver reliably and respond to change.</description>
			</item>
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>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>Lead Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/</guid>
				<description>Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments.</description>
			</item>
			<item>
				<title>Agnostic Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:49:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</guid>
				<description>Agnostic Agile is a movement that advocates for a flexible and context-driven approach to agility, emphasising the importance of principles over rigid frameworks. Originating from the need for adaptability in various methodologies, it encourages teams to tailor their practices based on specific requirements rather than conforming to a single ideology. This pragmatic approach allows practitioners to integrate diverse methodologies such as Scrum, Kanban, Lean, and Extreme Programming, fostering an environment that values critical thinking and professionalism. By prioritising value delivery, Agnostic Agile equips teams to respond effectively to evolving circumstances, ensuring predictable and sustainable value generation. This adaptability is essential in today&amp;rsquo;s dynamic environments, where the capacity to pivot and innovate can significantly influence an organisation&amp;rsquo;s success. Furthermore, Agnostic Agile promotes ethical practices by avoiding brand loyalty to specific frameworks, thereby nurturing a culture of continuous improvement and learning. This mindset empowers teams to experiment and refine their processes, ultimately supporting a long-term, systemic approach to agility that enhances organisational resilience and effectiveness. As such, Agnostic Agile is a crucial concept in contemporary product development and delivery, providing valuable insights for teams striving to thrive in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Current Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</guid>
				<description>Current Value is a vital metric within Evidence-Based Management that quantifies the real-time value a product or service provides to its users. It includes various indicators such as customer satisfaction, revenue impact, and performance feedback, which together offer insights into the value being realised at any moment. This concept is crucial for teams striving to deliver value in a predictable and sustainable manner, as it facilitates continuous assessment and adjustment based on actual performance rather than assumptions. By tracking Current Value, organisations can make data-driven decisions that improve their offerings and better align them with customer needs. This ongoing evaluation promotes a culture of responsiveness and adaptability, allowing teams to swiftly adjust to feedback and shifting market conditions. Unlike static measures, Current Value is dynamic and systemic, reflecting the changing landscape of customer expectations and business environments. It empowers teams to concentrate on delivering meaningful outcomes, ensuring that their efforts lead to long-term success and customer loyalty. This emphasis on real-time value delivery distinguishes Current Value from other concepts such as Value Stream Management or Customer Satisfaction, which may not fully capture the immediacy and comprehensive nature of the value being generated.</description>
			</item>
			<item>
				<title>Time to Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/time-to-market/</link>
				<pubDate>Thu, 10 Apr 2025 14:20:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/time-to-market/</guid>
				<description>Time to Market is a critical metric that evaluates how quickly an organisation can transform ideas into market-ready products or features, incorporating various measures such as lead time and cycle time to provide a comprehensive understanding of product development efficiency. This concept is essential for organisations striving to deliver value in a predictable and sustainable manner, as a shorter Time to Market allows teams to swiftly address customer needs and adapt to market fluctuations. By prioritising Time to Market, organisations can gain a competitive advantage, ensuring that their innovations reach customers ahead of competitors. This focus on agility promotes a culture of continuous improvement, encouraging teams to refine processes and eliminate inefficiencies. The systemic nature of Time to Market impacts not only individual projects but also the overall organisational capacity for innovation and adaptability. It aligns with Lean and Agile methodologies, fostering a mindset that prioritises speed while maintaining quality. Ultimately, a strong commitment to Time to Market nurtures an environment where delivering value becomes a core organisational principle, contributing to long-term success and resilience in an ever-evolving marketplace.</description>
			</item>
			<item>
				<title>Hybrid Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/hybrid-agile/</link>
				<pubDate>Thu, 10 Apr 2025 10:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/hybrid-agile/</guid>
				<description>Hybrid Agile refers to the practice of integrating agile methodologies into existing project management frameworks, often with the aim of achieving greater flexibility while maintaining a sense of control. This approach is commonly adopted by organisations that seek to enhance their project delivery processes but frequently results in ineffective outcomes. Instead of successfully merging the advantages of agile practices with traditional governance structures, Hybrid Agile often leads to a scenario where the rigidity of conventional methods undermines the intended agility, creating a situation described as the &amp;ldquo;worst of both worlds.&amp;rdquo; This concept highlights the challenges faced by delivery teams that encounter conflicting expectations, as leadership may cling to fixed plans while reducing agile roles to mere ceremonial functions rather than fostering genuine accountability. The persistence of command-and-control mindsets, coupled with the superficial adoption of agile terminology, creates a disconnect between the intended agile principles and the actual organisational structure. As such, Hybrid Agile is not a sustainable long-term solution; it can erode trust, hinder timely feedback, and perpetuate dysfunction within teams. This analysis serves to critique ineffective hybrid implementations and underscores the necessity for coherent systems of work that prioritise true agility over tactical compromises.</description>
			</item>
			<item>
				<title>GitHub</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/github/</link>
				<pubDate>Thu, 10 Apr 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/github/</guid>
				<description>GitHub is a comprehensive platform that facilitates version control, collaboration, and integration within software development. Originating as a hosting service for Git repositories, it has evolved to include features such as GitHub Actions for automating continuous integration and continuous delivery workflows, and GitHub Projects for task management and progress tracking. Its significance lies in its ability to enhance collaboration among development teams, reduce friction in development cycles, and support the efficient delivery of value. GitHub is essential for organisations seeking to maintain transparency and integrate workflows between development and operations teams, as its integration with CI/CD practices allows for the automation of testing, builds, and deployments, ensuring continuous validation and delivery of code changes. The platform&amp;rsquo;s features, including issues, pull requests, and discussions, foster effective communication and alignment on project goals. Additionally, GitHub&amp;rsquo;s compatibility with a variety of third-party tools and services further amplifies its effectiveness in modern DevOps environments. By utilising GitHub&amp;rsquo;s extensive toolset, organisations can enhance team collaboration, streamline development processes, and improve software delivery outcomes.</description>
			</item>
			<item>
				<title>Throughput</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/throughput/</link>
				<pubDate>Wed, 09 Apr 2025 14:41:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/throughput/</guid>
				<description>Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance.</description>
			</item>
			<item>
				<title>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>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>Tool</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/tool/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/tool/</guid>
				<description>A tool is a mechanism, technique, or software that assists teams in effectively implementing methods and practices within Agile, Lean, and DevOps environments. These tools are crucial for supporting collaboration, managing workflows, and fostering continuous improvement, as they enable teams to visualise and track progress, manage backlogs, and align with product goals. For instance, project management tools like JIRA and Azure Boards facilitate Agile practices by allowing teams to iterate and adapt to feedback. In DevOps, tools such as Jenkins and GitLab automate processes like Continuous Integration and Continuous Delivery, enhancing delivery speed and reliability while reducing human error. However, tools are not standalone solutions; they must be integrated into a broader organisational framework and aligned with defined methodologies. While they can enhance efficiency and provide visibility into workflows, tools cannot address organisational dysfunctions or improve processes without a solid methodological foundation. Therefore, tools should be viewed as enablers that support well-defined practices rather than replacements for strong methods or frameworks. Ultimately, the effective use of tools can significantly improve team performance and adaptability in complex environments, making them valuable assets in product development and organisational design.</description>
			</item>
			<item>
				<title>System Configuration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/system-configuration/</link>
				<pubDate>Wed, 09 Apr 2025 13:08:13 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/system-configuration/</guid>
				<description>System Configuration encompasses the technical setup and optimisation of software, hardware, and systems to ensure efficient and reliable operation. It is essential in Agile and DevOps environments, where the need for speed, efficiency, and flexibility is critical. This process establishes a robust foundation for operational performance, allowing teams to deliver high-quality products in a predictable and sustainable manner. Central to System Configuration are tools that automate and manage the integration of system components, such as Ansible, Chef, Puppet, and Terraform, which facilitate infrastructure as code and ensure consistent configurations across various environments. By optimising hardware and software components to work seamlessly together, System Configuration minimises bottlenecks and supports continuous integration and continuous delivery by automating testing, deployment, and monitoring. Its importance lies in enhancing workflow efficiency, fostering collaboration among teams, and reducing time spent on manual tasks, thereby allowing teams to concentrate on innovation and value creation. Furthermore, effective System Configuration is crucial for scaling Agile practices within larger organisations, as it ensures that systems are properly configured from the beginning, leading to efficient scaling with minimal disruption. Ultimately, System Configuration provides the tools and processes necessary for organisations to improve performance, reduce operational overhead, and maintain adaptable and scalable systems in a rapidly evolving landscape.</description>
			</item>
			<item>
				<title>Test First Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/test-first-development/</link>
				<pubDate>Tue, 25 Mar 2025 07:40:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/test-first-development/</guid>
				<description>Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>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 Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/</link>
				<pubDate>Fri, 21 Mar 2025 13:37:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/</guid>
				<description>Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations.</description>
			</item>
			<item>
				<title>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>Shift Left Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/</link>
				<pubDate>Mon, 17 Mar 2025 14:46:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/</guid>
				<description>The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development.</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>Internal Developer Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/</link>
				<pubDate>Mon, 24 Feb 2025 13:04:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/</guid>
				<description>An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery.</description>
			</item>
			<item>
				<title>Acceptance Test Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/</guid>
				<description>Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users.</description>
			</item>
			<item>
				<title>Agile 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 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 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>Automated Testing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/automated-testing/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/automated-testing/</guid>
				<description>Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment.</description>
			</item>
			<item>
				<title>Azure Boards</title>
				<link>https://engineering-leadership-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>Azure Pipelines</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-pipelines/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-pipelines/</guid>
				<description>Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements.</description>
			</item>
			<item>
				<title>Azure Repos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/</guid>
				<description>Azure Repos is a cloud-based source control service within the Azure DevOps ecosystem, designed to help teams manage their code repositories efficiently. It supports both Git and Team Foundation Version Control (TFVC), allowing teams to select the version control system that aligns with their specific workflows. By providing a centralised platform for code collaboration, Azure Repos integrates seamlessly with other Azure DevOps services, such as Azure Pipelines and Azure Boards, thereby enhancing the overall development lifecycle. Its significance lies in its ability to promote collaboration among team members, enabling concurrent work on code while minimising conflicts, which is essential for delivering value in a predictable and sustainable manner. Features like pull requests, branch policies, and code reviews help maintain code quality while facilitating rapid iteration and innovation. Additionally, Azure Repos fosters a culture of transparency and accountability by tracking changes and maintaining a clear history of contributions. This systemic approach to source control streamlines development processes and aligns with agile principles, promoting adaptability and responsiveness to change. By integrating with various tools and practices, Azure Repos empowers teams to focus on delivering high-quality software that effectively meets customer needs.</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>Continuous Integration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/</guid>
				<description>Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development.</description>
			</item>
			<item>
				<title>Cross Functional Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/</guid>
				<description>Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise.</description>
			</item>
			<item>
				<title>Cycle Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/</guid>
				<description>Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success.</description>
			</item>
			<item>
				<title>Daily Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
			<item>
				<title>Definition of Ready</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-ready/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-ready/</guid>
				<description>Definition of Ready (DoR) is a concept within the Scrum framework that outlines the criteria necessary for a Backlog Item to be considered ready for implementation by the development team. It emerges from the collaborative understanding among Developers, the Product Owner, and Stakeholders regarding what is required to proceed with a Backlog Item. The importance of DoR lies in its potential to enhance clarity and alignment within agile teams, yet it also presents challenges, such as creating a false sense of readiness, neglecting the need for ongoing refinement, and leading to misconceptions about its equivalence with the Definition of Done (DoD). Unlike the DoD, which is an absolute measure of completion, the subjective nature of DoR can result in partial implementation, risking the integrity of the development process. To mitigate these issues, it is suggested that teams adopt a more nuanced approach to defining readiness, ensuring that each Backlog Item meets specific criteria, such as having a clear outcome, hypothesis, and telemetry for evaluation. The INVEST criteria further guide the formulation of Product Backlog Items, emphasising their independence, negotiability, value, estimability, size, and testability. Ultimately, a well-defined DoR fosters effective communication and understanding within agile teams, contributing to successful product development and organisational design.</description>
			</item>
			<item>
				<title>Deployment Frequency</title>
				<link>https://engineering-leadership-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>Engineering Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/engineering-excellence/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/engineering-excellence/</guid>
				<description>Engineering excellence is a critical framework for achieving high-quality, maintainable, and scalable software systems, emphasising a culture of continuous improvement and technical rigor. Originating from the need for organisations to enhance their engineering standards, this approach focuses on delivering predictable, resilient, and valuable software. Its importance lies in several key areas: ensuring quality by driving consistency and reliability, reducing risk through early issue identification, enhancing scalability for long-term growth, improving efficiency in development processes, and strengthening collaboration among teams. Core principles of engineering excellence include software craftsmanship, which prioritises clarity and adaptability; modern software engineering practices that promote continuous validation and automation; proactive technical debt management to maintain code health; metrics and observability for data-driven improvements; and embedding security and compliance into development processes. Additionally, it advocates for scalable and resilient architecture to support sustainable evolution in response to changing demands. By adopting these principles, organisations can foster an environment that not only meets current software needs but also adapts to future challenges, ultimately driving success in agile, DevOps, and product development contexts.</description>
			</item>
			<item>
				<title>Engineering Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/engineering-practices/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/engineering-practices/</guid>
				<description>Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software&amp;rsquo;s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance.</description>
			</item>
			<item>
				<title>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>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>Modern Source Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/modern-source-control/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/modern-source-control/</guid>
				<description>Modern source control is a critical practice in software development that focuses on version control and branching strategies to manage codebase changes effectively. Originating from the need for collaborative coding, it utilises systems like Git to allow multiple developers to work simultaneously without conflicts, while also enabling the tracking of modifications, reverting to previous states, and maintaining a comprehensive development history. This practice is vital as it enhances a team&amp;rsquo;s ability to deliver value in a predictable and sustainable manner, facilitating the implementation of continuous integration and continuous delivery (CI/CD) pipelines that promote rapid feedback and reduced lead times. Such agility empowers organisations to swiftly adapt to market demands and customer feedback, fostering innovation. Additionally, modern source control encourages a systematic approach to development through branching strategies, such as feature branches or trunk-based development, which support parallel workstreams and minimise disruptions to the main codebase. This not only improves collaboration but also helps in managing technical debt by allowing teams to isolate and resolve issues more efficiently. By integrating these practices into their workflows, organisations can cultivate a resilient development environment that prioritises quality and efficiency, ultimately contributing to long-term success in product delivery.</description>
			</item>
			<item>
				<title>Release Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/release-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/release-management/</guid>
				<description>Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty.</description>
			</item>
			<item>
				<title>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>Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/software-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/software-development/</guid>
				<description>Software Development refers to the systematic techniques and methodologies used to create high-quality software solutions that align with user needs and business objectives. Originating from various practices such as Agile, Lean, and DevOps, it aims to improve collaboration, efficiency, and adaptability within development teams. This approach is vital as it allows organisations to deliver value in a predictable and sustainable manner, fostering a culture of continuous improvement and responsiveness to change. By emphasising iterative development, teams can swiftly adapt to feedback and changing requirements, ensuring the software remains relevant and effective. Additionally, the focus on automation, testing, and integration mitigates the risk of defects and accelerates delivery cycles, leading to more frequent releases and increased customer satisfaction. Software Development also encourages a comprehensive view of the software lifecycle, promoting cross-functional collaboration and knowledge sharing among team members. This long-term, systemic approach not only enhances software quality but also nurtures an innovative environment, enabling organisations to stay competitive in a fast-evolving market. The incorporation of evidence-based management principles further aids informed decision-making, equipping teams to effectively navigate complexity and uncertainty. By prioritising these practices, organisations can secure a sustainable competitive advantage through improved software development capabilities that align with their strategic goals and customer expectations.</description>
			</item>
			<item>
				<title>Technical Debt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/technical-debt/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/technical-debt/</guid>
				<description>Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape.</description>
			</item>
			<item>
				<title>Technical Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/technical-mastery/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/technical-mastery/</guid>
				<description>Technical Mastery is the pursuit of excellence in software craftsmanship, architecture, and engineering practices, characterised by a profound understanding of relevant technologies, methodologies, and tools. It is essential for teams aiming to deliver high-quality products efficiently and sustainably, as it directly influences their ability to provide predictable value. By fostering Technical Mastery, organisations enable their teams to confidently address complex challenges, ensuring that solutions are both effective and maintainable over time. This focus on quality and skill development not only reduces technical debt but also enhances collaboration and responsiveness to market changes. Furthermore, Technical Mastery aligns with the principles of Agile and DevOps by encouraging a shared understanding of best practices and nurturing a culture of experimentation and learning. It facilitates the implementation of robust engineering practices, such as automated testing and continuous integration, which are vital for maintaining a consistent flow of value delivery. As teams refine their skills, they can better align their efforts with organisational objectives, ultimately contributing to greater success and resilience in a rapidly changing environment.</description>
			</item>
			<item>
				<title>Test Automation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/</guid>
				<description>Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements.</description>
			</item>
			<item>
				<title>Test Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/test-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/test-driven-development/</guid>
				<description>Test Driven Development (TDD) is a software development methodology that prioritises the creation of automated tests prior to writing the actual code. Originating from the need for a structured approach to software design, TDD ensures that development is guided by the requirements specified in the tests, which clarifies the intended functionality of the software. This practice is crucial in the context of Agile and DevOps as it promotes a culture of quality and accountability, allowing teams to deliver consistent and sustainable value. By embedding testing into the development lifecycle from the beginning, TDD significantly reduces the risk of defects and simplifies the process of refactoring, with tests acting as a safety net. The long-term advantages of TDD extend beyond immediate improvements in code quality; it fosters a mindset of continuous improvement and adaptability among team members. This approach aligns seamlessly with Agile principles, enhancing collaboration and responsiveness to change while supporting technical excellence. By focusing on test coverage, teams can confidently introduce new features and enhancements, ensuring that existing functionalities remain intact. Ultimately, TDD not only improves individual projects but also cultivates a culture of reliability and trust within the organisation, leading to better outcomes for stakeholders and customers.</description>
			</item>
			<item>
				<title>Working Software</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/working-software/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/working-software/</guid>
				<description>Working Software is a fundamental artifact in Agile, Scrum, and Lean frameworks, serving as the tangible output of a team&amp;rsquo;s efforts throughout the development process. It emerges from iterative development cycles and acts as a demonstration of progress and value delivery. In Scrum, working software is the primary success metric for each Sprint, encapsulated in the Increment artifact, which is subject to inspection and adaptation based on stakeholder feedback. The Definition of Done ensures that the software meets established quality criteria, making it valuable and ready for release. The importance of working software lies in its ability to provide a concrete measure of progress, aligning teams and stakeholders around completed work and remaining tasks. It transcends mere code, representing deliverables that address real-world needs and customer expectations, thereby maintaining a focus on value delivery. In agile methodologies, the emphasis on working software fosters continuous feedback and improvement, enabling teams to release increments iteratively and adapt to evolving requirements. This focus enhances collaboration, increases transparency, and drives ongoing improvement within organisations. Ultimately, working software is not solely about technical execution; it is about consistently delivering value, responding to customer needs, and ensuring long-term sustainability, thereby contributing to customer satisfaction, innovation, and overall business success.</description>
			</item>
			<item>
				<title>Application Lifecycle Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/</guid>
				<description>Application Lifecycle Management (ALM) is the systematic approach to managing software applications throughout their entire lifecycle, from initial development to eventual retirement. Originating from the need for structured processes in software development, ALM integrates various practices, tools, and team collaboration to streamline workflows and enhance communication. Its importance lies in its ability to provide organisations with a comprehensive view of application development, aligning technical efforts with business goals while remaining adaptable to evolving requirements. By implementing methodologies such as continuous integration and continuous delivery, ALM fosters rapid feedback and iterative enhancements, which are critical in dynamic environments. This approach not only reduces deployment risks but also cultivates a culture of accountability and transparency within teams. Furthermore, ALM aids organisations in effectively managing their application portfolios, ensuring optimal resource allocation and proactive technical debt management. This long-term focus is essential for driving innovation and maintaining a competitive edge, as it allows teams to concentrate on delivering high-quality software that satisfies user demands and contributes to overall business success. The synergy between ALM and frameworks like Agile and DevOps amplifies its impact, establishing a solid foundation for ongoing improvement and value creation.</description>
			</item>
			<item>
				<title>Azure DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/</guid>
				<description>Azure DevOps is a comprehensive suite of tools developed by Microsoft that supports continuous integration and continuous delivery (CI/CD), enhances collaboration, and streamlines agile project management. It encompasses various functionalities, including Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for automating builds and deployments, and Azure Test Plans for managing testing efforts. This platform is crucial for organisations seeking to deliver value in a predictable and sustainable manner, as it promotes a culture of collaboration and transparency among teams. By providing a unified environment for development and operations, Azure DevOps facilitates the adoption of best practices in agile methodologies and DevOps principles, ensuring efficient software delivery that is responsive to evolving business needs. Its systemic approach encourages continuous improvement and learning, enabling organisations to swiftly adapt to market demands while upholding high-quality standards. The integration of tools within Azure DevOps mitigates silos, enhances communication, and fosters a shared understanding of project objectives, ultimately leading to improved outcomes and a culture of innovation. This capability is vital for organisations aiming to achieve operational excellence and maintain a competitive advantage in a fast-changing landscape.</description>
			</item>
			<item>
				<title>Install and Configuration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/install-and-configuration/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/install-and-configuration/</guid>
				<description>Install and Configuration encompasses the critical processes necessary for setting up and optimising tools, software, and platforms that underpin agile, lean, and DevOps methodologies. Originating from the need to establish efficient operational frameworks, this concept is vital for ensuring that teams have the appropriate systems in place to enhance collaboration, communication, and the continuous delivery of value. By prioritising proper installation and configuration, organisations can significantly reduce disruptions and technical debt, enabling teams to focus on producing high-quality products. This proactive strategy not only facilitates predictable and sustainable value delivery but also supports the creation of well-configured environments that align with team workflows and methodologies. Furthermore, effective practices in installation and configuration lead to long-term systemic improvements, fostering adaptability to changing requirements and promoting continuous innovation. This approach transcends mere technical setup; it reflects a strategic mindset that aligns tools with organisational objectives, ultimately boosting overall performance and agility. The capacity to swiftly adjust systems in response to feedback and evolving needs is a defining characteristic of high-performing teams, enhancing both efficiency and effectiveness in product development.</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>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>Platform Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/</guid>
				<description>Platform Engineering is the discipline focused on the design, construction, and maintenance of internal platforms that empower developers to deliver value independently, reliably, and swiftly. Originating from the need to streamline software development processes, it aims to alleviate cognitive load by abstracting the complexities of infrastructure and operations through well-crafted interfaces, tools, and APIs. This approach treats platforms as products, ensuring clear ownership, regular feedback, and ongoing enhancements based on developer requirements. A robust platform engineering capability fosters paved paths and self-service tools that facilitate secure, observable, and resilient software delivery while avoiding constraints that stifle innovation. By creating an environment conducive to rapid feedback, safe experimentation, and autonomous delivery across teams, Platform Engineering not only provides essential tools but also cultivates a cohesive developer experience that aligns with organisational strategy, ultimately enabling continuous value delivery at scale.</description>
			</item>
			<item>
				<title>Product Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/</guid>
				<description>Product Delivery refers to the comprehensive process of delivering functional software products to customers, integrating various stages such as planning, development, testing, and deployment into a unified workflow. Originating from methodologies like Agile, Lean, and DevOps, this approach is essential for organisations aiming to deliver consistent value in a predictable and sustainable manner, ensuring that products align with customer needs and expectations. By emphasising an end-to-end delivery process, Product Delivery enhances collaboration among cross-functional teams, streamlines workflows, and reduces cycle times. It fosters a culture of continuous improvement and adaptability, driven by feedback loops that allow teams to respond swiftly to customer insights and market changes. This systemic approach not only improves product quality but also establishes a resilient organisational framework conducive to long-term success. Prioritising Product Delivery cultivates an environment where innovation flourishes and team ownership is encouraged, leading to increased employee engagement and satisfaction. Ultimately, this focus on delivering value through a structured process is vital for maintaining competitiveness and responsiveness in a rapidly changing landscape, positioning Product Delivery as a cornerstone of contemporary product development.</description>
			</item>
			<item>
				<title>Technical Excellence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/technical-excellence/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/technical-excellence/</guid>
				<description>Technical Excellence encompasses the quality of engineering practices that facilitate high-quality software delivery, enhanced agility, and ongoing improvement within development teams. Originating from methodologies that prioritise best practices, it empowers teams to create maintainable, scalable, and resilient software. In the context of Agile, Technical Excellence is vital as it allows teams to swiftly adapt to changing requirements and market demands while ensuring product quality and sustainability. Key practices such as Test-Driven Development (TDD) and Continuous Integration and Continuous Delivery (CI/CD) play a significant role in maintaining high standards by automating testing and deployment processes, thus enabling more frequent and reliable software releases. Additionally, modular architecture supports scalability and responsiveness to new requirements, while emergent design principles promote flexibility in adapting software designs as understanding evolves. By fostering a culture of continuous improvement, Technical Excellence encourages teams to regularly evaluate and refine their practices, ensuring they can maintain quality and responsiveness to change. Embedding this capability within an organisation&amp;rsquo;s culture not only addresses immediate customer needs but also establishes a sustainable foundation for long-term success, allowing organisations to consistently deliver high-quality software while remaining adaptable and efficient in their development processes.</description>
			</item>
			<item>
				<title>Value Delivery</title>
				<link>https://engineering-leadership-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>Agentic Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/</link>
				<pubDate>Tue, 21 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/</guid>
				<description>Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation&amp;rsquo;s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term &amp;lsquo;agentic&amp;rsquo; implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</guid>
				<description>Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.</description>
			</item>
	</channel>
</rss>
