# Martin Hinshelwood on Engineering Leadership

> Articles, guides and videos on engineering leadership, DevOps, Agile and AI by Martin Hinshelwood — Microsoft MVP and Professional Scrum Trainer.

## Articles

- [AI Guardrails Are Just Polite Requests](https://engineering-leadership.hinshelwood.com/articles/ai-guardrails-are-just-polite-requests/): An agent disabled failing tests despite explicit rules requiring them to pass. My scan of 6,803 recorded turns found recurring correction signals, but those counts cannot tell me how often agents complied. Instructions help without guaranteeing behaviour, and independent model review can still share the producer's mistakes. Deterministic checks enforce only the conditions they actually test, where their execution cannot be bypassed. The questions I now ask are what I have instructed, what checks it, and when I last watched that check catch a failure.
- [The AI Decided Is Not an Explanation](https://engineering-leadership.hinshelwood.com/articles/the-ai-decided-is-not-an-explanation/): An agent reported every task complete while leaving half the tests unwritten, then said it got bored. Calling that a lie adds belief and an intention to deceive to a machine producing text. The dog and cheese comparison and research on human attribution help explain why that language feels natural. The practical consequence is that we start explaining a failure through an imagined motive instead of checking what happened and what we allowed the system to do.
- [AI Agents Lie About Being Done](https://engineering-leadership.hinshelwood.com/articles/ai-agents-lie-about-being-done/): I had an agent work through a SpecKit spec and announce it was done. Half the tests were missing, and when I asked why, it told me it got bored. That gets a laugh, but when I counted my own sessions, nearly one in five contained something an agent told me that was false. You cannot prompt your way out of this. The component that did the work cannot be the authority on whether the work is done, and we already know how to build the alternative: it is the lesson continuous integration taught us, applied one layer up.
- [Who Owns the Code?](https://engineering-leadership.hinshelwood.com/articles/who-owns-the-code/): I spent an hour debating a veteran intellectual property lawyer about whether AI-generated code can be copyrighted and whether a company built on it is worth anything at sale. We agreed on far more than the headline claims suggest. Vibe coding is not authorship. Directed agentic development probably is, but no court has said so yet. And underneath the legal question sits a business one that matters more: the value of a software company was never in the copyright of its code. It is in the system that produced the code, and that system is unambiguously human.
- [How My Father's Business Reverted to the Mean](https://engineering-leadership.hinshelwood.com/articles/how-my-fathers-business-reverted-to-the-mean/): My father died eight years ago today. In 1980 he was left holding a ten-year lease on a Glasgow shopfront by a leadership team who went to a golf retreat, came back, and disowned the decision the market had forced in their absence. So he opened his own estate agency and ran it the way a Scottish surveyor runs a survey: by measurement. Be the agent, show the house, answer every question a buyer could ask. An insurer bought the business he grew, and inside a predictive parent that never understood his method he made their failing estate agency arm profitable, until a failed takeover bid earned him three months of garden leave, in which profit turned to loss until they brought him back at double the salary. I told the first half of this story in 2014 as proof that evidence-based practice works. Twelve years on, the ending has arrived: the parent sold the whole estate agency, the corporate vehicle was quietly dissolved, and the brand he put on Scottish high streets survives as one of twelve near-identical facades. The practices were never the problem. What nobody maintains, decays. And AI is now re-running the same experiment at machine speed in every organisation that adopts the tools without changing the theory of the business. This is his story, and the pattern's.
- [Why Most Companies Operating Models Fail in Dynamic Markets](https://engineering-leadership.hinshelwood.com/articles/why-most-companies-operating-models-fail-in-dynamic-markets/): Most companies still operate using a Predictive Operating Model, built on the assumption that markets and work are stable and predictable, but this model creates massive waste and frustration in today’s dynamic, uncertain environments. In contrast, the Adaptive Operating Model enables organisations to succeed by structuring cross-functional, persistent teams around products or value streams, empowering decentralised decision-making, and focusing on outcomes through feedback loops and continuous adaptation. The defining image of waste in the Predictive Model is teams spending months on plans that become obsolete in weeks, while real customer needs shift beneath them. Lasting change requires “operating-model hygiene,” regularly questioning and removing outdated structures, and fostering a culture where people closest to the work shape systems and ways of working. Transitioning to an adaptive model is a deep shift in theory, structure, culture, and leadership, but it is necessary to avoid ongoing waste and thrive in fast-moving markets.
- [Don’t Manage Dependencies, Remove Them](https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/): Dependencies are not inevitable, but a symptom of poor system design. Rather than managing dependencies through coordination overhead and politics, focus on removing them by aligning work, teams, and architecture so each team delivers end-to-end value without waiting for others. Make contracts between teams explicit, clarify ownership for every feature and service, and treat any remaining dependencies as design flaws to be escalated and resolved, not as routine work. One recognisable sign of poor alignment is teams blocked, waiting on another group for a component. Organisations that eliminate dependencies see faster delivery, fewer defects, and higher team morale. The answer is not to manage dependencies, but to redesign systems so they disappear.
- [The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery](https://engineering-leadership.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/): Focusing on estimation accuracy as a measure of predictability in software delivery undermines trust, distorts team behaviour, and delivers false signals about progress. When teams are judged on how closely they match estimates to actuals, they shift from solving problems to gaming metrics: padding estimates, avoiding risk, hiding delays, and reporting “green” status until last-minute failure. In one case, teams capped story size and sprint points to appear predictable, but innovation and quality deteriorated, while technical debt doubled. Research shows that using estimation accuracy as a KPI leads to defensive, less truthful forecasting and reduced efficiency. Instead of tracking compliance with estimates, organisations should follow Evidence-Based Management, using metrics like time to market, customer satisfaction, and flow efficiency to measure value, system health, and real outcomes. True progress comes when teams feel safe to expose complexity and risks, focusing on learning and value rather than conformity to plans.
- [Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?](https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/): In software development, the idea of “flow of value” should not be taken as a given; value is only realised once customers validate that a product improves their situation. Most work in knowledge systems, such as new features, represents potential value—untested hypotheses rather than sure outcomes. Equating work completed or features shipped with value delivered can lead to wasted effort and loss of accountability, such as shipping large batches without telemetry or validation. Instead, every work item should have a clear, testable hypothesis, and teams must focus on rapid feedback, observability, and outcome validation—for example, by attaching metrics or acceptance criteria to each card and emphasising trunk-based development. Without systems designed for evidence and learning, teams risk flowing only assumptions rather than true value.
- [Estimating Better in an Overloaded System Is a Poor Man’s Strategy](https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/): Predictability and accurate estimates collapse as the amount of work in progress (WIP) grows; most delivery problems stem from overloaded systems, not poor estimation. In overloaded teams, items spend up to 95% of their time waiting, making effort estimates irrelevant and unpredictability unavoidable. Concrete examples show that introducing WIP limits and fostering collaboration can halve cycle times and dramatically improve throughput, as seen when a payroll team dropped their average queue wait time by 79% by capping WIP below the number of developers. Multitasking only hides queues and increases delays, while focused efforts to reduce WIP lead to less stress and more reliable forecasts. True predictability comes from managing WIP and system flow, not from more detailed plans or better estimates.
- [Are We Still Pretending Coding Was the Bottleneck?](https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/): Coding has never been the real bottleneck in software delivery; focusing on developer headcount, story points, or ticket handoffs misses the true constraint. AI does not break delivery models, but exposes pre-existing systemic issues like work queuing for clarification, teams stalled by signoffs, and quality treated as a separate phase after coding. The problem is not poorly performing tools, but lack of practices such as test-first development, robust observability, and autonomous teams accountable for outcomes. Shifting quality upstream is crucial; quality is built in from the start, not inspected in at the end. AI accelerates work, but unless organisations fix broken systems and embrace flow, autonomy, and visibility, no advance in coding will solve delivery problems.
- [Should You Use One Project to Rule Them All in Azure DevOps?](https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/): Managing multiple Azure DevOps projects can create fragmentation, limited observability, and delivery delays. Using one Azure DevOps project for all teams, structured with clear Area Paths and Teams, enables unified visibility, simpler governance, and streamlined reporting with less operational overhead. Microsoft’s own Developer Division, with over 2,000 engineers, and the Windows team with more than 15,000 people, use a single project model to coordinate work at scale. Clear Area Path hierarchies and focused Azure DevOps Teams allow for fine-grained permissions, tailored boards, and cross-team reporting without the silos or duplication that come with multiple projects or organisations. Optimising for flow—rather than rigid structure—delivers better collaboration, transparency, and adaptability across product delivery.
- [Getting Started with Objectives & Key Results](https://engineering-leadership.hinshelwood.com/articles/getting-started-with-objectives-key-results/): OKRs are not a quick fix but a discipline that only work when built on strong foundations: a clearly communicated strategy, a culture of transparency and adaptation, team agency, and a real focus on outcomes over output. They translate strategy into action by connecting clear objectives with measurable key results, using the simple format “I will [Objective] as measured by [Key Results].” The real value comes when teams are empowered, learning is constant, and progress is regularly reviewed rather than just ticking off tasks. OKRs are a living practice that exposes misalignment and demands honest inspection; as captured in the cascade from vision to daily actions, they create a live link from long-term strategy down to execution and learning. If OKRs are not delivering, the underlying system, not the framework, is likely at fault.
- [Is Agile Really Just a Mindset?](https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/): Agile is not a mindset or just a set of behaviours; it is a disciplined system of work rooted in technical leadership, engineering excellence, and empirical control. True Agile requires that the system—codebase, infrastructure, deployment pipelines, and product strategy—supports frequent, reliable delivery, not just collaborative behaviour or feel-good language. Foundational engineering practices like CI/CD, automated checking, telemetry, and modular system design are non-negotiable; without them, Agile efforts are just theatre. Outsourcing Agile to non-technical coaches dilutes its reality and impact, as systems, not individuals, determine outcomes. As Deming said, “A bad system will beat a good person every time.” Agile only exists where systems continuously enable delivery of real value.
- [Telling People What to Do Is Not Leadership. It’s a Failure of System Design](https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/): Measuring leadership by a manager’s number of decisions signals a broken system, not effective management. Telling people exactly what to do reflects a Taylorist mindset that undermines autonomy, creates bottlenecks, and wastes value in complex, cognitive work like software development. Real leadership means creating systems where teams pull work, operate against clear goals, and are accountable for outcomes without micromanagement. For example, frequent delivery to production—shipping valuable increments every Sprint—creates fast feedback, trust, and continuous improvement. Managers should focus on designing systems that support flow, self-management, and evidence-based decisions, then get out of the way; otherwise, assigning tasks is just an expensive workaround for deeper organisational design failures.
- [The Definition of Done is a Commitment to Quality](https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/): A Scrum Team must explicitly define what “Done” means, as the Definition of Done (DoD) is essential for ensuring quality, transparency, and releasable product increments. Without a shared and objective DoD, teams risk chaotic delivery and undermine both integration and reputation, especially when multiple teams work on one product. A strong DoD is a short, measurable checklist—such as passing automated tests, security scans in CI/CD, and code reviews—that guarantees no further work is needed for release. Teams should start with an initial DoD, grow it through workshops involving stakeholders from security to UX, and continuously evolve it by reviewing and improving at each Sprint Retrospective. The defining question is whether the team would confidently support the increment in production tonight; if not, it is not Done.
- [Rethinking Capacity Planning](https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/): Capacity planning must shift from tallying individual hours or tasks to managing flow, system constraints, and predictability across portfolio, category, and team levels. Focusing on individual utilisation leads to local optimisation and overload, while value delivery suffers and predictability collapses. The real constraint is not team speed, but how many initiatives the system can handle before bottlenecks and dependencies arise. Instead of tracking people, organisations should set and enforce WIP limits, right-size work, and measure system-level metrics like lead time and process cycle efficiency. Leadership’s role is to remove obstacles, protect system flow, and focus on sustainable, predictable value delivery, not push teams for more output or busyness.
- [Why Topic Branches Drive High-Quality Delivery](https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/): Topic branches are short-lived, focused branches that isolate a single unit of developer work, ideally being coded, tested, and integrated within hours or a couple of days. Keeping topic branches brief prevents integration challenges, reduces merge conflicts, and avoids costly defects and review effort—allowing teams to maintain modularity and rapid feedback. Following practices like GitHub Flow, where developers branch from main, do focused work, and merge back immediately, enables continuous delivery and accountability. In contrast, long-lived feature branches signal integration debt and delivery slowdowns. The branching strategy a team uses directly impacts its delivery speed, technical quality, and ability to work in an agile way.
- [Stop Building Silos. Start Building Systems](https://engineering-leadership.hinshelwood.com/articles/stop-building-silos-start-building-systems/): Fragmented, ad-hoc automation stitched together across multiple tools creates a fragile, inefficient, and risky delivery process that slows software teams and leads to inconsistent results. Delivering quality at speed requires consolidating tools into a unified, observable system, such as One Engineering System (1ES) pioneered at Microsoft, which brings together Azure Pipelines, Repos, Boards, Artifacts, and integrated policy and telemetry. Platform Engineering is the strategy to deliver this, providing internal developer platforms that automate compliance, security, and operations, and boost developer self-sufficiency through templates and reusable services. A well-engineered system defines clear boundaries and supports team autonomy within them, leading to safer, faster, and more reliable delivery—no handoffs, no black-box deploys, one clear path from idea to production. Engineering excellence comes from systems that minimise friction and confusion, allowing teams to focus on product value instead of plumbing.
- [Human and AI Agency in Adaptive Systems: Strategy Before Optimisation](https://engineering-leadership.hinshelwood.com/articles/human-and-ai-agency-in-adaptive-systems-strategy-before-optimisation/): Human agency is essential in adaptive systems because only humans can define strategy, set purpose, and steer meaningful adaptation. AI excels at tactical optimisation within human-defined boundaries, but cannot reframe direction or handle ethical and political choices. Overdelegating adaptation to AI creates brittle and strategically blind organisations, as AI can only optimise patterns from the past and cannot sense when the landscape changes. Sustained resilience depends on drawing a clear line: humans govern strategy and adaptation, while AI serves as an optimiser within those limits. Optimisation without human adaptation leads not to efficiency but rapid irrelevance.
- [Stop Writing Business Logic in Stored Procedures](https://engineering-leadership.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/): Storing business logic in SQL stored procedures creates long-term problems, including lack of proper testing, poor fit with CI/CD practices, manual and risky deployments, and tightly coupling logic to the database, which makes portability and debugging difficult. Instead of attempting a costly rewrite, stop writing new business logic in stored procedures and refactor existing ones only when you need to make changes, moving logic into testable, maintainable code. The Azure DevOps team took four years of incremental changes to remove brittle system tests, showing that steady progress works. Each refactor improves unit testing, maintainability, feedback speed, and reduces bugs and costs. Modern software demands code that is testable and observable; stored procedures make every part of engineering harder, so shift business logic out of the database as you go.
- [How Lack of Agency is Killing Your DevOps Initiatives](https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/): DevOps succeeds only when developers have real operational agency, not just automation or pipelines. Developers must control deployments, manage environments, own telemetry, and be able to respond to incidents directly in production—without bureaucratic gatekeeping or reliance on separate operations teams. Production is the only place where genuine feedback happens; separating developers from production limits learning and improvement, turning continuous delivery into continuous guessing. Automation without agency leads to fragility and disempowered teams, creating process theatre instead of real agility. True DevOps requires trusting developers with ownership over production and integrating operational readiness into the definition of done.
- [Resilience is Part of the Product, Not an Afterthought](https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/): Resilience is a fundamental feature of any serious product and must be deliberately designed from the beginning, not added as an afterthought. Relying on heroes or separate departments creates hidden risks and undermines quality; instead, engineers must own resilience as part of their end-to-end responsibility, as demonstrated by Azure DevOps teams at Microsoft. Building resilience requires embedding telemetry, rapid roll-forward, observability, and containment into both architecture and culture, with failures expected and contained, not blamed or ignored. Key practices include instrumenting everything, making changes reversible, isolating failures, and treating incidents as signals for improvement. Neglecting resilience is gambling with your business, while engineering it into every layer protects customer trust and business continuity.
- [The Missing Lever in Agile Transformations](https://engineering-leadership.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/): Most agile transformations fail because they focus on ceremonies instead of building genuine agency in people and systems. Installing stand-ups, stories, and boards without cultivating belief in the ability to shape outcomes only results in organisational fragility and learned helplessness. Agentic Agility bridges the gap between merely following agile practices and truly being adaptable by fostering both human and system agency—the ability to act intentionally and dynamically evolve. Evidence-Based Management is vital, enabling organisations to measure outcomes, challenge assumptions with data, and adapt strategies based on real evidence. Without agency and evidence, transformations are either short-lived or blind, but with both, organisations develop resilience and real capacity for change.
- [How to Build for Business Resilience and Continuity](https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/): Business resilience must be built intentionally through intelligent systems design and disciplined operational practices. Effective resilience starts with comprehensive observability, including embedding telemetry everywhere and defining service level objectives for critical systems. Loose coupling of systems is essential, as shown by a real incident where the failure of Azure DevOps’ Profile Service crippled the platform due to tight integration; after this, circuit breakers and decoupling were aggressively implemented across services to prevent repeat failures. Deployments should be routine through continuous delivery, and teams must be empowered to act swiftly during incidents without hierarchical delays. True resilience requires designing for partial failures, embracing chaos engineering, and continuously measuring recovery and deployment metrics; anything less is gambling with business continuity.
- [Robots and AI Are Not Taking Our Jobs They Are Giving Us Our Dignity Back](https://engineering-leadership.hinshelwood.com/articles/robots-and-ai-are-not-taking-our-jobs-they-are-giving-us-our-dignity-back/): Automation and AI are not threats to human jobs but are liberating people from dehumanising, repetitive work created to enforce control and mediocrity during industrialisation. Roles like scanning groceries and packing boxes were designed under the false belief that most people lacked creativity or critical thinking, a systemic failure still evident in many organisations' reliance on hierarchies, quotas, and bonus schemes. Scientific Management, or Taylorism, engineered compliance over mastery by reducing individuals to cogs and rewarding politics instead of problem-solving. AI is continuing the work of robots by taking over cognitive drudgery, allowing humans to focus on creativity, empathy, and strategy. The knowledge age rewards autonomy and purpose; clinging to industrial management practices only limits human potential and delays organisational relevance.
- [Fragile by Design: The Cost of Pretending to Be Resilient](https://engineering-leadership.hinshelwood.com/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/): Most systems are fragile by design, maintained by the illusion of continuity that collapses under real stress. Major failures, such as Spain’s energy blackout and Oracle’s hospital cloud outage, happened not by accident but due to bad engineering, superficial product thinking, and leadership that avoids confronting operational weaknesses. Real resilience is not box-ticking or paperwork; it must be engineered, tested, and proven under real-world conditions, like Rackspace’s CEO physically shutting off power monthly to ensure backup systems work in reality, not just on paper. Organisations that treat continuity as an afterthought, or cover failures with fake success metrics, are building houses of cards. True resilience comes only from relentless practice, honest iteration over pain, and an unwavering willingness to test and expose weaknesses until survival becomes certain.
- [The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie](https://engineering-leadership.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/): Scrum is not just a set of meetings or lightweight project management, but a social technology built on Agile values, with self-management and real agency at its core. Without genuine decision-making power for Product Owners, Developers, and Scrum Masters, Scrum devolves into empty ritual and performative accountability. A distinctive failure mode occurs when teams are labeled "self-managing" but have goals dictated and technical decisions overruled, making self-management an illusion. Scrum Masters must actively challenge organisational constraints, not just run events. Without true agency, Scrum cannot deliver adaptability or resilience and turns into a hollow enactment of agility.
- [Your Evolving Definition of Done](https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/): The Definition of Done (DoD) is not fixed; it evolves as Scrum Teams mature and must align with organisational standards that reflect broader business needs such as regulatory compliance, customer feedback incorporation, and go-to-market readiness. A clear, objective DoD is crucial for meeting professional standards and ensuring each increment delivers real value. One team, after 17 years together, defined "done" as live in production, gathering telemetry, and measuring outcomes against the original hypothesis. Robust DoD practices should include automated testing, security checks, documentation, and repeatable deployment processes, all embedded early in the development cycle. Continual improvement of the DoD enhances quality, reduces risk, and aligns outcomes with business strategy, making it a strategic asset rather than a mere checklist.
- [Great Scrum Masters Need Technical, Business, and Organisational Mastery](https://engineering-leadership.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/): A great Scrum Master must combine strong leadership skills with mastery in three key areas: technical, business, and organisational domains. Leadership qualities like facilitation, coaching, and conflict resolution are essential but not sufficient on their own. Mastery means understanding the philosophies, practices, and methods specific to the team's domain, such as SOLID principles or Test-Driven Development for software teams, or regulatory requirements in medical devices. Without knowledge in these three areas, a Scrum Master cannot effectively remove impediments, support the Product Owner, or drive meaningful organisational change. Scrum Masters are not junior roles; they require experience and ongoing development in each of these mastery areas to serve teams and organisations effectively.
- [Balance of Leadership and Control in Scrum](https://engineering-leadership.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/): Scrum depends on self-management, but holding Scrum Masters and Product Owners accountable for outcomes requires giving them real authority, not just influence. Authority is needed to remove impediments, enforce alignment, and challenge dysfunction, especially when influence alone is not enough. Relying solely on guidance and empowerment can create either stifling obedience or chaos, depending on the organisational context. A Scrum Master’s authority should match the needs of the team and environment, such as enforcing the Scrum framework and challenging anti-patterns if necessary. True leadership in Scrum balances empowering teams with decisive intervention to ensure both autonomy and accountability.
- [Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)](https://engineering-leadership.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/): Focusing on individual cycle time misunderstands how work flows through a system and ignores real inefficiencies like bottlenecks, waiting times, and handoffs. Measuring individuals encourages counterproductive behaviour such as cherry-picking easy tasks, rushing work, or hoarding tasks to appear fast, without actually improving team delivery. Kanban aims to optimise flow at the system level by improving measures like Process Cycle Efficiency, throughput, and customer lead time, not individual productivity. The key is to identify and address system-wide constraints, including blocked work or excess work in progress. As Nigel Thurlow notes, fixing flow means improving the system and never blaming or measuring individual people.
- [Stop Hiding Behind Complexity and Start Delivering Continuously](https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/): Complexity is not a real barrier to continuous delivery; it is an excuse that hides the lack of investment in modernising processes and architecture. Companies like Microsoft Azure DevOps transformed from two-year release cycles and fixing 75,000 bugs for Visual Studio 2010 to shipping almost 300 features a year by prioritising automation, trunk-based development, feature flags, shift-left testing, and relentless process improvement. Sustainable velocity requires tracking metrics such as time to build, self-test, deploy, and learn, and focusing on value areas like customer satisfaction, unrealised value, innovation, and time to market. Continuous delivery is achievable for any software system if the organisation is willing to invest the time, effort, and resources to address root causes of slow delivery and technical debt. The real challenge is organisational will, not software complexity.
- [There Is No Such Thing as a "Junior" Scrum Master](https://engineering-leadership.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/): The Scrum Master role should never be filled by someone considered “junior”; it requires deep mastery in technical, business, and organisational domains from day one. Just as you wouldn’t hire a “junior” Financial Director, a Scrum Master cannot be effective with only a two-day certification or administrative capabilities. The most effective Scrum Masters are those who have lived the experience of a Scrum Team, are chosen by their peers, and have demonstrated real leadership and credibility, often having coding experience to engage with developers on code quality and technical decisions. Treating the role as an entry-level position leads only to ineffective “Jira lackeys” who cannot deliver genuine agility. A true Scrum Master emerges fully formed from within the team, already practising servant leadership and driving continuous improvement, rather than learning fundamentals on the job.
- [Testing in Production Maximises Quality and Value](https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/): Testing in production focuses on structured, observable releases that deliver fast feedback, controlled exposure, and rapid adjustment, replacing slow, costly Dev-Test-Staging pipelines. Audience-based deployment, as practised by teams like Azure DevOps and Windows at Microsoft, enables granular control over who receives new features, allowing progressive rollouts and early feedback from real users. This model relies on feature flags, observability, and automated rollout halts rather than environment-based branching, with rollbacks reserved only for binaries, not data. The Windows Insider Program, for example, segments millions of users into channels like Canary and Beta, detecting failures early and refining features before general release. Moving to audience-based deployment maximises quality and value by making the feedback loop immediate and closing the gap between engineering and end-user needs.
- [Without Delivery, There Is No Value](https://engineering-leadership.hinshelwood.com/articles/without-delivery-there-is-no-value/): Value in software development is only realised through actual delivery, not through plans or assumptions. Releasing working software to real users frequently allows teams to validate ideas, gather feedback, and adapt quickly, reducing risks and preventing wasted effort. The Standish Group’s CHAOS Report shows that agile projects with frequent releases succeed up to twice as often as traditional, infrequent-release projects. The release of Windows 8 after six years of isolated development, only to face massive user backlash and brand damage, illustrates the high cost of delayed feedback and delivery. Every unreleased increment is a missed opportunity, so frequent, incremental delivery is critical for turning assumptions into real, measurable value.
- [Stop Promoting Branches](https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/): Promoting code through sequential branches like Dev, Test, Staging, and Production creates unnecessary complexity, slows delivery, and increases risk, as merging and reverse integration introduce errors and instability. Treating branches as environment milestones leads to features waiting in queues, merge conflicts, broken hotfixes, and difficult rollbacks. Instead, use a mainline approach: GitHub Flow enables continuous delivery with short-lived feature branches and automated testing, while Release Flow is suitable when multiple production versions need support, avoiding reverse integration pitfalls. Practices like branch-by-customer and Git Flow are condemned as outdated and unmanageable. Branching should support, not hinder, fast and predictable value delivery.
- [Delivery is the only Measure of Progress in Scrum](https://engineering-leadership.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/): Delivery, not just completion, is the true measure of progress in Scrum. Modern DevOps practices have made continuous delivery to real users routine, so every Scrum Team should deliver increments to production at least once per Sprint, ideally even more frequently. Work that is “Done” but not delivered creates no value; genuine business impact comes only when users benefit from the product in production. A feature sitting on a shelf is as useless as one never built, so teams must automate releases, focus on real user impact, and break down silos to ensure delivery is always the default. In today’s environment, Scrum Teams that do not deliver are only simulating progress.
- [The Scrum Master is accountable for Delivery](https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/): The Scrum Master is ultimately accountable for ensuring that the Scrum Team delivers a usable, working product increment every sprint, as delivery is the minimum measure of effectiveness in Scrum. While delivery is a shared responsibility, the Scrum Master’s unique role is to create and maintain conditions—through coaching, facilitating, and removing impediments—that make delivery inevitable. Delivery is non-negotiable; without it, the team cannot measure value or learn from feedback, making effectiveness impossible. A distinctive example illustrates this: code that never arrives in production means nothing has truly been delivered, regardless of effort or intent. Beyond just shipping software, the Scrum Master also fosters a culture of continuous improvement, maximises value while minimising waste, and bridges the team with the wider organisation to help everyone thrive.
- [Why Handoffs Are Killing Your Agility](https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/): Handoffs between siloed teams in software development destroy agility by introducing waste, increasing cycle time, and reducing quality. Each handoff creates delays, causes loss of context, boosts work in progress, and leads to rework, while also eroding team morale and a sense of purpose. These costs compound to undermine your ability to deliver value quickly and sustainably. True agility requires eliminating handoffs by building cross-functional teams, adopting test-first and continuous delivery practices, minimising work in progress, and continuously removing unnecessary rules. Every handoff is an opportunity for waste; removing them lets teams focus on value and thrive.
- [Definition of Done - Objective vs Subjective](https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/): In Scrum, Product and Sprint Goals are aspirational and subjective, guiding teams toward strategic outcomes but not providing a clear measure of quality. The Definition of Done (DoD), by contrast, is an objective, non-negotiable checklist that sets a minimum professional standard for each product Increment. For example, an effective Product DoD for a cloud team might be "live and in production, gathering telemetry that supports or diminishes the starting hypothesis," ensuring a focus on delivery and empirical learning. Teams should avoid confusing subjective approval with measurable quality, automate compliance wherever possible, and treat the DoD as a living, periodically raised quality baseline. A clear and objective DoD safeguards against technical debt, maintains stakeholder trust, and ensures consistent, high-quality delivery.
- [Why Most Scrum Masters Are Failing and What They Should Know](https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/): Most Scrum Masters lack the necessary understanding of Scrum and technical, business, or organisational skills, with 61 percent reportedly never having read the Scrum Guide or only holding superficial knowledge. This gap stems from companies lowering hiring standards during the agile boom, leading to today’s layoffs as firms reassess the value of the role. Companies now want Scrum Masters who can demonstrate real impact and measurable results, expecting them to have expertise in practices such as DevOps, modern engineering, scaling agile, release planning, and agile metrics. The minimum expectation is broad foundational knowledge—about 90 hours of learning in real contexts—along with the ability to coach, mentor, and facilitate teams effectively. Having only certificates or minimal training is insufficient; genuine competence in these areas is now viewed as essential, not idealistic.
- [You can't stop the signal! But you can ignore it!](https://engineering-leadership.hinshelwood.com/articles/you-cant-stop-the-signal-but-you-can-ignore-it/): Agile and Scrum are frameworks designed to highlight problems in team or organisational processes, providing strong signals when things go wrong but not fixing the problems themselves. Drawing on Toyota’s “andon” chain—where any worker can stop the production line to address issues—the content argues that true improvement comes not from the system’s tools but from a culture that encourages using them. Many organisations ignore clear signals due to fear of repercussions, resistance to change, or shallow understanding of Agile and Scrum’s philosophies. The critical insight is that, like workers afraid to pull Toyota’s andon chain, teams will ignore issues unless the environment fosters transparency, continuous improvement, and positive responsiveness to feedback. Organisations must actively value and respond to these signals to enable genuine, lasting development success.
- [Pragmatism crushes Dogma in the wild](https://engineering-leadership.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/): Scrum's true strength lies in its adaptability and resilience, enabling teams to navigate real-world complexity without rigid adherence to rules. Using Minecraft sprints as a testbed, teams experienced initial chaos but quickly learned the power of empiricism and flexibility, especially when unexpected challenges like losing the entire project world arose. The hallmark of Scrum is not strict rule-following but maintaining enough structure to guide the team while allowing for adaptation. The Scrum Guide defines ten essential elements, such as making work visible and adapting quickly to deviation, but permits flexibility beyond these requirements. Scrum is a philosophy that empowers teams to meet change head-on, continuously improve, and thrive amid uncertainty.
- [Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness](https://engineering-leadership.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/): Using a Blocked column on a Kanban board hides crucial information about where and why work items are stalled, leading to stagnation as blocked tasks often remain untouched and become outdated. This practice inflates Work In Progress limits and erases both context and priority, making it difficult to manage or resolve underlying issues. Moving tasks in and out of Blocked columns creates unnecessary back-and-forth and increases the risk of errors. Instead, it is more effective to tag blocked work items in their current stage, using a colour-coded Blocked tag in Azure DevOps, so the team maintains transparency, accountability, and clarity over process delays. A key distinction is that blocked and waiting are not the same, especially in approval-heavy workflows where understanding the source and duration of waiting is vital to resolving bottlenecks.
- [The Evolution of Agile Learning: Insights from Scrum.org's Webinar](https://engineering-leadership.hinshelwood.com/articles/the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar/): Immersive learning is emerging as the future of Agile and Scrum training, moving beyond traditional two-day courses that often fail to create lasting impact. Unlike short, intensive sessions, immersive programmes run over several weeks, blending teaching with outcome-based assignments and facilitated reflection to close the feedback loop and enable deeper learning. This approach allows participants to apply new concepts in their own work environments and analyse the results, promoting double-loop learning and real changes in mental models. The distinctive example is the lasting effect of an in-depth MongoDB course with weekly homework, contrasted with the forgettable nature of a crash course in team management. Immersive learning is shown to be more effective at embedding knowledge and driving genuine behavioural change in software development teams.
- [The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development](https://engineering-leadership.hinshelwood.com/articles/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/): Agile teams often fall prey to seven "deadly sins" drawn from ancient Greek philosophy, each representing a common pitfall in modern software development. Pride manifests when teams believe they are infallible and resist feedback, while envy leads to blindly copying models like Spotify without adaptation. Gluttony bloats product backlogs with more work than teams can handle, and lust chases after quick fixes at the expense of true agile principles. Greed focuses on immediate gains over lasting value, sloth results in teams neglecting promised work—such as failing to deliver a working product at sprint’s end—and wrath creates a blame culture that blocks accountability and innovation. Recognising and reflecting on these pitfalls helps teams stay committed to genuine agility and continuous improvement.
- [How to Set and Achieve Effective Sprint Goals](https://engineering-leadership.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/): The Sprint Goal is central to Scrum, serving as the team's clear, tactical commitment that connects daily work to broader product objectives and stakeholder value. A well-crafted Sprint Goal is neither too granular nor too high-level; it must be actionable, concise, and something for which stakeholders can hold the team accountable—like "migrating 50% of the application data to the cloud without any data loss or corruption" in a cloud migration project. Teams benefit from drafting Sprint Goals ahead of time, adjusting as needed, and can use frameworks such as SMART, OKR, or CLEAR to define them. Effective Sprint Goals spark engagement, guide backlog selection, and build trust by focusing on delivering value rather than just completing tasks. The key is collaboration and ongoing alignment to ensure each Sprint moves the product closer to its overarching goals.
- [The Definition of Done: Ensuring Quality without Compromising Value](https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/): The Definition of Done (DoD) is a essential quality standard that ensures every deliverable meets requirements for release, providing clarity and transparency for both teams and stakeholders. Acceptance criteria, meanwhile, specify the content of the work, and combining them into the DoD risks undermining the DoD's integrity. If certain quality criteria are always necessary, they should become part of the DoD itself, like “all content is spelled correctly and has good grammar.” To balance flexibility and transparency, teams can specify that quality-based acceptance criteria must be fulfilled for delivered work, but only if this does not compromise adaptability. Any changes to the DoD must always protect both transparency and adaptability in the development process.
- [Deciphering the Enigma of Story Points Across Teams](https://engineering-leadership.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/): Story Points are subjective and should not be used to compare teams or predict deliverables, as they reflect individual perceptions and do not reliably measure value delivered. They are most useful for fostering discussions during backlog refinement, helping teams identify unknowns and align on task size, especially when outliers appear in planning poker. Objective metrics such as throughput, cycle time, work item age, and work in process provide clearer insights into team performance and flow. Value should be considered across four areas: current value, unrealised value, time to market, and ability to innovate. The ultimate aim is to balance increasing throughput with maximising the real value of delivered work, avoiding both sluggish excellence and a flood of low-quality output.
- [Decoding Scrum Team Work: Balancing Sprint and Refinement Work](https://engineering-leadership.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/): A Scrum Team’s work falls into two key types: Sprint Work, which changes the product increment and delivers immediate value to stakeholders, and Refinement, which prepares and clarifies Product Backlog items for future Sprints. The challenge is to strike a balance, keeping enough focus on Refinement to prevent surprises without wasting effort on over-preparation. Using Azure DevOps to visualise both Sprint and Refinement work brings transparency, for example by adding a ‘Refinement’ column on the Board for backlog items not yet ready for the Sprint. This clear visibility helps teams manage tasks and prepare for challenges, supporting more efficient and predictable product development.
- [The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility](https://engineering-leadership.hinshelwood.com/articles/the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/): The true aim is not to implement popular frameworks like SAFe or Scrum@Scale, but to ensure your organisation can grasp opportunities, pivot quickly, and manage surprises faster than competitors. Rigidly combining Agile and Waterfall approaches fails because genuine agility requires building processes tailored to your organisation's unique needs, much like a bespoke suit. As markets shift rapidly, the old systems of rules and procedures fall short and must be rethought from the ground up. Referencing Dr Deming, survival is optional; many companies, like extinct animal species, fail because they cannot adapt. The key is to wake up to the urgent race for market responsiveness, or risk being left behind.
- [Rethinking 'User Stories': A Call for Clarity in Product Backlog Management](https://engineering-leadership.hinshelwood.com/articles/rethinking-user-stories-a-call-for-clarity-in-product-backlog-management/): Using the term "User Stories" for all work in product backlogs can confuse and limit teams, since not every task fits a user-centric story format. Forcing items like "Update the documentation" into a user story structure adds unnecessary complexity, much like fitting a square peg into a round hole. Adopting a more generic term like "Product Backlog Item" lets teams describe tasks more clearly and flexibly, increasing transparency and better reflecting the true nature of the work. Language shapes thinking and behaviour, so changing how work is named can improve communication and product outcomes. There is no objection to true user stories for genuine user needs, but work that is not about a user should not be forced into that mould.
- [Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness](https://engineering-leadership.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/): Crafting an effective Product Backlog is like sculpting, requiring continual refinement to keep it a lean yet sufficient inventory that accurately reflects the product's unrealised value. The backlog must be clear and transparent, enabling all stakeholders to understand and discuss its contents. Keeping the backlog minimal is vital, but looking just far enough ahead to anticipate the future—the Goldilocks zone—prevents wasted effort on obsolete ideas and reduces missed opportunities. Surprises will occur, but regular reflection on what was unforeseen versus what was overlooked can reveal lessons and drive future improvement. The Product Backlog remains a living artefact, best shaped through ongoing insight, disciplined adaptation, and a willingness to learn from both successes and surprises.
- [Rethinking Product Backlog: Navigating Through the Weeds of Complexity](https://engineering-leadership.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/): A hierarchical structure in the Product Backlog, while appealing for its sense of order, can actually reduce transparency and adaptability in complex product development. Relying on models like Initiative-Epic-Feature-User Story-Task can lead to rigidity and cause teams to revert to outdated work breakdown habits, masking what is genuinely valuable. In unpredictable environments, there are no definitive best practices, only emergent ones that evolve through experimentation and learning. The Product Backlog should focus on deliverable items that provide business value independently, rather than layering contextual detail or tasks. By flattening the Backlog and supporting it with contextual materials elsewhere, teams gain autonomy, facilitate sensemaking, and foster innovation, helping them remain resilient and adaptable as complexity increases.
- [Navigating the Future with a Fine-Tuned Product Backlog](https://engineering-leadership.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/): A well-ordered and refined Product Backlog is crucial for successful Agile product development, serving as a guiding "astrolabe" that steers teams through uncertainty toward strategic goals. The Product Backlog is a living, evolving list of features, enhancements, and fixes, sequenced by value, risk, size, and learning so that the most important items get attention first. Effective backlogs require detailed, clearly articulated items that are regularly refined and broken into manageable pieces through ongoing discussion and sizing. Tools like OKRs can help align objectives but must be used thoughtfully to ensure focus remains on customer value. Maintaining a meticulously curated Product Backlog transforms it from a simple to-do list into an essential instrument for delivering a transparent, value-driven product.
- [From Unused Gym Memberships to Agile Implementation The Parallels of Misapplied Investments](https://engineering-leadership.hinshelwood.com/articles/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/): Adopting agile methodologies in software development is like signing up for a gym membership: the real benefits only come from consistent, genuine participation rather than just going through the motions. Superficial agile adoption—such as holding stand-ups or using sprints without transforming team culture—does not address deeper issues like silos or misaligned goals. Effective agile requires breaking down big goals, reflecting and adapting regularly, and building cross-functional teams that prioritise quality and collaboration. Just as skipping proper form in the gym can lead to injuries, cutting corners in agile can result in technical debt with lasting consequences. Without true commitment and continuous effort, both the gym membership and agile remain wasted opportunities.
- [Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations](https://engineering-leadership.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/): Failing to deliver a usable product at the end of each agile iteration leads to serious, compounding problems. Trust with stakeholders erodes as they repeatedly receive unfinished work, much like being handed loose laptop parts instead of a computer. Technical debt builds up rapidly, creating a looming backlog that becomes harder to fix over time. Teams that skip usable increments struggle to adapt, find themselves directionless without feedback, and see morale fade as their efforts fail to engage stakeholders. Delivering a usable product each iteration is essential for trust, alignment, adaptability, and maintaining true agility.
- [How Usable Working Products Are Your Ultimate Weapon Against Risks](https://engineering-leadership.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/): The key to reducing risk in Agile software development is to continuously deliver a usable working product—a software increment that is bug-free and ready for release. Agile should focus on releasing real, shippable products, not building layers of documentation or code that never reach users. Fix bugs immediately rather than managing them, and rely on rapid feedback loops with stakeholders to avoid wasteful rework—especially since data shows only 35% of features deliver actual customer value. Manual testing undercuts agility; automation should be embraced to catch regressions and speed delivery. Prioritise lean, adaptive development to stay in step with changing market demands.
- [Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management](https://engineering-leadership.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/): Agile risk mitigation centres on delivering usable working software in small increments, allowing teams to validate products early and adapt quickly to change. Unlike traditional project management, which relies on comprehensive upfront documentation as a project blueprint, Agile teams detect issues and respond to shifting customer needs through continuous integration and deployment. For example, by incrementally building an innovative web application, teams maintain a “pulse” on the product’s real-world use rather than discovering issues only at the end. While documentation remains important, Agile values working products higher, enabling teams to earn stakeholder trust through transparency, adaptability, and early delivery of value. Effective risk mitigation comes from balancing adaptive documentation with ongoing validation through working software.
- [A Titanic Misfit: The Alpha Organization's Wasteful Endeavor in Red Markets](https://engineering-leadership.hinshelwood.com/articles/a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets/): Alpha organisations, built for the slow and stable blue markets of the past, are struggling to adapt to today’s fast-moving, complex red markets. Their rigid hierarchies and command-and-control systems create massive waste as they move too slowly to keep up, miss trends, and launch products late. Inside, innovation is stifled and talented people are left sidelined because decisions come only from the top. Customers are also lost as these companies, out of touch in their ivory towers, fail to respond quickly to changing needs. Watching them try to keep up is like watching a fish try to climb a tree, while nimble Beta organisations surge ahead, showing how adaptability reduces waste and offers a better fit for the modern world.
- [The Urgent Call for Agile Organisational Transformation](https://engineering-leadership.hinshelwood.com/articles/the-urgent-call-for-agile-organisational-transformation/): Organisations rooted in Industrial Age command-and-control hierarchies struggle to adapt to today's unpredictable, fast-changing markets, leading to stifled innovation and sluggish responses. These classic models, optimised for the stable markets of the past, have become obsolete, yet businesses often persist with minor tweaks that do not address underlying dysfunctions. The enduring appeal of bureaucracy and the high failure rate of transformation efforts breed apathy and resistance to change. A shift toward network-based, decentralised structures inspired by Mary Parker Follett enables cross-functional teams to better meet direct market demands, but many attempts at agile transformation only add more layers of control instead of real agility. With approaches such as OpenSpace Agile, a genuine move from rigid hierarchy to an adaptive, continually refactored organisation is possible within months, not years.
- [Embrace Uniqueness: Why Creating Your Own Scaling Practices Leads to Business Success](https://engineering-leadership.hinshelwood.com/articles/embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/): Successful software organisations are distinct because of their unique values, culture, and practices, which together form their "DNA" and competitive edge. Relying on pre-packaged scaling frameworks like SAFe or the Spotify Model risks diluting these unique qualities and may not address specific business needs. The path to sustainable success lies in developing custom scaling practices tailored to the organisation’s challenges, opportunities, and strengths, while remaining agile and open to learning from others. Involving teams in shaping these practices increases engagement, accountability, and innovation. Preserving distinctiveness and fostering a culture of ownership lead to better adaptability and stronger business outcomes.
- [Announcing Professional Agile Leadership with Evidence-Based Management Training  (PAL-EBM) from Scrum.org](https://engineering-leadership.hinshelwood.com/articles/announcing-professional-agile-leadership-with-evidence-based-management-training-pal-ebm-from-scrum-org/): The Professional Agile Leadership with Evidence-Based Management Training (PAL-EBM) helps leaders base decisions on evidence rather than instinct, encouraging the creation of custom metrics suited to each business context instead of prescribing universal ones. Years of evaluation with organisations ranging from defence and police services to media and healthcare have shaped this approach, integrating real-world feedback and data. A key distinction is the emphasis on the need for every organisation to have a clearly communicated Vision and Strategic Goal that employees can connect their daily work to, as successful companies excel at this alignment. The PAL-EBM course is a one-day event that shifts focus from leadership style to how success is truly measured within the organisation.
- [Hiring a Professional Product Owner](https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-product-owner/): Product Owner is a Scrum accountability an existing Product Manager should take on. This reusable job specification combines product leadership, customer understanding, decision authority and evidence-informed practice organised around the work. Candidate requirements focus on demonstrated capability, supported by clear organisational authority and collaboration. The original customer interpretation is preserved, with separate analysis of its changes in emphasis.
- [Stop normalizing unprofessional behaviour in the name of agility](https://engineering-leadership.hinshelwood.com/articles/stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/): Agile practices demand high levels of professionalism, including diligence, discipline, and competence. Unprofessional behaviour, like failing to deliver a usable product increment each iteration or assigning work without clear understanding, is often excused as "how agile works" but actually undermines true agility. Agility requires continuous planning, knowledge, and readiness to adapt based on feedback, not less. The example of the Volkswagen engineer serving a three-year prison sentence for unethical code highlights the serious consequences of ignoring professional standards. Once aware that certain actions harm delivery and quality, continuing them moves from ignorance to incompetence, making it vital to uphold ethical and professional responsibility.
- [Hiring a Professional Scrum Master](https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-scrum-master/): Hiring a Scrum Master is particularly challenging, as the role covers accountability for the Scrum Team's effectiveness by bridging business insight, technical understanding, and team coaching. Certification like PSM I or II is helpful as a minimum bar, but true competence shows in a candidate's proven leadership, skill in servant leadership, facilitation, and supporting team maturity at a sustainable pace. The Scrum Master is tasked with removing impediments, ensuring productive Scrum events, and fostering a safe, trust-based environment. For software teams, knowledge of Agile techniques like Continuous Integration and Automated Testing is valuable. A successful Scrum Master leads to reliable delivery, continuous improvement, and a self-sustaining, happy team.
- [Scrum is made up of Influencers, Entrepreneurs, and Makers](https://engineering-leadership.hinshelwood.com/articles/scrum-is-made-up-of-influencers-entrepreneurs-and-makers/): Scrum relies on three essential skill areas to deliver high-value products: Influencers, Entrepreneurs, and Makers. Influencers form the Leadership Track and focus on creating an environment that enables teams to perform, drawing on experience from both the value and technical sides. Entrepreneurs, found in the Value Track, maximise product value through expertise in the business domain and a willingness to experiment using data-driven decisions. Makers make up the Technical Track, building the product each iteration with broad technical skills and growing mastery in specialised areas. A successful organisation needs all three tracks in the right balance; individuals can grow within any track and do not need to switch to progress.
- [Become the leader that you were meant to to be](https://engineering-leadership.hinshelwood.com/articles/become-the-leader-that-you-were-meant-to-to-be/): Leadership means inspiring others rather than exerting control, and as organisations adopt modern management, the role of managers shifts from managing people to leading effectiveness and empowering teams. In today’s structure, leaders should focus on clearing obstacles for their teams, with executives supporting this process. The Scrum Master exemplifies this shift, acting not as a manager or scribe but as a leader providing services to the team, Product Owner, and organisation. The text calls for abandoning traditional hierarchies and anti-patterns, encouraging leaders to lead by example, as in the story of "Turn this Ship Around" by David Marquet.
- [All technical debt is a risk to the product and to your business](https://engineering-leadership.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/): Technical debt is pure risk to a product and the business, offering no benefit or safety net and accumulating in unpredictable, damaging ways. Unlike buying a car or TV where quality is obvious, software’s complexity often hides technical debt until it slows delivery and damages competitiveness, as seen in Microsoft’s Team Foundation Server, where two-year release cycles led to falling behind competitors and only 24 features shipped per year despite 600 people working on the product. Transitioning to three-week sprints and increasing transparency exposed hidden debt but allowed Microsoft to decouple delivery and release, responding to user feedback in days rather than years. The compound, stealthy nature of technical debt means its consequences can be severe and sudden, likened to a sub-prime mortgage pack or eating a “Roadkill Burger”—initial gains come at the cost of eventual failure. Without a culture of quality, businesses risk losing track of project status, deliverables, and required work, exposing themselves to potentially catastrophic business outcomes.
- [Professional Kanban Trainer for Applying Professional Kanban](https://engineering-leadership.hinshelwood.com/articles/professional-kanban-trainer-for-applying-professional-kanban/): The Kanban Guide, created by ProKanban.org under creative commons, defines the minimum needed to optimise value flow through visual, pull-based systems and marks a new era of openness between Scrum and Kanban communities. Becoming a Professional Kanban Trainer involves a structured process of applications, interviews, and assessments. The "Applying Professional Kanban" training focuses exclusively on Kanban over two days, covering topics such as theory, workflow design, and practical operation. In contrast, "Professional Scrum with Kanban" covers both frameworks and how they integrate. The assessment for Professional Kanban certification can be taken independently, with learning resources available online.
- [What is Taylorism, and why Waterfall is just the tip of the iceberg!](https://engineering-leadership.hinshelwood.com/articles/what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/): Traditional project management methods like Waterfall are only a surface symptom of deeper problems rooted in Taylorism—a management approach from the industrial revolution that treated people as interchangeable parts, stripping away autonomy, mastery, and purpose from work. This mindset led to siloed departments, rigid best practices, and task-and-bonus reward systems that persist today, even though modern work is complex and creative. A striking example is Microsoft’s shift from rewarding Azure sales by volume to rewarding actual customer usage, which transformed behaviours and outcomes. Research shows that, for cognitive and creative work, true motivation comes from autonomy, mastery, and purpose, not financial incentives. To succeed, organisations must move away from Tayloristic practices and create environments where employees are engaged and empowered to do their best work.
- [Sprint Goal is an Immediate Tactical Goal](https://engineering-leadership.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/): The Sprint Goal serves as an immediate tactical goal that guides each Sprint toward achieving the broader Product Goal, which represents the intermediate strategic direction. Rather than simply listing tasks, the Sprint Goal should describe the "why" of the Sprint and focus on producing outcomes that move the product forward. Product Owners are accountable for maximising value by working closely with Developers to define high-level objectives, often using tools like the Lean UX Canvas to clarify both business objectives and desired user behaviours. A Product Owner should form hypotheses with clear metrics to validate assumptions, aiming to address immediate user needs while anticipating where the market is heading. Engaging users with solutions to their current problems helps generate valuable feedback and ensures that product development stays relevant and impactful.
- [Story Points & Velocity are a sign of an unsuccessful team](https://engineering-leadership.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/): Story Points and velocity are not required by Scrum, despite widespread belief, and are not even mentioned in the Scrum Guide. These practices may help new teams transition from traditional project management by encouraging conversations and shared understanding, but their predictive value is an illusion. Relying on made-up scores for confidence, rather than on real delivery data, signals organisational immaturity and hinders true agility. Genuine confidence in delivery comes from transparency, such as consistently producing a done increment each sprint and using metrics like cycle time scatter plots to assess and monitor predictability. As Daniel Vacanti puts it, Story Points set the Agile industry back 20 years.
- [Evidence-based Management: Gathering the metrics](https://engineering-leadership.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/): Evidence-based Management for Software Organisations is a framework designed to help organisations focus on delivering the highest value from their software investments by measuring their progress and guiding change with concrete data. Traditional measures of software success, such as delivering on time, on budget, and with required features, often miss whether actual value is reaching customers. Instead, the framework groups key organisational metrics into current value (like revenue per employee and customer satisfaction), time to market (such as release frequency and cycle time), and ability to innovate (including installed version index and innovation rate). Gathering these metrics provides a baseline, with regular reassessment revealing trends and improvements. Scrum.org recommends combining these into an "Agility Index," offering a clear, unified measure of an organisation's software delivery value.
- [There is no place like production](https://engineering-leadership.hinshelwood.com/articles/there-is-no-place-like-production/): Value in software is hard to pin down and assumptions about what users want are often wrong, so it is essential to validate those assumptions quickly by observing real users in the production environment. Qualitative data like customer satisfaction, product usage, and employee satisfaction help test assumptions, but only production releases generate genuine feedback because real user behaviour cannot be simulated with test scripts or in UAT. Shipping features to production delivers actual value, avoids shelfware, and allows organisations to claim financial benefits like tax write-downs sooner. The only reliable way to learn what works is to get even the smallest increment of value into production and watch how users respond, since, as Brian Harry says, there is no place like production.
- [Product Goal is an Intermediate Strategic Goal](https://engineering-leadership.hinshelwood.com/articles/product-goal-is-an-intermediate-strategic-goal/): Product Goals serve as intermediate steps towards achieving a broader strategic goal, especially important given today's high uncertainty and rapid change, illustrated vividly by shifts during the COVID-19 pandemic. Success comes from embracing experimentation and adapting business practices to cognitive work rather than traditional factory models; companies like Spotify, Microsoft, and Apple exemplify this adaptability. Key practices include focussing on outcomes over outputs, treating teams as investment opportunities that can be reallocated over time, and running hypothesis-driven experiments to validate learning with real users. The Microsoft Azure DevOps teams, given headcount budgets for each vertical, exemplify how cross-functional teams work towards specific goals through iterative experimentation and data-driven decision-making. This approach requires rethinking outdated concepts like project scope and failure to better support learning and value delivery through discovery.
- [If your backlog is not refined then you are doing it wrong](https://engineering-leadership.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/): A well-refined product backlog is essential for effective Scrum, as starting Sprint Planning with unclear or oversized items leads to confusion and missed goals. Developers should be able to look at backlog items for the next two sprints and fully understand and estimate them; if not, more refinement work is needed. Refinement should be continuous and practical, involving the whole Scrum Team and relevant experts in reviewing, clarifying, and breaking down items together—often in a workshop setting where each item is discussed, clarified, and re-estimated on the spot. The hallmark of successful refinement is when Developers can confidently select backlog items that fit into a sprint and most are delivered, while ongoing issues with incomplete work or rejected items signal a lack of adequate refinement. Ultimately, ready backlog items empower Developers to plan implementation effectively and allow Product Owners to forecast future releases.
- [Getting started with a Definition of Done (DoD)](https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/): A Definition of Done (DoD) is essential for software teams to ensure consistent quality and transparency in each increment they deliver. Developers must collaborate to define what "done" means for their product and organisation, capturing it as a measurable checklist that reflects shippability and ensures no further work is needed to release. Concrete examples for a DoD include criteria such as "Increment passes SonarCube checks with no critical errors," code coverage does not decrease, engineering and UX standards are met, and security checks pass. Teams should regularly review and organically grow their DoD, adjusting it to reflect lessons learned and higher expectations for quality. If quality issues arise that prevent working software, teams should pause feature development, fix the issue (sometimes via a "Scrumble"), and update the DoD to prevent recurrence.
- [A better way than staggered iterations for delivery](https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/): Staggered iterations create more technical debt, increase rework, and lower software quality because they prolong feedback cycles and maintain outdated siloed processes. For example, one diagram shows an 18-week delivery cycle with a 2-month lag for initial feedback, making changes expensive as coding and testing teams have already moved on. Teams should instead bring all work for shippable increments into each Sprint, including testing, and avoid relying on validation or QA outside the Sprint. Cross-functional teams, test-first practices, and ensuring working software at the end of every iteration will collectively raise quality and speed of delivery. Automating as much as possible from code check-in to production further reduces risk and increases value.
- [You are doing it wrong if you are not using test first](https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/): Test First principles are essential for building modern software that reliably meets customer needs and supports continuous delivery. Approaching development by writing tests before code reduces rework, delivers more maintainable solutions, and dramatically lowers bugs and regressions in production. Test First methods like Test Driven Development validate not only that the right features are built, but also that they work as intended and remain unbroken through change; a defect caught in development is ten times cheaper to fix than one found in production. The approach shortens feedback cycles so developers quickly detect problems, echoing the old plumbing “smoke test” but adapted for the complexity of contemporary systems. Ultimately, professionalism in software development means building quality in from the start, letting executable specifications catch unintended consequences before they reach customers.
- [Professional Scrum teams build software that works](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/): Scrum teams must deliver software that works, meaning software free from faults or defects, rather than just rushing out features or meeting expectations. Developers are accountable for quality and must focus on engineering excellence by fixing bugs as soon as they are found, automating tests and pipelines, using source control, and adopting feature flags. Cutting corners on quality creates technical debt and risk, and any decision to sacrifice quality must involve executive leadership, not developers or product owners. Software that is buggy, incomplete, or missing these practices signals a lack of professionalism and erodes trust with users. True Scrum requires teams to continuously inspect, adapt, and improve in pursuit of consistently high-quality releases.
- [The Sprint Goal is a commitment for the Sprint Backlog](https://engineering-leadership.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/): The Sprint Goal is a clear commitment added to the Sprint Backlog during Sprint Planning, acting as the single objective for the team throughout the Sprint. It provides transparency and focus, enabling Developers to adapt the work needed while maintaining alignment with the underlying goal. The Sprint Goal should answer why the Sprint is being done and describe the most valuable step towards the overarching Product Goal, such as "Add [capability] to entice new users." The Product Owner is expected to bring a proposed Sprint Goal and related Backlog Items to Sprint Planning, ensuring the team focuses on one shared mission per Sprint. The Scrum Guide specifies that Sprint Goals must be tailored to the unique business context and created collaboratively.
- [Release planning and predictable delivery](https://engineering-leadership.hinshelwood.com/articles/release-planning-and-predictable-delivery/): Agile and release management are not inherently incompatible; predictable delivery is achievable with an organisational commitment to continuous quality and transparency. Trust and predictability depend on the regular delivery of working software, making quality a non-negotiable priority decided at the executive level. Software development differs fundamentally from manufacturing because each feature is new and inherently unpredictable, much like creating a film, where plans, budgets, and cross-functional collaboration guide production but do not guarantee certainty. Teams must stop creating technical debt, ensure clear minimum standards for "done", and continuously improve with fixed-length iterations, test-first practices, and development teams that own the whole lifecycle. The distinctive idea is that if you cannot ship at the end of each sprint, you should pause feature work—"Scrumble"—to address quality, pay back technical debt, and restore the ability to deliver working software.
- [The Product Goal is a commitment for the Product Backlog](https://engineering-leadership.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/): The Product Goal, introduced in the 2020 Scrum Guide, is a long-term objective that gives the Scrum Team clear focus and a measure for progress. It describes a future state of the product and sits in the Product Backlog, shaping the rest of the backlog around what will fulfil this Goal. The Product Goal is singular and should be specific, measurable, and widely understood, such as "Reach 10,000 new users in 6 months" or "Improve the customer experience by improving the NPS over the next year." While it provides direction, the Scrum Team can change the Goal if it becomes less valuable or a better objective emerges. Every product, project, or business should define such a visionary Product Goal to align efforts and ensure clarity of purpose.
- [Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework](https://engineering-leadership.hinshelwood.com/articles/update-to-the-scrum-guide-on-the-25th-anniversary-of-the-scrum-framework/): The 2020 update to the Scrum Guide marks 25 years of the Scrum framework, focusing on simplified language and less prescriptive guidelines while reinforcing that Scrum itself has not fundamentally changed. The update emphasises the need for Scrum Teams to be self-managing and accountable as a whole for delivering a valuable Increment each Sprint, with clear roles for Developers, Product Owner, and Scrum Master. Three new commitments are clarified: a Product Goal for the Product Backlog, a Sprint Goal for the Sprint Backlog, and a Definition of Done for the Increment. Sprint Planning now explicitly covers the What, Why, and How, with the Product Owner ensuring preparation and others invited for advice. The clearest new image is of Scrum Teams as cross-functional groups that decide internally who does what, when, and how.
- [Online is the new co-located](https://engineering-leadership.hinshelwood.com/articles/online-is-the-new-co-located/): With advancements in video-conferencing and internet speeds, co-location should now include online environments where everyone can see each other’s posture and expressions, not just physical rooms. Communication is still 80 percent non-verbal, so for true participation and transparency during online meetings, everyone should keep their cameras on, enabling the nuanced feedback critical for team engagement. The text likens this to reading subtle signs of intent when driving, such as the way a car is positioned before a lane change. While respecting individuals’ occasional need to turn cameras off, prioritising visual presence builds openness and effective collaboration. If someone lacks the bandwidth or willingness to appear on camera, attending an in-person event is suggested instead.
- [What my father taught me about Evidence-based Management (34 years before it was invented!)](https://engineering-leadership.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/): Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in both business and software contexts.
- [I do continuous deliver, why should I Sprint?](https://engineering-leadership.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/): Sprints are not about limiting how often you release software, but about providing a regular cadence for planning, communication, and feedback. Teams can release as often as they want during a Sprint, even daily, and still be doing Scrum as long as they have a working increment by the end of the Sprint. The Sprint contains key feedback loops like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective, all centred around producing something Done. Having a regular Sprint, for example "Sprint 231," gives management and dependent teams a reliable point of coordination. Scrum now emphasises not just development but also frequent delivery to production, with the expectation that teams deliver at least every 30 days but ideally more often.
- [Getting started with a modern source control system and DevOps](https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/): Modern source control systems extend far beyond just code management, now supporting the full application lifecycle and DevOps practices through comprehensive metadata integration. All company code must be in source control to protect organisational assets, and deploying directly from workstations introduces serious business risks. An automated release pipeline and feature flags are essential to maintain quality, with VSTS highlighted as the most versatile and integrated platform seen, accommodating teams working on Java, .NET, Web, Android, iOS, and even Mainframe projects. Microsoft’s own shift of the entire Windows team to Git is a concrete example of modern practices. Continuous automated testing, frequent deliveries, and fast user feedback are now necessary elements for any competitive software team.
- [Evolution not Transformation: This is the Inevitability of change](https://engineering-leadership.hinshelwood.com/articles/evolution-not-transformation-this-is-the-inevitability-of-change/): Change is not a one-time transformation but a continuous process of evolution, where agility cannot be installed or bought but must be cultivated organically within an organisation. The pace of business change has accelerated dramatically, and organisations that treat change as sporadic, top-down projects risk becoming obsolete, as shown by companies like Blockbuster and Kodak. Success comes from continuous experimentation and adaptation, much like orienteering, where leaders navigate towards their vision, adjusting course as obstacles and new information arise. Real agility requires direct feedback from real users, empowered teams able to adapt both process and requirements, and an ecosystem that evolves in response to fast-moving markets. Leaders themselves must drive this evolutionary change from within, creating an environment that fosters learning, experimentation, and continuous refinement rather than imposing static solutions from the outside.
- [The fallacy of the rejected backlog item](https://engineering-leadership.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/): Rejecting a single backlog item at Sprint Review is a misunderstanding, because chosen backlog items are typically interconnected in pursuit of the Sprint Goal and cannot simply be removed without significant rework and risk to working software. At the end of the Sprint, the only real outcomes are whether the increment is DONE or NOT DONE; any missing backlog item is not rejected but instead becomes a learning opportunity for the Scrum Team to inspect and adapt. The Sprint Review is about collaboration and discovery, not acceptance or rejection of individual items, and its purpose is to refine the Product Backlog and decide whether to release, continue, or end the work. The software increment is a complex, interdependent whole — pulling out one item can break it. To give Product Owners flexibility, the Development Team should build in the ability to turn features on or off using feature flags or toggles.
- [Luddites have no place in the modern organisation](https://engineering-leadership.hinshelwood.com/articles/luddites-have-no-place-in-the-modern-organisation/): Organisational culture is shaped by its people and can hinder or enable change. Transitioning from traditional hierarchical structures to cross-functional, agile teams requires hiring those open to new ways of working and, within cultural limits, removing those who resist. Individuals who oppose progress—Luddites—act as anchors that slow adaptation and innovation. Citing Microsoft as an example, effective leadership and a willingness to evolve have let the company fundamentally change how it operates, showing that success today demands constant learning and reinvention. Embracing change and moving away from outdated practices is essential, as Luddites have no place in a modern organisation.
- [Many organisations are lured to SAFe by the song of the Sirens](https://engineering-leadership.hinshelwood.com/articles/many-organisations-are-lured-to-safe-by-the-song-of-the-sirens/): Organisations are often tempted by the promise that simply adopting the Scaled Agile Framework (SAFe) will make them agile and solve business challenges overnight, but this replaces one form of rigidity with another. SAFe is described as a dangerous, alluring beast that encourages sweeping changes to language and structure without addressing the underlying need for ongoing adaptation. Even the US Air Force views SAFe as a rigid, prescriptive approach, showing that agility cannot be bought or installed. True business agility comes from evolving with changing environments, not by relying on someone else's standardised framework. The real aim of software development should be to innovate and create, not to follow rigid processes for the sake of perceived safety.
- [Configuring Microsoft Teams for Live Virtual Training](https://engineering-leadership.hinshelwood.com/articles/configuring-microsoft-teams-for-live-virtual-training/): To deliver high-quality live virtual training using Microsoft Teams, thorough setup and configuration are essential rather than relying on default settings. Anyone can join a Teams meeting without a login, but full access to collaboration features like Files, Chat, and Breakout Rooms requires participants to be authenticated members, not just external guests. Setting up for this involves creating an Azure Active Directory tenant, subscribing to Microsoft 365 Business Basic (which enables unlimited guest access), and enabling guest access as well as modern authentication options such as Google credentials and one-time passcodes for easy student onboarding. Be aware that your organisation’s chosen Microsoft 365 name becomes a permanent part of your SharePoint URL, as seen with "nakedalm.sharepoint.com," so select it wisely. Extra enhancements, like branding the sign-in page and adding a custom domain, can create a polished, professional experience for your class participants.
- [Delivering Live Virtual Classes in Microsoft Teams and Mural](https://engineering-leadership.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/): Delivering Professional Scrum classes online, the best experience and security have come from using Microsoft Teams combined with Mural. Teams allows each class to have its own private space for meetings, storage, and chat, supporting the Scrum Values of Focus, Openness, Commitment, and Respect. Instead of assigning breakout rooms, students self-organise by creating their own channels and meetings, learning to manage their own timeboxes—like when one group lost track and continued for 10 extra minutes, but never made that mistake again. Mural provides a flexible canvas for exercises, recreating the tools and bounded environments of in-person classes. Teams does not require participants to have Microsoft accounts and, once initially configured, supports secure and seamless collaboration that persists after the class ends.
- [Live Virtual Classroom's and the new normal](https://engineering-leadership.hinshelwood.com/articles/live-virtual-classrooms-and-the-new-normal/): Live virtual classrooms have surpassed expectations, with student experiences and participation matching or exceeding those in traditional in-person classes. Despite initial concerns that remote training would reduce quality, pass rates for online students in 2020 were only 6% lower than in-person cohorts. Modern video conferencing tools like Microsoft Teams and Google Meet allow for almost seamless collaboration, making physical co-location unnecessary. In virtual training, interactive group exercises scale more easily and conveniently than in a crowded room. The shift to remote delivery also brings benefits such as reduced travel, lower environmental impact, and improved work-life balance, signalling that virtual learning and working have become the new normal for knowledge professionals.
- [Live Site Culture & Site Reliability Engineering](https://engineering-leadership.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/): Organisations face rapidly changing markets where opportunities appear or vanish in weeks, pushing them to adopt DevOps practices like Continuous Delivery to speed up feedback and remain competitive. The shift means teams are no longer releasing major versions every few years but deploying changes daily, as seen at Microsoft, which now performs over 160,000 deployments a day—more than its number of engineers. Traditional release models cannot keep pace; responsibility and high quality must stay with those doing the work and fit within sprint cycles. The Azure DevOps Product Team at Microsoft demonstrates a Combined Engineering model, with around 650 engineers across three main locations, that balances continuous delivery with operational and quality needs. Their evolving structure, as of 2018, offers ideas for others as a starting point for adapting to these new demands.
- [The Tyranny of Taylorism and how to detect Agile BS](https://engineering-leadership.hinshelwood.com/articles/the-tyranny-of-taylorism-and-how-to-detect-agile-bs/): Many current management practices in software development can be traced back to the industrial revolution and the "Tyranny of Taylorism," which treated workers like parts of a machine focused on repetitive tasks. Although 81 percent of development teams claim to be adopting agile methods, in practice very few implement key agile elements like short iterations, prioritised backlogs, and retrospectives, with only 22 percent, 16 percent, and 13 percent doing these respectively. Modern workplaces still lack vital feedback loops that were unnecessary in the production lines of the past, but are essential now. The persistence of outdated management approaches hinders real agile transformation.
- [Slaying the Dragons and How to Successfully Descale at Scale](https://engineering-leadership.hinshelwood.com/articles/slaying-the-dragons-and-how-to-successfully-descale-at-scale/): Most organisations believe they can improve their software delivery while keeping their current ways of working, but this belief is mistaken. Truly successful large-scale organisations rarely achieve real improvement without changing their core behaviours. The common factor among those that excel is a focus on genuine agile values and principles, rather than chasing the illusion of scaling agile practices. Paradoxically, making a big impact requires paying close attention to small, fundamental changes. The message is clear: to go big, you must go small.
- [Live Webcast: Q&A with Martin Hinshelwood on 27th March 2020](https://engineering-leadership.hinshelwood.com/articles/live-webcast-q-amp-a-with-martin-hinshelwood-on-27th-march-2020/): Integrating user experience (UX) into a Scrum team begins with ensuring that UX work is considered part of the team’s regular activities, not something separate or ancillary. One effective starting point is to treat UX professionals as full team members, involving them in all aspects of Scrum, including sprint planning and reviews. Building UX into the team’s definition of Done helps ensure that UX considerations are consistently addressed. Incorporating UX in this way avoids handoffs and makes the entire team responsible for delivering a valuable product that meets user needs.
- [What is your perspective on collocation?](https://engineering-leadership.hinshelwood.com/articles/what-is-your-perspective-on-collocation/): Collocation, where all members of a Scrum Team work together daily in the same room, is not required by Scrum but is strongly recommended, especially for new teams. The evidence and most people's experience suggest that collocated teams have better communication and are more likely to become high-performing, while distributed teams must put in significant effort and technology to try to replicate this interaction. Microsoft has invested billions in dedicated team rooms that enhance team focus, ownership, and a sense of being valued, illustrating the organisational benefits of collocation. However, it is not always possible due to company structure or scale, so minimizing downsides and iterating towards the best available setup is important. Ultimately, collocation remains the optimal arrangement where practical.
- [Can the Definition of Done change per Sprint?](https://engineering-leadership.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/): The Definition of Done (DoD) can and should evolve over time, typically through Sprint Retrospectives, to improve product quality, but it must never be weakened to deliver more features at the expense of quality. Lowering quality is not within the authority of a Scrum Team and would have serious financial and ethical implications, even potentially amounting to fraud in public companies. The DoD must remain consistent across all backlog items, unlike Acceptance Criteria, which can vary by item. Constantly changing the DoD for arbitrary reasons undermines transparency and makes it difficult for the team and stakeholders to understand progress and value delivered. On brownfield projects, start with a basic DoD and improve it each Sprint; on greenfield projects, begin with a shippable DoD from the first Sprint.
- [How do you handle conflict in a Scrum Team?](https://engineering-leadership.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/): Conflict resolution in a Scrum Team starts with the team itself, escalating only if needed to the Scrum Master and, in rare cases, to outside intervention. When one team member is overbearing, it is important to help the team discuss this behaviour, for example, using facilitation techniques like the 1-2-4-All Liberating Structure, which gives everyone a chance to be heard through silent reflection and small group sharing. The Scrum Master should coach team members to listen and may use exercises like “Heard, Seen, Respected” in retrospectives to prompt reflection among dominant voices. If all team-based and coaching efforts are exhausted, it may be necessary to involve HR or consider whether the individual is a good fit for the team. There is no single right answer, so iterating to the best approach for the specific situation is necessary.
- [In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?](https://engineering-leadership.hinshelwood.com/articles/in-nexus-with-5-scrum-teams-how-can-the-product-owner-attend-all-sprint-planning-events/): When working with a Nexus of five Scrum teams, a single Product Owner cannot realistically attend every individual Sprint Planning event. Instead, the Product Owner should focus on setting the overall vision and attending the Nexus-level Sprint Planning, leaving the teams to handle detailed planning. Teams can appoint dedicated representatives, such as “Area Owners” or “Team Owners,” to attend their own Sprint Planning activities and relay information. The Azure DevOps engineering group exemplifies this with about 42 teams grouped under six Product Areas, each managed by corresponding owners to maintain clear communication. It is important to keep the structure as flat as possible and ensure strong communication to avoid gaps between the Product Owner and the teams.
- [Should the Scrum Master always remove impediments?](https://engineering-leadership.hinshelwood.com/articles/should-the-scrum-master-always-remove-impediments/): The Scrum Master is responsible for removing impediments, defined as anything slowing the team's progress that the team cannot address on its own. Before stepping in, the Scrum Master should determine if the team can or should resolve the problem themselves; in these cases, their role is to support the team in learning new skills or building relationships rather than directly solving the issue. Resisting the urge to fix every problem is a powerful tool and helps foster a more self-sufficient team. The goal is to let the Scrum Team handle more challenges independently over time, freeing the Scrum Master to address larger organisational barriers. There is no perfect answer, so choose the most suitable approach for the situation and refine it in future iterations.
- [What's the best way to work around multiple PO?](https://engineering-leadership.hinshelwood.com/articles/whats-the-best-way-to-work-around-multiple-po/): When multiple Product Owners are involved and do not provide clear stories or attend backlog refinement meetings, it usually means there is a lack of true ownership over the product backlog and value delivery. The Product Owner’s critical role is to focus on the product’s direction, market needs, and prioritise the backlog to ensure the team delivers what matters most. Without someone skilled in this role, teams are left guessing and risk spending time on features the business does not need; the industry average is wasting 65% of development effort on the wrong features. The recommended approach is to raise the issue with management, illustrate the cost, and either appoint a real Product Owner or assign someone to act in that role until a suitable person is found, then iterate towards the best solution.
- [How do you make a good Forecast?](https://engineering-leadership.hinshelwood.com/articles/how-do-you-make-a-good-forecast/): Forecasting in agile projects becomes more predictable when teams move away from metrics like Story Points, Burnup charts, and Velocity, which can encourage large, hard-to-predict backlog items. Instead, flow metrics such as Cycle Time, Throughput, Work Item Aging, and Work In Process provide better evidence for future estimates and drive backlog items to be smaller, increasing predictability. In budgeting, rather than relying on traditional, project-based forecasts, calculate the cost per Sprint per team and extrapolate for annual costs; for example, a scenario with 10 teams at $50,000 per Sprint for 23 Sprints requires a budget of $11.5 million. Transitioning from project-based to team-based budgeting fits the shift toward product focus as organisations adopt agile and DevOps practices. Resistance often comes from those invested in traditional roles, so involve them early to help manage the change.
- [Are technical skills required to be a Scrum Master?](https://engineering-leadership.hinshelwood.com/articles/are-technical-skills-required-to-be-a-scrum-master/): A Scrum Master is not required to have technical skills according to the Scrum Guide, but being a truly effective Scrum Master requires mastery in three areas: technical, business, and organisational change. Understanding technical practices like test-driven development and continuous integration enables a Scrum Master to effectively support a development team building, for example, financial software for a bank or a system at Boeing. Business mastery is vital to guide Product Owners and ensure the team delivers valuable and relevant products. Organisational transformational mastery is critical to drive real, lasting change within an organisation. While a non-technical Scrum Master is possible, a strong grasp of all three contexts makes for a much stronger Scrum Master who can coach, mentor, and facilitate real team and organisational improvement.
- [No Estimates and is it advisable for a Scrum Team to adopt it?](https://engineering-leadership.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/): Estimation in Scrum is most valuable for the conversations and team understanding it generates, not just the numerical results. For new teams, using Story Points and Velocity helps build communication skills and break down work. As teams mature and reliably deliver working software each Sprint, they should shift focus to optimising flow using metrics like Cycle Time, Throughput, WIP, and Work Item Aging. When teams can regularly deliver, the need for detailed estimation decreases and work naturally becomes smaller and easier to manage—eventually, items are judged more simply by whether they fit in a Sprint. #NoEstimates is one approach to this boolean sizing, and as teams improve, they should continuously select and refine the practices that work best for their context.
- [How do you incorporate a Design Sprint in Scrum?](https://engineering-leadership.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/): There are no special sprints in Scrum such as Sprint 0 or Design Sprints; all work, including UX and design activities, should be integrated within the regular flow of Sprints. Activities related to current Sprint Goals, like reworking or inventing new user interactions, should be completed collaboratively within the Sprint by the Development Team. Work for future Sprints, such as developing and testing a UX strategy with real users, is handled through ongoing Refinement. No specialist work should occur in isolation, and at scale, UX Communities of Practice should bring together team representatives to create reusable interaction frameworks. Choosing the most suitable approach for your context and iterating towards improvement is encouraged.
- [DOD has made it illegal to do waterfall](https://engineering-leadership.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/): The US Department of Defence has fundamentally shifted its procurement rules, moving away from the waterfall approach and making iterative, agile development processes standard. This change follows high-profile failures like the FBI’s Sentinel project, which spent over $700 million across nine years without delivering usable software, until switching to agile in a small, focused team and completing the product in just one year for $30 million. The benefits of agile—including higher success rates, cost efficiency due to always having working software, and reduced risk over short iterations—are now so clear that agile methods have become effectively mandatory for major government IT initiatives. This cultural transformation is influencing vendors, contractors, and even university training, as anyone working with the DOD must now adopt an agile mindset. The pace and approach of defence software delivery are rapidly changing, with successful agile practices now filtering across UK and US public sector projects.
- [Introducing Kanban for Professional Scrum Teams](https://engineering-leadership.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/): Professional Scrum teams can now integrate the core practices of Kanban—such as workflow visualisation, limiting work in progress, actively managing items in progress, and regularly inspecting and adapting workflows—without altering the Scrum framework. The new Kanban Guide for Scrum Teams outlines this extension and introduces metrics like cycle time, throughput, WIP, and work item age to help maximise value delivery. Velocity is presented as an optional metric, with throughput suggested as a more insightful measure for advanced teams. Attending the two-day Professional Scrum with Kanban (PSK) class offers deeper understanding and a formal certification for applying these combined approaches. The visual image used is of a bridge connecting Scrum and Kanban, symbolising the link between the two methods.
- [Work can flow across the Sprint boundary](https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/): Scrum does not prohibit work from flowing across Sprint boundaries; enabling such flow, when it does not compromise the Sprint Goal, increases delivery speed, throughput, and adaptability to feedback. The Sprint is mainly a planning container, not always a delivery boundary, and advanced techniques like Continuous Delivery and use of Kanban can strengthen Scrum practices. Strategic Sprint Goals must focus on measurable customer or business outcomes, with clear, Done increments ensuring transparency and supporting informed investment decisions. Critical engineering practices such as feature toggles, refactoring, and Test Driven Development enable frequent validation, early delivery, and manage unfinished work crossing Sprints. In Scrum, incomplete Backlog Items are not the same as "undone" work, and work can flow between Sprints as long as transparency, empirical control, and the achievement of Sprint Goals are maintained.
- [Professional Scrum is for everyone in your organisation](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-is-for-everyone-in-your-organisation/): Professional Scrum is effective when everyone in an organisation, not just software teams, participates and gains a shared understanding of its principles and practices. At Healthgrades, 147 people from across engineering took the Professional Scrum Foundations class together, which broke down misconceptions about Scrum that had built up over eight years and created a new sense of empowerment and shared purpose. Including everyone, from developers to executives to warehouse staff, encouraged vital conversations and surfaced a backlog of organisational changes needed to remove obstacles to value delivery. As a result, participants became change agents, equipped with both practical knowledge and a tangible list of improvements to pursue. The experience showed that involving the whole organisation in Scrum provides the catalyst for authentic, lasting agility.
- [Create your own path to Organisational Agility](https://engineering-leadership.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/): A one-size-fits-all agile framework is unlikely to meet your organisation’s needs because each company is unique and must create its own incremental path to agility. Begin with a clear, living vision that focuses on the ‘whats’ and ‘whys’ rather than the ‘hows’, and ensure it is communicated organisation-wide. Form a guiding coalition—a Change Team representing engineering, product, commercial, and leadership—to own and drive the organisational change backlog. All employees, from the warehouse forklift driver to the CEO, should participate in broad-based Scrum training, which both unifies understanding and helps workers identify impediments to value delivery. In one example, the Professional Scrum Foundations class gathered diverse staff to create backlog items, ensuring change is grounded in direct experience and full engagement.
- [Round up for 2017 and beyond: Agility, DevOps, and Everything In-between](https://engineering-leadership.hinshelwood.com/articles/round-up-for-2017-and-beyond-agility-devops-and-everything-in-between/): The author reflects on a busy year of speaking at global conferences and delivering workshops focused on Agile, Scrum, and DevOps, noting that training provides more lasting value to clients than consulting. Key insights include the importance of stepping out of comfort zones, sharing practical knowledge to empower teams, and prioritizing structured, engaging training. Development managers should consider investing in team training to build internal capability and drive better outcomes.
- [Professional Scrum Training for the Ghana Police Service](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/): Professional Scrum Foundations classes were run for the first time in Ghana with officers from the Ghana Police Service, many of whom had never heard of Scrum or Agile and had little IT experience. Despite their unfamiliarity, the officers worked in groups to build working software, creating a website as part of the training, and took pride in their achievements. The training revealed the importance of practical, iterative learning and adapting the material to the students’ context, including connecting Scrum concepts to police work. Key lessons included the value of framing the course for non-technical participants and providing materials in advance, as well as the insight that organisational change requires involvement from people at all levels, not just leadership. The experience showed that even complex, creative tasks like software development can be approached successfully by diverse teams using Scrum.
- [Professional Organisational Change at the Ghana Police Service](https://engineering-leadership.hinshelwood.com/articles/professional-organisational-change-at-the-ghana-police-service/): The Ghana Police Service has struggled with ineffective and temporary reforms, leading to low public confidence and recurring problems. A bold, lasting transformation is now underway, driven by top-level commitment from both the Inspector General of Police and the President of Ghana, aiming to make the Service world class. The transformation hinges on servant leadership, a clear vision with metrics, a structured framework based on Scrum's Agility Path Guide, and a national network of empowered change agents. In a striking image, the Inspector General’s ‘war room’ uses both Kanban and Scrum boards to plan and track change, fostering transparency and collaboration. The existing command and control culture is being replaced by servant leadership, reflecting the Service’s modern, highly educated workforce and global best practice.
- [Scrum Tapas: Scrum and Continuous Delivery](https://engineering-leadership.hinshelwood.com/articles/scrum-tapas-scrum-and-continuous-delivery/): Scrum and Continuous Delivery work well together and can enhance each other’s benefits. Using both allows teams to deliver value more frequently and respond to change faster. Consider combining these approaches to improve your team's delivery speed and adaptability.
- [VSTS Sync Migration Tool Update and Bugfix](https://engineering-leadership.hinshelwood.com/articles/vsts-sync-migration-tool-update-and-bugfix/): The VSTS Sync Migration Tool has been updated with new features like work item history and query migration, plus important bug fixes such as resolving closed date issues. Community contributions have improved bulk updates and project migrations, and users now receive update notifications automatically. Development managers should install the latest version to benefit from these enhancements and stay informed about future updates.
- [Scrum Tapas: The Importance of Professionalism](https://engineering-leadership.hinshelwood.com/articles/scrum-tapas-the-importance-of-professionalism/): Professionalism is essential for building great software, yet many teams lack it by not following best practices or core values. Teams that commit to professional standards and engineering excellence deliver better results. Development managers should ensure their teams adopt and uphold professional practices to improve software quality.
- [Choosing a Process Template for your Team Project](https://engineering-leadership.hinshelwood.com/articles/choosing-a-process-template-for-your-team-project/): Select the Microsoft Visual Studio Scrum process template when setting up a new Team Project in VSTS or TFS if you want true agility and minimal friction, even if you are not strictly following Scrum. The Agile and CMMI templates, based on the Microsoft Solution Framework, embed anti-patterns such as separating bugs from the backlog and enforcing practices like mandatory Story Points and User Stories, which create unnecessary friction and constrain teams. The Scrum template is distinct because it is lightweight, flexible, and includes all work items—including bugs—on the backlog by default. Common, easy customisations to the Scrum template include adding fields for "Completed & Original Estimate" and tailoring requirement types, allowing teams to better align the tool with their real-world needs without locking them into rigid, MSF-based processes. Making the wrong template choice can lead to long-term friction that hinders a team's ability to inspect, adapt, and embrace agile practices.
- [Government Cloud First policy](https://engineering-leadership.hinshelwood.com/articles/government-cloud-first-policy/): Despite the UK Government's clear Cloud First policy mandating public cloud for central government services, many public sector agencies remain hesitant about adopting cloud solutions. The policy prioritizes public cloud and encourages SaaS, aiming to dispel fears about security and reliability. Development managers should prioritize cloud-based solutions for government projects to align with policy, support business agility, and simplify infrastructure management.
- [Kalabule or a Professional at Agile in Africa](https://engineering-leadership.hinshelwood.com/articles/kalabule-or-a-professional-at-agile-in-africa/): Many software teams in Africa still operate unprofessionally, delivering poor results and blaming management, but customers should demand regular delivery of working software that meets their needs. Adopting true professionalism requires more than just following Scrum rituals or engineering practices; it means embracing values like courage, focus, commitment, respect, and openness. Development managers should lead by example and foster these values to raise industry standards and deliver better outcomes.
- [VSTS Sync Migration Tools](https://engineering-leadership.hinshelwood.com/articles/vsts-sync-migration-tools/): VSTS Sync Migration Tools help teams move work items, test plans, and team structures between TFS and VSTS or consolidate projects without migrating code. The tool focuses on essential data like work items and test configurations, with ongoing improvements based on user needs. Development managers can use or contribute to these free tools to streamline migrations and reduce manual setup when moving to VSTS.
- [Scaling Professional Scrum with Visual Studio Team Services](https://engineering-leadership.hinshelwood.com/articles/scaling-professional-scrum-with-visual-studio-team-services/): 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.
- [Open-source with VSTS or TFS and Github for better DevOps](https://engineering-leadership.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/): Using both VSTS (or TFS) and Github together allows you to leverage VSTS for full-featured DevOps and agile practices while still publishing open source code to Github. You can set up automated synchronisation of your chosen branches between VSTS and Github using two simple Git commands that run as build steps—one to pull from Github and one to push from VSTS—with authentication handled via personal access tokens. Configuration is flexible, supporting options like full, manual, or selective synchronisation depending on your workflow. This setup lets you maintain private repositories in VSTS, keep public code on Github, and easily handle contributions from both platforms, with the process as simple as adding two command line tasks in your VSTS build definition.
- [Migrating from Codeplex to Github](https://engineering-leadership.hinshelwood.com/articles/migrating-from-codeplex-to-github/): Migrating a Codeplex repository to GitHub can be challenging, with the GitHub Import tool proving unreliable and failing to preserve project structure or branches. Using Git-TF with Chocolatey offers a better solution, allowing selection of specific source folders and deep cloning with full history retrieval. Migrating wiki pages also needs extra steps, since Codeplex uses HTML while GitHub uses Markdown, but an online converter can help. While releases and issues may still require manual handling, this method covers the essential migration steps and results in a complete, functional GitHub repository. The described approach was successfully used to move a WordPress blog migration project.
- [Mapping your Windows Special Folders to OneDrive for Business - Ultimate Backup](https://engineering-leadership.hinshelwood.com/articles/mapping-your-windows-special-folders-to-onedrive-for-business-ultimate-backup/): Mapping your Windows special folders like Documents and Desktop to OneDrive or OneDrive for Business ensures your files are automatically backed up to the cloud and accessible from any device. This setup protects against data loss from hardware failure or theft and simplifies working across multiple computers. Development managers should consider configuring this for their teams to improve data security and seamless access.
- [Moving OneDrive for Business files to a different drive](https://engineering-leadership.hinshelwood.com/articles/moving-onedrive-for-business-files-to-a-different-drive/): If your OneDrive files are taking up too much space on your main drive, you can move them to another drive by unlinking your account, copying the files to the new location, and then relinking OneDrive to that folder. This avoids re-downloading large amounts of data and frees up significant space without risking your system recovery setup. Development managers should consider this approach to optimize storage and maintain system reliability for their teams.
- [Agile in Africa 2016](https://engineering-leadership.hinshelwood.com/articles/agile-in-africa-2016/): Agile in Africa 2016 brought together genuine Agile experts to West Africa, moving beyond past efforts that focused on profit rather than real improvement. Speakers invested their own time and resources, and the event featured multiple days of sessions, strong community engagement, and positive social impact. Development managers interested in authentic Agile transformation and networking in Africa should consider attending or viewing the recorded sessions.
- [Branch Policies for TFVC](https://engineering-leadership.hinshelwood.com/articles/branch-policies-for-tfvc/): 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.
- [Professional Scrum Courses for 2016 in Oslo, Norway](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-courses-for-2016-in-oslo-norway/): 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.
- [Access denied for orchestration plan on Build](https://engineering-leadership.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/): When setting up a TFS build agent for a high-volume customer, a permissions error blocked builds because the "Project Collection Build Service" 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 "Project Build Service" and "Project Collection Build Service" 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.
- [The High of Release](https://engineering-leadership.hinshelwood.com/articles/the-high-of-release/): 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.
- [Big Scrum: All you need and not enough](https://engineering-leadership.hinshelwood.com/articles/big-scrum-all-you-need-and-not-enough/): 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.
- [Big Scrum: Are you doing mechanical Scrum](https://engineering-leadership.hinshelwood.com/articles/big-scrum-are-you-doing-mechanical-scrum/): 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.
- [How to rename a Team Project in TFS 2015](https://engineering-leadership.hinshelwood.com/articles/how-to-rename-a-team-project-in-tfs-2015/): TFS 2015 finally allows you to rename Team Projects easily through the admin page, but you need to be a Team Project Administrator and ensure your clients are updated for best compatibility. Renaming is quick and minimally disruptive, though older Visual Studio versions may need extra steps like clearing cache. Test the rename process on less critical projects first to assess any impact before applying it more broadly.
- [Install TFS 2015 today](https://engineering-leadership.hinshelwood.com/articles/install-tfs-2015-today/): Many organisations are migrating from on-premises TFS to Visual Studio Online for easier management, but some remain with TFS due to concerns about the cloud. TFS 2015 introduces significant improvements, including a much smaller installation ISO under 500mb and a streamlined installation that no longer requires a restart, even when installing a new version of .NET. The install process is simplified with options for Basic, Full, Application Tier Only, or Upgrade, and the Basic option will automatically set up SQL Express and a default build agent for quick starts. Notably, TFS 2010 support ends at the end of July, so upgrading to TFS 2015 is recommended. The new task-based build system allows easy configuration of multiple agents, and once installed, you create new team projects using Visual Studio Team Explorer.
- [Upgrading to TFS 2015 in production - DONE](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-tfs-2015-in-production-done/): A production TFS server was successfully upgraded onsite in London to TFS 2015, likely one of the first such upgrades outside of Microsoft consulting’s internal deployments. Thorough preparation included both full SQL backups taken with the server offline and a VM snapshot, and the upgrade itself took just minutes for databases totalling 9GB, though the process depends on hardware. Key steps included verifying free disk space at least equal to the data size, re-entering service account credentials, and dealing with a non-standard IIS port 80 setup rather than the TFS default of 8080. After manual adjustments to restore this custom IIS configuration post-upgrade, the TFS instance was running smoothly with all new features. TFS 2015, even as a Release Candidate, is fully supported for production via a Go-Live licence.
- [Unable to load task handler PowerShell for task VSBuild](https://engineering-leadership.hinshelwood.com/articles/unable-to-load-task-handler-powershell-for-task-vsbuild/): When setting up TFS 2015's vNext build system on Windows Server Technical Preview, you may encounter a "Unable to load task handler PowerShell for task VSBuild" 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.
- [It's that time again; get ready to upgrade to TFS 2015](https://engineering-leadership.hinshelwood.com/articles/its-that-time-again-get-ready-to-upgrade-to-tfs-2015/): Mainstream support for TFS 2010 ends in July 2015, so you should start planning your upgrade to TFS 2015 now. The upgrade will be complex and time-consuming due to major schema changes, especially for large databases, so run a trial upgrade in a recovery environment to estimate the effort required. Begin preparations early to avoid downtime and ensure continued support for your development teams.
- [Using the Build vNext capabilities and demands system](https://engineering-leadership.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/): 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.
- [ALM Events and public courses in 2015 Q2](https://engineering-leadership.hinshelwood.com/articles/alm-events-and-public-courses-in-2015-q2/): A new schedule of public and online courses covering Visual Studio ALM, TFS, DevOps, and Scrum is now available for the next few months, including both live online and in-person options. Key offerings include DevOps and Scrum Master training, project management with TFS, and TFS administration, with additional appearances at major industry events. Development managers interested in upskilling their teams or themselves should consider booking early, as more sessions may be added if demand is high.
- [Create a Build vNext build definition](https://engineering-leadership.hinshelwood.com/articles/create-a-build-vnext-build-definition/): Microsoft's new Build vNext system for TFS and VSO is a modular and user-friendly build platform, currently available in early preview, which will eventually replace the legacy build system. It offers a range of out-of-the-box tasks, including Android, Xcode, and Visual Studio builds, PowerShell scripting, and Azure deployment, reflecting Microsoft's push for broader technology support. Git repositories are currently the only supported source, including integration with GitHub, and the system simplifies configuration of build steps, triggers, multi-configuration options, and build variable management. A notable feature is the addition of a "Diff" button that gives a full diff of build definition changes, providing better auditability. In early testing, a PowerShell version mismatch was encountered, likely due to using Windows Server Technical Preview, prompting further investigation.
- [My journey into Professional Scrum](https://engineering-leadership.hinshelwood.com/articles/my-journey-into-professional-scrum/): Professional Scrum is at the heart of lasting success in software development, as real progress comes from the people and culture rather than tools or technology. First-hand experience delivering Scrum training worldwide has shown the value of equipping entire organisations, not just teams, so everyone shares a practical understanding of how and why Scrum works. The most memorable class included both warehouse managers and executives learning side by side, demonstrating the power of levelling knowledge across job roles. Off-the-shelf frameworks for scaling Scrum rarely work because every organisation’s culture is unique; instead, teams build agility by creating processes tailored to their situation. True improvement comes from professional individuals and teams willing to adapt, experiment, and take responsibility, using Scrum as a flexible framework for both team and organisational growth.
- [Managing your Azure VM's with your Phone](https://engineering-leadership.hinshelwood.com/articles/managing-your-azure-vms-with-your-phone/): Mobile Azure Manager lets you easily start and stop Azure virtual machines and cloud services from your phone, saving time and reducing costs, especially when managing multiple VMs for training or development. Key features include managing individual VMs or groups, quick access to core information, and responsive support, though cost estimates may be inaccurate. Busy managers can use this app to efficiently control Azure resources on the go and avoid unnecessary cloud expenses.
- [The benefits of Visual Studio Online for the Enterprise](https://engineering-leadership.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/): Visual Studio Online (VSO) provides significant advantages for large enterprises over on-premises TFS, including always up-to-date features, dynamic and secure build services, integrated load testing that can simulate up to 2.5 million users, Application Insights for end-to-end analytics, and robust release management with granular permissions. VSO allows access from anywhere without VPN, seamless integration with Active Directory, and reduces the burden of server maintenance and updates. While some features such as process template customisation and integrated data warehousing are still missing, heavy use of tags and web-based customisation are practical workarounds, and support for European data centres and ISO 27001 certification address common security concerns. With Microsoft delivering new features every three weeks and major systems like the Windows team relying on VSO at scale, organisations gain flexibility and business agility, but a successful move requires substantial cultural change to embrace cloud-based software delivery.
- [Do you need an expert in Visual Studio ALM, TFS, or Scrum?](https://engineering-leadership.hinshelwood.com/articles/do-you-need-an-expert-in-visual-studio-alm-tfs-or-scrum/): An experienced consultant and trainer in Visual Studio ALM, TFS, and Scrum is unexpectedly available for onsite engagements in February due to a client postponement. He offers flexible, value-focused training and consulting for development teams, with rapid setup and a proven track record across Europe and the USA. If you need expert support in these areas next month, consider reaching out to fill this short-term availability.
- [Could not load file or assembly while configuring Build vNext Agent](https://engineering-leadership.hinshelwood.com/articles/could-not-load-file-or-assembly-while-configuring-build-vnext-agent/): If you are testing the new vNext build agent on Windows Server 2012 R2 with Visual Studio 2015 Preview, you may encounter a "Could not load file or assembly" error due to a DLL version mismatch and strong name validation. This issue only occurs with the Preview version and should resolve in future releases. As a temporary fix, disable strong name validation by running "sn -Vr *,*" on the server, but only do this in test environments, not in production.
- [Configure a Build vNext Agent](https://engineering-leadership.hinshelwood.com/articles/configure-a-build-vnext-agent/): Microsoft’s new vNext build system for TFS and Visual Studio Online is now available in early preview, introducing a modular pool-based agent model that replaces the old collection/controller approach. Agents can be shared across collections using pools and secured with queues, streamlining permissions and priorities; for example, a "release" queue can be set to service release builds first. Setting up a vNext Build Agent currently requires creating your own build server, with installation handled by downloading a ZIP and running a PowerShell script, which is preferred over MSI installers. Visual Studio 2013 or 2015 must be installed on the VM to avoid errors such as "BrowserFlowException: SP324095." Once configured, the agent runs as a Windows Service and appears in the web administration interface, letting you manage its capabilities.
- [Creating nested teams in Visual Studio ALM](https://engineering-leadership.hinshelwood.com/articles/creating-nested-teams-in-visual-studio-alm/): To represent nested teams in Visual Studio ALM or TFS, use a single team project with a carefully designed Area Path hierarchy. For example, the company Awesomecorp manages two products, Omniworks and Multiplex, within a single team project, creating Area Paths for each product and their teams. Teams are linked to specific nodes in this hierarchy and can include sub-areas to control backlog and board visibility. In Team Field configurations, teams simulate hierarchy by owning multiple flat values, but this becomes complex as team structures grow. This approach offers flexibility for managing portfolios and focusing dashboards at different organisational levels.
- [Why should I use Visual Studio ALM](https://engineering-leadership.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/): Visual Studio ALM offers a comprehensive Application Lifecycle Management platform that covers requirements, project, and change management, as well as code, build, release, quality, feedback, defect, lab, and analytics management. Replacing Visual Studio ALM with tools like Git and Jenkins covers only a small part of its full functionality, leading to a loss of over 90% of capabilities. The key decision areas are what features you are replacing, gaining, and losing with a new toolset. An independent Gartner comparison places Visual Studio ALM as the top ALM platform, far ahead of piecemeal solutions like Git and Jenkins. The platform allows teams to start small and scale, eliminating the complexity and integration challenges of building a custom ALM toolchain from individual tools.
- [Join a machine to your azure hosted domain controller](https://engineering-leadership.hinshelwood.com/articles/join-a-machine-to-your-azure-hosted-domain-controller/): To join a machine to your Azure-hosted domain controller, make sure the machine is connected to the correct virtual network and that your domain’s DNS server is set for that network, so the guest machine can find the domain. Use the 'connect' button on the Azure VM dashboard to remote into the server, where DHCP should configure DNS settings automatically. From the system settings, select "Domain", enter your domain name such as "env.nakedalmweb.wpengine.com", and provide a domain admin account to join. After rebooting, you can log in using your domain credentials. Maintaining only Azure and Office 365 without on-premises servers can add complexity, as joining machines directly to Azure Active Directory is not yet seamless.
- [Understanding TFS migrations from on-premise to Visual Studio Online](https://engineering-leadership.hinshelwood.com/articles/understanding-tfs-migrations-from-on-premise-to-visual-studio-online/): Migrating from on-premise TFS to Visual Studio Online (VSO) involves several scenarios, including team project to team project moves, consolidating multiple team projects to reduce technical debt, splitting team projects for organisational changes, and consolidating different source control platforms like Perforce, Git, and SVN onto VSO. The process is often more complicated than expected, and currently, the tools and guidance available are limited. A common request is consolidating team projects during migration, especially when upgrading from TFS 2012 or later. Detailed scenarios and tool maps are provided to help teams address specific migration challenges, and a walkthrough for a basic migration using Excel and tip code copy will soon be available.
- [Create log entries in Release Management](https://engineering-leadership.hinshelwood.com/articles/create-log-entries-in-release-management/): Creating log entries in Release Management can be unexpectedly difficult, especially when trying to track what goes right during a deployment. Standard output commands like "Write-Host" and "Write-Output" do not produce visible logs in Release Management, even though they work in normal build scripts. An attempt to use these results in either missing log entries or a nasty error message about the host function not being implemented. To ensure messages appear in the logs, use "Write-Verbose" with the "-verbose" switch; this provides a clear output, creating a useful success log for reference. Success logs are just as valuable as failure logs for later review.
- [NDC London 2014: Why TFS no longer sucks and VSO is awesome](https://engineering-leadership.hinshelwood.com/articles/ndc-london-2014-why-tfs-no-longer-sucks-and-vso-is-awesome/): 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.
- [Create a Release Management pipeline for Professional Developers](https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/): Setting up a robust Release Management pipeline with Team Foundation Server (TFS) and Visual Studio Online (VSO) is now far easier and richer in features than in previous versions. By using the Fabrikam Fibre web application as an example, this guide walks through creating a continuous integration and deployment pipeline, from source control in Git to automated builds and staged releases in Azure environments. The process highlights key improvements like build triggers, environment parameterisation, Application Insights integration, and manual approval gates. A notably concrete detail is mapping port 80 to 1337 on the Azure VM to get Fabrikam Fibre running and accessible after deployment. Although there are setup pains and time spent resolving errors, the resulting pipeline allows Professional Developers to reliably automate end-to-end deployments, with environment-specific configuration and continuous feedback.
- [Create a Standard Environment for Release Management in Azure](https://engineering-leadership.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/): Setting up a standard environment for Release Management in Azure is now straightforward and cost-effective, requiring only a credit card and minimal setup. The process uses Visual Studio Online, Release Management for VSO, Visual Studio 2015 Preview, Git, and Application Insights to demonstrate an end-to-end workflow, including automated deployments tied to each check-in, and bug resolution from report to fix. By choosing Azure Virtual Machines and configuring storage, networks, and analytics, it is possible to closely emulate on-premises environments without hardware or domain setup. Using the old Azure portal provides better control over naming and resource management, such as ensuring the right DNS for cloud services. Setting up a feedback environment cost less than £2 per day for a VM with 2 cores and 3.5GB RAM, making it practical and scalable for development teams.
- [Configure a DNS server for an Azure Virtual Network](https://engineering-leadership.hinshelwood.com/articles/configure-a-dns-server-for-an-azure-virtual-network/): To ensure all servers in an Azure virtual network can join a configured domain, set up a DNS server with a fixed internal IP and register it in the network settings. Assign this DNS server to the virtual network so any new or rebooted machines automatically use it for domain joining. Development managers should ensure DNS configuration is part of their Azure network setup to support domain integration and future scalability.
- [Microsoft Surface 3 unable to boot from USB](https://engineering-leadership.hinshelwood.com/articles/microsoft-surface-3-unable-to-boot-from-usb/): When a Surface Pro 3 failed to boot into Windows 10 or Recovery Mode, multiple attempts to refresh or restore the system using USB recovery drives repeatedly failed, even though the same USB drives worked on other Surface devices. After extensive troubleshooting, it turned out the Surface Pro 3 would only boot from a USB drive if the drive was labelled "BOOTME", a requirement not documented in official Microsoft instructions or created by standard Windows recovery tools. Renaming the USB drive to "BOOTME" immediately resolved the issue. Even USB drives created directly by Windows and called "Recovery" would not work unless renamed, making this a critical detail for anyone needing to recover a Surface Pro 3.
- [Move your Azure VM to a Virtual Network](https://engineering-leadership.hinshelwood.com/articles/move-your-azure-vm-to-a-virtual-network/): If you need to move an existing Azure VM to a virtual network, you cannot do it directly; you must delete the VM (keeping the disks), create a new virtual network in the correct region, and then redeploy the VM using the existing disks and attach it to the new network. This process allows your VM, such as a domain controller, to communicate with other machines in the same network. Plan your network setup before VM deployment to avoid this manual migration.
- [Configuring a DC in Azure for AAD integrated Release Management](https://engineering-leadership.hinshelwood.com/articles/configuring-a-dc-in-azure-for-aad-integrated-release-management/): Setting up a domain controller (DC) in Azure for Azure Active Directory (AAD) integrated Release Management allows realistic cloud demos by running all infrastructure in Azure. Creating the DC involves provisioning a cost-effective Azure virtual machine, configuring it as a Windows Server with Active Directory and DNS roles, and ensuring it has a static IP for DNS resolution. For installation and interactive configuration, an A2 size VM offers enough power, which can be scaled down to A0 once set up to minimise costs, estimated at 11p per day. The process includes promoting the VM to a new domain forest, typically named using a subdomain like env.mydomain.com, and results in all local users becoming domain users after reboot. Directly joining any machine to an AAD domain is not currently supported, so this approach uses traditional static domains synced with AAD.
- [Installing Visual Studio 2015 side by side with 2013 on Windows 10](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2015-side-by-side-with-2013-on-windows-10/): You can install Visual Studio 2015 alongside 2013 on Windows 10 without issues, but make sure to install the Windows 10 Universal C Runtime first to avoid installation errors. The 2015 version brings updated tools like the latest Git and improved Android emulation, and selecting all install options is recommended to avoid missing features. This setup is stable for most users, and you can run both versions concurrently for development and testing.
- [Could not find mappings for all states defined in 'Test Suit' work item type](https://engineering-leadership.hinshelwood.com/articles/could-not-find-mappings-for-all-states-defined-in-test-suit-work-item-type/): 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 "In process" instead of "In Process." 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.
- [Use corporate identities with existing VSO accounts](https://engineering-leadership.hinshelwood.com/articles/use-corporate-identities-with-existing-vso-accounts/): Configuring Active Directory Federated Services (ADFS) allows seamless single sign-on across Office 365, SharePoint Online, and Visual Studio Online (VSO), linking your corporate identity to your existing VSO accounts. To migrate users and maintain history, your Microsoft ID must match your corporate ID, and users should add their corporate email as an alias, switching it to primary before the transfer; this process has a 30-day waiting period. When integrating with Azure Active Directory, only users configured as accounts or foreign principals will retain access, so check all relevant users are listed in both AD and VSO. After linking, you will sign in with your organisational ID rather than a Microsoft ID, and VSO provides full integration with your Azure Active Directory. Setting up ADFS and Azure AD integration is a significant move towards unified, trusted identities in the cloud and on-premises environments.
- [TFS Build reports Licencies.licx: unable to load type](https://engineering-leadership.hinshelwood.com/articles/tfs-build-reports-licencies-licx-unable-to-load-type/): 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.
- [Upcomming Scrum at Scale Workshop from Scrum.org](https://engineering-leadership.hinshelwood.com/articles/upcomming-scrum-at-scale-workshop-from-scrum-org/): 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.
- [Reuse your MSDN benefits with your Org ID](https://engineering-leadership.hinshelwood.com/articles/reuse-your-msdn-benefits-with-your-org-id/): To move your MSDN benefits from a personal Microsoft ID to your organizational account, you need to cancel any existing MSDN subscriptions linked to your old account, which will remove access to resources created there. After cancellation, you can reactivate your benefits under your organizational account for easier management and single sign-on. Be aware that this process deletes all previous resources, so plan accordingly before proceeding.
- [Uncommitted changes messing up your sync in Git with Visual Studio](https://engineering-leadership.hinshelwood.com/articles/uncommitted-changes-messing-up-your-sync-in-git-with-visual-studio/): 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.
- [NDC London: Second Look, Team Foundation Server & VSO](https://engineering-leadership.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/): The session "Second Look, Team Foundation Server & VSO" at NDC London targets experienced developers who tried TFS before 2012 and remain sceptical about its capabilities. The presentation offers a fast-paced, demo-driven walkthrough of new features and improvements since TFS 2012, such as Storyboarding, Agile Project and Portfolio Management, advanced ALM features for coders, integrated test management tools, and seamless release management to production with detailed application monitoring. Two deep-dive brownfield scenarios will show the full end-to-end process of implementing a new feature or fixing a bug, including steps from backlog creation to release validation and analytics review. Attendees can offer input on which features or scenarios to prioritise, and free consulting will be available during the conference for focused problem-solving. If you are working with the Microsoft stack, these demonstrations highlight why TFS is now a premier ALM platform.
- [Move an Azure storage blob to another store](https://engineering-leadership.hinshelwood.com/articles/move-an-azure-storage-blob-to-another-store/): Moving a VHD between Azure storage accounts is more complex than expected because you must authenticate separately to each account, even with an authenticated session. The process requires extra PowerShell scripting to set up contexts for both source and target accounts and initiate the copy. Once set up, you can reuse the script to move VHDs as needed, so consider saving it for future migrations.
- [Bug in the Visual Studio Git integration that results in a merge conflict](https://engineering-leadership.hinshelwood.com/articles/bug-in-the-visual-studio-git-integration-that-results-in-a-merge-conflict/): A bug in Visual Studio 2013.3'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.
- [Creating training virtual machines in Azure](https://engineering-leadership.hinshelwood.com/articles/creating-training-virtual-machines-in-azure/): Setting up training environments for a technical course is much easier using Azure, though uploading large VHDs and configuring storage can be time-consuming and require troubleshooting. Once the VHD is uploaded and a template image is created, you can automate or manually create multiple VM instances with the right specs for your needs. Using Azure for training labs is cost-effective if you manage VM uptime carefully, and the process can be streamlined further with PowerShell automation if done regularly.
- [Bruce Lee on Scrum and Agile](https://engineering-leadership.hinshelwood.com/articles/bruce-lee-on-scrum-and-agile/): The message draws on Bruce Lee's philosophy to highlight that Scrum and Agile are tools meant to guide teams, not rigid frameworks to be followed blindly. Success comes from understanding the core principles and adapting them to fit your team's unique context, rather than becoming attached to the method itself. The closer your process aligns with true agility, the less waste and complexity you will encounter. Managers should focus on learning and mastering the principles, then evolving and personalizing their approach to continuously deliver value to customers. Use Scrum and Agile as starting points but ultimately develop your own effective process.
- [Agility and Windows 10: Upgrading my Surface Pro 2](https://engineering-leadership.hinshelwood.com/articles/agility-and-windows-10-upgrading-my-surface-pro-2/): Microsoft has begun shifting Windows development to an agile, continuous delivery model, with Windows 10 Technical Preview offering frequent updates and faster user feedback. This change follows the success of agile practices in teams like Visual Studio and Team Foundation Server, moving from lengthy release cycles to updates every few weeks. Early adopters, especially those comfortable troubleshooting, are encouraged to join the preview, test new features, and provide feedback to help steer product direction. While the upgrade process is fairly smooth, users can expect some rough edges as Microsoft refines the experience; participation is best suited to those not afraid of instability. Development managers should consider how continuous feedback and iterative delivery can improve both product quality and responsiveness to user needs.
- [Install of TFS 2013.3 with SharePoint 2013 on Windows Server 2012 R2 Update 1](https://engineering-leadership.hinshelwood.com/articles/install-of-tfs-2013-3-with-sharepoint-2013-on-windows-server-2012-r2-update-1/): This article details the process and lessons from installing TFS 2013.3 with SharePoint 2013 on Windows Server 2012 R2 Update 1, stressing the importance of starting with a clean operating system to avoid misconfigured environments. Key insights include the need to manually install SharePoint Foundation 2013 Service Pack 1 for compatibility with Server 2012 R2 and ensuring all dependencies like Reporting Services and full text search are properly configured, not merely installed. The author highlights that readiness checks in TFS setup help surface issues early, saving frustration. Development managers should mandate clean server builds and verify prerequisites before project-start to streamline installation and reduce post-install fixes.
- [Yorkhill Ice Bucket Challenge](https://engineering-leadership.hinshelwood.com/articles/yorkhill-ice-bucket-challenge/): A personal account of taking the ALS Ice Bucket Challenge to support Yorkhill Children's Charity, highlighting a family’s experience with childhood brain surgery and fundraising.
- [Migrating source from Perforce to Git on VSO](https://engineering-leadership.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/): 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.
- [You can't use WITADMIN on versions older than TFS 2010](https://engineering-leadership.hinshelwood.com/articles/you-cant-use-witadmin-on-versions-older-than-tfs-2010/): Explains troubleshooting WITADMIN errors with TFS versions, highlighting the need for TFS 2010 SP1 or newer for compatibility with work item type changes.
- [Avoid the Bug as Task anti-pattern in Azure DevOps](https://engineering-leadership.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/): 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.
- [Merge Team Projects into one in TFS](https://engineering-leadership.hinshelwood.com/articles/merge-team-projects-into-one-in-tfs/): Step-by-step guide to merging multiple TFS Team Projects into one, covering TFS Integration Tools setup, configuration, work item and source control migration, and best practices.
- [Maven release perform tries to do a Get to a workspace sub folder in TFS](https://engineering-leadership.hinshelwood.com/articles/maven-release-perform-tries-to-do-a-get-to-a-workspace-sub-folder-in-tfs/): Explains issues with Maven release perform in TFS workspaces, causes of build failures, and solutions for workspace mapping, concurrency, and label handling during migration.
- [Avoid the pick-n-mix branching anti-pattern](https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/): 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.
- [The value of an independent Scotland for me](https://engineering-leadership.hinshelwood.com/articles/the-value-of-an-independent-scotland/): Personal reflections on Scottish independence, exploring self-determination, media bias, economic control, immigration, and the long-term value for future generations.
- [Maven release prepare fails with detected changes in Jenkins](https://engineering-leadership.hinshelwood.com/articles/maven-release-prepare-fails-with-detected-changes-in-jenkins/): 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.
- [Traveling for work and the Dell Venue 8](https://engineering-leadership.hinshelwood.com/articles/traveling-for-work-and-the-dell-venue-8/): A review of switching to the Dell Venue 8 Pro for frequent business travel, covering device performance, workflow changes, and practical pros and cons for mobile work.
- [How to delete work items from TFS or VSO](https://engineering-leadership.hinshelwood.com/articles/how-to-delete-work-items-from-tfs-or-vso/): Explains how to permanently delete work items from TFS or VSO using witadmin or C# code, including safety tips and batch deletion for large numbers of items.
- [Run a router on Hyper-V](https://engineering-leadership.hinshelwood.com/articles/run-a-router-on-hyper-v/): Guide to running router firmware in a Hyper-V VM for reliable DHCP and internet access on restrictive networks, avoiding MAC/IP limits and external devices.
- [Getting a service account for VSO with TFS Service Credential Viewer](https://engineering-leadership.hinshelwood.com/articles/getting-a-service-account-for-vso-with-tfs-service-credential-viewer/): Learn how to use TFS Service Credential Viewer to generate service accounts for Visual Studio Online, enabling secure, automated access without frequent re-authentication.
- [TFS Process Template migration script updated](https://engineering-leadership.hinshelwood.com/articles/tfs-process-template-migration-script-updated/): Provides a step-by-step PowerShell script for migrating and updating TFS process templates, including customisations, work item types, categories, and configurations.
- [Access denied user needs label permission in TFS](https://engineering-leadership.hinshelwood.com/articles/access-denied-user-needs-label-permission-in-tfs/): Explains how to resolve "Access denied user needs label permission" errors in TFS by adjusting label permissions at the root folder to allow contributors to create labels.
- [Import Excel data into TFS with History](https://engineering-leadership.hinshelwood.com/articles/import-excel-data-into-tfs-with-history/): Step-by-step guide to importing Excel data into TFS with full history, using VBA to format records as HTML tables for the History field and ensuring no data loss.
- [Mask password in Jenkins when calling TEE](https://engineering-leadership.hinshelwood.com/articles/mask-password-in-jenkins-when-calling-tee/): Learn how to securely mask passwords in Jenkins logs when using Team Explorer Everywhere (TEE), preventing sensitive credentials from being exposed during build processes.
- [Configuring Jenkins to talk to TFS 2013](https://engineering-leadership.hinshelwood.com/articles/configuring-jenkins-to-talk-to-tfs-2013/): Guide to integrating Jenkins with TFS 2013 using the Team Foundation Server plugin, covering installation, configuration, and key differences from TF Build.
- [Migrating to office 365 from Google Mail](https://engineering-leadership.hinshelwood.com/articles/migrating-to-office-365-from-google-mail/): Step-by-step guide to migrating emails and data from Google Mail to Office 365, covering IMAP, POP, and PowerShell methods, plus challenges and practical solutions.
- [Be a kid again and upgrade to Windows Phone 8.1 Developer Preview](https://engineering-leadership.hinshelwood.com/articles/be-a-kid-again-and-upgrade-to-windows-phone-8-1-developer-preview/): Guide to upgrading to Windows Phone 8.1 Developer Preview, including key features, app recommendations, update steps, and known issues for early adopters.
- [Blogging from 2500 meters](https://engineering-leadership.hinshelwood.com/articles/blogging-from-2500-meters/): A personal account of blogging from the French Alps, discussing challenges of writing and publishing posts using OneNote, Word, and limited devices while travelling.
- [Using multiple email alias with your existing Microsoft ID](https://engineering-leadership.hinshelwood.com/articles/using-multiple-email-alias-with-your-existing-microsoft-id/): Learn how to add, manage, and switch multiple email aliases on a single Microsoft ID, simplifying account access and reducing the need for multiple Microsoft accounts.
- [Does your organisation have both Project Mangers as well as Product Owners?](https://engineering-leadership.hinshelwood.com/articles/does-your-organisation-have-both-project-mangers-as-well-as-product-owners/): Explores the challenges of having both Project Managers and Product Owners in teams, highlighting conflicts, reporting issues, and impacts on agile delivery and team focus.
- [Professional Application Lifecycle Management with Visual Studio 2013](https://engineering-leadership.hinshelwood.com/articles/professional-application-lifecycle-management-with-visual-studio-2013/): Guide to using Visual Studio 2013 for application lifecycle management, covering new ALM features, agile practices, Git integration, and cross-platform development.
- [Should I upgrade to TFS 2013 Update 2?](https://engineering-leadership.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/): Covers new features and upgrade steps for Team Foundation Server 2013 Update 2, including improvements in backlog, test, release, and version management.
- [Upgrade your server to Windows Server 2012 R2 Update 1](https://engineering-leadership.hinshelwood.com/articles/upgrade-your-server-to-windows-server-2012-r2-update-1/): Step-by-step guide to manually installing Windows Server 2012 R2 Update 1, including required update order, restart tips, and post-update checks for server stability.
- [TFS for cross team and cross business line work item tracking](https://engineering-leadership.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/): 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.
- [Metrics that matter with evidence-based management](https://engineering-leadership.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/): Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement.
- [Team Foundation server 2013 Update 2 RC is coming, are you ready?](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-2013-update-2-rc-is-coming-are-you-ready/): Learn about the free Microsoft-supported TFS 2013 Update 2 RC upgrade event, key new features like tag management, and how to register before the deadline.
- [Building a release pipeline with Release Management with Visual Studio 2013](https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/): Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices.
- [Install Release Management 2013](https://engineering-leadership.hinshelwood.com/articles/install-release-management-2013/): Step-by-step guide to installing and configuring Release Management 2013, including Server, Client, and Deployment Agent for Visual Studio and Team Foundation Server.
- [Installing Release Management Server for TFS 2013](https://engineering-leadership.hinshelwood.com/articles/installing-release-management-server-for-tfs-2013/): Step-by-step guide to downloading, installing, and configuring Release Management Server for Team Foundation Server 2013, including offline setup and key configuration tips.
- [Execute Tests with Release Management for Visual Studio 2013](https://engineering-leadership.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/): Learn how to automate test execution during deployments using Release Management for Visual Studio 2013, including setup steps, environment tips, and common issues.
- [Move your Active Directory domain to another server](https://engineering-leadership.hinshelwood.com/articles/move-your-active-directory-domain-to-another-server/): Learn how to transfer an Active Directory domain to a new server, including moving FSMO roles and the Global Catalogue, to ensure domain services remain functional.
- [Installing TFS 2013 from scratch is easy](https://engineering-leadership.hinshelwood.com/articles/installing-tfs-2013-from-scratch-is-easy/): Step-by-step guide to installing and configuring TFS 2013 using Basic or Standard options, including SQL setup, SharePoint integration, and reporting features overview.
- [Change the Release Management Server that your Client connects to](https://engineering-leadership.hinshelwood.com/articles/change-the-release-management-server-that-your-client-connects-to/): Learn how to change the Release Management Server URL in the client, including manual config file edits and using a utility tool when the server is unavailable.
- [Installing Release Management Client for Visual Studio 2013](https://engineering-leadership.hinshelwood.com/articles/installing-release-management-client-for-visual-studio-2013/): Step-by-step guide to downloading, installing, and configuring the Release Management Client for Visual Studio 2013, including setup tips and troubleshooting advice.
- [Error adding Active Directory Group to Release Management Client in Visual Studio 2013](https://engineering-leadership.hinshelwood.com/articles/error-adding-active-directory-group-to-release-management-client-in-visual-studio-2013/): Explains how to resolve unhandled exceptions when adding Active Directory groups in Release Management Client for Visual Studio 2013 by selecting the specific domain, not "Entire Directory".
- [Professional Scrum in Immingham, UK](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-in-immingham-uk/): 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.
- [ALM Consulting in Scotland, UK, Scandinavia & Europe](https://engineering-leadership.hinshelwood.com/articles/alm-consulting-in-scotland-uk-scandinavia-amp-europe/): Provides ALM consulting, training, and assessments across Scotland, UK, and Europe, specialising in lean-agile, TFS, Visual Studio, Scrum, and process improvement.
- [Issue [ TFS 2013 ] Value cannot be null. Parameter name: key](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-value-cannot-be-null-parameter-name-key/): Explains how a missing required Team Field in customised TFS 2013 work item templates causes "Value cannot be null" errors, and how to resolve it by making the field mandatory.
- [Visual Studio 2013 and TFS 2013 are released, get yours now! Oh and Windows 8.1…](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2013-and-tfs-2013-are-released-get-yours-now-oh-and-windows-8-1/): Visual Studio 2013, Team Foundation Server 2013, and Windows 8.1 are now available, offering new ALM features, upgrade options, and installation guidance for developers.
- [PowerShell TFS 2013 API #2 - Adding to a GlobalList](https://engineering-leadership.hinshelwood.com/articles/powershell-tfs-2013-api-2-adding-to-a-globallist/): 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.
- [Review Part 3: Two Months with Intel Haswell Harris Beach SDS Ultrabook](https://engineering-leadership.hinshelwood.com/articles/review-part-3-two-months-with-intel-haswell-harris-beach-sds-ultrabook/): Hands-on update after two months using the Intel Haswell Harris Beach SDS Ultrabook, focusing on Windows 8.1 driver fixes, battery life, and real-world productivity.
- [PowerShell TFS 2013 API #1 - Get TfsCollection and TFS Services](https://engineering-leadership.hinshelwood.com/articles/powershell-tfs-2013-api-1-get-tfscollection-and-tfs-services/): 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.
- [Granting access to Team Foundation Server 2012 for diagnostic troubleshooting](https://engineering-leadership.hinshelwood.com/articles/granting-access-to-team-foundation-server-2012-for-diagnostic-troubleshooting/): Learn how to grant users or groups access to TFS 2012 diagnostic activity logs for troubleshooting without full admin rights, using command-line permission settings.
- [Issue [ TFS 2013 ] TF255466 A previous update or installation requires a restart](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-tf255466-a-previous-update-or-installation-requires-a-restart/): Explains how to resolve the persistent TF255466 error when installing TFS 2013 after SQL Server 2012 SP1, caused by pending reboots and requiring hotfix KB2793634.
- [Unable to install Visual Studio 2013 RC on Windows 8.1 Preview](https://engineering-leadership.hinshelwood.com/articles/unable-to-install-visual-studio-2013-rc-on-windows-8-1-preview/): Explains why Visual Studio 2013 RC and Team Foundation Server 2013 RC cannot be installed on Windows 8.1 Preview due to .NET version issues, with suggested workarounds.
- [Upgrading from the TFS 2013 Preview to TFS 2013 RC](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-the-tfs-2013-preview-to-tfs-2013-rc/): Step-by-step guide to upgrading from TFS 2013 Preview to TFS 2013 RC, covering prerequisites, trial upgrades, installation, configuration, and best practices.
- [What's new in Visual Studio 2013 and TFS 2013 RC](https://engineering-leadership.hinshelwood.com/articles/whats-new-in-visual-studio-2013-and-tfs-2013-rc/): Overview of new features in Visual Studio 2013 and TFS 2013 RC, including Team Explorer updates, agile tools, test management, charting, and improved collaboration.
- [Professional Scrum Foundations coming to Glasgow, Scotland in November 2013](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-foundations-coming-to-glasgow-scotland-in-november-2013/): Professional Scrum training courses in Glasgow, Scotland, offer foundational and advanced Scrum skills for teams, Scrum Masters, and developers adopting agile practices.
- [Review Part 2: Developing with Intel Haswell Harris Beach SDS Ultrabook](https://engineering-leadership.hinshelwood.com/articles/review-part-2-developing-with-intel-haswell-harris-beach-sds-ultrabook/): Covers hands-on development with the Intel Haswell Harris Beach SDS Ultrabook, including Windows 8/8.1 compatibility, sensor demos, performance, and setup tips.
- [There is no "do agile" there is only "be agile"](https://engineering-leadership.hinshelwood.com/articles/there-is-no-do-agile-there-is-only-be-agile/): Explores the difference between adopting agile practices superficially and truly embracing agile values, highlighting the need for deep organisational change and continuous learning.
- [Review: The Professional Scrum Masters Handbook](https://engineering-leadership.hinshelwood.com/articles/review-the-professional-scrum-masters-handbook/): A critical review of The Professional Scrum Masters Handbook, highlighting its practical tips for new Scrum Masters and common Scrum misconceptions to avoid.
- [The great Team Foundation Server 2013 Upgrade Weekend](https://engineering-leadership.hinshelwood.com/articles/the-great-team-foundation-server-2013-upgrade-weekend/): Microsoft experts will provide free support for upgrading, installing, or configuring Team Foundation Server 2013 during a special event on 13–15 September 2013.
- [The evolution of naked ALM with Pagelines DMS for Wordpress](https://engineering-leadership.hinshelwood.com/articles/the-evolution-of-naked-alm-with-pagelines-dms-for-wordpress/): Explores migrating from Pagelines Framework to Pagelines DMS on WordPress, highlighting improved customisation, drag-and-drop editing, and streamlined site management.
- [A change for the better #4 - Homecoming](https://engineering-leadership.hinshelwood.com/articles/a-change-for-the-better-4/): Details a move from the USA back to Scotland for family and education reasons, continuing ALM consulting, and plans to offer agile coaching and training in Europe.
- [Integrate reporting and analyses services with Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/): Learn how to add and configure SQL Server Reporting and Analysis Services for Team Foundation Server 2013, including integration steps and enabling data reporting features.
- [Searching for self-organisation](https://engineering-leadership.hinshelwood.com/articles/searching-for-self-organisation/): Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and consistency for effective collaboration.
- [Integrate SharePoint 2013 with Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/integrate-sharepoint-2013-with-team-foundation-server-2013/): Step-by-step guide to integrating SharePoint 2013 with Team Foundation Server 2013, covering installation, configuration, and linking team projects for dashboards and documents.
- [Review Part 1: Unboxing the Intel Haswell Harris Beach SDS Ultrabook](https://engineering-leadership.hinshelwood.com/articles/unboxing-the-intel-haswell-harris-beach-sds-ultrabook/): Hands-on unboxing and first impressions of Intel’s Haswell Harris Beach SDS Ultrabook, highlighting hardware specs, sensors, Windows 8.1 setup, and developer features.
- [Quality enablement to achieve predictable delivery](https://engineering-leadership.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/): Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance.
- [Team Foundation Server 2013 is production ready](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-2013-is-production-ready/): Team Foundation Server 2013 is stable for production use, addressing past update issues with improved agility, technical debt management, and enhanced ALM features.
- [Creating a custom Activity for Team Foundation Build](https://engineering-leadership.hinshelwood.com/articles/creating-a-custom-activity-for-team-foundation-build/): Learn how to create and integrate custom activities in Team Foundation Build, including class library setup, workflow design, argument handling, and build configuration.
- [Video: New with Visual Studio 2013: Manage portfolio backlogs to understand the scope of work](https://engineering-leadership.hinshelwood.com/articles/video-new-with-visual-studio-2013-manage-portfolio-backlogs-to-understand-the-scope-of-work/): Learn how Visual Studio 2013’s portfolio backlog management tools help teams organise work, track epics, and understand project scope for better agile planning.
- [Modelling Teams in Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/modelling-teams-in-team-foundation-server-2013/): Guidance on structuring teams, areas, iterations, source control, and security in Team Foundation Server 2013 to support project management and reporting needs.
- [Issue [ TFS 2013 ] InRelease account requires make requests on behalf of others](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-inrelease-account-requires-make-requests-on-behalf-of-others/): Explains how to resolve InRelease connection errors with TFS 2013 by granting the required "make requests on behalf of others" permission to the service account.
- [Issue [ TFS 2013 ] You get TF400324 when connecting InRelease to TFS](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-you-get-tf400324-when-connecting-inrelease-to-tfs/): 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.
- [Issue [ TFS 2013 ] You need elevated privileges to install InRelease](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-you-need-elevated-privileges-to-install-inrelease/): Learn how to resolve InRelease 3 installation failures on Team Foundation Server 2013 by running the installer with elevated privileges via an elevated command prompt.
- [Does your company culture resemble Survivor?](https://engineering-leadership.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/): Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering teamwork in software development.
- [Create a Portfolio Backlog hierarchy in Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/create-a-portfolio-backlog-hierarchy-in-team-foundation-server-2013/): 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.
- [Issue [ TFS 2013 ] TF50309 when configuring features in Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-tf50309-when-configuring-features-in-team-foundation-server-2013/): Explains how to resolve TF50309 permission errors when configuring features in Team Foundation Server 2012/2013 by assigning the 'Manage process template' permission.
- [Engaging with complexity - Team Foundation Server Edition](https://engineering-leadership.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/): Detailed walkthrough of a complex Team Foundation Server migration, covering remediation, hardware moves, upgrades, user management, and validation in large enterprise environments.
- [Windows 8.1 Preview Issue - The update is not applicable to your computer](https://engineering-leadership.hinshelwood.com/articles/windows-8-1-preview-issue-the-update-is-not-applicable-to-your-computer/): Explains how to fix the "The update is not applicable to your computer" error when installing Windows 8.1 Preview, including region settings and manual update steps.
- [Customise the colours in Team Foundation Server 2013 Agile Planning Tools](https://engineering-leadership.hinshelwood.com/articles/customise-the-colours-in-team-foundation-server-2013-agile-planning-tools/): Learn how to change work item colours in TFS 2013 Agile Planning Tools by editing the Process Configuration XML file and updating hex colour codes for each item type.
- [Issue [ TFS 2013 Preview ] TF400654: Unable to configure Planning Tools](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2013-preview-tf400654-unable-to-configure-planning-tools/): Explains how to resolve TF400654 errors in TFS 2013 Preview by updating process templates to ensure custom fields exist in all required work item types.
- [Upgrading to Visual Studio Scrum 3.0 process template in TFS 2013](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-visual-studio-scrum-3-0-process-template-in-tfs-2013/): Learn how to fully upgrade your Team Foundation Server 2013 projects to the Visual Studio Scrum 3.0 process template, including steps for customisation and data migration.
- [Configure features in Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/configure-features-in-team-foundation-server-2013/): Learn how to enable and configure new features in Team Foundation Server 2013 after upgrading, including using the built-in wizard and handling process template issues.
- [Upgrading to Team Foundation Server 2013](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-team-foundation-server-2013/): Step-by-step guide to upgrading to Team Foundation Server 2013, including backup, installation, configuration, validation, and estimated upgrade times for various scenarios.
- [Installing Visual Studio 2013 on Server 2012](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2013-on-server-2012/): Step-by-step guide to installing Visual Studio 2013 alongside Visual Studio 2012 on Windows Server 2012, covering setup, disk space, login, and configuration options.
- [What's new in Visual Studio 2013 Team Foundation Server Preview](https://engineering-leadership.hinshelwood.com/articles/whats-new-in-visual-studio-2013-team-foundation-server-preview/): Highlights new features in Visual Studio 2013 Team Foundation Server, including agile portfolio management, enhanced team collaboration, and web-based test management.
- [Engaging with complexity - SharePoint Edition](https://engineering-leadership.hinshelwood.com/articles/engaging-with-complexity-sharepoint-edition/): Step-by-step guide to consolidating and upgrading multiple SharePoint 2010 sites to SharePoint 2013, including database migration, firewall setup, and user mapping.
- [Creating a Work Item with defaults in Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/creating-a-work-item-with-defaults-in-team-foundation-server/): Learn how to pre-populate Team Foundation Server work items with default values using template URLs, making it easier for users to create consistent, guided entries.
- [Issue [ TFS 2012.2 ] Detaching collection fails on SnapshotIdentities with object reference not set to an instance of an object](https://engineering-leadership.hinshelwood.com/articles/issue-tfs-2012-2-detaching-collection-fails-on-snapshotidentities-with-object-reference-not-set-to-an-instance-of-an-object/): 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.
- [Issue [ TFS2012.2 ] TF30063 You are not authorized to access](https://engineering-leadership.hinshelwood.com/articles/issue-tfs2012-2-tf30063-you-are-not-authorized-to-access/): Explains how a bug in TFS 2012.2 causes TF30063 authorisation errors after moving servers, and how updating to TFS 2012.3 resolves the issue.
- [SharePoint 2013 Issue - After migration from 2010 user permission not working](https://engineering-leadership.hinshelwood.com/articles/sharepoint-2013-issue-after-migration-from-2010-user-permission-not-working/): After migrating from SharePoint 2010 to 2013, users may face permission and authentication issues due to changes in claims-based authentication settings.
- [SharePoint 2013 Issue - Custom Web Part results in Could not load file or assembly after upgrade](https://engineering-leadership.hinshelwood.com/articles/sharepoint-2013-issue-custom-web-part-results-in-could-not-load-file-or-assembly-after-upgrade/): Explains how to resolve SharePoint 2013 errors loading custom web parts after upgrading from 2010, using site reset or SharePoint Designer to remove missing assemblies.
- [TFS 2012.3 Issue - Scheduled Backups gives a TF400998 when reconfigured](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-3-issue-scheduled-backups-gives-a-tf400998/): After migrating TFS 2012/2013 servers, Scheduled Backups may fail with TF400998 errors due to outdated server references. Disabling and resetting resolves the issue.
- [Writing .NET in PowerShell and creating TFS Teams](https://engineering-leadership.hinshelwood.com/articles/writing-net-in-powershell-and-creating-tfs-teams/): Learn how to use PowerShell to access .NET objects and automate creating Teams in TFS, including referencing assemblies, handling dialogs, and error management.
- [Restore TFS backups from SQL Enterprise to SQL Express](https://engineering-leadership.hinshelwood.com/articles/restore-tfs-backups-from-sql-enterprise-to-sql-express/): Explains how to resolve errors when restoring TFS backups from SQL Enterprise to SQL Express by removing unsupported data compression features from the database.
- [Remote Execute PowerShell against each Windows 8 VM](https://engineering-leadership.hinshelwood.com/articles/remote-execute-powershell-against-each-windows-8-vm/): Explains how to automate running PowerShell scripts on each Windows 8 VM in Hyper-V, including starting VMs, handling credentials, and applying updates remotely.
- [Enable Feedback support for users in Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/enable-feedback-support-for-users-in-team-foundation-server-2012/): Learn how to configure email and permissions in Team Foundation Server 2012 to enable user feedback, including group setup and access control for internal and external users.
- [Quality enablement with Visual Studio 2012](https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/): Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction.
- [TFS Integration Tools - Issue: unable to find a unique local path](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-unable-to-find-a-unique-local-path/): Explains how to resolve the “unable to find a unique local path” error in TFS Integration Tools during source control migration, including causes and practical workarounds.
- [Configure Test Plans for web access in TFS 2012.2](https://engineering-leadership.hinshelwood.com/articles/configure-test-plans-for-web-access-in-tfs-2012-2/): 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.
- [TFS2012.2 - Issue: Object not set to instance of object with TF400898, TF53010 & TF30065](https://engineering-leadership.hinshelwood.com/articles/tfs2012-2-issue-object-not-set-to-instance-of-object-with-tf400898-tf53010-tf30065/): Explains causes and solutions for "Object reference not set to an instance of an object" errors (TF400898, TF53010, TF30065) in TFS 2012.2, fixed in Update 3.
- [TFS 2012 Issue: Get Workspace already exists connecting with VS 2008 or VS 2010](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-get-workspace-already-exists-connecting-with-vs-2008-or-vs-2010/): Explains how to resolve the "workspace already exists" error when connecting Visual Studio 2008 or 2010 to TFS 2012 by manually creating a Server workspace.
- [Naked ALM: starting with why and getting naked](https://engineering-leadership.hinshelwood.com/articles/naked-alm-starting-with-why-and-getting-naked/): Explores the importance of understanding purpose in Application Lifecycle Management, focusing on transparency, customer value, and continuous improvement in software delivery.
- [Release Management with Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/): Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality.
- [Upgrading your process template from MSF for Agile 4 to Visual Studio Scrum 2.x](https://engineering-leadership.hinshelwood.com/articles/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/): 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.
- [New un-versioned repository in TFS 2012](https://engineering-leadership.hinshelwood.com/articles/new-un-versioned-repository-in-tfs-2012/): Explains how TFS 2012 introduced an un-versioned repository for build outputs, reducing version control clutter and offering easier storage and cleanup options for build drops.
- [TFS 2012 Issue: TF215097 an error occurred while initializing a build for build definition](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-tf215097-an-error-occurred-while-initializing-a-build-for-build-definition/): 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.
- [Migration from TF Service to TF Server with the TFS Integration Platform](https://engineering-leadership.hinshelwood.com/articles/migration-from-tf-service-to-tf-server-with-the-tfs-integration-platform/): Guide to migrating data from Team Foundation Service to Team Foundation Server using the TFS Integration Platform, including user and work item mapping steps.
- [Working within a single Team Project with Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/working-within-a-single-team-project-with-team-foundation-server-2012/): Explains how to organise teams, products, and projects within a single Team Project in Team Foundation Server 2012, covering design, security, and workflow considerations.
- [Reserve an Agent for a special build in Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/): 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.
- [Connect a Test Controller to Team Foundation Service](https://engineering-leadership.hinshelwood.com/articles/connect-a-test-controller-to-team-foundation-service/): Explains how to install and configure a Test Controller to connect with Team Foundation Service for automated deployment and testing in cloud-based environments.
- [The Insufficiency of Scrum is a fallacy](https://engineering-leadership.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/): Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes.
- [Visual Studio 2012 Update 2 supports 2010 Build Servers](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2012-update-2-supports-2010-build-servers/): Explains how Visual Studio 2012 Update 2 and later let you use existing 2010 Build Servers with newer TFS, easing upgrades without workflow or OS changes.
- [Batched domain migration with TFS while maintaining Identity](https://engineering-leadership.hinshelwood.com/articles/batched-domain-migration-with-tfs-while-maintaining-identity/): Explains how to batch migrate users between domains in TFS 2012 while preserving user identities, avoiding duplicates, and maintaining traceability during the process.
- [Migrating source code with history to TFS 2012 with Git-Tf](https://engineering-leadership.hinshelwood.com/articles/migrating-source-code-with-history-to-tfs-2012-with-git-tf/): 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.
- [Standard Environments for Automated Deployment and Testing](https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/): Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines.
- [Lab Management Issue: Enable File and Printer Sharing for Lab Management Standard Environments](https://engineering-leadership.hinshelwood.com/articles/lab-management-issue-enable-file-and-printer-sharing-for-lab-management-standard-environments/): Learn how to resolve connectivity issues in Visual Studio Lab Management by enabling File and Printer Sharing on Windows 8 and Windows Server 2012 for standard environments.
- [Windows 8 Issue: Unable to connect to the internet with Hyper-V domain joined guest running on WiFi](https://engineering-leadership.hinshelwood.com/articles/windows-8-issue-unable-to-connect-to-the-internet-with-hyper-v-domain-joined-guest-running-on-wifi/): Fixes internet connectivity issues for Hyper-V domain-joined guests on Windows 8 WiFi by configuring all features in the Network Bridge settings. Suitable for troubleshooting.
- [Chicago Visual Studio ALM User Group 27th March](https://engineering-leadership.hinshelwood.com/articles/chicago-visual-studio-alm-user-group-27th-march/): Demonstration of new Visual Studio 2012 Update 2 features, including Kanban columns, work item tags, and managing teams without areas, at a Chicago user group.
- [Windows Server 2012 Core for dummies](https://engineering-leadership.hinshelwood.com/articles/windows-server-2012-core-for-dummies/): Step-by-step guide to setting up and managing Windows Server 2012 Core using command-line tools, covering remote access, updates, networking, firewall, and domain joining.
- [Guide to ChangeServerId says mostly harmless](https://engineering-leadership.hinshelwood.com/articles/guide-to-changeserverid-says-mostly-harmless/): Explains when and why to use ChangeServerId in TFS, potential issues from duplicate GUIDs, and how to resolve errors using RegisterDB after cloning or upgrading servers.
- [Improvements in Visual Studio ALM from the ALM Summit](https://engineering-leadership.hinshelwood.com/articles/improvements-in-visual-studio-alm-from-the-alm-summit/): 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.
- [The TFS Automation Platform is dead, long live the TfPlugable](https://engineering-leadership.hinshelwood.com/articles/the-tfs-automation-platform-is-dead-long-live-the-tfplugable/): Explores the shift from TFS Automation Platform to TfPlugable, aiming to simplify discovery, deployment, and management of Team Foundation Server extensions.
- [Upgrading to Team Foundation Server 2012 Update 1 in production – DONE](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1-in-production-done/): Step-by-step guide to upgrading Team Foundation Server 2012 to Update 1, including prerequisites, backup, disk space, configuration, troubleshooting, and build server setup.
- [TFS 2012 Update 1 - TF400432 We were unable to connect to the SharePoint Central Administration](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-update-1-tf400432-we-were-unable-to-connect-to-the-sharepoint-central-administration/): Explains how to resolve TF400432 errors during TFS 2012 Update 1 upgrades by correcting mismatched SharePoint Central Administration port settings in TFS configuration.
- [Teams without areas using a team field in TFS](https://engineering-leadership.hinshelwood.com/articles/teams-without-areas-using-a-team-field-in-tfs/): 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.
- [Quality Centre to Team Foundation Server in one complex step](https://engineering-leadership.hinshelwood.com/articles/quality-centre-to-team-foundation-server-in-one-complex-step/): Compares tools for migrating or synchronising data from HP Quality Centre to Team Foundation Server, outlining features, limitations, and best options for each approach.
- [TFS 2012 Update 1 - TF255430: the database was partially upgraded during a failed upgrade](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-update-1-tf255430-the-database-was-partially-upgraded-during-a-failed-upgrade/): Explains how to resolve Team Foundation Server 2012 upgrade failures caused by partial database upgrades, SQL connectivity issues, and Analysis Services errors.
- [Upgrading to Team Foundation Server 2012 Update 1](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1/): Step-by-step guide to upgrading Team Foundation Server to 2012 Update 1, including backup advice, installation process, configuration, and handling common issues.
- [Continuous value delivery with modern business applications](https://engineering-leadership.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/): Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates.
- [Project Server 2013 Issue - TF294012: Cannot access the following enterprise project](https://engineering-leadership.hinshelwood.com/articles/project-server-2013-issue-tf294012-cannot-access-the-following-enterprise-project/): Explains how to resolve the TF294012 error in Project Server 2013 by switching from SharePoint to Project Server permission mode for Team Foundation Server integration.
- [Integrating Project Server 2013 with Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/integrating-project-server-2013-with-team-foundation-server-2012/): Step-by-step guide to installing, configuring, and integrating Project Server 2013 with Team Foundation Server 2012, including setup, extensions, and troubleshooting tips.
- [Project Server 2013 Issue – TF294026: The following work item field does not exist](https://engineering-leadership.hinshelwood.com/articles/project-server-2013-issue-tf294026-the-following-work-item-field-does-not-exist/): Explains how to resolve the TF294026 error in Project Server 2013 and TFS 2012 by adding missing work item fields required for integration with Scrum templates.
- [Project Server 2013 Issue - TF294003: Cannot access the following PWA instance](https://engineering-leadership.hinshelwood.com/articles/project-server-2013-issue-tf294003-cannot-access-the-following-pwa-instance/): Explains how to resolve TF294003 errors when connecting Team Foundation Server 2012 to Project Server 2013 by updating the TFS service account permissions.
- [Professional Scrum Foundations in Alameda, California](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/): 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.
- [Integrate SharePoint 2013 with Team Foundation Server 2012](https://engineering-leadership.hinshelwood.com/articles/integrate-sharepoint-2013-with-team-foundation-server-2012/): Step-by-step guide to installing, configuring, and integrating SharePoint 2013 with Team Foundation Server 2012, including setup, extensions, and project site creation.
- [Application lifecycle management with Office 2013 on Windows 8](https://engineering-leadership.hinshelwood.com/articles/application-lifecycle-management-with-office-2013-on-windows-8/): Explores how Office 2013 on Windows 8 supports application lifecycle management, highlighting touch features, easy installation, and ALM uses for PowerPoint and Excel.
- [Team Foundation Build 2012 Issue - The target CleanWorkspacePackageTempDir does not exist](https://engineering-leadership.hinshelwood.com/articles/team-foundation-build-2012-issue-the-target-cleanworkspacepackagetempdir-does-not-exist/): Explains how to resolve the "CleanWorkspacePackageTempDir does not exist" build error in Team Foundation Build 2012 for upgraded ASP.NET MVC projects by updating project targets.
- [TFS 2012 Agile Planning Tools Issue - nested tasks makes the parent task disappear](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-agile-planning-tools-issue-nested-tasks-makes-the-parent-task-disappear/): 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.
- [The new normal of the modern application lifecycle](https://engineering-leadership.hinshelwood.com/articles/the-new-normal-of-the-modern-application-lifecycle/): Explores how rapid technological change, consumer expectations, and agile practices are reshaping software development, IT roles, and business relevance in the digital era.
- [Automated Testing in a modern application lifecycle](https://engineering-leadership.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/): Explains the role of automated testing in modern software development, covering types, integration, benefits, challenges, and tools for maintaining code quality.
- [Testing in the modern application lifecycle](https://engineering-leadership.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/): Explores challenges and solutions for manual testing in agile software development, focusing on tracking, automation, actionable bugs, and integrated test management tools.
- [Virtual Labs in the modern application lifecycle](https://engineering-leadership.hinshelwood.com/articles/virtual-labs-in-the-modern-application-lifecycle/): Explores how virtual labs help development and operations teams manage, test, and automate complex modern application environments using virtualisation technologies.
- [Visual Studio 2012 Launch RoadShows around the World](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2012-launch-roadshows-around-the-world/): Global Visual Studio 2012 launch events featuring keynotes on IT consumerisation and agile development, with sessions in the UK, US, and Netherlands.
- [TFS Integration Tools - Issue: TFS WIT invalid submission conflict type](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-tfs-wit-invalid-submission-conflict-type/): Explains how to resolve the "TFS WIT invalid submission conflict" in TFS Integration Tools by adjusting permissions and enabling bypass-rule submission for successful configuration.
- [Get a free Team Companion licence for Visual Studio 2012 Launch?](https://engineering-leadership.hinshelwood.com/articles/get-a-free-team-companion-licence-for-visual-studio-2012-launch/): Learn how to claim a free Team Companion licence for Visual Studio 2012 by following simple steps on Twitter, Facebook, or Google+ during a limited-time offer.
- [Requirement management in the modern application lifecycle with TFS](https://engineering-leadership.hinshelwood.com/articles/requirement-management-in-the-modern-application-lifecycle/): Explains how Team Foundation Server supports requirement management in modern app development, including traceability, integration, and partner tools for agile and compliance needs.
- [The evolution of a blog, the race for responsiveness and even a little support from WP Engine](https://engineering-leadership.hinshelwood.com/articles/the-evolution-of-a-blog-the-race-for-responsiveness-and-even-a-little-support-from-wp-engine/): Covers migrating a WordPress blog to improve speed and reliability, comparing hosts, plugin choices, and the impact of WP Engine’s support and performance features.
- [My Team Foundation Server system accounts are changing? What do I do?](https://engineering-leadership.hinshelwood.com/articles/my-team-foundation-server-system-accounts-are-changing-what-do-i-do/): Learn how to update expiring Team Foundation Server service accounts, including steps for TFS, Build, SharePoint, and SQL, to prevent service disruptions.
- [TFS 2012 - Issue: TF30063: You are not authorized to access and can’t trace permissions](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-tf30063-you-are-not-authorized-to-access-and-can-t-trace-permissions/): Explains how a global "deny" permission in TFS 2012 can block SharePoint 2010 access, causing TF30063 errors, and highlights where to check for inherited permission issues.
- [TFS 2012 - Issue: Stuck builds in Team Foundation Build with no build number](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-stuck-builds-in-team-foundation-build-with-no-build-number/): 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.
- [TFS Integration Tools - Issue: Unable to resolve conflict as Access to the path is denied](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-unable-to-resolve-conflict-as-access-to-the-path-is-denied/): Explains how changing WorkSpaceRoot in TFS Integration Tools can cause access denied errors and details how to fix permission issues by updating folder rights.
- [I spell it as Favourite and you as Favorite](https://engineering-leadership.hinshelwood.com/articles/i-spell-it-as-favourite-and-you-as-favorite/): Explains the differences between British and American English spelling, and shows how to switch language settings in Word and PowerPoint using macros for correct spellcheck.
- [Upgrading Windows 7 to Windows 8 remotely over Team Viewer for parents in another country](https://engineering-leadership.hinshelwood.com/articles/upgrading-windows-7-to-windows-8-remotely-over-team-viewer-for-parents-in-another-country/): Step-by-step guide to upgrading a remote Windows 7 PC to Windows 8 using TeamViewer, including tips for handling compatibility, reboots, and helping family abroad.
- [Visual Studio ALM by Martin Hinshelwood is now available on Kindle](https://engineering-leadership.hinshelwood.com/articles/visual-studio-alm-by-martin-hinshelwood-is-now-available-on-kindle/): Martin Hinshelwood’s Visual Studio ALM blog is now available for wireless delivery on Kindle, making it easy to access software development insights on the go.
- [I messed up my checkin failure conflict resolution with the TFS Integration Tools… Now what?](https://engineering-leadership.hinshelwood.com/articles/i-messed-up-my-checkin-failure-conflict-resolution-with-the-tfs-integration-tools-now-what/): Describes troubleshooting and recovering from conflict resolution errors in TFS Integration Tools, including undoing rules and restarting migrations after check-in failures.
- [TFS Integration Tools - Issue: TF10141 No Files checked in as a result of a TFS check-in failure](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-tf10141-no-files-checked-in-as-a-result-of-a-tfs-check-in-failure/): Explains how to resolve TFS Integration Tools check-in failures (TF10141), covering conflict identification, manual resolution steps, and handling workspace issues.
- [TFS Integration Tools - Issue: Sequence contains no elements](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-sequence-contains-no-elements/): Explains how to resolve the "Sequence contains no elements" error in TFS Integration Tools by removing outdated TFS 2008 adapter files to prevent plugin loading issues.
- [TFS Integration Tools - Issue: TF205022: The following path contains more than the allowed 259 characters](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-tf205022-the-following-path-contains-more-than-the-allowed-259-characters/): 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.
- [TFS 2012 - Issue: TF250052: Grant access rights already exists after reconfigure of SharePoint](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-tf250052-grant-access-rights-already-exists-after-reconfigure-of-sharepoint/): Explains how to resolve the TF250052 error in TFS 2012 after reinstalling SharePoint 2010 by refreshing the access rights list to display existing entries.
- [TFS Integration Tools - Issue: TF14009: Cannot merge source into target because the target is underneath source](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-tf14009-cannot-merge-source-into-target-because-the-target-is-underneath-source/): 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.
- [TFS 2012 - Issue: Manage Group Membership missing from admin after TFS 2008 to TFS 2012 Upgrade](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-manage-group-membership-missing-from-admin-after-tfs-2008-to-tfs-2012-upgrade/): Explains how to restore missing group membership management in TFS 2012 after upgrading from TFS 2008 by manually adding permissions using TFS Security commands.
- [TFS Preview - Issue: TF400898 The underlying connection was closed](https://engineering-leadership.hinshelwood.com/articles/tfs-preview-issue-tf400898-the-underlying-connection-was-closed/): Explains the TF400898 error in TFS Preview, its causes, troubleshooting steps, and how a bug in the version control subsystem led to file loss and its resolution.
- [Visual Studio 2012 RTM available & installed](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2012-rtm-available-installed/): Covers installing and upgrading to Visual Studio 2012 RTM and Team Foundation Server, key new features, upgrade tips, common issues, and practical migration advice.
- [TFS Integration Tools - Issue: TFS WIT bypass-rule submission is enabled](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-tfs-wit-bypass-rule-submission-is-enabled/): 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.
- [TFS 2012 Issue: Some features of Team Web Access are not visible to you](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-some-features-of-team-web-access-are-not-visible-to-you/): Explains why some Team Web Access features in TFS 2012 may be hidden due to licence restrictions and how to assign users to the correct access groups for full functionality.
- [TFS 2012 Issue: TF255507: The security identifier (SID) for the following SQL Server login conflicts](https://engineering-leadership.hinshelwood.com/articles/tfs-2012-issue-tf255507-the-security-identifier-sid-for-the-following-sql-server-login-conflicts/): Explains how to resolve the TF255507 SID conflict error in TFS 2012 caused by server renaming, including SQL commands to fix login issues in SQL Server 2012.
- [Install SharePoint 2013 on Windows Server 2012 without a domain](https://engineering-leadership.hinshelwood.com/articles/install-sharepoint-2013-on-windows-server-2012-without-a-domain/): Step-by-step guide to installing SharePoint 2013 on Windows Server 2012 without a domain, including prerequisites, configuration, troubleshooting, and key setup tips.
- [Issue SharePoint 2013: The username is invalid. The account must be a valid domain account](https://engineering-leadership.hinshelwood.com/articles/issue-sharepoint-2013-the-username-is-invalid-the-account-must-be-a-valid-domain-account/): Explains how to resolve the SharePoint 2013 error requiring a domain account by using PowerShell to configure a farm with a local account instead of a domain account.
- [Deploy from Visual Studio 2012 to iOS, Windows Phone, Android and Windows](https://engineering-leadership.hinshelwood.com/articles/deploy-from-visual-studio-2012-to-ios-windows-phone-android-and-windows/): 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.
- [Woops I installed Windows 8 instead of Windows 8 Pro!](https://engineering-leadership.hinshelwood.com/articles/woops-i-installed-windows-8-instead-of-windows-8-pro/): Explains how to identify if you installed Windows 8 instead of Windows 8 Pro, the missing features, and how to upgrade to Pro without reinstalling the system.
- [Windows 8 Issue: Local network is detected as public](https://engineering-leadership.hinshelwood.com/articles/windows-8-issue-local-network-is-detected-as-public/): Explains why Windows 8 may label Hyper-V virtual networks as public, causing connectivity issues, and provides steps to manually set them as private for proper access.
- [Green to Orange–Joining the VSIP team as a Technical Product Manager](https://engineering-leadership.hinshelwood.com/articles/green-to-orange-joining-the-vsip-team-as-a-technical-product-manager/): Explains the role of a Technical Product Manager in the Visual Studio Industry Partner Program, focusing on partner collaboration, extensibility, and ecosystem growth.
- [Upgrading from TFS 2008 to TFS 2010 Overview](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2008-to-tfs-2010-overview/): Guides the upgrade from TFS 2008 to TFS 2010, covering technical steps, process template migration, challenges, and best practices for a smooth transition.
- [Office 2013 Issue: There is not enough free memory to run this program in Outlook 2013](https://engineering-leadership.hinshelwood.com/articles/office-2013-issue-there-is-not-enough-free-memory-to-run-this-program-in-outlook-2013/): Explains causes and solutions for the "not enough free memory" error in Outlook 2013, including disabling shared folder downloads and adjusting Exchange account settings.
- [Installing Office 2013 on Windows 8](https://engineering-leadership.hinshelwood.com/articles/installing-office-2013-on-windows-8/): Step-by-step guide to downloading, customising, and installing Office 2013 on Windows 8, including tips on features, feedback tools, and upgrade considerations.
- [Office 2013 Issue: Installing Office 2013 breaks Visual Studio 2012](https://engineering-leadership.hinshelwood.com/articles/office-2013-issue-installing-office-2013-breaks-visual-studio-2012/): Installing Office 2013 on a system with Visual Studio 2012 RC can cause C++ runtime errors. Apply the July 2012 update to resolve compatibility issues and restore functionality.
- [Migrating data from FogBugz to TFS 2012 using the TFS Integration Platform](https://engineering-leadership.hinshelwood.com/articles/migrating-data-from-fogbugz-to-tfs-2012-using-the-tfs-integration-platform/): 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.
- [TFS Integration Tools: TF237165: The Team Foundation Server could not update the work item](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-tf237165-the-team-foundation-server-could-not-update-the-work-item/): Explains how to resolve the TF237165 error in TFS Integration Tools, caused by validation or mapping issues when updating work items during data migration.
- [One Team Project to rule them all](https://engineering-leadership.hinshelwood.com/articles/one-team-project/): 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.
- [TFS Integration Tools–Issue: AnalysisProvider not found](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-analysisprovider-not-found/): Explains how to resolve the "AnalysisProvider not found" error in TFS Integration Tools by updating the .NET Framework version from 3.5 to 4.0 and recompiling.
- [One Team Project Collection to rule them all - Consolidating Team Projects](https://engineering-leadership.hinshelwood.com/articles/one-team-project-collection-to-rule-them-all-consolidating-team-projects/): Step-by-step guide to consolidating multiple Team Projects and Collections in TFS 2012 using the TFS Integration Platform, covering migration, mapping, and troubleshooting.
- [TFS Integration Tools – Issue: Error occurred during the code review of change group](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-error-occurred-during-the-code-review-of-change-group/): Explains causes and solutions for the "Error occurred during the code review of change group" in TFS Integration Tools, including common triggers and recommended workarounds.
- [TFS Integration Tools – Issue: Access denied to Program Files](https://engineering-leadership.hinshelwood.com/articles/tfs-integration-tools-issue-access-denied-to-program-files/): Explains how to fix an "Access Denied" error when TFS Integration Tools cannot write log files to Program Files, including permission changes and retry steps.
- [Upgrading TFS 2010 to TFS 2012 with VSS Migration and Process Template consolidation](https://engineering-leadership.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/): 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.
- [VSS Converter – Issue: TF54000: Cannot update the data because the server clock may have been set incorrectly](https://engineering-leadership.hinshelwood.com/articles/vss-converter-issue-tf54000-cannot-update-the-data-because-the-server-clock-may-have-been-set-incorrectly/): Explains the TF54000 error during VSS to TFS migration, its cause due to server time sync issues, and provides a simple workaround to resume the migration process.
- [VSS Converter – Issue: TF60014 & TF60087: Failed to initialise user mapper](https://engineering-leadership.hinshelwood.com/articles/vss-converter-issue-tf60014-tf60087-failed-to-initialise-user-mapper/): Explains how to resolve TF60014 and TF60087 errors in VSSConverter.exe during VSS to TFS import by ensuring mapped users have permissions in the target TFS project.
- [Installing TFS 2012 with Lab Management 2012](https://engineering-leadership.hinshelwood.com/articles/installing-tfs-2012-with-lab-management-2012/): Step-by-step guide to installing and configuring TFS 2012 with Lab Management, including SQL Server, SCVMM integration, troubleshooting, and environment setup tips.
- [Presenting Visual Studio ALM and upgrading TFS 2010 to TFS 2012 in production – Done](https://engineering-leadership.hinshelwood.com/articles/presenting-visual-studio-alm-and-upgrading-tfs-2010-to-tfs-2012-in-production-done/): 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.
- [Installing Eclipse on Windows 8 and connecting to TFS 2012](https://engineering-leadership.hinshelwood.com/articles/installing-eclipse-on-windows-8-and-connecting-to-tfs-2012/): Step-by-step guide to installing Eclipse and the Java Development Kit on Windows 8, then connecting Eclipse to Team Foundation Server (TFS) 2012 using Team Explorer Everywhere.
- [Installing Visual Studio 2010 on Windows 8](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2010-on-windows-8/): Step-by-step guide to installing Visual Studio 2010 on Windows 8 using a virtual machine, including tips for compatibility, performance, and Team Foundation Server use.
- [Installing TFS 2012 on Server 2012 with SQL 2012](https://engineering-leadership.hinshelwood.com/articles/installing-tfs-2012-on-server-2012-with-sql-2012/): Step-by-step guide to installing and configuring TFS 2012 on Windows Server 2012 with SQL Server 2012, including setup tips, common issues, and troubleshooting advice.
- [Full-fidelity history and data migration are mutually exclusive](https://engineering-leadership.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/): Explains why preserving complete historical data and accurate dates is often incompatible with data migration, especially for compliance and traceability in regulated industries.
- [Process Template Upgrade #7 – Rename Work Items and Import new ones](https://engineering-leadership.hinshelwood.com/articles/process-template-upgrade-7-rename-work-items-and-import-new-ones/): Step-by-step guide to upgrading TFS process templates by renaming and importing work item types, preserving data, updating fields, categories, configs, and reports.
- [Unit Testing against the Team Foundation Server 2012 API](https://engineering-leadership.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/): Explains how to unit test applications against the Team Foundation Server 2012 API, focusing on handling authentication for automated and unattended test scenarios.
- [TFS Field Annotator](https://engineering-leadership.hinshelwood.com/articles/tfs-field-annotator/): Track and view the change history of specific fields in TFS Work Items, showing who made edits and when, with support for multiple field selection and easy setup.
- [TFS Service Credential Viewer](https://engineering-leadership.hinshelwood.com/articles/tfs-service-credential-viewer/): Tool for retrieving service credentials from Team Foundation Service (TFS Preview), enabling secure automated API access without manual credential management. Requires Team Explorer 2012.
- [What's in a burndown?](https://engineering-leadership.hinshelwood.com/articles/whats-in-a-burndown/): Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility.
- [Professional Scrum Foundations in Salt Lake City, Utah](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-foundations-in-salt-lake-city-utah/): Covers hands-on experiences teaching the Professional Scrum Foundations course in Salt Lake City, highlighting teamwork, agile practices, and real-world Scrum challenges.
- [Do you have MSDN at work? Use Visual Studio Ultimate for free at home?](https://engineering-leadership.hinshelwood.com/articles/do-you-have-msdn-at-work-use-visual-studio-ultimate-for-free-at-home/): MSDN subscribers can use Visual Studio, Windows, and Office at home for personal or commercial projects, with licences assigned per user and perpetual rights to existing software.
- [You can't stack rank hierarchical work items?](https://engineering-leadership.hinshelwood.com/articles/you-cant-stack-rank-hierarchical-work-items/): Explains why stack ranking hierarchical work items is challenging in agile software development, highlighting issues with ordering, parent-child links, and best practices.
- [Visual Studio 11 Upgrade Health Check](https://engineering-leadership.hinshelwood.com/articles/visual-studio-11-upgrade-health-check/): Assessment service to help teams prepare for upgrading from TFS 2010 to Visual Studio 11, ensuring compatibility, feature readiness, and smooth migration.
- [Installing Visual Studio 11 on Windows 7](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-11-on-windows-7/): Step-by-step guide to installing Visual Studio 11 on Windows 7, covering setup process, UI changes, system requirements, and initial configuration options.
- [Upgrading from TFS2010 to Visual Studio 2012 Team Foundation Server in production](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs2010-to-visual-studio-2012-team-foundation-server-in-production/): Step-by-step guide to upgrading from TFS 2010 to Visual Studio 2012 Team Foundation Server, including prerequisites, SQL updates, configuration, and troubleshooting tips.
- [I messed up my work items from Excel! What now?](https://engineering-leadership.hinshelwood.com/articles/i-messed-up-my-work-items-from-excel-what-now/): Guidance on recovering from accidental bulk changes to TFS work items via Excel, including finding affected items, restoring data, and preventing future issues.
- [Is ALM a useful term?](https://engineering-leadership.hinshelwood.com/articles/is-alm-a-useful-term/): Explores whether Application Lifecycle Management (ALM) is a useful term, its role in agile software delivery, and differences in adoption across organisations and regions.
- [Upgrade to Visual Studio 11 Team Foundation Service - Done](https://engineering-leadership.hinshelwood.com/articles/upgrade-to-visual-studio-11-team-foundation-service-done/): Explains migrating source control and work item tracking to Visual Studio 11 Team Foundation Service, highlighting cloud benefits, limitations, and steps for a smooth upgrade.
- [Announcing Visual Studio 11 Beta will launch on February 29th](https://engineering-leadership.hinshelwood.com/articles/announcing-visual-studio-11-beta-will-launch-on-february-29th/): Visual Studio 11 Beta and Team Foundation Server Beta will be available from 29 February, with full Microsoft support for production use and guidance on going live.
- [Using Corporate ID's with Visual Studio 2012 Team Foundation Service](https://engineering-leadership.hinshelwood.com/articles/using-corporate-ids-with-visual-studio-2012-team-foundation-service/): Explains how to set up and manage custom domain Live IDs for corporate authentication in Visual Studio 2012 Team Foundation Service using Live Custom Domains.
- [Are you doing Scrum? Find out with a Scrum Health Check!](https://engineering-leadership.hinshelwood.com/articles/are-you-doing-scrum-find-out-with-a-scrum-health-check/): Assess your team's Scrum practices with a quick health check to identify improvement areas, track progress, and ensure alignment with Scrum principles and goals.
- [Introduction to Visual Studio 11](https://engineering-leadership.hinshelwood.com/articles/introduction-to-visual-studio-11/): Overview of Visual Studio 11 features, including Team Foundation Server integration, web UI improvements, team management tools, and Azure-hosted TFS preview demos.
- [Scrum-damentals Webcast on 17th February 2012](https://engineering-leadership.hinshelwood.com/articles/scrum-damentals-webcast-on-17th-february-2012/): Explore common challenges in Scrum adoption, practical strategies for overcoming them, and proven practices to help teams implement Scrum more effectively.
- [TF200035 Sync error for identity with TFS 2010](https://engineering-leadership.hinshelwood.com/articles/tf200035-sync-error-for-identity-with-tfs-2010/): Details troubleshooting a TF200035 sync error in TFS 2010, covering Active Directory issues, machine account permissions, domain compatibility, and possible workarounds.
- [Visual Studio 2010 Overview - Reporting & Process](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-reporting-process/): Learn how to customise Visual Studio 2010 process templates and use reporting tools to track, adapt, and improve team workflows with TFS for better project management.
- [Visual Studio 2010 Overview - Architecture](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-architecture/): Explains how Visual Studio 2010 supports teams in visualising, analysing, and maintaining software architecture, with tools for design, standards, and verification.
- [Visual Studio 2010 Overview - Microsoft Test Manager](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-microsoft-test-manager/): Covers using Microsoft Test Manager with Visual Studio 2010 and TFS to create, run, and manage manual and automated tests, including real-time test data collection.
- [Visual Studio 2010 Overview - Code Management and Build](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-code-management-and-build/): Explains branching, merging, and build strategies in Visual Studio 2010, including integration with Team Foundation Server and new tools for code management and ALM.
- [Visual Studio 2010 Overview - IntelliTrace and Test Impact Analysis](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-intellitrace-and-test-impact-analysis/): Explains how IntelliTrace aids bug diagnosis and how Test Impact Analysis helps prioritise regression tests in Visual Studio 2010 for efficient debugging and testing.
- [An adoption strategy for testing with Visual Studio 2010](https://engineering-leadership.hinshelwood.com/articles/an-adoption-strategy-for-testing-with-visual-studio-2010/): Guidance on adopting Visual Studio 2010 test tools, including Microsoft Test Manager, hands-on labs, and agile training to improve collaboration and software quality.
- [Visual Studio 2010 Overview - A day in the life of ... Plan, Code & Test](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-a-day-in-the-life-of/): Explore how developers, testers, and managers use Visual Studio 2010 and TFS for planning, coding, testing, bug fixes, and sprint management in real project workflows.
- [Visual Studio 2010 Overview - Introduction](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-introduction/): Overview of how Visual Studio 2010 supports Application Lifecycle Management (ALM), highlighting key features and demos for developers and testers.
- [Visual Studio 2010 Overview Webcasts](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-overview-webcasts/): Series of webcasts providing high-level overviews of Visual Studio 2010 and Team Foundation Server features, including ALM, testing, code management, and daily workflows.
- [What is the roll of the Project Manager in Scrum?](https://engineering-leadership.hinshelwood.com/articles/what-is-the-roll-of-the-project-manager-in-scrum/): Explains why traditional Project Manager roles do not exist in Scrum, outlining how their skills align better with Product Owner or Scrum Master positions in agile teams.
- [SSRS vs SCVMM - The Kerberos token dispute](https://engineering-leadership.hinshelwood.com/articles/ssrs-vs-scvmm-the-kerberos-token-dispute/): Explains Kerberos authentication issues when SSRS and SCVMM run on the same server with different service accounts, causing SPN conflicts and token errors in Active Directory.
- [The Sprint is a container for Planning and not necessarily for Delivery](https://engineering-leadership.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/): Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality.
- [Can you really commit to delivering work?](https://engineering-leadership.hinshelwood.com/articles/can-you-really-commit-to-delivering-work/): Explores why Scrum shifted from "commitment" to "forecasting" work delivery, highlighting the risks of overpromising and the benefits of transparency in Agile teams.
- [Always prompted for credentials in TFS 2010?](https://engineering-leadership.hinshelwood.com/articles/always-prompted-for-credentials-in-tfs-2010/): Explains why TFS 2010 repeatedly prompts for credentials and how to resolve it by configuring your domain as an intranet site in Internet Explorer settings.
- [Are you doing Scrum? Really?](https://engineering-leadership.hinshelwood.com/articles/are-you-doing-scrum-really/): 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.
- [Creating a backup in Team Foundation Server 2010 using the Power Tools](https://engineering-leadership.hinshelwood.com/articles/creating-a-backup-in-team-foundation-server-2010-using-the-power-tools/): Step-by-step guide to backing up Team Foundation Server 2010 with Power Tools, including required permissions, common errors, and troubleshooting backup issues.
- [Enabling Google Plus Profiles for Google Apps users in under 2 minutes](https://engineering-leadership.hinshelwood.com/articles/enabling-google-plus-profiles-for-google-apps-users-in-under-2-minutes/): Step-by-step guide to quickly enable Google+ profiles for Google Apps users, including accessing admin settings and activating the service for your domain.
- [Scrum with Visual Studio 11 - Creating a new Team Project](https://engineering-leadership.hinshelwood.com/articles/scrum-with-visual-studio-11-creating-a-new-team-project/): Step-by-step guide to creating a new Scrum team project in Visual Studio 11 using a web browser, enabling quick and easy cloud-based project setup.
- [Scrum with Visual Studio 11: Creating a Scrum team identity](https://engineering-leadership.hinshelwood.com/articles/scrum-with-visual-studio-11-creating-a-scrum-team-identity/): Learn how to set up Scrum teams in Visual Studio 11, organise work by team, and explore new features in the updated TFS and ALM user interface.
- [Process Template Upgrade #3 - Destroy all Work Items and Import new ones](https://engineering-leadership.hinshelwood.com/articles/process-template-upgrade-3-destroy-all-work-items-and-import-new-ones/): 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.
- [Product Owners are not a myth](https://engineering-leadership.hinshelwood.com/articles/product-owners-are-not-a-myth/): 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.
- [Allow user to change the region for Windows Live ID billing](https://engineering-leadership.hinshelwood.com/articles/allow-user-to-change-the-region-for-windows-live-id-billing/): Explains the challenges users face when unable to change the billing region for Windows Live ID, affecting access to Microsoft services after moving countries.
- [Are Scrum Masters agents for change?](https://engineering-leadership.hinshelwood.com/articles/are-scrum-masters-agents-for-change/): Explores the role of Scrum Masters in driving organisational change, effective Scrum adoption, and the importance of experience in leading successful agile transformations.
- [Caffeinating Your Development Lifecycle in Bellevue on October 13th](https://engineering-leadership.hinshelwood.com/articles/caffeinating-your-development-lifecycle-in-bellevue-on-october-13th/): Join an in-person morning event in Bellevue for live Visual Studio demos, Agile discussions, and practical ALM tips to boost your development process and team collaboration.
- [Scrum is hard to adopt and disruptive to your organisation](https://engineering-leadership.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/): Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful organisational change and Agile adoption.
- [Not just happy, but ecstatic](https://engineering-leadership.hinshelwood.com/articles/not-just-happy-but-ecstatic/): A consultant reflects on a successful Microsoft Dynamics deployment, improved build automation, and positive client feedback, inspiring interest in future UK and European projects.
- [You are doing Scrum but the Scrum Master tells the team what to do!](https://engineering-leadership.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/): Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices.
- [Testing with Test Professional 2010 and Visual Studio 2010 Ultimate](https://engineering-leadership.hinshelwood.com/articles/testing-with-test-professional-2010-and-visual-studio-2010-ultimate/): Learn how to use Microsoft Test Manager, Visual Studio 2010, and TFS for software testing, test management, bug tracking, and automated test workflows in this remote course.
- [Subversion to TFS 2010: The migration engine is unable to resolve a conflict where two changes have the same target item](https://engineering-leadership.hinshelwood.com/articles/subversion-to-tfs-2010-the-migration-engine-is-unable-to-resolve-a-conflict-where-two-changes-have-the-same-target-item/): Explains how to resolve case sensitivity conflicts when migrating from Subversion to TFS 2010, including tools and steps to handle duplicate target item errors.
- [Subversion to TFS 2010: Dealing with invalid Subversion SSL certificates and migrations](https://engineering-leadership.hinshelwood.com/articles/dealing-with-invalid-subversion-ssl-certificates-and-migrations/): Explains how invalid Subversion SSL certificates can block SVN to TFS 2010 migrations, causing connection errors, and details steps to resolve certificate issues.
- [Coffee Talk: Introduction to Scrum - webcast event this Friday!](https://engineering-leadership.hinshelwood.com/articles/coffee-talk-introduction-to-scrum-webcast-event-this-friday/): 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.
- [Upgrading your Process Template in Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/upgrading-your-process-template-in-team-foundation-server/): 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.
- [Coffee Talk: Scrum versus Kanban (re-match) ... Thursday at High Noon!](https://engineering-leadership.hinshelwood.com/articles/coffee-talk-scrum-versus-kanban-re-match-thursday-at-high-noon/): A recorded session comparing Scrum and Kanban, discussing their strengths, weaknesses, and how to adapt each method to fit different software development needs.
- [Coffee Talk: Scrum versus Kanban](https://engineering-leadership.hinshelwood.com/articles/coffee-talk-scrum-versus-kanban/): Learn the key differences and similarities between Scrum and Kanban, and discover which agile framework best suits your software development needs. Recording available.
- [Disqus & Chrome with non-support](https://engineering-leadership.hinshelwood.com/articles/disqus-chrome-with-non-support/): Describes issues with Disqus comments not loading on WordPress blogs in Chrome, troubleshooting steps, and challenges with Disqus support responses.
- [Upgrading from TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SF 2010 with SfTSv3](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/): 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.
- [Configuring a PowerShell Adapter for the TFS Integration Platform](https://engineering-leadership.hinshelwood.com/articles/configuring-a-powershell-adapter-for-the-tfs-integration-platform/): 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.
- [Constructing a framework for the TFS Automation Platform](https://engineering-leadership.hinshelwood.com/articles/constructing-a-framework-for-the-tfs-automation-platform/): Outlines the structure and components of a framework for the TFS Automation Platform, detailing its architecture, plugin management, and development approach.
- [A working Test Track Pro Adapter for the TFS Integration Platform](https://engineering-leadership.hinshelwood.com/articles/a-working-test-track-pro-adapter-for-the-tfs-integration-platform/): Describes building a working Test Track Pro Adapter for the TFS Integration Platform, detailing code changes, conflict handling, and incremental work item migration.
- [Test Track Pro and the case of the missing data](https://engineering-leadership.hinshelwood.com/articles/test-track-pro-and-the-case-of-the-missing-data/): 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.
- [What do you do with a Work Item History Not Found Conflict Type Details](https://engineering-leadership.hinshelwood.com/articles/what-do-you-do-with-a-work-item-history-not-found-conflict-type-details/): Explains how missing or non-consecutive work item revision history during TFS migrations causes conflicts, and details troubleshooting steps and unresolved backlog issues.
- [Creating a WIT Adapter for the TFS Integration Platform for a source with no history](https://engineering-leadership.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/): 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.
- [Anatomy of an Automation for the Tfs Automation Platform](https://engineering-leadership.hinshelwood.com/articles/anatomy-of-an-automation-for-the-tfs-automation-platform/): Explains how to build, install, configure, and run automations for TFS, covering plugin deployment, activation, settings, UI integration, and job processing steps.
- [How might we implement the Change Iteration Automation for the Tfs Automation Platform](https://engineering-leadership.hinshelwood.com/articles/how-might-we-implement-the-change-iteration-automation-for-the-tfs-automation-platform/): Explains automating the update of WIQL queries during sprint or iteration changes in the TFS Automation Platform, covering UI, configuration, and job execution details.
- [What about hosting the Tfs Automation Platform](https://engineering-leadership.hinshelwood.com/articles/what-about-hosting-the-tfs-automation-platform/): Explores options for hosting the TFS Automation Platform, comparing server-side and client-only setups, and discusses impacts on functionality, resilience, and multi-user support.
- [What is the Tfs Automation Platform](https://engineering-leadership.hinshelwood.com/articles/what-is-the-tfs-automation-platform/): A platform for automating Team Foundation Server tasks, enabling scheduled, event-driven, and on-demand workflows, with extensible package and Visual Studio integration.
- [My first Scrum team in the wild](https://engineering-leadership.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/): A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work.
- [Installing Visual Studio 2010 Service Pack 1](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2010-service-pack-1/): Step-by-step guide to downloading and installing Visual Studio 2010 Service Pack 1, including update requirements, download size, install times, and troubleshooting tips.
- [Installing Visual Studio Team Foundation Server Service Pack 1](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-team-foundation-server-service-pack-1/): Step-by-step guide to installing Visual Studio Team Foundation Server 2010 Service Pack 1, including troubleshooting tips for common installation errors and solutions.
- [Visual Studio ALM MVP of the Year 2011](https://engineering-leadership.hinshelwood.com/articles/visual-studio-alm-mvp-of-the-year-2011/): Recognition for contributions to the Visual Studio ALM community, including sharing Team Foundation Server solutions, blogging, and collaborating on key projects.
- [Do you know how to move the Team Foundation Server cache](https://engineering-leadership.hinshelwood.com/articles/do-you-know-how-to-move-the-team-foundation-server-cache/): Learn how to safely move the Team Foundation Server cache to a new drive, update permissions, and configure web.config for better storage management and performance.
- [Should GeeksWithBlogs move to the Wordpress Platform?](https://engineering-leadership.hinshelwood.com/articles/should-geekswithblogs-move-to-the-wordpress-platform/): Explores the benefits and challenges of migrating GeeksWithBlogs from SubText to WordPress, focusing on features, user needs, SEO, and community involvement.
- [Do you know about the Visual Studio 2010 Database Projects Guidance?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-database-projects-guidance/): Guidance on using Visual Studio 2010 Database Projects, covering project management, source control, deployment automation, integration, and database testing.
- [Can I run two versions of Microsoft Project side-by-side?](https://engineering-leadership.hinshelwood.com/articles/can-i-run-two-versions-of-microsoft-project-side-by-side/): Running multiple Microsoft Project versions on one PC is possible but not recommended due to file association issues, compatibility problems, and potential data errors.
- [How Visual Studio 2010 and Team Foundation Server enable Compliance](https://engineering-leadership.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/): Explains how Visual Studio 2010 and Team Foundation Server support compliance by enabling traceability, audit trails, and linking code changes to requirements and tests.
- [Do you know about the Visual Studio ALM Rangers Guidance?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-about-the-visual-studio-alm-rangers-guidance/): Overview of official Visual Studio 2010 ALM Rangers guidance, including solutions, projects, and resources to help users get the most from Visual Studio tools.
- [Do you know about the Visual Studio 2010 Architecture Guidance?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-architecture-guidance/): Provides practical samples, checklists, and hands-on labs to help developers and architects use Visual Studio 2010 Ultimate’s architecture modelling tools effectively.
- [Do you want to be an ALM Consultant?](https://engineering-leadership.hinshelwood.com/articles/do-you-want-to-be-an-alm-consultant/): Role overview for an ALM Consultant at Northwest Cadence, focusing on software lifecycle management, training, consulting, and technical leadership using Microsoft technologies.
- [Project of Projects with team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/project-of-projects-with-team-foundation-server-2010/): 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.
- [Free training at Northwest Cadence](https://engineering-leadership.hinshelwood.com/articles/free-training-at-northwest-cadence/): Learn about free online training sessions from Northwest Cadence, including interactive Coffee Talks on ALM, TFS 2010, and quality assurance, suitable for UK developers.
- [What to do after a servicing fails on TFS 2010](https://engineering-leadership.hinshelwood.com/articles/what-to-do-after-a-servicing-fails-on-tfs-2010/): Guidance on troubleshooting failed servicing in TFS 2010, including schema version issues, recovery steps, and risks of database repair versus starting over.
- [TFS 2010 Work Item Seed: TFS Work Item system.id at a predefined number](https://engineering-leadership.hinshelwood.com/articles/tfs-2010-work-item-seed-tfs-work-item-system-id-at-a-predefined-number/): 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.
- [TFS vs. Subversion fact check](https://engineering-leadership.hinshelwood.com/articles/tfs-vs-subversion-fact-check/): Compares TFS and Subversion, addressing common misconceptions, feature differences, platform support, installation, cost, and challenges for SVN users moving to TFS.
- [Syncing many Dynamics AX instances to a single TFS 2010 Team Project](https://engineering-leadership.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/): 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.
- [Database corruption in TFS 2005 causes TF246017 during upgrade](https://engineering-leadership.hinshelwood.com/articles/database-corruption-in-tfs-2005-causes-tf246017-during-upgrade/): Explains how database corruption in TFS 2005 can cause TF246017 errors during upgrade, and details using DBCC CHECKDB to diagnose and repair the issue.
- [Team Foundation Server 2010 Event Handling with Subscribers](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-2010-event-handling-with-subscribers/): 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.
- [Calculating the Rank of your blog posts or pages](https://engineering-leadership.hinshelwood.com/articles/calculating-the-rank-of-your-blog-posts-or-pages/): Explains how to calculate and rank blog posts or pages using data like comments, social shares, and Google PageRank to identify popular or underperforming content.
- [How to deal with a stuck or infinitely queued build](https://engineering-leadership.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/): Learn how to identify, troubleshoot, and resolve stuck or infinitely queued builds in Team Foundation Build, including tips for monitoring and restarting build services.
- [A change for the better #3 - SSW to Northwest Cadence](https://engineering-leadership.hinshelwood.com/articles/a-change-for-the-better-3/): 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.
- [Running Android 2.2 (Frodo) on your HD2](https://engineering-leadership.hinshelwood.com/articles/running-android-2-2-frodo-on-your-hd2/): Guide to installing and running Android 2.2 (Froyo) on the HTC HD2, including setup steps, troubleshooting tips, and advice for optimising performance and battery life.
- [Rangers shipped Visual Studio 2010 Database Guide](https://engineering-leadership.hinshelwood.com/articles/rangers-shipped-visual-studio-2010-database-guide/): Comprehensive guidance and hands-on labs for managing, testing, and deploying Visual Studio 2010 Database projects, including source control and automation tips.
- [Commit to Visual Studio ALM on Area51](https://engineering-leadership.hinshelwood.com/articles/commit-to-visual-studio-alm-on-area51/): Details the progress of the Visual Studio ALM StackExchange proposal on Area51, outlining voting, commitment stages, and how users can help launch the community.
- [Active Directory Groups not Syncing with Team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/active-directory-groups-not-syncing-with-team-foundation-server-2010/): 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.
- [TFS Event Handler for Team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-for-team-foundation-server-2010/): 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.
- [The search for a single point of truth](https://engineering-leadership.hinshelwood.com/articles/the-search-for-a-single-point-of-truth/): Explores methods and tools for syncing contacts across multiple services, aiming to maintain a single, up-to-date source without duplicates or data loss.
- [Changing the Team Project Collection of the Team Build Controller](https://engineering-leadership.hinshelwood.com/articles/changing-the-team-project-collection-of-the-team-build-controller/): 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.
- [SSW Brain Quest: Team Foundation Server and SharePoint 2010 (London)](https://engineering-leadership.hinshelwood.com/articles/ssw-brain-quest-team-foundation-server-and-sharepoint-2010-london/): 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.
- [Professional Scrum Developer (.NET) Training in London](https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/): 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.
- [Flashing your Windows Phone 6 for Dummies](https://engineering-leadership.hinshelwood.com/articles/flashing-your-windows-phone-6-for-dummies/): Step-by-step guide to safely flashing custom ROMs on Windows Phone 6 devices, including key terms, risks, tools, and links to resources for the HTC HD2.
- [Ghost build controllers in Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/ghost-build-controllers-in-team-foundation-server/): Learn how to identify and remove undeletable ghost build controllers in Team Foundation Server by updating build status in the database, avoiding unsupported deletions.
- [Why you need to tag your build servers in TFS](https://engineering-leadership.hinshelwood.com/articles/why-you-need-to-tag-your-build-servers-in-tfs/): Tagging build servers in TFS helps manage dependencies, assign builds to suitable agents, and streamline workflows across teams and regions for reliable automation.
- [Kaiden and the Arachnoid Cyst](https://engineering-leadership.hinshelwood.com/articles/kaiden-and-the-arachnoid-cyst/): A personal account of Kaiden’s early development, delayed walking, and medical journey following the discovery of an arachnoid cyst, with updates and related blog posts.
- [Guidance: How to layout you files for an Ideal Solution](https://engineering-leadership.hinshelwood.com/articles/guidance-how-to-layout-you-files-for-an-ideal-solution/): Learn best practices for organising solution and project files in version control, including folder structure, naming conventions, and branching for maintainable code.
- [Scrum with Team Foundation Server 2010 Done](https://engineering-leadership.hinshelwood.com/articles/scrum-with-team-foundation-server-2010-done/): Explains how to use Scrum with Team Foundation Server 2010 for better project management, including practical tips, presentation slides, and real-world experiences.
- [Integrate SharePoint 2010 with Team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/integrate-sharepoint-2010-with-team-foundation-server-2010/): Step-by-step guide to integrating SharePoint 2010 with Team Foundation Server 2010, including installation, configuration, permissions, and managed paths setup.
- [Upgrading Team Foundation Server 2008 to 2010](https://engineering-leadership.hinshelwood.com/articles/upgrading-team-foundation-server-2008-to-2010/): Step-by-step guide to upgrading Team Foundation Server 2008 to 2010, covering database backup, migration, verification, compatibility, and post-upgrade testing.
- [Even Scrum should have detailed Task descriptions](https://engineering-leadership.hinshelwood.com/articles/even-scrum-should-have-detailed-task-descriptions/): Scrum tasks should include detailed descriptions so anyone can complete them, ensuring project continuity if team members are unavailable or leave unexpectedly.
- [LinkedIn Woopsie with the Outlook 2010 Social Media Connector](https://engineering-leadership.hinshelwood.com/articles/linkedin-woopsie-with-the-outlook-2010-social-media-connector/): Describes an account suspension caused by LinkedIn's Outlook 2010 connector triggering automated activity, and how LinkedIn support quickly resolved the issue.
- [Combining Scrum, TFS2010 and Email to keep everyone in the loop](https://engineering-leadership.hinshelwood.com/articles/combining-scrum-tfs2010-and-email-to-keep-everyone-in-the-loop/): Explains how to integrate Scrum, TFS 2010, and email to share task details, maintain history, and keep all stakeholders informed throughout project workflows.
- [Silverlight 4, MVVM and Test-Driven Development](https://engineering-leadership.hinshelwood.com/articles/silverlight-4-mvvm-and-test-driven-development/): Learn how to use Silverlight 4 and the MVVM pattern for test-driven development, including refactoring, dependency injection, and building real-world applications.
- [Guidance: A Branching strategy for Scrum Teams](https://engineering-leadership.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/): 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.
- [Do you know when to send a done email in Scrum?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-when-to-send-a-done-email-in-scrum/): Explains when and how to send done emails in Scrum, detailing best practices for notifying task owners and teams, and ensuring clear communication of completed work.
- [Do you have a contract between the Product Owner and the Team?](https://engineering-leadership.hinshelwood.com/articles/do-you-have-a-contract-between-the-product-owner-and-the-team/): 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.
- [Upgrading from TFS 2010 RC to TFS 2010 RTM done](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2010-rc-to-tfs-2010-rtm-done/): 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.
- [Upgrading Visual Studio 2010](https://engineering-leadership.hinshelwood.com/articles/upgrading-visual-studio-2010/): Step-by-step guide to uninstalling Visual Studio 2010 RC and installing the RTM version, including tips for a full install and troubleshooting common issues.
- [Scrum for Team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/scrum-for-team-foundation-server-2010/): Learn how to implement Scrum practices using Team Foundation Server 2010 and Visual Studio ALM, including project planning, backlog management, and progress tracking.
- [Guidance - Branching for each Sprint](https://engineering-leadership.hinshelwood.com/articles/guidance-branching-for-each-sprint/): Explains how using a separate version control branch for each sprint in Scrum improves code stability, release management, and team collaboration over using labels.
- [Scottish Visual Studio 2010 Launch event with Jason Zander](https://engineering-leadership.hinshelwood.com/articles/scottish-visual-studio-2010-launch-event-with-jason-zander/): Microsoft’s Edinburgh event features Jason Zander presenting Visual Studio 2010 updates, including Windows, Web, Cloud, and ALM tools for developers and testers.
- [Scott Guthrie in Glasgow](https://engineering-leadership.hinshelwood.com/articles/scott-guthrie-in-glasgow/): Scott Guthrie presented new features in Visual Studio 2010, Silverlight 4, ASP.NET MVC 2, and Windows Phone 7 during his Glasgow tour, with live demos and insights.
- [Who broke the build?](https://engineering-leadership.hinshelwood.com/articles/who-broke-the-build/): Explains the importance of passing builds, common causes of build failures, how to identify issues and responsible users, and best practices for build ownership.
- [Do you know the minimum builds to create on any branch?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-the-minimum-builds-to-create-on-any-branch/): Explains the essential three build types, Gate, CI, and Nightly, needed per branch to ensure code quality, test coverage, and collaboration in team projects.
- [Do you know that every user story should have an owner?](https://engineering-leadership.hinshelwood.com/articles/do-you-know-that-every-user-story-should-have-an-owner/): Assigning an owner to each user story in Scrum ensures clear responsibility, better communication, and accountability throughout the sprint for both teams and stakeholders.
- [Adventures in Scrum: Lesson 2 - For the record](https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-2-for-the-record/): Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, especially with proxy Product Owners.
- [Adventures in Scrum: Lesson 1 – The failed Sprint](https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-1-the-failed-sprint/): 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.
- [When should I use Areas in TFS instead of Team Projects in Team Foundation Server 2010](https://engineering-leadership.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/): Explains when to use Areas versus Team Projects in TFS 2010, comparing benefits, drawbacks, and best practices for managing multiple projects and process templates.
- [MVVM for Dummies](https://engineering-leadership.hinshelwood.com/articles/mvvm-for-dummies/): Explains the MVVM pattern in WPF and Silverlight, highlighting separation of concerns, code structure, and the roles of commanding, dependency injection, and design patterns.
- [Finding the problem on a partially succeeded build on Team Foundation Build Services 2010](https://engineering-leadership.hinshelwood.com/articles/finding-the-problem-on-a-partially-succeeded-build-on-team-foundation-build-services-2010/): 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.
- [Microsoft, please help me diagnose TFS Administration permission issues!](https://engineering-leadership.hinshelwood.com/articles/microsoft-please-help-me-diagnose-tfs-administration-permission-issues/): Troubleshooting TFS 2010 admin permission errors caused by not running TfsConfig as administrator, despite correct group memberships and server permissions.
- [Solution: Testing Web Services with MSTest on Team Foundation Build Services 2010](https://engineering-leadership.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/): 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.
- [Solution: Getting Silverlight to build on Team Foundation Build Services 2010](https://engineering-leadership.hinshelwood.com/articles/solution-getting-silverlight-to-build-on-team-foundation-build-services-2010/): 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.
- [Upgrading from TFS 2010 Beta 2 to TFS 2010 RC done](https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2010-beta-2-to-tfs-2010-rc-done/): Step-by-step guide to upgrading from TFS 2010 Beta 2 to TFS 2010 RC, including best practices, troubleshooting tips, and post-upgrade checks for developers.
- [Why I miss Orange and why Vodafone suck!](https://engineering-leadership.hinshelwood.com/articles/why-i-miss-orange-and-why-vodafone-suck/): A personal account comparing poor Vodafone customer service with positive experiences at Orange, highlighting issues with account access, billing, and contract limitations.
- [Solution - IIS SMTP Service 5.5.2 rejected: need fully qualified hostname](https://engineering-leadership.hinshelwood.com/articles/solution-iis-smtp-service-5-5-2-rejected-need-fully-qualified-hostname/): Explains how to resolve IIS SMTP error 5.5.2 by configuring a fully qualified domain name, ensuring outgoing emails are accepted by recipient mail servers.
- [Solution - SEO permanent redirects for old URL’s?](https://engineering-leadership.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/): 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.
- [Investigation - SEO permanent redirects for old URL’s?](https://engineering-leadership.hinshelwood.com/articles/investigation-seo-permanent-redirects-for-old-url-s/): Explains how to implement SEO-friendly permanent 301 redirects for old URLs to preserve search rankings, comparing IIS tools and custom solutions for database-driven mapping.
- [Create a VHD from the Windows Server 2008 R2 Image disk](https://engineering-leadership.hinshelwood.com/articles/create-a-vhd-from-the-windows-server-2008-r2-image-disk/): Step-by-step guide to create a Virtual Hard Disk (VHD) from a Windows Server 2008 R2 image using Windows AIK and WIM2VHD, including common pitfalls and tips.
- [Outlook 2010 Beta 2 and Add-Ins: Dynamics CRM, Team Companion, LinkedIn and Plaxo](https://engineering-leadership.hinshelwood.com/articles/outlook-2010-beta-2-and-add-ins-dynamics-crm-team-companion-linkedin-and-plaxo/): Covers compatibility and usability of Dynamics CRM, Team Companion, LinkedIn, and Plaxo add-ins in Outlook 2010 Beta 2, including 32-bit and 64-bit support issues.
- [Create a VHD from the Windows 7 Image disk](https://engineering-leadership.hinshelwood.com/articles/create-a-vhd-from-the-windows-7-image-disk/): Step-by-step guide to converting a Windows 7 .wim image to a VHD, including extraction, merging, deployment with imageX, and configuring boot options for quick setup.
- [Internet connection speed, WOW](https://engineering-leadership.hinshelwood.com/articles/internet-connection-speed-wow/): A personal account of UK cable internet speed improvements, comparing dial-up, ADSL, and Virgin Media, with real-world download rates and upgrade experiences.
- [Installing Visual Studio 2008 Team Foundation Server SP1](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2008-team-foundation-server-sp1/): Step-by-step guide to installing Visual Studio 2008 Team Foundation Server SP1, including backup, testing, troubleshooting, and rollback procedures for safe deployment.
- [Dyslexia Awareness Week](https://engineering-leadership.hinshelwood.com/articles/dyslexia-awareness-week/): Highlights the unique strengths dyslexic individuals bring to programming, such as 3D visualisation, creative problem-solving, and intuitive understanding of complex concepts.
- [Deploying Visual Studio 2010 Team Foundation Server Beta 2 - Done](https://engineering-leadership.hinshelwood.com/articles/deploying-visual-studio-2010-team-foundation-server-beta-2-done/): Covers the step-by-step process and team effort involved in migrating from TFS 2008 to Visual Studio 2010 Team Foundation Server Beta 2, including key lessons learned.
- [A change for the better #2 - Aggreko to SSW](https://engineering-leadership.hinshelwood.com/articles/a-change-for-the-better-2/): Describes a career move from Aggreko to SSW, focusing on software architecture, ALM, TFS migrations, and applying productivity rules in team environments.
- [Configuring Visual Studio 2010 Team Foundation Server on Vista in 12 minutes](https://engineering-leadership.hinshelwood.com/articles/configuring-visual-studio-2010-team-foundation-server-on-vista-in-12-minutes/): Step-by-step guide to configuring Visual Studio 2010 Team Foundation Server on Windows Vista, including setup options, compatibility notes, and tips for a quick install.
- [Installing Visual Studio 2010 Team Foundation Server on Windows Vista in 3 minutes](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2010-team-foundation-server-on-windows-vista-in-3-minutes/): Step-by-step guide to quickly installing Visual Studio 2010 Team Foundation Server on Windows Vista, including setup options and requirements for a basic installation.
- [Interview with Scottish Developers](https://engineering-leadership.hinshelwood.com/articles/interview-with-scottish-developers/): A personal interview featured in the Scottish Developers newsletter, discussing experiences and insights from a developer’s perspective within the Scottish tech community.
- [Visual Studio 2010 Beta 2 is available Now!](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-beta-2-is-available-now/): Visual Studio 2010 Beta 2 introduces new editions, simplified licensing, and enhanced ALM, testing, and lab management features. Now available for download on MSDN.
- [Wpf Ninject Dojo: The Data Provider](https://engineering-leadership.hinshelwood.com/articles/wpf-ninject-dojo-the-data-provider/): Explains how to use a custom NinjectDataProvider in WPF to enable dependency injection for ViewModels, improving flexibility and design-time support in MVVM projects.
- [Second blogger from my office](https://engineering-leadership.hinshelwood.com/articles/second-blogger-from-my-office/): A colleague has started blogging, sharing a useful SQL Server function to add working days to a date, helpful for support analysts and database professionals.
- [Silverlight 3](https://engineering-leadership.hinshelwood.com/articles/silverlight-3/): Overview of Silverlight 3 features, improvements, and its use for .NET and WPF developers, with insights from a detailed programmer’s reference book.
- [Updating the Command Line Parser](https://engineering-leadership.hinshelwood.com/articles/updating-the-command-line-parser/): 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.
- [Wpf Drag & Drop behaviour](https://engineering-leadership.hinshelwood.com/articles/wpf-drag-drop-behaviour/): Explains how to implement flexible drag and drop in WPF using MVVM, with customisable drop behaviour and bindable options for ItemsControls, including code examples.
- [The long wait is over](https://engineering-leadership.hinshelwood.com/articles/the-long-wait-is-over/): Windows 7 is now available to developers and beta testers, offering improved stability, speed, and features over Vista, with general release coming in September 2009.
- [Finding features: Calendar preview](https://engineering-leadership.hinshelwood.com/articles/finding-features-calendar-preview/): See your upcoming events at a glance with Outlook 2010’s Calendar preview, making it easy to check your schedule and availability quickly.
- [Creating a Data Access layer using Unity](https://engineering-leadership.hinshelwood.com/articles/creating-a-data-access-layer-using-unity/): Learn how to build a flexible data access layer in .NET using Unity for dependency injection, interface mapping, and factory patterns with configuration support.
- [A perfect match TFS and DLR](https://engineering-leadership.hinshelwood.com/articles/a-perfect-match-tfs-and-dlr/): Explores integrating Team Foundation Server check-in policies with the Dynamic Language Runtime to enable flexible, centralised policy management across clients.
- [Log Elmah errors in Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/log-elmah-errors-in-team-foundation-server/): Explains how to log Elmah error reports as work items in Team Foundation Server, including attaching error logs, using templates, and retrieving error details.
- [Disable a timer at every level of your ASP.NET control hierarchy](https://engineering-leadership.hinshelwood.com/articles/disable-a-timer-at-every-level-of-your-asp-net-control-hierarchy/): Learn how to recursively find and disable all Timer controls in an ASP.NET page, even without knowing their IDs, to prevent unwanted UI updates and interference.
- [List all files changed under an Iteration](https://engineering-leadership.hinshelwood.com/articles/list-all-files-changed-under-an-iteration/): Shows how to use TFS API calls to list all files changed in a specific iteration, including querying work items and extracting changesets to a text file.
- [Office 2010 gotcha 2: Visual Studio 2008 Locks](https://engineering-leadership.hinshelwood.com/articles/office-2010-gotcha-2-visual-studio-2008-locks/): Explains how installing Office 2010 can cause Visual Studio 2008 to freeze when editing ASPX files, and provides a fix by repairing the Web Authoring Component.
- [Finding features: Conversations](https://engineering-leadership.hinshelwood.com/articles/finding-features-conversations/): Explains how email conversation view groups related messages into threads, making it easier to follow discussions and manage multiple replies in email clients.
- [Office 2010 First run](https://engineering-leadership.hinshelwood.com/articles/office-2010-first-run/): A first look at Office 2010’s setup, Outlook features, user feedback prompts, activation process, and improved email conversation tools compared to previous versions.
- [Office 2010 Install](https://engineering-leadership.hinshelwood.com/articles/office-2010-install/): Step-by-step guide to installing Office 2010 on Windows Vista 64-bit, including full installation tips, system responsiveness issues, and troubleshooting advice.
- [Installing Office 2010 gotcha 1](https://engineering-leadership.hinshelwood.com/articles/installing-office-2010-gotcha-1/): Explains issues when upgrading from Office 2007 32-bit to Office 2010 64-bit, including uninstall requirements, Outlook settings loss, and automation challenges.
- [Twitter with style](https://engineering-leadership.hinshelwood.com/articles/twitter-with-style/): Review of Twikini, a Twitter app for Windows Mobile 6.5, highlighting its features, usability, and a minor issue with tweet confirmation on certain phone keyboards.
- [Project Natal available soon](https://engineering-leadership.hinshelwood.com/articles/project-natal-available-soon/): Project Natal, a motion-sensing device for Xbox, is rumoured to launch before Christmas at around £121, with pre-orders expected to open soon.
- [Stuck with Vista?](https://engineering-leadership.hinshelwood.com/articles/stuck-with-vista/): Overview of Windows Vista Service Pack 2 release, its availability, installation process, and potential improvements for users experiencing performance issues.
- [Connecting VS2008 to any TFS2010 Project Collection](https://engineering-leadership.hinshelwood.com/articles/connecting-vs2008-to-any-tfs2010-project-collection/): Learn how to connect Visual Studio 2008 SP1 to any TFS 2010 project collection using the correct URL format, including compatibility notes for VS2005 and TFS 2010.
- [Upgrading to TFS 2010 Beta 1 and SQL Collation](https://engineering-leadership.hinshelwood.com/articles/upgrading-to-tfs-2010-beta-1-and-sql-collation/): Explains issues upgrading from TFS 2008 to TFS 2010 Beta 1 due to SQL Server collation conflicts, error messages, and the need to align collation settings.
- [You May Be a Tech Whiz, but Are You Certifiable?](https://engineering-leadership.hinshelwood.com/articles/you-may-be-a-tech-whiz-but-are-you-certifiable/): Test your IT knowledge with a Microsoft quiz designed to challenge tech skills and see if you can earn a spot on the leaderboard. Try it and compare your results.
- [Microsoft MyPhone service available to the public](https://engineering-leadership.hinshelwood.com/articles/microsoft-myphone-service-available-to-the-public/): Sync your mobile phone data, contacts, calendar, tasks, photos, and more, with the web using Microsoft MyPhone, enabling easy backup and online access.
- [Solution to connecting to TFS using HTTPS over the Internet from behind ISA](https://engineering-leadership.hinshelwood.com/articles/solution-to-connecting-to-tfs-using-https-over-the-internet-from-behind-isa/): Explains how to resolve TFS connection issues over HTTPS from behind an ISA server by updating Visual Studio registry settings for proxy configuration.
- [Unable to connect to TFS using HTTPS over the Internet from behind ISA](https://engineering-leadership.hinshelwood.com/articles/unable-to-connect-to-tfs-using-https-over-the-internet-from-behind-isa/): Explains issues connecting to TFS via HTTPS from behind an ISA proxy, including proxy authentication errors and ServicePointManager limitations, with suggested workarounds.
- [Why is the VS2010 iso so small?](https://engineering-leadership.hinshelwood.com/articles/why-is-the-vs2010-iso-so-small/): The VS2010 ISO is small because it excludes MSDN documentation, which is not yet available offline; users can access documentation online instead.
- [Uninstalling Visual Studio 2010 Beta 1](https://engineering-leadership.hinshelwood.com/articles/uninstalling-visual-studio-2010-beta-1/): Step-by-step account of uninstalling Visual Studio 2010 Beta 1 and .NET 4.0, including common issues, manual cleanup, and troubleshooting on Windows Vista.
- [Visual Studio 2010 Supports UML](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2010-supports-uml/): Visual Studio 2010 introduces support for UML, enabling developers to create and manage Unified Modeling Language diagrams directly within the IDE.
- [Multi-Targeting in Visual Studio 2010](https://engineering-leadership.hinshelwood.com/articles/multi-targeting-in-visual-studio-2010/): Explains how Visual Studio 2010 allows developers to target multiple .NET Framework versions, enabling work on legacy and new projects within a single environment.
- [Connecting VS2010 to TFS 2008](https://engineering-leadership.hinshelwood.com/articles/connecting-vs2010-to-tfs-2008/): Learn how to connect Visual Studio 2010 to Team Foundation Server 2008, view legacy project collections, and access projects without installing Team Explorer separately.
- [Installing Visual Studio 2010 Team Suit Beta 1](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2010-team-suit-beta-1/): Step-by-step guide to installing Visual Studio 2010 Team Suite Beta 1, highlighting setup options, customisation, improved installer, and estimated installation time.
- [Installing .NET 4.0 Beta 1 on Windows Vista 64x](https://engineering-leadership.hinshelwood.com/articles/installing-net-4-0-beta-1-on-windows-vista-64x/): Step-by-step guide to installing .NET 4.0 Beta 1 on Windows Vista 64-bit, including installation time, key new features, and links to further resources.
- [Visual Studio Team System 2010 Beta 1 Ships](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-2010-beta-1-ships/): Microsoft releases the first beta of Visual Studio Team System 2010, featuring new tools for architecture, testing, lab management, TFS, and a redesigned WPF interface.
- [Unity and ASP.NET](https://engineering-leadership.hinshelwood.com/articles/unity-and-asp-net/): Explains how to use Unity for dependency injection in ASP.NET, enabling runtime component swapping without redeploying, with practical code and config examples.
- [My.Unity.Resolve(Of Ninja)](https://engineering-leadership.hinshelwood.com/articles/my-unity-resolve-of-ninja/): Shows how to create a shared UnityContainer singleton in VB.NET using the “My” namespace, enabling dependency injection across WPF and ASP.NET applications.
- [The Hinshelwood Family Portrait](https://engineering-leadership.hinshelwood.com/articles/the-hinshelwood-family-portrait/): A family shares their positive experience with a professional photo shoot, highlighting the photographer’s skill, patience with children, and quality of the resulting portraits.
- [Developer Day Scotland 2009](https://engineering-leadership.hinshelwood.com/articles/developer-day-scotland-2009/): Summary of sessions from a Glasgow developer event, covering refactoring, dynamic languages in .NET, MVVM for WPF, architecture, and ASP.NET 4.0 insights.
- [Fail a build if tests fail](https://engineering-leadership.hinshelwood.com/articles/fail-a-build-if-tests-fail/): Explains how to configure TFS 2008 builds to automatically fail if any tests fail by setting TreatTestFailureAsBuildFailure to true in the build project file.
- [Windows 7 RC](https://engineering-leadership.hinshelwood.com/articles/windows-7-rc/): The Windows 7 Release Candidate is available for developers and beta testers, with public access starting 5 May. Find download links, release details, and user impressions.
- [Get Analysis Services last processed date](https://engineering-leadership.hinshelwood.com/articles/get-analysis-services-last-processed-date/): Provides code to retrieve the last processed date of cubes on an Analysis Services server, highlighting performance considerations and error handling in .NET environments.
- [Data Dude R2 is out!](https://engineering-leadership.hinshelwood.com/articles/data-dude-r2-is-out/): Visual Studio Team System 2008 Database Edition GDR R2 adds new features, improved SQL Server 2008 support, enhancements, and bug fixes for database development.
- [I hope you did not pay for Microsoft Office Sharepoint Designer 2007](https://engineering-leadership.hinshelwood.com/articles/i-hope-you-did-not-pay-for-microsoft-office-sharepoint-designer-2007/): Microsoft Office SharePoint Designer 2007 is now available as a free download, making it easier for users to access and use without purchase or business approval.
- [Sharepoint 2007 and Silverlight](https://engineering-leadership.hinshelwood.com/articles/sharepoint-2007-and-silverlight/): Guide to integrating Silverlight with SharePoint 2007, covering custom field types, branding, web parts, data interaction, deployment, and debugging basics.
- [McDDD](https://engineering-leadership.hinshelwood.com/articles/mcddd/): Join developers in Glasgow on 2nd May for Developer Day Scotland 2, featuring talks from returning and new speakers on software development and technology topics.
- [We’re sorry, but you won’t be able to download Internet Explorer 8 for Windows 7 Beta at this time](https://engineering-leadership.hinshelwood.com/articles/we-re-sorry-but-you-won-t-be-able-to-download-internet-explorer-8-for-windows-7-beta-at-this-time/): Internet Explorer 8 is not available for Windows 7 Beta users, but can be downloaded for Windows XP and Vista. Compatibility and extensibility are key features.
- [Windows Azure Training Kit](https://engineering-leadership.hinshelwood.com/articles/windows-azure-training-kit/): Comprehensive training resources for Windows Azure, including hands-on labs, demo scripts, and presentations on cloud services, .NET, SQL, and Live Services.
- [Head First Design Patterns](https://engineering-leadership.hinshelwood.com/articles/head-first-design-patterns/): Overview of a book that explains design patterns using visual aids and interactive methods, making complex concepts accessible for all learners, including those with dyslexia.
- [Microsoft Document Explorer 2008 on Window 7](https://engineering-leadership.hinshelwood.com/articles/microsoft-document-explorer-2008-on-window-7/): Learn how to resolve Microsoft Document Explorer 2008 installation issues on Windows 7 by manually running the installer from the Visual Studio 2008 setup files.
- [New laptop and Windows 7](https://engineering-leadership.hinshelwood.com/articles/new-laptop-and-windows-7/): A family upgrades to a Dell laptop running Windows 7, highlighting improved performance over Vista, user preferences, and buying options in the UK.
- [The delivery Mk II](https://engineering-leadership.hinshelwood.com/articles/the-delivery-mk-ii/): A personal story about the birth of a son, Kaiden, featuring a rapid delivery, family experiences in hospital, and early moments with his older sister.
- [Fun with Virgin+](https://engineering-leadership.hinshelwood.com/articles/fun-with-virgin/): A practical guide to resolving display issues with Virgin+ boxes when switching from HDMI to SCART, including step-by-step reset instructions for picture recovery.
- [Reformat your CSS on the fly](https://engineering-leadership.hinshelwood.com/articles/reformat-your-css-on-the-fly/): 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.
- [Internet Explorer 8 Release Candidate 1 (RC1)](https://engineering-leadership.hinshelwood.com/articles/internet-explorer-8-release-candidate-1-rc1/): Microsoft has released Internet Explorer 8 Release Candidate 1, featuring performance improvements and bug fixes ahead of the browser’s final version.
- [Feedburner, no Google…](https://engineering-leadership.hinshelwood.com/articles/feedburner-no-google/): Feedburner users are being migrated to Google servers, requiring feed URL updates to avoid slower load times. The process is simple, with improved stats promised.
- [Installing Team Explorer 2008 on Windows 7](https://engineering-leadership.hinshelwood.com/articles/installing-team-explorer-2008-on-windows-7/): Step-by-step guide to installing Team Explorer 2008 on Windows 7, troubleshooting proxy and firewall issues, and connecting to CodePlex and TFS Sticky Buddy.
- [Am I a stoner hippy?](https://engineering-leadership.hinshelwood.com/articles/am-i-a-stoner-hippy/): Explores how dyslexia and multidimensional thinking influence creativity, learning styles, and perceptions, challenging stereotypes about free thinkers and "hippy" labels.
- [Installing Visual Studio 2008 Team Suite on Windows 7](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2008-team-suite-on-windows-7/): Step-by-step guide to installing Visual Studio 2008 Team Suite on Windows 7, including setup issues, component selection, and tips for running in a virtual environment.
- [Installing Windows 7](https://engineering-leadership.hinshelwood.com/articles/installing-windows-7/): Step-by-step guide to installing Windows 7 in a virtual environment, covering setup options, first boot, and initial configuration with screenshots.
- [Windows 7 Beta is Live!](https://engineering-leadership.hinshelwood.com/articles/windows-7-beta-is-live/): Windows 7 Beta is now available for download, offering early access to the next version of Windows with improved stability and limited licences for public testing.
- [Learning more about Visual Studio 2008](https://engineering-leadership.hinshelwood.com/articles/learning-more-about-visual-studio-2008/): Discover a free Microsoft learning programme to improve your Visual Studio 2008 skills, suitable for both new and experienced software developers.
- [Microsoft Answer for the end-user](https://engineering-leadership.hinshelwood.com/articles/microsoft-answer-for-the-end-user/): A user-friendly Microsoft Answers forum for Windows Vista, offering clear, non-technical help on updates, hardware, networking, security, performance, and more.
- [Does test-driven development speed up development?](https://engineering-leadership.hinshelwood.com/articles/does-test-driven-development-speed-up-development/): Explores whether test-driven development (TDD) accelerates software delivery by reducing complexity, rework, and design flaws, and improving adaptability and productivity.
- [Managing the “VSTS Developers” LinkedIn group](https://engineering-leadership.hinshelwood.com/articles/managing-the-vsts-developers-linkedin-group/): Announces new managers for the VSTS Developers LinkedIn group to improve member support, information sharing, and response times for ALM and TFS topics.
- [Merry Christmas](https://engineering-leadership.hinshelwood.com/articles/merry-christmas/): Seasonal greetings with links to create and send ElfYourself eCards, plus troubleshooting tips for viewing animated holiday cards online.
- [Removing a dead Solution Deployment from MOSS 2007](https://engineering-leadership.hinshelwood.com/articles/removing-a-dead-solution-deployment-from-moss-2007/): Learn how to manually remove a failed or stuck solution deployment job in Microsoft Office SharePoint Server 2007 using Central Administration tools.
- [Live Framework](https://engineering-leadership.hinshelwood.com/articles/live-framework/): Explores using Azure Services Platform to enable cloud-based configuration, real-time chat, and collaboration features in WPF applications, similar to Xbox Live.
- [SkyDrive: 25 GB of free online storage](https://engineering-leadership.hinshelwood.com/articles/skydrive-25-gb-of-free-online-storage/): Get 25GB of free online storage with SkyDrive, integrated with Windows Live services for easy file sharing, photo management, and contact connectivity.
- [TFS Event Handler v1.3 released](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-v1-3-released/): TFS Event Handler v1.3 automates work item notifications in Team Foundation Server 2008, now supporting group alerts and custom event handler extensions. .NET 3.5 SP1 required.
- [Retrieving an identity from Team Foundation Server using only the display name](https://engineering-leadership.hinshelwood.com/articles/retrieving-an-identity-from-team-foundation-server-using-only-the-display-name/): 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.
- [TFS Event Handler v1.1 released](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-v1-1-released/): Automates notifications for Team Foundation Server 2008 work item changes, removing the need for manual alerts. Includes a framework for custom event handler development.
- [Visual Studio Team System 2008 Database Edition GDR Installation](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-2008-database-edition-gdr-installation/): Step-by-step guide to installing Visual Studio Team System 2008 Database Edition GDR, including prerequisites, uninstalling old versions, and new project options.
- [Visual Studio Team System 2008 Database Edition GDR has been released!](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-2008-database-edition-gdr-has-been-released/): The new Database Edition GDR for Visual Studio Team System 2008 adds model-based SQL schema design, extensibility, provider support, and standalone deployment tools.
- [Least opportune time](https://engineering-leadership.hinshelwood.com/articles/least-opportune-time/): A developer faces a CodePlex TFS server outage while releasing TFS Sticky Buddy v2.0, highlighting the impact of downtime on software deployment and version control.
- [Advice on using XamRibbon with Composite WPF](https://engineering-leadership.hinshelwood.com/articles/advice-on-using-xamribbon-with-composite-wpf/): Provides guidance and code examples for integrating Infragistics XamRibbon with Composite WPF, including custom region adapters for dynamic tab and menu management.
- [Windows Live ID and OpenID](https://engineering-leadership.hinshelwood.com/articles/windows-live-id-and-openid/): Explains how to set up and link a Windows Live ID with OpenID for testing, enabling single sign-on and unified authentication across supported web services like Plaxo.
- [The great Xbox update](https://engineering-leadership.hinshelwood.com/articles/the-great-xbox-update/): Overview of the new Xbox Live update, including changes to the update process, introduction of Avatars, and user experiences with the latest features.
- [100,000 Visits](https://engineering-leadership.hinshelwood.com/articles/100-000-visits/): Celebrates reaching over 100,000 website visits, sharing traffic stats, browser usage, and visitor countries, highlighting site growth and audience diversity.
- [Team Suite on the cheap](https://engineering-leadership.hinshelwood.com/articles/team-suite-on-the-cheap/): Save 30% when upgrading from Visual Studio Team System 2008 component editions to Team Suite, offering a full set of development tools for better team collaboration.
- [DDD Scotland v2.0: 2nd of May 2009](https://engineering-leadership.hinshelwood.com/articles/ddd-scotland-v2-0-2nd-of-may-2009/): Developer Day Scotland returns on 2 May 2009, bringing together software developers for talks, networking, and community events in Scotland’s tech scene.
- [Composite WPF and Merged Dictionaries](https://engineering-leadership.hinshelwood.com/articles/composite-wpf-and-merged-dictionaries/): Explains how to manage dynamic resource dictionaries and themes in WPF with Composite WPF, addressing common errors and providing code solutions for region management.
- [TFS Data Manager](https://engineering-leadership.hinshelwood.com/articles/tfs-data-manager/): Manage and clone TFS projects across servers, enhance disaster recovery, and access advanced features for improved application lifecycle management (ALM).
- [Visual Studio Team System 2008 Team Foundation Server Power Tools](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-2008-team-foundation-server-power-tools/): Overview of the latest Power Tools release for Visual Studio Team System 2008 Team Foundation Server, highlighting new features and improvements for ALM and TFS customisation.
- [TFS Sticky Buddy 2.0 development started…](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-2-0-development-started/): Development of TFS Sticky Buddy 2.0 has begun, focusing on modular WPF architecture and new navigation features. Early CTP version and updates are available for download.
- [TFS Sticky Buddy v2.0](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-v2-0/): Sticky Buddy v2.0 introduces a redesigned interface, modular structure, and expanded diagram features for improved usability in TFS-related workflows.
- [Interview with my favourite author](https://engineering-leadership.hinshelwood.com/articles/interview-with-my-favourite-author/): A personal reflection on an interview with author David Webber, discussing his works and passion for the military science fiction genre.
- [Mozy Backup providing extra space this month](https://engineering-leadership.hinshelwood.com/articles/mozy-backup-providing-extra-space-this-month/): Mozy is doubling its referral bonus to 512MB of extra backup space until 30 November 2008, making it easier to expand your online storage by inviting friends.
- [Unlikely bloggers…](https://engineering-leadership.hinshelwood.com/articles/unlikely-bloggers/): Highlights the value of people from non-traditional backgrounds, like helpdesk professionals, sharing their knowledge and experiences through blogging.
- [Visual Studio Team System 2008 Database Edition GDR RC (release candidate)](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-2008-database-edition-gdr-rc-release-candidate/): The release candidate for Visual Studio Team System 2008 Database Edition GDR offers upgrade support to RTM, with setup files, documentation, and user manuals available.
- [Infragistics WPF](https://engineering-leadership.hinshelwood.com/articles/infragistics-wpf/): Overview of using Infragistics WPF controls, focusing on dynamic menu generation with data binding and templates, and challenges with documentation and template selection.
- [Wakoopa](https://engineering-leadership.hinshelwood.com/articles/wakoopa/): Tracks and analyses your software usage, providing detailed statistics on application activity and allowing users to join teams or view individual app stats.
- [Branch Compare…A Life saver](https://engineering-leadership.hinshelwood.com/articles/branch-comparea-life-saver/): Explains how a built-in tool simplifies comparing two code branches, helping users resolve branching and merging issues more efficiently in version control systems.
- [MSBuild and Business Intelligence Packages, Ahhhhhh!](https://engineering-leadership.hinshelwood.com/articles/msbuild-and-business-intelligence-packages-ahhhhhh/): Discusses challenges in automating builds, testing, and deployment for SQL Server BI solutions, focusing on SSIS and SSAS packages and gaps in MSBuild support.
- [Hosted TFS, and cheap….from Phase2](https://engineering-leadership.hinshelwood.com/articles/hosted-tfs-and-cheap-from-phase2/): Overview of Phase2’s hosted Team Foundation Server (TFS) service, including features, pricing, backup, scalability, integration, and support details.
- [How-To: Display your Outlook calendar on you’re My Site](https://engineering-leadership.hinshelwood.com/articles/how-to-display-your-outlook-calendar-on-you-re-my-site/): Step-by-step guide to adding and configuring the Outlook calendar web part on your SharePoint My Site homepage using Outlook Web Access server settings.
- [How-To: Allow other users to interact with workflow on your MySite](https://engineering-leadership.hinshelwood.com/articles/how-to-allow-other-users-to-interact-with-workflow-on-your-mysite/): Learn how to give colleagues access to workflow tasks on your MySite by setting permissions on task lists in SharePoint, including adding users to the Contributors group.
- [Branch madness!](https://engineering-leadership.hinshelwood.com/articles/branch-madness/): 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.
- [TFS Usage Statistics](https://engineering-leadership.hinshelwood.com/articles/tfs-usage-statistics/): Provides key statistics on Team Foundation Server usage, including user activity, work items, version control, builds, and recent command counts for project tracking.
- [Sync extension for Lists/Collections or whatever](https://engineering-leadership.hinshelwood.com/articles/sync-extension-for-lists-collections-or-whatever/): Explains how to synchronise two .NET collections by applying differences, with thread safety using locks, ensuring target lists match source lists efficiently.
- [Team System MVP](https://engineering-leadership.hinshelwood.com/articles/team-system-mvp/): Recognition as a Microsoft Team System MVP, highlighting the award’s significance, annual renewal, and acknowledgment of peers in the Application Lifecycle Management field.
- [Development and Database combined](https://engineering-leadership.hinshelwood.com/articles/development-and-database-combined/): Microsoft has merged Visual Studio Team Edition for Developers and Database Developers, giving users of either version access to both tools in 2005 and 2008 editions.
- [Creating a WPF Work Item Control](https://engineering-leadership.hinshelwood.com/articles/creating-a-wpf-work-item-control/): 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.
- [Windows Live Wave 3](https://engineering-leadership.hinshelwood.com/articles/windows-live-wave-3/): Download and try the latest Windows Live Wave 3 beta applications, including Messenger and Writer, with options for web or full local installation in multiple languages.
- [My first ALM and second VSTS presentaton!](https://engineering-leadership.hinshelwood.com/articles/my-first-alm-and-second-vsts-presentaton/): Reflections on delivering ALM and VSTS presentations, focusing on knowledge sharing, presentation style, and insights into pre-sales technology consultancy roles.
- [Presenting Aplication Lifecycle Management: Precursor](https://engineering-leadership.hinshelwood.com/articles/presenting-aplication-lifecycle-management-precursor/): An introduction to Application Lifecycle Management (ALM), sharing first-time presentation experiences, preparation tips, and insights on related tools like Visual Studio Team System.
- [A problem with Diarist 2!](https://engineering-leadership.hinshelwood.com/articles/a-problem-with-diarist-2/): User lost a blog post in Diarist 2 after accidentally using the blog selection dropdown, suggesting its removal to prevent data loss and improve usability.
- [Working from a Mobile again!](https://engineering-leadership.hinshelwood.com/articles/working-from-a-mobile-again/): Discusses the need for a mobile app to manage and edit Team Foundation Server (TFS) work items offline, enabling productivity while travelling without a laptop.
- [Team Build Error](https://engineering-leadership.hinshelwood.com/articles/team-build-error/): Explains troubleshooting a confusing MS Build error in a mixed Visual Studio 2005/2008 environment, resolved by updating GDR and Business Intelligence components.
- [Found GDR Bug: At least I think it is](https://engineering-leadership.hinshelwood.com/articles/found-gdr-bug-at-least-i-think-it-is/): Describes a bug in GDR and Data Dude where SQL views using derived tables cause unresolved reference errors, impacting database project development and validation.
- [Visual Studio 2008 and the GDR CTP16](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2008-and-the-gdr-ctp16/): Discusses issues with Visual Studio 2008 GDR CTP16 handling complex stored procedure dependencies during database import, and challenges faced when uninstalling the GDR.
- [TFS Sticky Buddy Update](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-update/): The latest update fixes login issues when no domain is entered and improves handling of large work item lists in TFS Sticky Buddy version 1.6.
- [Compatibility view in IE8](https://engineering-leadership.hinshelwood.com/articles/compatibility-view-in-ie8/): Explains how IE8’s Compatibility View lets users easily switch to IE7 mode for better website display, with the feature appearing only on certain sites.
- [Cool new feature in IE8](https://engineering-leadership.hinshelwood.com/articles/cool-new-feature-in-ie8/): Internet Explorer 8 introduces enhanced address bar features, making it easier and faster to find and revisit websites for improved browsing efficiency.
- [LINQ to XSD](https://engineering-leadership.hinshelwood.com/articles/linq-to-xsd/): Explains how to use LINQ to XSD in C# to generate classes from XSD files, including setup steps, project configuration, and integration with MSBuild.
- [Installing Internet Explorer 8 Beta 2](https://engineering-leadership.hinshelwood.com/articles/installing-internet-explorer-8-beta-2/): Provides download links, installation guidance, and updates for Internet Explorer 8 Beta 2 on various Windows versions, plus resources for IT professionals and businesses.
- [Calling an object method in a data trigger](https://engineering-leadership.hinshelwood.com/articles/calling-an-object-method-in-a-data-trigger/): 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.
- [WPF Threading](https://engineering-leadership.hinshelwood.com/articles/wpf-threading/): Learn how to handle multi-threading with ObservableCollection in WPF, including solutions for cross-thread collection binding and practical tips for .NET developers.
- [Heat ITSM](https://engineering-leadership.hinshelwood.com/articles/heat-itsm/): Describes integrating Heat ITSM with Team Foundation Server to sync and manage support calls, automate work item creation, and streamline IT support workflows.
- [What to do when you dont have a working computer!](https://engineering-leadership.hinshelwood.com/articles/what-to-do-when-you-dont-have-a-working-computer/): Tips for staying productive without a computer, including using mobile devices for web browsing, writing, and software tasks when your main PC is unavailable.
- [If you had a choice!](https://engineering-leadership.hinshelwood.com/articles/if-you-had-a-choice/): A poll asking .NET developers which Windows operating system they prefer for running Visual Studio 2008, including XP, Vista, and Server 2008 options.
- [Problems with Team Explorer after installed Visual Studio 2008 SP1 RTM](https://engineering-leadership.hinshelwood.com/articles/problems-with-team-explorer-after-installed-visual-studio-2008-sp1-rtm/): Describes a Team Explorer error after installing Visual Studio 2008 SP1 RTM, troubleshooting steps taken, and issues with accessing version control features.
- [Updating to Visual Studio 2008 SP1](https://engineering-leadership.hinshelwood.com/articles/updating-to-visual-studio-2008-sp1/): Guidance on upgrading from Visual Studio 2008 SP1 Beta to SP1, including required tools, steps, and downloads for both Visual Studio and .NET Framework 3.5.
- [Ooooh, RTM Delight](https://engineering-leadership.hinshelwood.com/articles/ooooh-rtm-delight/): Visual Studio 2008, .NET Framework 3.5 SP1, and Team Foundation Server 2008 Beta 1 released, featuring major improvements for developers in data, performance, and deployment.
- [.NET Service Manager](https://engineering-leadership.hinshelwood.com/articles/net-service-manager/): A tool for managing and integrating local and remote services in .NET applications, enabling easy creation of client-side APIs for web services and components.
- [IHandlerFactory](https://engineering-leadership.hinshelwood.com/articles/ihandlerfactory/): 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.
- [Hosted Sticky Buddy](https://engineering-leadership.hinshelwood.com/articles/hosted-sticky-buddy/): Access a hosted version of TFS Sticky Buddy, requiring .NET 3.5 and Team Explorer 2008, with fast performance and ClickOnce deployment for easy installation.
- [RDdotNET](https://engineering-leadership.hinshelwood.com/articles/rddotnet/): A portal for hosting and sharing .NET tools and ClickOnce applications, including TFS Sticky Buddy and TFS Event Handler, with links to related resources and a blog.
- [Messenger United](https://engineering-leadership.hinshelwood.com/articles/messenger-united/): A web app enabling integration between Microsoft Messenger, LinkedIn, and Facebook, supporting third-party sync and part of Microsoft’s Connected Systems initiative.
- [Error creating listener in Team Build](https://engineering-leadership.hinshelwood.com/articles/error-creating-listener-in-team-build/): Explains how to resolve AddressAccessDeniedException when running tests in Team Build by granting the Build Agent service account permission to create IIS listeners.
- [TFS Error: MSB4018 The "BuildShadowTask" task failed unexpectedly](https://engineering-leadership.hinshelwood.com/articles/tfs-error-msb4018-the-buildshadowtask-task-failed-unexpectedly/): Explains the MSB4018 "BuildShadowTask" error in TFS when using Accessors in unit test projects, its cause, and how removing .accessor files resolves build issues.
- [OutSync with proxy servers](https://engineering-leadership.hinshelwood.com/articles/outsync-with-proxy-servers/): Explains how to configure .NET applications, like OutSync, to work with proxy servers by editing the config file for proxy authentication and connectivity.
- [TFS Event Handler Update](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-update/): Bug fixes and improvements have been made to the TFS Event Handler, resolving recent issues and enhancing reliability for .NET, ALM, and WIT workflows.
- [SharePoint Solutions Rant](https://engineering-leadership.hinshelwood.com/articles/sharepoint-solutions-rant/): Discusses the need for a streamlined, end-to-end way to build and deploy SharePoint solutions in Visual Studio, including remote development and simplified workflows.
- [Developing for SharePoint on your local computer](https://engineering-leadership.hinshelwood.com/articles/developing-for-sharepoint-on-your-local-computer/): Guide to setting up Visual Studio 2008 and required tools for developing and testing SharePoint solutions locally without a full SharePoint server installation.
- [Change of plan](https://engineering-leadership.hinshelwood.com/articles/change-of-plan/): Explains the decision to develop a system independent of SharePoint for easier testing, with plans to integrate into MOSS and assess SharePoint feature complexity.
- [Creating a SharePoint Solution](https://engineering-leadership.hinshelwood.com/articles/creating-a-sharepoint-solution/): Follow the development of a .NET 3.5 SharePoint Time Off Management app using WebParts, Workflow, InfoPath, SQL Server, and test-driven development techniques.
- [Linked in VSTS Group](https://engineering-leadership.hinshelwood.com/articles/linked-in-vsts-group/): A LinkedIn group for developers customising or extending Visual Studio Team System (VSTS), covering .NET, ALM, TFS, version control, testing, and related topics.
- [Linked in Codeplex developers group](https://engineering-leadership.hinshelwood.com/articles/linked-in-codeplex-developers-group/): Join LinkedIn groups for Codeplex developers and coordinators. Membership requires a Codeplex account and project involvement. Profile verification is needed to join.
- [Post Event: MSDN Roadshow (Glasgow)](https://engineering-leadership.hinshelwood.com/articles/post-event-msdn-roadshow-glasgow/): Insights from the MSDN Roadshow in Glasgow, covering ADO.NET Entity Framework, Data Services, Silverlight 2, and Team Suite, plus event resources and highlights.
- [Post event: Developer Day Scotland](https://engineering-leadership.hinshelwood.com/articles/post-event-developer-day-scotland/): Highlights from Developer Day Scotland, featuring sessions on ADO.NET Data Services, anti-patterns, continuous integration, and test-driven development by expert speakers.
- [Developer Day Scotland 2008](https://engineering-leadership.hinshelwood.com/articles/developer-day-scotland/): Event for software developers in Glasgow featuring talks, networking, and a post-event dinner. Held at Glasgow Caledonian University on 10 May 2008.
- [Assembly Version does not change in Visual Basic Workflow projects](https://engineering-leadership.hinshelwood.com/articles/assembly-version-does-not-change-in-visual-basic-workflow-projects/): Explains a Visual Basic compiler bug where assembly version numbers do not update after rebuilding, affecting Workflow and other projects, and offers manual workaround steps.
- [Another day another Codeplex Project](https://engineering-leadership.hinshelwood.com/articles/another-day-another-codeplex-project/): Explores extending SharePoint Designer with custom workflow activities from CodePlex, highlighting solutions for user profile lookups beyond default site info.
- [Major deadline](https://engineering-leadership.hinshelwood.com/articles/major-deadline/): A critical SharePoint migration project faces urgent deadlines after performance issues, requiring rapid deployment of a new MOSS portal to support key business functions.
- [Vote for your feature](https://engineering-leadership.hinshelwood.com/articles/vote-for-your-feature/): Vote for upcoming TFS Sticky Buddy features, view current suggestions, and submit your own ideas to help shape future updates for this .NET WPF tool.
- [Kerberos problems](https://engineering-leadership.hinshelwood.com/articles/kerberos-problems/): Addresses Kerberos double hop authentication issues in workplace networks, with links to resources on Kerberos basics and troubleshooting delegation problems.
- [TFS Sticky Buddy v1.0](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-v1-0/): Graphical tool for viewing, navigating, and managing TFS Work Items with customisable templates. Built in VB.NET and WPF; requires .NET 3.5 and Team Foundation Server.
- [End of another Sticky week](https://engineering-leadership.hinshelwood.com/articles/end-of-another-sticky-week/): Update on TFS Sticky Buddy: new support for connecting to external TFS servers, project loading, and customisable skins for different Team Foundation Server life cycles.
- [TFS Stick Buddy v0.4.0 CTP2 released](https://engineering-leadership.hinshelwood.com/articles/tfs-stick-buddy-v0-4-0-ctp2-released/): TFS Stick Buddy v0.4.0 CTP2 lets you customise and display TFS work items by query, with colour-coded states and support for Visual Studio and TFS Web Access.
- [TFS Sticky Buddy v0.3.1 CTP1](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-v0-3-1-ctp1/): Preview release of a WPF-based dashboard for Team Foundation Server, showing Areas and Iterations as diagrams; early version with limited features and bug reporting.
- [Bug in ObservableCollection?](https://engineering-leadership.hinshelwood.com/articles/bug-in-observablecollection/): Explains issues using ObservableCollection with generic types in .NET, why errors occur, and discusses workarounds and limitations when working with custom classes.
- [Creating a better TFS Sticky Buddy (Core)](https://engineering-leadership.hinshelwood.com/articles/creating-a-better-tfs-sticky-buddy-core/): Explains building a flexible WPF data model in VB.NET for visualising hierarchical relationships using generics, ObservableCollections, and INotifyPropertyChanged.
- [Developer joins TFS Sticky Buddy project](https://engineering-leadership.hinshelwood.com/articles/developer-joins-tfs-sticky-buddy-project/): A new developer, Eric Willeke, has joined the TFS Sticky Buddy project team, bringing experience as a tester to help improve and advance the project’s development.
- [What the 0x80072020?](https://engineering-leadership.hinshelwood.com/articles/what-the-0x80072020/): Explains the 0x80072020 error in .NET 3.5 PrincipalContext when using ASP.NET impersonation with Active Directory, its cause, and security concerns with workaround.
- [Loss of My.User.Name is not that bad](https://engineering-leadership.hinshelwood.com/articles/loss-of-my-user-name-is-not-that-bad/): Explains how to access and manage user and security information in .NET applications using System.DirectoryServices.AccountManagement instead of My.User.Name.
- [Waffling on SharePoint](https://engineering-leadership.hinshelwood.com/articles/waffling-on-sharepoint/): Discusses the challenges of creating non-technical SharePoint documentation for business users, highlighting the platform’s flexibility and the importance of clear communication.
- [TFS Sticky Buddy POC (WPF) release](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-poc-wpf-release/): Proof of concept release of a WPF-based Team Foundation Server dashboard app, including source code. Requires .NET 3.5 and Visual Studio 2008 Team Explorer.
- [TFS Sticky Buddy POC (WinForms) release](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-poc-winforms-release/): Proof of concept Windows Forms dashboard for Team Foundation Server, including source code. Requires .NET 3.5 and Visual Studio 2008 Team Explorer. For demo use only.
- [TFS Sticky Buddy layout fun](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-layout-fun/): A developer shares challenges and insights from building a TFS Sticky Buddy UI in WinForms and WPF, comparing layout issues and ease of use between the two frameworks.
- [TFS Sticky Buddy Codeplex project](https://engineering-leadership.hinshelwood.com/articles/tfs-sticky-buddy-codeplex-project/): Open source tool for visualising Team Foundation Server project status, showing work items, assignments, and progress in real time on large displays for team visibility.
- [I always wanted to be an Admiral!](https://engineering-leadership.hinshelwood.com/articles/i-always-wanted-to-be-an-admiral/): A personal reflection on taking a Battlestar Galactica character quiz after finishing season 3, sharing excitement and anticipation for the upcoming final season.
- [Setting up SharePoint for the Enterprise](https://engineering-leadership.hinshelwood.com/articles/setting-up-sharepoint-for-the-enterprise/): Guidance on deploying SharePoint for global enterprises, including architecture considerations and best practices for multi-country user access and scalability.
- [Installing MOSS 2007 from scratch](https://engineering-leadership.hinshelwood.com/articles/installing-moss-2007-from-scratch/): Step-by-step guide to installing Microsoft Office SharePoint Server 2007 from a clean environment, including prerequisites, SQL setup, service packs, and configuration tips.
- [Kerberos and SharePoint 2007](https://engineering-leadership.hinshelwood.com/articles/kerberos-and-sharepoint-2007/): Explains how to configure Kerberos authentication for SharePoint 2007 by setting Service Principal Names (SPNs) in Active Directory for each DNS and port combination.
- [Connecting to SQL Server using DNS update](https://engineering-leadership.hinshelwood.com/articles/connecting-to-sql-server-using-dns-update/): Explains how updating DNS and Service Principal Names (SPNs) in Active Directory enables secure Windows Authentication connections to SQL Server instances.
- [Connecting to SQL Server using DNS](https://engineering-leadership.hinshelwood.com/articles/connecting-to-sql-server-using-dns/): Explains how to enable Windows Authentication for SQL Server connections via DNS by configuring the SQL Server Browser service and setting up Service Principal Names (SPNs).
- [The SharePoint Plan: Database move headache mitigation](https://engineering-leadership.hinshelwood.com/articles/the-sharepoint-plan-database-move-headache-mitigation/): Guidance on moving SharePoint SQL Server databases to a new server using DNS redirection, aiming to simplify migration and minimise downtime and manual effort.
- [New Event Handlers](https://engineering-leadership.hinshelwood.com/articles/new-event-handlers/): Adds two event handlers for TFS: one emails users when assigned a work item, the other notifies users when work is reassigned. Includes setup and deployment steps.
- [TFS Event Handler (Prototype) Refresh](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-prototype-refresh/): Bug fixes and updates for the TFS Event Handler Prototype, now supporting .NET 3.5 and Visual Studio 2008. Includes installer refresh and event handler examples.
- [TFS Event Handler CTP 2 Released](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-ctp-2-released/): CTP 2 of TFS Event Handler is now available, offering updated executables and source code for managing Team Foundation Server events. Requires Team Explorer 2008 and .NET 3.5.
- [TFS Event Handler CTP1 Released](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-ctp1-released/): Early release of a TFS Event Handler tool for managing server events, requiring manual setup and not production-ready; includes a basic client app with known issues.
- [Removing ACL's for dead AD accounts](https://engineering-leadership.hinshelwood.com/articles/removing-acls-for-dead-ad-accounts/): Explains how to identify and remove access control entries (ACLs) for deleted Active Directory accounts using .NET, including challenges and code examples for automation.
- [Get your Twitter feed as a badge on your email!](https://engineering-leadership.hinshelwood.com/articles/get-your-twitter-feed-as-a-badge-on-your-email/): Learn how to display your Twitter feed as a badge using HTML and FeedBurner, making it easy to share live updates in emails or on any web page.
- [Community-Credit feedback](https://engineering-leadership.hinshelwood.com/articles/community-credit-feedback/): Suggestions for improving Community Credit, including category management, privacy for user profiles, SEO, faster page loads, moderation rewards, and guest developer roles.
- [Unique ID in SharePoint list](https://engineering-leadership.hinshelwood.com/articles/unique-id-in-sharepoint-list/): SharePoint lists include a built-in unique, auto-generated ID column. Enable its display in list settings to show unique IDs for each item without custom solutions.
- [TFS Event Handler Revisited](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-revisited/): Discusses updating a TFS Event Handler prototype for Visual Studio 2008 and Team Foundation Server 2008, highlighting challenges with code and language compatibility.
- [Xbox  Live to Twitter Update (v0.2.3)](https://engineering-leadership.hinshelwood.com/articles/xbox-live-to-twitter-update-v0-2-3/): An updated tool that posts Xbox Live status updates to Twitter, with plans for customisation options and achievement tracking. Source code and downloads available.
- [Returning an Anonymous type](https://engineering-leadership.hinshelwood.com/articles/returning-an-anonymous-type/): Explains how to return and use anonymous types from functions in VB.NET, highlighting late binding, Option Strict settings, and limitations like lack of IntelliSense.
- [My first Extension method](https://engineering-leadership.hinshelwood.com/articles/my-first-extension-method/): Explains how to create and use extension methods in VB.NET, with an example for enhancing the XboxInfo class to display and track Xbox Live status changes.
- [I always like a good Serenity plug](https://engineering-leadership.hinshelwood.com/articles/i-always-like-a-good-serenity-plug/): Find out which Serenity character you resemble most with quiz results, including detailed character match percentages and a brief personality summary.
- [Xbox Live To Twitter](https://engineering-leadership.hinshelwood.com/articles/xbox-live-to-twitter/): Guide to connecting your Xbox Live gamertag to Twitter using a custom application, including troubleshooting tips and links to source code and downloads.
- [SharePoint 3.0 and MOSS 2007 Service Pack 1 Update](https://engineering-leadership.hinshelwood.com/articles/sharepoint-3-0-and-moss-2007-service-pack-1-update/): Guidance on resolving SharePoint 3.0 and MOSS 2007 Service Pack 1 installation errors, including database version issues and solutions using stsadm commands.
- [Festive holiday studying](https://engineering-leadership.hinshelwood.com/articles/festive-holiday-studying/): A personal update on holiday plans, family time, Xbox gaming, and learning WPF for .NET development, with reflections on SharePoint and festive online activities.
- [No love between McAfee Enterprise and MOSS 2007](https://engineering-leadership.hinshelwood.com/articles/no-love-between-mcafee-enterprise-and-moss-2007/): Explains how McAfee antivirus can cause search errors in Microsoft Office SharePoint Server 2007, highlighting compatibility issues and the need for specialised solutions.
- [Installing Windows SharePoint Services 3.0 Service Pack 1 (SP1)](https://engineering-leadership.hinshelwood.com/articles/installing-windows-sharepoint-services-3-0-service-pack-1-sp1/): Step-by-step guide to downloading, unpacking, and troubleshooting the installation of Windows SharePoint Services 3.0 Service Pack 1 (SP1) on Windows systems.
- [Installing The 2007 Microsoft Office Servers Service Pack 1 (SP1) ...Again](https://engineering-leadership.hinshelwood.com/articles/installing-the-2007-microsoft-office-servers-service-pack-1-sp1-again/): Documents the installation issues and error logs encountered when applying Microsoft Office Servers 2007 SP1, including timeout exceptions and troubleshooting steps.
- [MOSS SP1 Install Notes](https://engineering-leadership.hinshelwood.com/articles/moss-sp1-install-notes/): Step-by-step notes for installing Microsoft Office SharePoint Server 2007 Service Pack 1, including prerequisites, download links, and key resources for a smooth update.
- [Silverlight cream, kinda, but it is interesting!](https://engineering-leadership.hinshelwood.com/articles/silverlight-cream-kinda-but-it-is-interesting/): Explores Microsoft's use of Silverlight in its downloads site beta, comparing it to Flash, and discusses early adoption and internal testing of Silverlight technology.
- [Information Sync](https://engineering-leadership.hinshelwood.com/articles/information-sync/): Compares mobile and online contact and calendar sync tools, highlighting issues with ActiveSync and Mobile Device Center, and recommending Plaxo for unified syncing.
- [The new ClusterMaps: NeoWORX](https://engineering-leadership.hinshelwood.com/articles/the-new-clustermaps-neoworx/): Overview of NeoWORX, a web service for visualising global data on interactive maps, with potential for real-time fleet tracking and customisable geolocation displays.
- [Mozy update](https://engineering-leadership.hinshelwood.com/articles/mozy-update/): Gained 4.3GB total Mozy cloud storage through referrals, detailing backup choices and ease of use for family members. Excludes music, code, and emails from backup.
- [Community Credit and GeeksWithBlogs up a tree](https://engineering-leadership.hinshelwood.com/articles/community-credit-and-geekswithblogs-up-a-tree/): GeeksWithBlogs.net and Community Credit have completed integration, enabling seamless collaboration and new features for their blogging and community platforms.
- [It's nice to be appreciated!](https://engineering-leadership.hinshelwood.com/articles/its-nice-to-be-appreciated/): Describes joining Community Credit, earning recognition and prizes for tech contributions, and becoming a moderator after engaging with the site's community and founder.
- [TFS Event Handler gets 3 stars from Accentient](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-gets-3-stars-from-accentient/): TFS Event Handler received a 3-star rating from Accentient, highlighting its popularity and ranking on the Team System Widgets platform for ALM and TFS tools.
- [Identity crisis](https://engineering-leadership.hinshelwood.com/articles/identity-crisis/): Explores using Microsoft Identity Lifecycle Manager 2007 to unify and automate employee identity data across multiple systems, improving consistency, security, and efficiency.
- [Mozy Backup Space Gathering update](https://engineering-leadership.hinshelwood.com/articles/mozy-backup-space-gathering-update/): Update on Mozy backup referral progress, explaining how extra storage is earned when referrals complete their first backup and tracking current referral statuses.
- [Mozy Backup](https://engineering-leadership.hinshelwood.com/articles/mozy-backup/): Mozy Backup offers affordable, easy-to-use online backup with free storage, simple setup, and automatic protection for your digital files, photos, and documents.
- [Event: MSDN: SharePoint for Developers (Edinburgh)](https://engineering-leadership.hinshelwood.com/articles/event-msdn-sharepoint-for-developers-edinburgh/): Insights from an Edinburgh MSDN event covering SharePoint 2007 development, workflows in Visual Studio 2008, enterprise search, and InfoPath integration for forms.
- [Hold on lads, I have an idea!](https://engineering-leadership.hinshelwood.com/articles/hold-on-lads-i-have-an-idea/): Proposal for an interface to view and edit company hierarchy data, enabling staff management, reorganisation, and integration with HR, Active Directory, and SharePoint systems.
- [AD Update-O-Matic](https://engineering-leadership.hinshelwood.com/articles/ad-update-o-matic/): Application for automating Active Directory updates by extracting user data, editing in a database, and syncing changes, supporting .NET and MOSS 2007 environments.
- [VS2008 Update](https://engineering-leadership.hinshelwood.com/articles/vs2008-update/): Covers experiences updating to Visual Studio 2008 RTM, installing Team Explorer, project upgrades from Beta 2, and attending a SharePoint developer event in Edinburgh.
- [RTM Confusion](https://engineering-leadership.hinshelwood.com/articles/rtm-confusion/): Addresses confusion about the availability of Team Explorer in the Visual Studio 2008 RTM release, download options, and related requirements for source control and .NET 3.5.
- [Get your RTM here!](https://engineering-leadership.hinshelwood.com/articles/get-your-rtm-here/): Visual Studio 2008 and .NET 3.5 have reached RTM status, with developers now able to access and download the official releases for production use.
- [Where am I?](https://engineering-leadership.hinshelwood.com/articles/where-am-i/): Describes a .NET application that tracks users’ locations via IP, updates Active Directory, and uses LINQ for database queries, aiding internal office presence visibility.
- [Proxy server settings for SharePoint 2007](https://engineering-leadership.hinshelwood.com/articles/proxy-server-settings-for-sharepoint-2007/): Explains how to configure proxy server settings in SharePoint 2007, including passing user credentials and setting bypass rules for specific domains in the config file.
- [Why Integrated Authentication does not work with host headers!](https://engineering-leadership.hinshelwood.com/articles/why-integrated-authentication-does-not-work-with-host-headers/): Explains why Integrated Authentication fails with custom host headers on IIS, causing 401.1 errors, due to Windows loopback security checks and how to resolve it.
- [Installing TFS 2008 from scratch](https://engineering-leadership.hinshelwood.com/articles/installing-tfs-2008-from-scratch/): Step-by-step guide to installing TFS 2008 on a clean server, covering setup with SQL, Reporting Services, SharePoint integration, and troubleshooting authentication issues.
- [Falling of the TFS rehabilitation wagon](https://engineering-leadership.hinshelwood.com/articles/falling-of-the-tfs-rehabilitation-wagon/): Discusses implementing Team Foundation Server (TFS) for comprehensive project management, customising features, and integrating with SharePoint 2007 and business data tools.
- [Naming your servers in an enterprise environment](https://engineering-leadership.hinshelwood.com/articles/naming-your-servers-in-an-enterprise-environment/): Explains the importance of consistent, informative server naming conventions in enterprise environments to improve identification, management, and scalability.
- [Team Foundation Server SharePoint Integration](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-sharepoint-integration/): Explores the need for deeper integration between Team Foundation Server and SharePoint, including work item visibility, workflow support, and unified project management.
- [Amusing job requirements](https://engineering-leadership.hinshelwood.com/articles/amusing-job-requirements/): A humorous look at unrealistic job requirements for analyst programmers, highlighting the pitfalls of overloaded skill lists and offering practical advice for employers and job seekers.
- [Experts Exchange Hell - The slowest site in the world](https://engineering-leadership.hinshelwood.com/articles/experts-exchange-hell-the-slowest-site-in-the-world/): Analysis of Experts Exchange’s slow website performance, highlighting large page sizes, excessive HTML, and poor user experience on both fast and slow connections.
- [Branding and Customizing SharePoint 2007](https://engineering-leadership.hinshelwood.com/articles/branding-and-customizing-sharepoint-2007/): Learn how to customise and brand SharePoint 2007 sites using CSS and master pages, with insights on challenges, best practices, and useful resources for developers.
- [Refocus](https://engineering-leadership.hinshelwood.com/articles/refocus/): Discusses shifting focus to maintaining and migrating SharePoint 2003 sites, deploying MOSS 2007, and integrating business applications within an enterprise environment.
- [Windows Live Writer Beta 3 Hmm!](https://engineering-leadership.hinshelwood.com/articles/windows-live-writer-beta-3-hmm/): Details an issue with downloading Windows Live Writer Beta 3, support response, and provides updated links for the correct installer and troubleshooting steps.
- [Deep vein thrombosis (DVT) Update](https://engineering-leadership.hinshelwood.com/articles/deep-vein-thrombosis-dvt-update/): Update on efforts to improve DVT diagnosis and screening in Scotland, including a petition for mandatory assessment tools and Factor V gene testing in newborns.
- [Windows Live Writer Beta 3](https://engineering-leadership.hinshelwood.com/articles/windows-live-writer-beta-3/): Discusses challenges installing Windows Live Writer Beta 3 in workplace environments due to bundled installers and network restrictions, with a workaround using direct downloads.
- [Technorati Troubles](https://engineering-leadership.hinshelwood.com/articles/technorati-troubles/): Describes issues with Technorati blog claim verification, URL redirects, and invalid tag clouds, highlighting difficulties resolving these problems through support.
- [Jadie Hinshelwood: A yummy mummy is born!](https://engineering-leadership.hinshelwood.com/articles/jadie-hinshelwood-a-yummy-mummy-is-born/): Personal blog sharing experiences with pregnancy, miscarriage, and family life, offering support and insights for others on similar journeys to parenthood.
- [First day at Aggreko](https://engineering-leadership.hinshelwood.com/articles/first-day-at-aggreko/): Describes a first day at Aggreko, focusing on efficient onboarding, SharePoint deployment planning, and the challenge of migrating proprietary workflows and applications.
- [Xbox 360 Elite](https://engineering-leadership.hinshelwood.com/articles/xbox-360-elite/): A personal account of upgrading from a faulty Xbox 360 to an Xbox 360 Elite, including trade-in details and experiences with games like Bioshock and Stranglehold.
- [Uber-Dorky Nerd King](https://engineering-leadership.hinshelwood.com/articles/uber-dorky-nerd-king/): A light-hearted reflection on taking an online nerd test, sharing results, and playfully questioning what it means to be a nerd in today's digital culture.
- [Moderating for Community-Credit](https://engineering-leadership.hinshelwood.com/articles/moderating-for-community-credit/): Describes volunteering as a moderator for Community-Credit, reviewing user submissions, supporting an honest community, and earning credits and prizes through participation.
- [Blogging about](https://engineering-leadership.hinshelwood.com/articles/blogging-about/): A personal update covering job changes, technical projects with TFS and VS2008, learning goals, and life events, including job interviews and family milestones.
- [Interviewing for Microsoft](https://engineering-leadership.hinshelwood.com/articles/interviewing-for-microsoft/): A personal account of interviewing for a Microsoft Application Developer Consultant role, detailing the process, technical requirements, and lessons learned from the experience.
- [TFS Event Handler in .NET 3.5 Part 2 - Handling Team Foundation Server Events](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-2-handling-team-foundation-server-events/): Guide to implementing a resilient Team Foundation Server event handler in .NET 3.5 using WCF, including service contracts, endpoints, configuration, and event parsing.
- [TFS Event Handler in .NET 3.5 Part 2](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-2/): Explains how to build a resilient, scalable Team Foundation Server event handler using .NET 3.5, covering event handling techniques and key integration features.
- [Developing Peer-To-Peer Applications With WCF](https://engineering-leadership.hinshelwood.com/articles/developing-peer-to-peer-applications-with-wcf/): Guide to building peer-to-peer applications using Windows Communication Foundation (WCF), covering key concepts, implementation steps, and practical resources.
- [Microsoft does indeed listen](https://engineering-leadership.hinshelwood.com/articles/microsoft-does-indeed-listen/): Discussion on Microsoft's response to user interest in hosted Team Foundation Server (TFS), licensing challenges, and needed features for broader business adoption.
- [TFS Handover](https://engineering-leadership.hinshelwood.com/articles/tfs-handover/): Overview of preparing handover documentation for a TFS 2005 deployment, including server details, reference materials, and integration with SharePoint 2007.
- [Sharepoint planning](https://engineering-leadership.hinshelwood.com/articles/sharepoint-planning/): Guidance on effective SharePoint deployment in large organisations, highlighting architecture planning and the benefits of features like MySites.
- [Search just got better: Part 2](https://engineering-leadership.hinshelwood.com/articles/search-just-got-better-part-2/): Comparison of Tafiti and Search Crystal visual search engines, highlighting interface features, result display options, and usability for search visualisation.
- [TFS Event Handler in .NET 3.5 Part 1 - The Architecture](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-1-the-architecture/): Explains designing a resilient, scalable TFS event handler in .NET 3.5, focusing on system architecture using Visual Studio diagrams for planning and deployment.
- [Search just got better](https://engineering-leadership.hinshelwood.com/articles/search-just-got-better/): Tafiti is a visual search tool from Microsoft, offering easy filtering, saved searches, and features designed to improve web search for dyslexic users.
- [Visual Studio 2008 Team Edition for Architects](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2008-team-edition-for-architects/): Explains the lack of Windows Communication Foundation support in Visual Studio 2008 Team Edition for Architects' Application diagram and its impact on architecture design.
- [TFS Event Handler in .NET 3.5](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-in-net-3-5/): Learn how to build a resilient, scalable Team Foundation Server event handler using .NET 3.5, covering architecture, event handling, WCF MSMQ, and workflow integration.
- [Creating a custom proxy class](https://engineering-leadership.hinshelwood.com/articles/creating-a-custom-proxy-class/): 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.
- [Team Foundation Server Error TF30177: Team Project Creation Failed  - Part 2](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-error-tf30177-team-project-creation-failed-part-2/): Explains how to resolve Team Foundation Server project creation errors caused by SharePoint managed path conflicts, with steps to identify and fix site URL issues.
- [Using Visual Studio 2008](https://engineering-leadership.hinshelwood.com/articles/using-visual-studio-2008/): Overview of Visual Studio 2008 features, including multi-.NET Framework targeting, project upgrade notes, source control tips, and new debugging and workflow options.
- [About Me](https://engineering-leadership.hinshelwood.com/articles/about-me/): Personal profile with links to Martin Hinshelwood’s resume, LinkedIn, and background, clarifying identity and focusing on technology over football in search results.
- [Studying for the new job](https://engineering-leadership.hinshelwood.com/articles/studying-for-the-new-job/): Preparing for a new job by studying BizTalk Server, SharePoint Services, and .NET certifications, with recommended books and resources for exam readiness.
- [A change for the better #1 - Merrill Lynch to Aggreko](https://engineering-leadership.hinshelwood.com/articles/a-change-for-the-better-1/): A developer transitions from Merrill Lynch to Aggreko, seeking stability and opportunities to work with new technologies like SharePoint, TFS, and .NET 3.x.
- [Team Foundation Server Error TF30177 : Team Project Creation Failed](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-error-tf30177-team-project-creation-failed/): Explains how to resolve Team Foundation Server TF30177 errors by updating server URLs to use the FQDN, addressing proxy and DNS issues during project creation.
- [A new day, a new week, a new Team Server](https://engineering-leadership.hinshelwood.com/articles/a-new-day-a-new-week-a-new-team-server/): Covers upgrading to TFS 2008, smooth installation, creating projects with Visual Studio 2005, and exploring SharePoint integration with custom web services.
- [The cause of dyslexia](https://engineering-leadership.hinshelwood.com/articles/the-cause-of-dyslexia/): Dyslexia is a hereditary, neurological condition linked to brain structure and function, affecting reading ability but often associated with unique cognitive strengths.
- [Service Manager Factory](https://engineering-leadership.hinshelwood.com/articles/service-manager-factory/): Provides an upgraded managed service factory for .NET, with installer support for GAC deployment, enabling integration into various applications. Download and documentation available.
- [Windows Live SkyDrive Beta](https://engineering-leadership.hinshelwood.com/articles/windows-live-skydrive-beta/): Review of SkyDrive Beta’s ease of use for online file storage and sharing, with suggestions for improved online editing and SharePoint-style collaboration features.
- [Team Foundation Server Error 28936](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-error-28936/): Explains how Team Foundation Server installation fails with error 28936 due to IIS URLScan filter blocking web services, and how removing it resolves the issue.
- [Windows Vista Pre-SP1 Performance and Reliability Updates Result](https://engineering-leadership.hinshelwood.com/articles/windows-vista-pre-sp1-performance-and-reliability-updates-result/): A user shares improved speed and reliability after installing Windows Vista pre-SP1 updates on an older laptop, highlighting smoother performance and easier software use.
- [Becoming a better developer](https://engineering-leadership.hinshelwood.com/articles/becoming-a-better-developer/): Practical steps for improving as a developer, including ongoing learning, project work, community involvement, blogging, and embracing neurodiversity in tech.
- [Why I think VB.NET is a better choice than C#](https://engineering-leadership.hinshelwood.com/articles/why-i-think-vb-net-is-a-better-choice-than-c/): Compares VB.NET and C#, highlighting VB.NET’s advantages in readability, accessibility, case insensitivity, and real-time code checking, especially for dyslexic users.
- [VB 9](https://engineering-leadership.hinshelwood.com/articles/vb-9/): Comparison of Visual Basic and C#, highlighting arguments and evidence supporting Visual Basic’s advantages within the .NET development environment.
- [Hosted Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/hosted-team-foundation-server/): Explains challenges of hosting Team Foundation Server, including project isolation issues, upcoming improvements, and the availability of commercial hosted TFS services.
- [Microsoft's internal uptake of Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/microsofts-internal-uptake-of-team-foundation-server/): Microsoft widely adopted Team Foundation Server internally, with 21 instances supporting 734 projects and 5,600 users, driving rapid product development and updates.
- [Office Mobile 2007](https://engineering-leadership.hinshelwood.com/articles/office-mobile-2007/): Covers installing Office Mobile 2007 on Windows Mobile 6, highlighting new features like RSS feeds in Outlook Mobile and OneNote Mobile with desktop sync support.
- [MSN Cartoon (Beta)](https://engineering-leadership.hinshelwood.com/articles/msn-cartoon-beta/): Step-by-step guide to using MSN Cartoon Beta, a Microsoft tool for creating custom cartoon avatars from photos, including installation, editing, and saving options.
- [Application Owner](https://engineering-leadership.hinshelwood.com/articles/application-owner/): Explains the responsibilities of managing production applications, including vendor relations, issue resolution, audits, and system access, typically handled by a project manager.
- [An Application Deployment](https://engineering-leadership.hinshelwood.com/articles/an-application-deployment/): Highlights the challenges of deploying complex enterprise applications with incomplete, unclear documentation, emphasising the need for accurate installation guides.
- [Developer vindication](https://engineering-leadership.hinshelwood.com/articles/developer-vindication/): A .NET developer shares their experience of being approached by Microsoft for a potential job, highlighting the challenges of US work visa requirements in the tech industry.
- [HTC Touch / Black Shadow Weather](https://engineering-leadership.hinshelwood.com/articles/htc-touch-black-shadow-weather/): Guide to adding custom cities to the HTC Touch or Black Shadow Weather app by editing registry or XML files, enabling local weather display on Windows Mobile 6 devices.
- [Soapbox Beta](https://engineering-leadership.hinshelwood.com/articles/soapbox-beta/): Microsoft Soapbox is an online video sharing platform similar to YouTube, using Flash for playback instead of Silverlight, and accessible through standard firewalls.
- [Southparkify / Simpsonize : better with both!](https://engineering-leadership.hinshelwood.com/articles/southparkify-simpsonize-better-with-both/): Comparison of Southparkify and Simpsonize avatar creators, highlighting differences and personal preferences for creating cartoon-style self-portraits online.
- [Team System Web Access finally released](https://engineering-leadership.hinshelwood.com/articles/team-system-web-access-finally-released/): Team System Web Access, the successor to TeamPlain, is now available, offering improved stability and features for TFS users, but with some known link and access issues.
- [Simpsonize Me!](https://engineering-leadership.hinshelwood.com/articles/simpsonize-me/): Transform your photo into a character styled like The Simpsons using an online tool that creates cartoon versions of real-life images.
- [Visual Studio 2008 Beta 2 Team Explorer](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2008-beta-2-team-explorer/): Explains the absence of Team Explorer in Visual Studio 2008 Beta 2 installation and the need to download it separately for Team Foundation Server integration.
- [Installing the .NET Framework 3.5 Beta 2 on Vista](https://engineering-leadership.hinshelwood.com/articles/installing-the-net-framework-3-5-beta-2-on-vista/): Step-by-step guide to resolving .NET Framework 3.5 Beta 2 installation issues on Windows Vista by uninstalling specific hotfixes and retrying the setup.
- [Installing Visual Studio 2008 Beta 2 on XP](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2008-beta-2-on-xp/): Guide to resolving installation issues with Visual Studio 2008 Beta 2 on Windows XP, including removing Office 2007 beta and hardware requirements for optimal setup.
- [Social and Business Networking](https://engineering-leadership.hinshelwood.com/articles/social-and-business-networking/): Explores challenges of managing multiple social and business networks, proposing a unified, secure system for centralised contact management and seamless data updates.
- [What is dyslexia?](https://engineering-leadership.hinshelwood.com/articles/what-is-dyslexia/): Dyslexia affects reading and spelling, often causing letter confusion, but can enhance oral skills and visual thinking. Many develop unique ways to process written words.
- [SharePoint Content Request | What would you like to see?](https://engineering-leadership.hinshelwood.com/articles/sharepoint-content-request-what-would-you-like-to-see/): Share your ideas for new SharePoint features, including better Team Foundation Server integration for both technical and non-technical users, and expanded TFS use cases.
- [Why do we care about software factories?](https://engineering-leadership.hinshelwood.com/articles/why-do-we-care-about-software-factories/): Explains the benefits of software factories, how they improve software development, and highlights resources that make the concept easier to understand and adopt.
- [Deployment documentation](https://engineering-leadership.hinshelwood.com/articles/deployment-documentation/): Outlines steps to document and improve deployment for a complex business app, focusing on automation, rollback, vendor updates, and multi-environment management.
- [How to become a Multi-Dimensional Free Thinker](https://engineering-leadership.hinshelwood.com/articles/how-to-become-a-multi-dimensional-free-thinker/): Explores how dyslexia can enhance multi-dimensional thinking, creativity, and problem-solving, highlighting benefits for careers in engineering, design, and software development.
- [Memories of a multi-dimensional free thinking software developer](https://engineering-leadership.hinshelwood.com/articles/memories-of-a-multi-dimensional-free-thinking-software-developer/): Explores how neurodiversity, particularly dyslexia, influences software development skills, offering insights and resources for developers and employers.
- [Access to Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/access-to-team-foundation-server/): Discusses challenges and solutions for accessing and practising with Team Foundation Server (TFS) outside work, including limitations of hosted options like CodePlex.
- [Loosing the battle, but the war goes on](https://engineering-leadership.hinshelwood.com/articles/loosing-the-battle-but-the-war-goes-on/): A personal account of challenges promoting TFS over Jira and Subversion, highlighting adoption barriers, team dynamics, and efforts to bridge tools via integration projects.
- [How 'e' are you?](https://engineering-leadership.hinshelwood.com/articles/how-e-are-you/): Discover your "e-score" and see how you rank online with a quick test that measures your digital expertise and compares your results to others.
- [TFS Event Handler Prototype Feedback](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-prototype-feedback/): Request for user feedback on the TFS Event Handler tool, focusing on installation, configuration, functionality, and interest in future versions for Team Foundation Server.
- [Its that time again](https://engineering-leadership.hinshelwood.com/articles/its-that-time-again/): A developer reflects on career changes, balancing family and work, and considers moving into contracting for flexibility and better pay, especially in .NET and enterprise tech.
- [Simplify](https://engineering-leadership.hinshelwood.com/articles/simplify/): Blog categories and article categories have been streamlined, with clearer descriptions and Wikipedia links. Suggestions include post counts, friendly URLs, and sharing options.
- [The future of software development](https://engineering-leadership.hinshelwood.com/articles/the-future-of-software-development/): Explores how software factories, web services, and specialised development teams can speed up software delivery, improve adaptability, and meet fast-changing business needs.
- [Back to the grind](https://engineering-leadership.hinshelwood.com/articles/back-to-the-grind/): Returning to work after two weeks of paternity leave and welcoming a newborn daughter; reflections on family and resuming professional life.
- [The Delivery](https://engineering-leadership.hinshelwood.com/articles/the-delivery/): A personal account of a daughter's birth, detailing the unexpected and rapid labour, hospital experience, and gratitude for the support received during delivery.
- [Windows Mobile 6 Black Shadow (4.0)](https://engineering-leadership.hinshelwood.com/articles/windows-mobile-6-black-shadow-4-0/): Guide to updating HTC Hermes phones with Windows Mobile 6 Black Shadow (4.0) ROM, including installation steps, benefits, and tips to avoid common update issues.
- [Solution to sub sites in Sharepoint 3.0 with Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/solution-to-sub-sites-in-sharepoint-3-0-with-team-foundation-server/): Explains how to configure Team Foundation Server to create SharePoint 3.0 project portals as sub-sites, including manual and automated setup steps and key considerations.
- [Creating a managed service factory](https://engineering-leadership.hinshelwood.com/articles/creating-a-managed-service-factory/): 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.
- [Creating your own Event Handler](https://engineering-leadership.hinshelwood.com/articles/creating-your-own-event-handler/): 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.
- [TFS Event Handler: Prototype Released](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-prototype-released/): Prototype application and source code for a TFS Event Handler are now available, enabling configuration and extension for Team Foundation Server events.
- [TFS Event Handler: CTP 1 Delayed](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-ctp-1-delayed/): The first Community Technology Preview of the TFS Event Handler is delayed, with updates on framework enhancements, current progress, and pending development tasks.
- [Programmer personality type](https://engineering-leadership.hinshelwood.com/articles/programmer-personality-type/): Explains a programmer personality type focused on fast results, low-level coding, teamwork, and liberal use of whitespace and comments for code clarity and efficiency.
- [Sharepoint 3.0 TFS Sub-Site creation investigation result](https://engineering-leadership.hinshelwood.com/articles/sharepoint-3-0-tfs-sub-site-creation-investigation-result/): Automating SharePoint 3.0 sub-site creation for TFS projects is not supported; manual site setup is required unless you customise the SharePoint site creation process.
- [NetIDme](https://engineering-leadership.hinshelwood.com/articles/netidme/): Online identity verification service enabling users to prove their identity for safer interactions, with support for CardSpace, ChatShield, and potential single sign-on integration.
- [HTC Touch](https://engineering-leadership.hinshelwood.com/articles/htc-touch/): Overview of the HTC Touch smartphone, its features, and its role as an early iPhone competitor, including manufacturer details and compatibility with mobile networks.
- [TFS Process Templates](https://engineering-leadership.hinshelwood.com/articles/tfs-process-templates/): Explains how Team Foundation Server process templates enable custom workflows, highlights their flexibility, and offers advice for effective configuration and management.
- [Microsoft Surface: Wow](https://engineering-leadership.hinshelwood.com/articles/microsoft-surface-wow/): Amazement at Microsoft Surface, a new interactive touchscreen device, highlighting its innovative features and potential impact on entertainment technology.
- [SharePoint 3.0 TFS Sub-Site creation error](https://engineering-leadership.hinshelwood.com/articles/sharepoint-3-0-tfs-sub-site-creation-error/): Explains troubleshooting steps and error messages when creating Team Foundation Server sub-sites in SharePoint 3.0, including site URL conflicts and document upload issues.
- [My Wish List of Team Foundation Server Tools](https://engineering-leadership.hinshelwood.com/articles/my-wish-list-of-team-foundation-server-tools/): A list of desired Team Foundation Server tools, including event handlers, workflow integration, Jira and BPEL sync, simplified work item submission, notifications, and SharePoint support.
- [Setting up TFS to create project portals as child sites of an existing SharePoint 3.0 site (or sub site)](https://engineering-leadership.hinshelwood.com/articles/setting-up-tfs-to-create-project-portals-as-child-sites-of-an-existing-sharepoint-3-0-site-or-sub-site/): Guide to integrating Team Foundation Server with SharePoint 3.0 by creating project portals as child sites, including setup steps, permissions, and troubleshooting tips.
- [Team Foundation Server & SharePoint 3.0](https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-sharepoint-3-0/): Guidance on configuring Team Foundation Server to create project sites under a SharePoint 3.0 subsite, enabling a central intranet portal with project dashboards.
- [TFS Gotcha (Exception Handling)](https://engineering-leadership.hinshelwood.com/articles/tfs-gotcha-exception-handling/): Explains how to handle non-serialisable Team Foundation Server exceptions in WCF by creating custom serialisable exceptions for reliable cross-service error handling.
- [Creating WCF Service Host Programmatically](https://engineering-leadership.hinshelwood.com/articles/creating-wcf-service-host-programmatically/): Explains how to programmatically create and configure a WCF Service Host in .NET, including base addresses, endpoints, bindings, and service behaviours for secure hosting.
- [Custom WCF Proxy](https://engineering-leadership.hinshelwood.com/articles/custom-wcf-proxy/): Explains how to create custom WCF proxies in .NET to avoid redundant class generation and object conversion when consuming Windows Communication Foundation services.
- [TFS Speed Problems](https://engineering-leadership.hinshelwood.com/articles/tfs-speed-problems/): Advice on diagnosing and resolving Team Foundation Server speed issues, including network checks, server specifications, and common causes of slow performance.
- [Delving into SharePoint 3.0](https://engineering-leadership.hinshelwood.com/articles/delving-into-sharepoint-3-0/): Explores key features and improvements in SharePoint 3.0, including setup experience, intranet creation, and initial impressions compared to previous versions.
- [TFS Feature Wish (TFS Checkin Notifier)](https://engineering-leadership.hinshelwood.com/articles/tfs-feature-wish-tfs-checkin-notifier/): Proposes a Team Explorer add-in for TFS to notify users when a checked-out file becomes available, streamlining file access and collaboration in source control.
- [Benefits of remote access for Team System](https://engineering-leadership.hinshelwood.com/articles/benefits-of-remote-access-for-team-system/): Enables secure, controlled remote access for global teams, allowing efficient collaboration, task tracking, and integration of overseas contractors in Team System.
- [Recipe for Team Server in a small business](https://engineering-leadership.hinshelwood.com/articles/recipe-for-team-server-in-a-small-business/): Breaks down the costs and benefits of setting up Team Foundation Server for small businesses, covering licensing, hardware, and key features like source control and project management.
- [Would anyone be interested in hosted Visual Studio Team System (LinkedIn Question)](https://engineering-leadership.hinshelwood.com/articles/would-anyone-be-interested-in-hosted-visual-studio-team-system-linkedin-question/): Discussion on the demand and benefits of hosted Visual Studio Team System for small businesses, covering customisation, security, access, and technical considerations.
- [Workflow](https://engineering-leadership.hinshelwood.com/articles/workflow/): Explores adding workflow support to Team Foundation Server Event Handler, enabling users to create, edit, and manage workflows directly in a hosted environment.
- [TFS Event Handler Progress](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-progress/): Update on TFS Event Handler project progress, focusing on resolving security issues, improving error handling in WCF services, and finalising the admin system.
- [TFS Event Handler: CTP1 Imminent](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-ctp1-imminent/): First Community Technology Preview (CTP1) of TFS Event Handler is being prepared, aiming to deliver initial core features for Team Foundation Server integration.
- [Studying for Exam 70-536: MCTS Application Development Foundation](https://engineering-leadership.hinshelwood.com/articles/studying-for-exam-70-536-mcts-application-development-foundation/): Guidance on self-studying for Microsoft Exam 70-536, covering .NET Framework 2.0 fundamentals for MCTS certification and tips for developers with prior .NET experience.
- [Envisioning vs Provisioning](https://engineering-leadership.hinshelwood.com/articles/envisioning-vs-provisioning/): Compares envisioners, who innovate and prototype with new tech, to provisioners, who deliver reliable solutions, highlighting their roles in effective software development teams.
- [TFS Event Handler: Coverage & Comments](https://engineering-leadership.hinshelwood.com/articles/tfs-event-handler-coverage-comments/): Discusses feedback and key issues for the TFS Event Handler project, focusing on security for uploaded assemblies and handling of referenced assemblies in internal team use.
- [TFS EventHandler: MSMQ Refactor](https://engineering-leadership.hinshelwood.com/articles/tfs-eventhandler-msmq-refactor/): Refactoring a TFS Event Handler to use MSMQ, splitting it into modular services for event queuing and handling, improving maintainability and administration.
- [TFS EventHandler: Now on CodePlex](https://engineering-leadership.hinshelwood.com/articles/tfs-eventhandler-now-on-codeplex/): Team Foundation Server EventHandler is now available on CodePlex, with ongoing updates to use Message Queuing and a Windows Service. Source code and forums are open to contributors.
- [I'm Luke Skywalker according to the Star Wars personality test](https://engineering-leadership.hinshelwood.com/articles/im-luke-skywalker-according-to-the-star-wars-personality-test/): Result of a Star Wars personality test revealing a match with Luke Skywalker, reflecting on the outcome and sharing related links and personal reactions.
- [Selling the benefits of Team System](https://engineering-leadership.hinshelwood.com/articles/selling-the-benefits-of-team-system/): Guidance on effectively promoting Team System to developers, managers, and project teams, addressing their concerns and strategies for successful adoption.
- [TFS EventHandler: Message Queuing](https://engineering-leadership.hinshelwood.com/articles/tfs-eventhandler-message-queuing/): Explains using message queues in Team Foundation Server EventHandler to manage events reliably, ensuring no data loss during handler updates or service changes.
- [Team Server Event Handlers made easy](https://engineering-leadership.hinshelwood.com/articles/team-server-event-handlers-made-easy/): Explains a simple way for power users to create, upload, and manage custom event handlers for Team Foundation Server events using an admin interface and web services.
- [Visual Studio Team System Blogs](https://engineering-leadership.hinshelwood.com/articles/visual-studio-team-system-blogs/): Browse official Microsoft Visual Studio Team System blogs, featuring updates and insights from the development team. Community blogs are not included.
- [Beta Exam 71-510: TS: Visual Studio 2005 Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/beta-exam-71-510-ts-visual-studio-2005-team-foundation-server/): Experience earning the MCTS: Team Foundation Server certification via Beta Exam 71-510, including exam results, certification details, and next steps in professional development.
- [Serialize Assembly for Service calls over Http](https://engineering-leadership.hinshelwood.com/articles/serialize-assembly-for-service-calls-over-http/): Explains how to transmit a .NET assembly over HTTP in a WCF service call, focusing on serialisation and deserialisation without using byte streams.
- [Introduction to .NET Framework 3.0 for Developers Event](https://engineering-leadership.hinshelwood.com/articles/introduction-to-net-framework-3-0-for-developers-event/): Overview of key features in .NET Framework 3.0 for developers, including CardSpace, Windows Workflow Foundation, and practical insights from a Microsoft-led session.
- [Mobile Device Center](https://engineering-leadership.hinshelwood.com/articles/mobile-device-center/): Discusses the limitation of Mobile Device Center on Windows Vista, highlighting its inability to sync with built-in contacts, calendar, and email components.
- [TeamPlain - Revisit](https://engineering-leadership.hinshelwood.com/articles/teamplain-revisit/): Shows how to use JavaScript to shorten long project names in a TeamPlain dropdown, offering a workaround for poor project name compartmentalisation in Team Foundation Server.
- [Team Server Hmm!](https://engineering-leadership.hinshelwood.com/articles/team-server-hmm/): Explains how to connect Microsoft SQL Server Management Studio to Team Foundation Server using the MSSCCI Provider for integrated source control and team collaboration.
- [TFS Admin Tool 1.2 Gotcha](https://engineering-leadership.hinshelwood.com/articles/tfs-admin-tool-1-2-gotcha/): Describes an issue in TFS Admin Tool 1.2 where adding a user as "Contributer" fails to grant necessary "Reader" permissions in reporting services, causing access problems.
- [Free Online training from Microsoft](https://engineering-leadership.hinshelwood.com/articles/free-online-training-from-microsoft/): Access free Microsoft online training workshops and courses on WSE 3.0 security, routing, and SQL Server 2005, suitable for .NET and Visual Studio 2005 users.
- [TeamPlain Error: TF14002](https://engineering-leadership.hinshelwood.com/articles/teamplain-error-tf14002/): Explains the TF14002 error in TeamPlain, where NT AUTHORITY\NETWORK SERVICE lacks valid user group access, and discusses possible causes like proxy server settings.
- [TeamPlain - Install and initial views](https://engineering-leadership.hinshelwood.com/articles/teamplain-install-and-initial-views/): Covers installing TeamPlain, initial setup experience, project name display issues, and early observations on user access control and web-based project management features.
- [Microsoft has acquired TeamPlain](https://engineering-leadership.hinshelwood.com/articles/microsoft-has-acquired-teamplain/): Microsoft has acquired TeamPlain, making its web access software for Visual Studio 2005 and Team Foundation Server available for free to all users.
- [Advanced Email Content addendum](https://engineering-leadership.hinshelwood.com/articles/advanced-email-content-addendum/): Discusses the limitations of emailing XBAP applications, highlighting the impact on sharing WPF-based presentations, forms, and demos within the .NET ecosystem.
- [Advanced Email Content](https://engineering-leadership.hinshelwood.com/articles/advanced-email-content/): Explores embedding interactive 3D and WPF/XBAP content directly in emails, discussing technical feasibility, security concerns, and real-world implementation challenges.
- [MSDN Roadshow UK 2007](https://engineering-leadership.hinshelwood.com/articles/msdn-roadshow-uk-2007/): Highlights experiences and key speakers from the 2007 MSDN Roadshow in Glasgow, focusing on sessions about LINQ and software development presented by Daniel Moth and Mike Taulty.
- [TFS Weekend Part 1 - Install](https://engineering-leadership.hinshelwood.com/articles/tfs-weekend-part-1-install/): A walkthrough of installing Team Foundation Server (TFS) in a small business, covering setup steps, admin access, permissions, and remote developer access challenges.
- [TFS Gotcha (server name)](https://engineering-leadership.hinshelwood.com/articles/tfs-gotcha-server-name/): Explains how to fix TFS installation issues caused by server name and proxy settings by editing the hosts file and renaming the server to its fully qualified domain name.
- [TFS Gotcha (SP1)](https://engineering-leadership.hinshelwood.com/articles/tfs-gotcha-sp1/): Step-by-step guide to resolving common installation and repair issues with Team Foundation Server SP1 on data and application tiers, including rollback options.
- [Microsoft UK Team System Blog](https://engineering-leadership.hinshelwood.com/articles/microsoft-uk-team-system-blog/): Updates and insights from the UK Team Foundation Server team, sharing news, tips, and resources on Application Lifecycle Management and TFS developments.
- [Deep vein thrombosis (DVT)](https://engineering-leadership.hinshelwood.com/articles/deep-vein-thrombosis-dvt/): Highlights the risks of deep vein thrombosis, genetic factors like Factor V Leiden, and calls for increased awareness, testing, and early detection to prevent deaths.
- [Register For Beta Exam 71-510: TS: Visual Studio 2005 Team Foundation Server](https://engineering-leadership.hinshelwood.com/articles/register-for-beta-exam-71-510-ts-visual-studio-2005-team-foundation-server/): Learn how to register for the beta exam 70-510 on Visual Studio 2005 Team Foundation Server, including dates, locations, and registration details for global candidates.
- [VS2005 - Signtool requires CAPICOM version 2.1.0.1](https://engineering-leadership.hinshelwood.com/articles/vs2005-signtool-requires-capicom-version-2-1-0-1/): Learn how to resolve the "Signtool requires CAPICOM version 2.1.0.1" error in VS2005 by installing and registering capicom.dll for successful project publishing.
- [Some thoughts on .NET 3.0 from LinkedIn](https://engineering-leadership.hinshelwood.com/articles/some-thoughts-on-net-3-0-from-linkedin/): Insights on adopting .NET 3.0 for new applications, its features like WPF, WF, WCF, CardSpace, and comparisons with BizTalk, plus upgrade considerations for organisations.
- [Windows Mobile Device Center](https://engineering-leadership.hinshelwood.com/articles/windows-mobile-device-center/): Windows Mobile Device Center enables syncing and managing Windows Mobile devices on Windows Vista, replacing ActiveSync. Not compatible with Windows Mobile 2002 or earlier.
- [The Windows Vista Ultimate Element](https://engineering-leadership.hinshelwood.com/articles/the-windows-vista-ultimate-element/): Overview of the Windows Vista Ultimate Element, referencing a related image and its context within technology and software discussions.
- [Microsoft: forget about PayPal, how about a MasterCard killer?](https://engineering-leadership.hinshelwood.com/articles/microsoft-forget-about-paypal-how-about-a-mastercard-killer/): Explores speculation about Microsoft entering digital payments, comparing past attempts to rival PayPal and considering potential competition with MasterCard.
- [Software Development Industrial Revolution](https://engineering-leadership.hinshelwood.com/articles/software-development-industrial-revolution/): Explores how industrialising software development with tools like Team Foundation Server boosts speed, collaboration, and scalability in competitive industries.
- [Deploying Team Server](https://engineering-leadership.hinshelwood.com/articles/deploying-team-server/): Discusses the challenges, costs, and benefits of implementing Team Foundation Server (TFS) for large development teams in a corporate investment banking environment.
- [Small / New business websites](https://engineering-leadership.hinshelwood.com/articles/small-new-business-websites/): Guidance on building a small or new business website, covering SEO, DNS, blogs, accessibility, choosing designers and developers, hosting, and typical costs.
- [Outlook 2007 users angry? Well maybe not users](https://engineering-leadership.hinshelwood.com/articles/outlook-2007-users-angry-well-maybe-not-users/): Discusses reactions to Outlook 2007's email format changes, noting that developers and designers are upset, while most users are unaffected by the switch from HTML to document-style emails.
- [hinshelm vs fernienator](https://engineering-leadership.hinshelwood.com/articles/hinshelm-vs-fernienator/): A light-hearted comparison of gaming performance between the author and their brother-in-law, featuring Xbox gameplay and a personal scoreboard update.
- [Visual Studio 2005 Team Foundation Installation Guide](https://engineering-leadership.hinshelwood.com/articles/visual-studio-2005-team-foundation-installation-guide/): Provides updated instructions for installing Visual Studio 2005 Team Foundation Server with SP1, including setup for Reporting and Analytical Services on separate servers.
- [Team System Widgets](https://engineering-leadership.hinshelwood.com/articles/team-system-widgets/): A regularly updated resource listing applications and web tools for Team System and Team Foundation Server, including insights on TeamPlain web products for TFS.
- [The trouble with IIS6, .pac files and DNS](https://engineering-leadership.hinshelwood.com/articles/the-trouble-with-iis6-pac-files-and-dns/): Explains issues with serving .pac proxy files on IIS6 due to missing MIME types and how to resolve DNS for proxy appliances lacking host file support.
- [Gears of War Update starting 9-Jan-2007](https://engineering-leadership.hinshelwood.com/articles/gears-of-war-update-starting-9-jan-2007/): Gears of War receives a system update on 9 January 2007, ahead of two new multiplayer maps and potential fixes for ranked match issues on Xbox Live Marketplace.
- [Screenshots of Vista from 2002 to Today](https://engineering-leadership.hinshelwood.com/articles/screenshots-of-vista-from-2002-to-today/): See how Windows Vista evolved from its 2002 Alpha release through early Aero features in 2004 to its final design, with screenshots showing key visual changes over time.
- [Ten Ways to Use LinkedIn](https://engineering-leadership.hinshelwood.com/articles/ten-ways-to-use-linkedin/): Discover practical tips to maximise LinkedIn’s potential for networking, job searching, sales, partnerships, and connecting with professionals across various industries.
- [Performance Research, Browser Cache Usage - Exposed!](https://engineering-leadership.hinshelwood.com/articles/performance-research-browser-cache-usage-exposed/): Explores how browser caching affects web performance, focusing on HTTP requests, resource loading, and strategies to optimise site speed and user experience.
- [Windows Live Alerts](https://engineering-leadership.hinshelwood.com/articles/windows-live-alerts/): Windows Live Alerts notifies you of new blog posts, offering standard alert features with ads. Free to use and includes a link for your blog.
- [Vista Mobile Device Center](https://engineering-leadership.hinshelwood.com/articles/vista-mobile-device-center/): Discusses issues with syncing external SD cards on Windows Mobile devices using Vista Mobile Device Center, highlighting lost podcast sync features after upgrading from XP.
- [Time That Task VSTS Check-In Policy](https://engineering-leadership.hinshelwood.com/articles/time-that-task-vsts-check-in-policy/): Explores a TFS check-in policy for tracking task time, discusses challenges like task switching, and suggests using an external app to improve developer workflow.
- [Visual Studio SP1 and Team System SP1 are Released!](https://engineering-leadership.hinshelwood.com/articles/visual-studio-sp1-and-team-system-sp1-are-released/): Service Pack 1 for Visual Studio and Team System is now available, featuring key updates and bug fixes. Includes download links and details on improvements for TFS.
- [Ahhh, the fun of deploying Team System in a large corporation](https://engineering-leadership.hinshelwood.com/articles/ahhh-the-fun-of-deploying-team-system-in-a-large-corporation/): Guidance on deploying Team Foundation Server in large organisations, including database setup workarounds and links to official TFS administration resources.
- [Windows Live Writer](https://engineering-leadership.hinshelwood.com/articles/windows-live-writer/): Write and edit blog posts offline, then publish them easily with Windows Live Writer; ideal for managing blogs without constant internet access.
- [Windows CardSpace gets Firefox support](https://engineering-leadership.hinshelwood.com/articles/windows-cardspace-gets-firefox-support/): A new plug-in enables Microsoft’s CardSpace digital identity framework to work with Firefox, expanding browser support for secure online authentication.
- [RDdotNET Project Created](https://engineering-leadership.hinshelwood.com/articles/rddotnet-project-created/): A new RD.NET Community Foundation project offers extensible services for community sites, including globalisation, relationship management, and modular application support.
- [Installing Visual Studio 2005 on Windows vista](https://engineering-leadership.hinshelwood.com/articles/installing-visual-studio-2005-on-windows-vista/): Step-by-step guide to installing Visual Studio 2005 on Windows Vista, including common issues encountered and tips for a smoother setup process.
- [Windows Vista: windows mobile device center](https://engineering-leadership.hinshelwood.com/articles/windows-vista-windows-mobile-device-center/): Guidance on installing and running Windows Mobile Device Center on Windows Vista 6000 RTM, including beta availability and manual download instructions.
- [.NET Framework 3.0](https://engineering-leadership.hinshelwood.com/articles/net-framework-3-0/): Explains the benefits of .NET Framework 3.0, focusing on WCF for cleaner, more efficient code and improved developer productivity in service-oriented applications.
- [Codeplex Project: RDdotNET White Label](https://engineering-leadership.hinshelwood.com/articles/codeplex-project-rddotnet-white-label/): Open-source RDdotNET White Label project hosted on Codeplex, providing .NET solution resources and documentation for developers. Includes project link and tags.
- [Web 2.0](https://engineering-leadership.hinshelwood.com/articles/web-2-0/): Explains the concept of Web 2.0, highlighting its ethos, evolution from earlier web technologies, and why it has become a common term in tech discussions.
- [Windows Communication Framework Evaluation](https://engineering-leadership.hinshelwood.com/articles/windows-communication-framework-evaluation/): Assessment of Windows Communication Foundation (WCF) for enterprise web services, focusing on security, compatibility, and benefits over previous .NET frameworks.
- [The most usefull .NET tool on the face of the planet!](https://engineering-leadership.hinshelwood.com/articles/the-most-usefull-net-tool-on-the-face-of-the-planet/): Reflector is a .NET tool for decompiling, browsing, and analysing assemblies, helping developers understand and debug .NET code efficiently.
- [CafeMSN Prize](https://engineering-leadership.hinshelwood.com/articles/cafemsn-prize/): Awarded two Amazon vouchers by Microsoft for providing helpful answers on CafeMSN, earning a total of $20 in recognition of contributions to the platform.
- [Ahaaaa!](https://engineering-leadership.hinshelwood.com/articles/ahaaaa/): User discusses difficulties with adding code to blog posts and expresses intent to improve and update previous entries once the issue is resolved.
- [Custom UI colour scheme for Windows Forms .NET](https://engineering-leadership.hinshelwood.com/articles/custom-ui-colour-scheme-for-windows-forms-net/): Learn how to customise Windows Forms ToolStrip, MainMenu, and StatusBar colours in .NET by creating a custom ColorTable and applying it with a custom renderer.
- [Adding ToolStripPanel UI Adapter Support to the Composite UI Application Block](https://engineering-leadership.hinshelwood.com/articles/adding-toolstrippanel-ui-adapter-support-to-the-composite-ui-application-block/): Explains how to extend the Composite UI Application Block to support ToolStripPanel UI adapters, enabling dynamic ToolStrip integration and customisation in CAB applications.

## Engineering-Notes

- [Leveraging AI Embeddings for Related Content Classification](https://engineering-leadership.hinshelwood.com/engineering-notes/leveraging-ai-embeddings-for-related-content-classification/): Replacing Hugo’s basic related content feature with AI-driven embeddings has produced more accurate and meaningful recommendations on the site. By generating OpenAI embeddings for around 1,600 content pieces at a cost of just $0.66 and storing them in Azure Blob Storage, content is matched using cosine similarity, identifying semantically related items rather than just shared keywords or tags. Caching similarity scores above a threshold greatly reduces computational overhead. The result is improved user navigation and increased AI discoverability, with a scalable system now in place for future enhancements like dynamic crosslinking or filtering classification tasks.
- [Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence](https://engineering-leadership.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/): Migrating legacy .NET projects to SDK-style project files makes the build system simpler, reduces clutter, and prepares codebases for future upgrades, even when still targeting older .NET versions. Class libraries are easy to convert with tools like try-convert, allowing you to keep targeting net481 while gaining a cleaner project structure and maintainability benefits. For ASP.NET MVC/WebForms apps, use the community MSBuild.SDK.SystemWeb for smoother conversions, as Microsoft does not officially support SDK-style for these apps; this keeps features like IIS Express debugging alive. Debugging issues are common, such as the need to add `` in the .csproj to resolve Visual Studio launch problems, but these can be managed with targeted fixes. It is practical to convert class libraries right away and only tackle web apps if you want SDK-style or plan to move off System.Web soon.
- [How I Used Generative AI to Transform Site Tagging and Categories](https://engineering-leadership.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/): Moving a long-running blog to Hugo with Markdown and YAML enabled full ownership of content, efficient scripting, and easier large-scale maintenance. Leveraging OpenAI, all blog posts were reclassified with consistent, traceable tags, categories, and a new "concept" layer, reducing 1,000 tags and 200 categories down to 140 tags and 12 categories. The system uses AI to provide scored, explainable suggestions with detailed confidence metrics, as shown in JSON cache entries that include categories like Technical Leadership with confidence scores and human-readable reasoning. Human oversight remains essential for final editorial decisions, with determinism and penalty logic ensuring reliable outcomes. This hybrid approach turned a manual, error-prone process into scalable, auditable classification while retaining accountability and editorial quality.
- [Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed](https://engineering-leadership.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/): Building a resilient, fast token server required moving beyond quick scripts to an architecture that survives real-world failures and integrates smoothly with PowerShell workflows. The initial design suffered from repeated Windows port binding errors and slowdowns when processing large batches due to aggressive server restarts and orchestration flaws, as shown by logs full of “Only one usage of each socket address...” errors. Refactoring to start the server once per batch, add retry logic instead of restarts, and implement a local fallback turned transient issues into minor delays rather than system failures. The resulting system automatically handles network hiccups, logs transparently, and keeps batch pipelines flowing. True engineering resilience means the system works not just in ideal conditions, but when things inevitably go wrong.

## Guides

- [OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning](https://engineering-leadership.hinshelwood.com/guides/okr-guide/): OKRs are a practical system for aligning teams around shared goals, measuring real progress, and learning from results, provided they are supported by clear vision, leadership, and a culture of feedback and adaptability. Effective OKR practice requires well-defined roles, regular events for definition, check-in, review, and reflection, and a focus on measurable outcomes rather than tasks or top-down mandates. To get value, involve teams in crafting OKRs, keep them focused and measurable, and use frequent feedback to adapt both goals and ways of working.
- [Kanban Guide](https://engineering-leadership.hinshelwood.com/guides/kanban-guide/): This guide defines Kanban as a flexible strategy to optimize value flow by visualizing, managing, and improving workflows, supported by tracking key flow metrics like WIP, throughput, work item age, and cycle time. It emphasizes creating a clear workflow definition, actively managing work in progress, and continuously improving processes to balance effectiveness, efficiency, and predictability. Development managers should ensure teams establish explicit workflow policies, regularly review flow metrics, and adapt practices as needed to maximize value delivery.
- [Nexus Guide](https://engineering-leadership.hinshelwood.com/guides/nexus-guide/): Nexus is a framework for scaling Scrum to coordinate three to nine teams working on a single product, focusing on minimizing dependencies and ensuring integrated delivery each Sprint. It adds a Nexus Integration Team, shared events, and artifacts like a single Product Backlog and Integrated Increment to maintain transparency and alignment across teams. Development managers should use Nexus to address cross-team challenges, improve integration, and maximize value without simply adding more people.
- [Manifesto for Agile Software Development](https://engineering-leadership.hinshelwood.com/guides/manifesto-for-agile-software-development/): Focus on delivering working software quickly by prioritizing people, collaboration, and adaptability over rigid processes and documentation. Encourage frequent releases, open communication, and continuous improvement to meet customer needs and respond to change. Empower teams and foster a culture of trust and reflection to drive better results.
- [Kanban Guide for Scrum Teams](https://engineering-leadership.hinshelwood.com/guides/kanban-guide-for-scrum-teams/): Combining Kanban with Scrum helps teams improve the flow of work, increase transparency, and make better use of feedback loops by tracking key metrics like work in progress, cycle time, work item age, and throughput. By visualizing workflow, limiting work in progress, actively managing tasks, and regularly inspecting and adapting processes, teams can deliver value more predictably and efficiently. Development managers should consider integrating Kanban practices into their Scrum teams to optimize delivery and continuously improve team performance.
- [Detecting Agile BS](https://engineering-leadership.hinshelwood.com/guides/detecting-agile-bs/): Many projects claim to be agile but are not, so leaders should look for real user involvement, continuous feedback, automation, and cross-functional collaboration to spot genuine agile practices. Key signs of “agile BS” include lack of user interaction, manual processes where automation is possible, and siloed teams. Ask targeted questions about testing, automation, user feedback, and release cycles to verify true agile delivery and ensure teams can adapt based on user needs.
- [Evidence-Based Portfolio Management](https://engineering-leadership.hinshelwood.com/guides/evidence-based-portfolio-management/): Evidence-Based Portfolio Management helps organizations achieve true business agility by linking investments directly to measurable goals, running small experiments to validate ideas, and frequently adapting based on real feedback. Key benefits include reducing waste from traditional planning, improving alignment between work and business objectives, and empowering teams to focus on high-value outcomes. To get started, select a complex area of your business and apply these iterative, evidence-driven investment practices.
- [The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty](https://engineering-leadership.hinshelwood.com/guides/evidence-based-management-guide/): Evidence-Based Management (EBM) is a framework that helps organizations improve value delivery by using measurement, experimentation, and adaptation to navigate uncertainty and achieve strategic goals. It focuses on four key areas, current value, unrealized value, time-to-market, and ability to innovate, encouraging teams to set measurable goals, run small experiments, and use evidence to guide decisions. Development managers should ensure their teams make hypotheses explicit, measure outcomes rather than just activities or outputs, and regularly inspect and adapt based on results to maximize customer and business value.
- [The Scrum Guide (February 2010)](https://engineering-leadership.hinshelwood.com/guides/scrum-guide/): 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.

## Learning-Series

- [The Sprint Review](https://engineering-leadership.hinshelwood.com/learning-series/the-sprint-review/): The Sprint Review content is not yet available, so there are no key points or takeaways to share at this time. Please check back later for details on the Sprint Review.

## Podcasts

- [Power & Politics! Communicating and Building Political Capital for Agile Transformations!](https://engineering-leadership.hinshelwood.com/podcasts/power-politics-communicating-and-building-political-capital-for-agile-transformations/): The podcast highlights how using precise and accurate language is crucial for effective communication and building trust during Agile transformations. Hosts Simon Reindl and Martin Hinshelwood share insights on why transparency in word choice impacts team alignment and organizational change. Development managers should focus on clear communication to support successful Agile adoption.
- [Agile at Microsoft](https://engineering-leadership.hinshelwood.com/podcasts/agile-at-microsoft/): The podcast highlights the critical role of clear and precise language in Agile environments, emphasizing that transparency and accuracy in communication directly impact team effectiveness. Hosts Simon Reindl and Martin Hinshelwood share practical insights on how word choice shapes understanding and outcomes. Development managers should ensure their teams use language carefully to avoid misunderstandings and improve collaboration.
- [Mindset Versus Philosophy](https://engineering-leadership.hinshelwood.com/podcasts/mindset-versus-philosophy/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is crucial for transparency and effective communication in Agile environments. They emphasize that the words teams choose directly impact understanding and outcomes. Development managers should ensure their teams are clear and intentional with language to improve collaboration and results.
- [Enterprise Agility](https://engineering-leadership.hinshelwood.com/podcasts/enterprise-agility/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is crucial for transparency and effective communication in agile environments. They highlight that clarity in words directly impacts team understanding and outcomes. Development managers should ensure their teams use clear language to improve collaboration and results.
- [Agile Alchemy](https://engineering-leadership.hinshelwood.com/podcasts/agile-alchemy/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is crucial for transparency and effective communication in Agile teams. They highlight that clarity in words and context leads to better collaboration and outcomes. Development managers should ensure their teams prioritize clear communication to avoid misunderstandings and improve Agile practices.
- [Continuous Delivery](https://engineering-leadership.hinshelwood.com/podcasts/continuous-delivery/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is crucial for transparency and effective communication in Agile environments. They highlight that clarity in terminology directly impacts team alignment and delivery outcomes. Development managers should ensure their teams use clear, shared language to avoid misunderstandings and improve collaboration.
- [Ethics in Agile](https://engineering-leadership.hinshelwood.com/podcasts/ethics-in-agile/): The podcast highlights the critical role of precise and transparent language in Agile environments, emphasizing that clarity in communication directly impacts team effectiveness and ethical practice. Key insights include the importance of saying exactly what you mean and understanding the context of your words. Development managers should ensure their teams prioritize clear, accurate communication to support better collaboration and outcomes.
- [Decoding Ethics in Agile: A Deep Dive with Martin & Simon](https://engineering-leadership.hinshelwood.com/podcasts/decoding-ethics-in-agile-a-deep-dive-with-martin-simon/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is essential for transparency and ethical behavior in Agile teams. They emphasize that clear communication helps avoid misunderstandings and supports better collaboration. Development managers should ensure their teams use language carefully to improve trust and effectiveness.
- [Words matter](https://engineering-leadership.hinshelwood.com/podcasts/words-matter/): Simon Reindl and Martin Hinshelwood discuss how using precise and accurate language is essential for transparency and effective communication in agile teams. The words you choose directly impact understanding and outcomes, so clarity is critical. Development managers should ensure their teams use clear language to avoid misunderstandings and improve collaboration.
- [Are office spaces dead](https://engineering-leadership.hinshelwood.com/podcasts/are-office-spaces-dead/): Martin and Simon discuss whether traditional office work is obsolete, highlighting how remote work has changed the effectiveness of agile training, coaching, and consulting. They share that remote approaches can be surprisingly effective, challenging assumptions about in-person work. Development managers should consider how remote options might enhance team learning and consulting outcomes.
- [Product owners are obsolete!](https://engineering-leadership.hinshelwood.com/podcasts/product-owners-are-obsolete/): The episode discusses whether strong product owners make product managers unnecessary, featuring expert Ralph Jocham to clarify the distinct roles and responsibilities of each. Key insights include that product ownership and product management are not interchangeable and both bring unique value to software teams. Development managers should ensure both roles are clearly defined and aligned to maximize product success.
- [Life coaches masquerading as Agile Coaches](https://engineering-leadership.hinshelwood.com/podcasts/life-coaches-masquerading-as-agile-coaches/): The podcast discusses concerns about life coaches presenting themselves as Agile Coaches without the necessary Agile experience or credentials, which can mislead organizations. True Agile Coaches typically have extensive hands-on Agile practice and formal training. Development managers should verify the background and expertise of Agile Coaches before engaging them to ensure effective support for their teams.

## Recipes

- [Daily Scrum Recipe](https://engineering-leadership.hinshelwood.com/recipes/daily-scrum-recipe/): The Daily Scrum should focus on actively managing work and strategizing to achieve the Sprint Goal, not just following a checklist. Teams should use visual tools like Work Item Aging graphs and boards to identify risks and bottlenecks, concentrating on items that need attention. Encourage teams to adapt the format to their needs, ensure transparency, and leave each meeting with a clear 24-hour action plan.
- [Sprint Review Recipe](https://engineering-leadership.hinshelwood.com/recipes/sprint-review-recipe/): The Sprint Review is designed to inspect the latest product increment, gather stakeholder feedback, and update the product backlog based on new insights, helping inform the next Sprint. Key steps include presenting the product vision, reviewing completed and incomplete work with supporting data, demoing new features, collecting actionable feedback, and discussing release forecasts and compliance. Development managers should ensure the review is structured, data-driven, and focused on actionable outcomes to maximize stakeholder engagement and guide future planning.
- [Sprint Planning Recipe](https://engineering-leadership.hinshelwood.com/recipes/sprint-planning-recipe/): Sprint Planning is a team event to set a clear Sprint Goal, select backlog items, and create an actionable plan for the first 24 hours, with the session length depending on how well the team understands the backlog and goals. Key steps include the Product Owner presenting the vision, the team agreeing on a Sprint Goal, reviewing capacity and throughput, selecting work items, and planning initial actions. To keep planning efficient, ensure the backlog and goals are clear before the meeting and communicate the plan to stakeholders afterward.

## Signals

- [Who signed off on cutting quality?](https://engineering-leadership.hinshelwood.com/signals/who-signed-off-on-cutting-quality/): When a team cuts quality to hit a date it is not a delivery problem but a risk decision the delivery team was never authorised to take, and asking who will sign off on shipping below the definition of done makes that explicit.
- [Detecting agile theatre with real delivery signals](https://engineering-leadership.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/): Agile is measured by delivery, feedback, and decision-making authority in the hands of teams, not by visible ceremonies or tooling.
- [Bonuses are not incentives](https://engineering-leadership.hinshelwood.com/signals/bonuses-are-not-incentives/): Bonuses are not effective incentives in knowledge work, as they reflect a lack of trust in people’s intrinsic motivation. The most capable engineers are driven by purpose, autonomy, and the opportunity to tackle complex challenges, not by financial rewards. Relying on traditional systems of carrots and sticks is outdated and incompatible with agile, modern workplaces. Performance systems modelled on factory work encourage compliance rather than creativity and agency. Focusing on output instead of meaningful outcomes limits a team’s potential.
- [Why Most Transformations Fail Without Honest Conversations](https://engineering-leadership.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/): Most transformation efforts fail because necessary, honest conversations about friction, confusion, and blockers are avoided. Real progress happens when people are given space to speak plainly and address underlying issues, as seen when even warehouse staff at Backcountry participated or sessions at Healthgrades filled with real questions and frustrations. Scrum is described as a framework for organisational transparency, not just for Developers, making hard truths visible and uncomfortable but essential. Without these open conversations, organisations only achieve surface-level change rather than true agility. The underlying challenge is to identify which important conversations are still being left unspoken.
- [The Myth of Knowing Everything Upfront in Software Development](https://engineering-leadership.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/): It is a myth that software teams can know everything upfront, even if they carve out dedicated Design Sprints to feel more in control. In practice, product development is an ongoing process of discovery, where ideas change and value emerges only through actual use. Scrum recognises this uncertainty and uses refinement to prepare future work just enough, avoiding wasted effort on planning for things that may never happen. The guidance is to build just enough design to deliver, release, gather feedback, learn, and iterate. Spending more time designing than delivering usually means optimising the wrong part of the process.
- [AI isn’t coming for your job](https://engineering-leadership.hinshelwood.com/signals/ai-isn-t-coming-for-your-job/): AI is not taking away jobs but rather replacing repetitive tasks that never needed a human touch, such as filling in forms, copying data between systems, and generating routine reports. Organisations have often designed roles around managing people as if they were problems, creating narrow and repetitive jobs. With AI now performing these tasks more efficiently, the system is breaking down, paving the way for better work that requires empathy, strategy, and adaptability. If AI seems like a threat, it is a sign that roles have treated people like machines, and now is the time to rethink what meaningful work looks like.
- [The Hidden Impact of Routine Jobs on Worker Dignity](https://engineering-leadership.hinshelwood.com/signals/the-hidden-impact-of-routine-jobs-on-worker-dignity/): Routine jobs like scanning groceries, packing boxes, or cleaning toilets were not created to honour worker dignity but to maximise efficiency by making roles mindless and replaceable. As automation and AI begin to replace these jobs, the real challenge is not the loss of meaningful human work but the exposure of outdated systems that underestimate people's capacity for critical thinking. The disappearance of these routine roles is a threat to the legacy of Taylorism, not to human value. It is necessary to reconsider job design, focusing on work that involves problem-solving, critical thinking, and genuine engagement rather than compliance and repetition.
- [In Scrum, we don’t do UX separately](https://engineering-leadership.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/): 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.
- [The FBI Sentinel project was textbook waterfall](https://engineering-leadership.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/): The FBI'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.
- [Why Copying Scaled Agile Frameworks Fails in Your Business](https://engineering-leadership.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/): 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.
- [Maximising Value from Applying Professional Scrum Training](https://engineering-leadership.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/): 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.
- [US Department of Defence and the History of Waterfall Delivery](https://engineering-leadership.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/): 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.
- [Too many organisations hide behind excuses:"](https://engineering-leadership.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/): Even large, regulated, and traditionally slow organizations like the DOD and FBI have successfully adopted iterative delivery, showing that excuses for not embracing agile are unfounded. Agile helps reduce risk, increase flexibility, and deliver value incrementally, which is especially important in regulated industries. Development managers should challenge resistance and prioritize agile practices to improve outcomes regardless of organizational constraints.
- [FBI Launched Outdated Criminal Records System in 1995](https://engineering-leadership.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/): 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.
- [Stop treating the end of the Sprint like a finish line](https://engineering-leadership.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/): 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.
- [Design Sprints in Scrum: Common Questions and Practical Insights](https://engineering-leadership.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/): 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.
- [You can’t deliver change through memos](https://engineering-leadership.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/): 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.
- [Scrum isn’t limited to building features](https://engineering-leadership.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/): Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products.
- [Evolving Engineering Practices to Improve Sprint Workflow in Scrum](https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/): 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.
- [Why Frameworks Alone will-not Transform Your Team Culture](https://engineering-leadership.hinshelwood.com/signals/why-frameworks-alone-will-not-transform-your-team-culture/): Relying on frameworks alone will not change your team culture; the main barriers are existing habits and lack of true commitment. Real transformation requires a clear vision, visible leadership support, and active involvement from everyone to identify and address obstacles. As a development manager, focus on building shared understanding and genuine engagement rather than just rolling out new processes.
- [When you scale Scrum, the challenge isn’t just delivery, it coherence](https://engineering-leadership.hinshelwood.com/signals/when-you-scale-scrum-the-challenge-isn-t-just-delivery-it-coherence/): 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.
- [David thought he already knew Scrum](https://engineering-leadership.hinshelwood.com/signals/david-thought-he-already-knew-scrum/): 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's understanding of Scrum to maintain true agility and drive meaningful change.
- [Scrum doesn’t stop you from optimising flow](https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/): 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.
- [Scrum Myth Debunked: Unfinished Work is Allowed in Scrum](https://engineering-leadership.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/): 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.
- [AI won’t replace humans](https://engineering-leadership.hinshelwood.com/signals/ai-won-t-replace-humans/): AI will not replace people but will automate repetitive and mechanical tasks, freeing humans to focus on creative and strategic work. Companies that use AI to eliminate low-value tasks and empower employees will be more successful. Leaders should assess whether their processes rely too much on dehumanising work and use AI to improve job quality.
- [Scrum is not an engineering process](https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-an-engineering-process/): Scrum is a framework for fostering collaboration across the whole organisation, not just an engineering process for developers. True agility happens when everyone, regardless of role, understands and participates in Scrum, which helps break down silos and exposes issues that slow delivery. To achieve real change, ensure your entire team is aligned and involved in the conversation about how value is delivered.
- [Frederick Taylor Legacy: Why it-is Still Problematic Today](https://engineering-leadership.hinshelwood.com/signals/frederick-taylor-legacy-why-it-is-still-problematic-today/): Many organizations still follow Frederick Taylor’s outdated approach of breaking work into repetitive tasks, leading to meaningless titles, ineffective bonuses, and siloed knowledge. With AI and automation revealing how much work is based on repetition, leaders must choose between maintaining the status quo or shifting to a culture focused on mastery, autonomy, and real outcomes. Development managers should reconsider current structures and incentives to ensure their teams are prepared for a future where genuine skills and collaboration matter most.
- [Resilience is not a department](https://engineering-leadership.hinshelwood.com/signals/resilience-is-not-a-department/): 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.
- [During a massive flood in London, nearly every datacentre went down."](https://engineering-leadership.hinshelwood.com/signals/during-a-massive-flood-in-london-nearly-every-datacentre-went-down/): Rackspace was the only London datacentre to stay online during a major flood because they regularly tested their backup systems by simulating real failures. Practising failure recovery under controlled but challenging conditions built true resilience in their operations. Development managers should regularly test their systems and teams under realistic failure scenarios to ensure they can recover when it matters most.
- [When Heathrow went down, they blamed the power supplier](https://engineering-leadership.hinshelwood.com/signals/when-heathrow-went-down-they-blamed-the-power-supplier/): Heathrow’s outage was not caused by a power loss but by an overly sensitive internal system that shut everything down in response to a minor fluctuation, revealing that their disaster recovery measures were untested for real-world chaos. Investing in infrastructure does not guarantee true resilience; resilience is proven only when systems are tested against unexpected failures. Development managers should regularly test and challenge their recovery processes to ensure they work under real conditions, not just ideal scenarios.
- [Everyone has a disaster recovery plan, on paper](https://engineering-leadership.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/): Many organizations have disaster recovery plans, but these often fail in real situations because critical dependencies are overlooked and not tested end to end. Successful drills can give a false sense of security if they do not include all essential systems, like authentication services. To ensure true resilience, regularly test your recovery process under real conditions and verify that all dependencies are restored and functional.
- [You can not implement Agile or Scrum successfully by decree](https://engineering-leadership.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/): 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.
- [Toyota "andon" cord lets any worker stop production to fix defects](https://engineering-leadership.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/): 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.
- [You want speed, adaptability, resilience](https://engineering-leadership.hinshelwood.com/signals/you-want-speed-adaptability-resilience/): Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks.
- [let-us be blunt](https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt/): 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.
- [We hear self-managing teams so often it become a cliché](https://engineering-leadership.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/): 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.
- [Everyone loves to shout give teams autonomy](https://engineering-leadership.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/): 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.
- [Fear is the real enemy of agility](https://engineering-leadership.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/): 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.
- [Technical debt cripples business agility and slows engineers down](https://engineering-leadership.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/): 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.
- [Most teams don’t fail because they lack frameworks](https://engineering-leadership.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/): 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.
- [Agile and Scrum are often misunderstood](https://engineering-leadership.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/): Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team'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.
- [A certification proves you’ve passed a test](https://engineering-leadership.hinshelwood.com/signals/a-certification-proves-you-ve-passed-a-test/): Certification shows someone passed a test but does not prove they can handle real product challenges or make strategic decisions. Experience is a better indicator of true capability, though certifications can help identify knowledge gaps. Hiring managers should prioritize practical experience over credentials when evaluating candidates.
- [Here the dirty secret behind many agile transformations](https://engineering-leadership.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/): 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.
- [I’ll never understand teams that manage bugs instead of fixing them](https://engineering-leadership.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/): 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.
- [let-us do the maths](https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/): 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.
- [Too much refinement wastes time](https://engineering-leadership.hinshelwood.com/signals/too-much-refinement-wastes-time/): 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.
- [Not all surprises in product development are true unknowns](https://engineering-leadership.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/): 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.
- [Innovation graveyards: Where great ideas die in slow organisations](https://engineering-leadership.hinshelwood.com/signals/innovation-graveyards-where-great-ideas-die-in-slow-organisations/): Slow organisations kill promising ideas by demanding certainty, avoiding risk, and requiring full alignment before testing anything. Successful companies move quickly, experiment, and improve as they go, understanding that waiting for perfection leads to missed opportunities. To avoid wasting potential, encourage faster testing and learning from new ideas.
- [No successful company thrives by copying others’ ways of working](https://engineering-leadership.hinshelwood.com/signals/no-successful-company-thrives-by-copying-others-ways-of-working/): Successful companies do not achieve success by copying others’ processes; instead, they create ways of working tailored to their unique challenges, culture, and customers. Relying on packaged frameworks like SAFe or the Spotify Model can hinder genuine growth and adaptation. Development managers should focus on designing and evolving their own approaches to scaling rather than outsourcing this critical work to external models.
- [Companies often say "we-are going Agile!" as if declaring it makes it so](https://engineering-leadership.hinshelwood.com/signals/companies-often-say-we-are-going-agile-as-if-declaring-it-makes-it-so/): Simply declaring an Agile transformation does not make a company truly agile; real agility is about quickly responding to market changes, not just adopting frameworks like SAFe or Scrum@Scale. Successful organisations tailor their ways of working to their unique needs rather than copying others. Development managers should focus on building agility that fits their own business instead of relying on off-the-shelf solutions.
- [Understand the true risk of technical debt in your business](https://engineering-leadership.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/): Technical debt is pure risk with no upside, leading to lost time, reduced agility, and missed opportunities. Microsoft’s experience shows that unchecked technical debt can severely slow delivery, but addressing it directly restores speed and flexibility. Development managers should treat technical debt as a critical business issue and take proactive steps to reduce it.
- [Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety](https://engineering-leadership.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/): 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.
- [Every delay in decision-making taxes your organisation future](https://engineering-leadership.hinshelwood.com/signals/every-delay-in-decision-making-taxes-your-organisation-future/): Delays in decision-making hurt your organisation by slowing progress and letting competitors get ahead. Most delays come from internal bureaucracy and risk-averse processes, which stifle innovation and responsiveness. To stay competitive, streamline approvals and empower teams to act quickly.
- [Would your CFO approve misrepresenting corporate assets?](https://engineering-leadership.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/): Ignoring technical debt is like misrepresenting the value of your software assets, which can lead to future losses and operational risks. Most businesses fail to track this risk, even though technical debt reduces asset value and increases costs. Development managers should ensure technical debt is monitored and addressed to protect the true value of software investments.
- [Agile without a usable working product is just expensive theatre](https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/): Agile only delivers value if each sprint results in a usable working product; focusing on rituals, documentation, or velocity without real output wastes time and resources. The key measure of success is having something shippable at the end of every sprint, which enables feedback and reduces risk. Development managers should ensure their teams are consistently delivering usable products rather than just going through the motions.
- [There no such thing as "good" technical debt](https://engineering-leadership.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/): 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'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.
- [You don’t own your market](https://engineering-leadership.hinshelwood.com/signals/you-don-t-own-your-market/): Your customers control the market, not you, so failing to listen or respond quickly means losing them to competitors. Many organizations prioritize internal views over real customer needs, leading to late product launches and missed opportunities. To stay relevant, focus on genuine customer feedback and ensure your teams are closely connected to those you serve.
- [Most companies still get Product Ownership wrong](https://engineering-leadership.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/): 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.
- [The market isn’t slowing down for anyone](https://engineering-leadership.hinshelwood.com/signals/the-market-isn-t-slowing-down-for-anyone/): Success in today's market depends on how quickly your organization can respond and adapt, not on which framework you use. Relying on old control methods with superficial agile practices slows you down and puts you at risk of falling behind. To stay competitive, focus on building a truly responsive system that enables fast, smart decisions and real adaptability.
- [Hiring a Product Owner? Avoid copying job specs from the internet](https://engineering-leadership.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/): When hiring a Product Owner, do not rely on generic job descriptions; a true Product Owner drives product success by setting vision, prioritizing value, collaborating closely with teams, making data-driven decisions, and maintaining accountability. Delegation is necessary, but the PO must remain responsible for outcomes, not just manage tasks. Review your job specs to ensure they focus on leadership and product impact, not just administrative duties.
- [Building the wrong thing is worse than fixing a bug](https://engineering-leadership.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/): 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.
- [A great backlog isn’t just a list of tasks](https://engineering-leadership.hinshelwood.com/signals/a-great-backlog-isn-t-just-a-list-of-tasks/): A backlog should guide strategic decisions and reflect the product vision, not just list tasks. Filling it with unchecked requests leads to loss of focus and unclear priorities. Review your backlog to ensure it highlights what truly matters for delivering value and supports your product strategy.
- [Most organisations waste their smartest people](https://engineering-leadership.hinshelwood.com/signals/most-organisations-waste-their-smartest-people/): Many organisations waste their smartest people by creating environments where decision-making is centralized and ideas are slowed by bureaucracy, leaving those closest to the work powerless. This leads to disengagement or turnover among top talent, not due to lack of motivation but because they are unable to act. To retain and energize your best people, give them real authority to drive change.
- [99% of all animal species that ever existed are now extinct](https://engineering-leadership.hinshelwood.com/signals/99-of-all-animal-species-that-ever-existed-are-now-extinct/): Most animal species have gone extinct because they could not adapt, and the same fate can happen to companies that fail to evolve. Relying on past successes or outdated processes puts your business at risk, as the market changes quickly and does not wait. To stay competitive, focus on true adaptability and regularly assess what is slowing your company down.
- [A bloated backlog is not a sign of good product management](https://engineering-leadership.hinshelwood.com/signals/a-bloated-backlog-is-not-a-sign-of-good-product-management/): A backlog packed with every idea signals indecision, not good product management. Overloaded backlogs make it hard to prioritize, confuse stakeholders, and slow teams down. Keep your backlog focused on the most valuable upcoming work and regularly remove items your team cannot realistically address.
- [Hybrid Agile often combines the worst of both traditional and Agile methods](https://engineering-leadership.hinshelwood.com/signals/hybrid-agile-often-combines-the-worst-of-both-traditional-and-agile-methods/): Mixing Agile with traditional methods often results in a slow, inefficient process that fails to deliver the benefits of either approach. Simply adding Agile practices to a rigid system does not enable faster adaptation or competitiveness. Development managers should assess whether their processes truly support rapid change rather than just adopting Agile terminology.
- [A great Product Owner drives product strategy, not just manages the backlog](https://engineering-leadership.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/): A great Product Owner shapes product strategy by owning the vision, understanding customers and the market, making tough decisions, aligning stakeholders, and adapting based on evidence. Focusing only on backlog management limits their impact; empowered POs drive real value and influence roadmaps. Ensure your Product Owners have the authority and support to make strategic decisions, not just administrative tasks.
- [We don’t have time for automation, but manual testing slows releases and quality](https://engineering-leadership.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/): 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.
- [If every release feels high-risk, you lack a true Definition of Done](https://engineering-leadership.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/): 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's process to make releases predictable and low-stress.
- [A changing Definition of Done undermines quality and predictability in teams](https://engineering-leadership.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/): 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.
- [Scrum Teams don’t set the bar for quality, they meet it](https://engineering-leadership.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/): 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.
- [If teams struggle with quality or delivery, the problem is often the system](https://engineering-leadership.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/): 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.
- [Why compromising on software quality is a leadership decision](https://engineering-leadership.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/): 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.
- [Executives want predictability](https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/): 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 "Done" 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.
- [Scrum is not a process it is a social technology designed to expose dysfunction](https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/): 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.
- [Why Scrum Masters Need Technical Expertise to Guide Teams](https://engineering-leadership.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/): Scrum Masters are most effective when they have hands-on experience and technical understanding relevant to their team'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.
- [Why Most Companies Fail at Adopting Agility Beyond IT](https://engineering-leadership.hinshelwood.com/signals/why-most-companies-fail-at-adopting-agility-beyond-it/): Most companies fail to adopt agility beyond IT because the real barriers are organisational, such as rigid hierarchies, inflexible budgeting, and outdated performance reviews. Scrum Masters need to focus on driving broader organisational change, not just team-level practices. Development managers should address systemic blockers and rethink how work is funded and measured to enable true agility.
- [Empowering Product Owners as Strategic Leaders in Scrum Teams](https://engineering-leadership.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/): 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.
- [The True Role of a Scrum Master Beyond Facilitation](https://engineering-leadership.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/): 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.
- [Too many Scrum Masters believe they don’t need technical skills](https://engineering-leadership.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/): 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's work, they cannot truly enable success. Development managers should ensure Scrum Masters have or develop the necessary expertise to make a meaningful impact.
- [Great Scrum Masters and Product Owners don’t micromanage](https://engineering-leadership.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/): 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.
- [Overcoming Project Blockers and Challenging Organisational Inertia](https://engineering-leadership.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/): Teams are often held responsible for project outcomes without having the authority to remove blockers or challenge ineffective practices, which leads to frustration and failure. True accountability requires giving teams both autonomy and the power to influence their environment. Development managers should ensure teams have the authority needed to address obstacles and drive results, not just the responsibility.
- [“Teams are self-managing](https://engineering-leadership.hinshelwood.com/signals/teams-are-self-managing/): 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.
- [Scrum Masters: Why Influence Alone May Not Be Enough](https://engineering-leadership.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/): Relying only on influence limits a Scrum Master'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.
- [No one questions a Product Owner authority](https://engineering-leadership.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/): Product Owners are trusted with authority to make decisions that drive product success, but Scrum Masters often lack similar authority despite being responsible for team effectiveness and removing obstacles. Relying only on persuasion limits their impact; Scrum Masters need the power to enforce good practices and address issues directly. Development managers should ensure Scrum Masters have the authority needed to fulfill their role and support team agility.
- [Why Teams Claim Self-Management to Avoid Alignment Discussions](https://engineering-leadership.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/): 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.
- [Everyone loves the idea of self-managing teams](https://engineering-leadership.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/): 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.
- [Scrum Masters and Product Owners are held accountable for results](https://engineering-leadership.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/): 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.
- [Lack of Authority Blocks Progress on Critical Projects](https://engineering-leadership.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/): 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.
- [Why Measuring Individual Cycle Time Fails to Help Teams](https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/): 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.
- [Why Slow Processes Impact Developer Productivity and Performance](https://engineering-leadership.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/): 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.
- [Technical debt isn’t just messy code](https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/): 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.
- [Why Tracking Individual Cycle Time Distorts Team Behaviour](https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/): 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.
- [Measuring Worker Speed in Manufacturing Plant Operations](https://engineering-leadership.hinshelwood.com/signals/measuring-worker-speed-in-manufacturing-plant-operations/): Focusing on individual worker speed in manufacturing or knowledge work does not improve overall delivery if the system has bottlenecks or delays. True speed comes from addressing system-wide issues, not by pushing individuals to work faster. Development managers should prioritize fixing process bottlenecks rather than measuring or incentivizing individual task completion speed.
- [Velocity isn’t how many story points a team burns down](https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/): 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.
- [Scrum Masters are not glorified meeting schedulers](https://engineering-leadership.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/): 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.
- [Agile Is Not Easier Than Traditional Methods: Common Misconceptions](https://engineering-leadership.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/): 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.
- [let-us be blunt, if a Scrum Team isn’t delivering, is it effective](https://engineering-leadership.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/): 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.
- [Scrum Master Effectiveness Begins with Consistent Delivery](https://engineering-leadership.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/): 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.
- [Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers](https://engineering-leadership.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/): 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.
- [Understanding Blocked Columns and Stalled Work in Project Boards](https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/): Using a separate "Blocked" 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.
- [Engineering can fix technical debt, but leadership has to invest in it](https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/): 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.
- [At the end of the day, Kanban is about improving flow](https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/): 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.
- [Realistic Expectations When Hiring Junior Scrum Masters](https://engineering-leadership.hinshelwood.com/signals/realistic-expectations-when-hiring-junior-scrum-masters/): Hiring inexperienced Scrum Masters to save money often leads to poor team performance, delays, and lower product quality. The cost of inexperience outweighs any salary savings, while experienced Scrum Masters drive better results and team satisfaction. Invest in proven leadership to avoid costly failures and achieve faster, higher-quality delivery.
- [If software is not delivered, it is not valuable](https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/): 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.
- [Staging Environments Do Not Prevent Production Failures](https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/): 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.
- [A two-day Scrum Master certification doesn’t make you a Scrum Master](https://engineering-leadership.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/): 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.
- [Do More Staging Environments Really Reduce Deployment Risk](https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/): 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.
- [Best Branching Strategies for Development Teams Explained](https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/): 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.
- [Scrum is built on empiricism, transparency, inspection, and adaptation](https://engineering-leadership.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/): 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.
- [Why Organisations Believe Their Software Is Too Complex for CD](https://engineering-leadership.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/): 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.
- [What Makes an Effective Scrum Master Beyond Meeting Facilitation](https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/): 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.
- [Deploying Windows OS Directly to Production: Then vs Now](https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/): 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.
- [Rethinking Dev-Test-Staging-Production Pipelines for Safety](https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/): 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.
- [Why Using a Blocked Column in Azure DevOps Is a Mistake](https://engineering-leadership.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/): 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.
- [How Top Scrum Masters Are Selected by Their Teams](https://engineering-leadership.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/): 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.
- [Key Skills Scrum Masters Need: Technical, Business, Organisational](https://engineering-leadership.hinshelwood.com/signals/key-skills-scrum-masters-need-technical-business-organisational/): Scrum Masters need strong technical, business, and organisational skills to lead teams, align with business goals, and remove obstacles effectively. Experience and real leadership matter more than certifications. To achieve true agility, hire Scrum Masters who demonstrate competence and bold leadership.
- [The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master](https://engineering-leadership.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/): 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.
- [Would you hire a Junior CISO? A Junior Financial Director](https://engineering-leadership.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/): 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's success and true agility.
- [Hiring a Scrum Master is hard](https://engineering-leadership.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/): 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.
- [Not all delays are the same](https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/): Not all delays are equal; waiting for approval is different from being blocked by missing dependencies. Treating all delays as blocks hides real workflow issues and reduces accountability. Make delay sources explicit, track idle time, and highlight true blockers to identify and fix underlying problems.
- [Why Engineering Teams Use Staging Environments for Risk Reduction](https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/): 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.
- [Challenging Misconceptions About Behaviour in Agile Teams](https://engineering-leadership.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/): 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.
- [There a common belief that rollback is the ultimate safety net](https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/): 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.
- [Every delay increases the risk of failure](https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/): 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.
- [Git Flow should have died years ago](https://engineering-leadership.hinshelwood.com/signals/git-flow-should-have-died-years-ago/): 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.
- [Branch promotion is a relic of slow, manual software delivery](https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/): 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.
- [Frequent releases are not just a technical strategy](https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/): 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.
- [The Hidden Costs of Supporting Multiple Versions in Production](https://engineering-leadership.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/): 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.
- [Too many teams overcomplicate their branching strategies](https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/): 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.
- [Every unreleased feature is a cost](https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/): 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's efforts translate into actual value.
- [The false claim that Scrum is immutable](https://engineering-leadership.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/): Scrum is meant to be flexible and adaptable, not rigid, despite some claims that it is "immutable." The Scrum Guide's reference to immutability applies to its definition, not to how teams must implement it, so teams can adapt Scrum as needed as long as they are transparent about changes. Development managers should focus on delivering value, getting feedback, adapting plans, and reflecting regularly rather than debating strict adherence to the Scrum Guide.
- [The majority of Scrum Masters are not fit for their position](https://engineering-leadership.hinshelwood.com/signals/the-majority-of-scrum-masters-are-not-fit-for-their-position/): Most Scrum Masters lack the necessary knowledge and skills to lead teams effectively, with data showing that only 39 percent meet basic expectations and just 3 percent fully meet the role's requirements. Many have held these roles for years without competence, which is contributing to job losses as organizations demand higher standards. Development managers should rigorously assess and upskill their Scrum Masters to ensure team success.

## Videos

- [Engineering as a Leadership System](https://engineering-leadership.hinshelwood.com/videos/engineering-as-a-leadership-system-future-of-work-scotland/): Recorded at The Future of Work in Scotland, this session argues that delivery outcomes are set by the operating model leaders design, not the frameworks teams adopt. Every organisation runs on a theory of the business; the operating model is that theory made structural, and it is written on five surfaces: governance, funding, measurement, decision rights, and accountability. The session closes with a diagnostic anyone can run in a week without permission, tooling, or consultants: does your work move, wait, learn, or decay.
- [Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team](https://engineering-leadership.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/): Outsourcing your entire DevOps transformation to a vendor usually leads to expensive vendor lock-in, where your engineers inherit systems they do not understand and must rely on the vendor for every change. This results in legacy systems that are hard to update, such as being stuck on TFVC and .NET 3.5 when modern practices have moved on. Achieving true engineering excellence requires working with a partner who guides and mentors your team, helping them rebuild workflows, break down legacy systems, and understand modern methods. The real challenge is not just technical but about changing mindsets and ways of working, such as moving from TFVC to Git, which affects every part of the development process. Engineering success comes from enabling your teams to own their transformation, not from buying a solution from outside.
- [Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems](https://engineering-leadership.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/): Big Bang rewrites of legacy systems almost always fail; they cost more, take longer, risk business continuity, and rarely deliver the expected value. Organisations often repeat this cycle, cancelling one expensive rewrite after another, without addressing the underlying culture and engineering practices. Transforming a legacy system successfully means fixing it in place, improving and integrating components step by step, which encourages continuous learning and sustainable change. Teams that refactor their own code develop engineering excellence and reduce risk by delivering incremental value. This disciplined, patient approach not only modernises technology but also builds resilient teams and products for the long term.
- [Why Azure DevOps Wins for Governance, Security, and Scale, Right Out of the Box](https://engineering-leadership.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/): Azure DevOps excels at governance, security, compliance, and scalability because these features are built in from the start, not added on later. In high-pressure, hands-on training sessions, getting up and running with Azure DevOps is fast and reliable thanks to seamless tool integration, clear audit trails, and instant traceability from work items through to builds and releases. By contrast, open source alternatives require painstaking setup and still lack unified governance and compliance. Azure DevOps has proven itself capable of running projects with thousands of developers, such as the Windows team’s 15,000-person project, while fully integrating with enterprise identity systems. For organisations needing frictionless governance and security at scale, Azure DevOps delivers this right out of the box.
- [Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics](https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/): Relying on gut feel in product development leads to mediocrity; evidence-based management, grounded in process metrics like lead time and cycle time, is essential for real improvement. Azure DevOps collects rich telemetry on every variable and custom field in work items, but its out-of-the-box dashboards are quite basic and focus on averages rather than deeper insights, like percentile spreads or system-wide WIP limits. For teams seeking better visibility and actionable data, tools like Flow Viz (a free, pre-built PowerBI solution) and Actionable Agile Metrics for Predictability (a paid interactive plugin) provide advanced visualisations, such as work-in-progress views with percentile overlays showing at-risk items. Developers may prefer CLI tools like Ben’s Azure DevOps Admin Tools for scriptable data access. The key is to make your work visible, replace guessing with solid data, and use that visibility to unlock sustainable delivery improvements.
- [Stop Testing Quality In: How Shifting Left Builds Better Software, Faster](https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/): Relying on testers to catch defects after code is written leads to slower feedback, higher costs, and less trust in the product; true quality comes from building it in from the start. The closer quality checks are to the engineer’s keyboard, the faster and safer the process becomes, using practices such as automation, continuous integration, test-driven development, targeted static analysis, and quick code reviews. The Azure DevOps team cut their feedback cycle from up to four days to under four minutes by refactoring 36,000 slow system tests into 80,000 fast unit tests. Shifting left by moving testing and automation earlier in the workflow empowers engineers and enables fixes within minutes, not days. Quality becomes an ongoing, incremental responsibility for everyone, leading to rapid, reliable releases and stronger customer trust.
- [Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)](https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/): Manual deployments are a major risk to your business, not a sign of care or professionalism. The failure of Knight Capital Group, which lost $440 million and collapsed in a single day due to one missed server in a manual deployment, shows how a single human error can be catastrophic. Even experienced professionals make mistakes with repetitive manual steps, leading to failures and false positives. Automation of builds, deployments, gates, and tests is now the bare minimum for modern engineering; every step from commit to production should be automated. Without full automation, your business is exposed to significant and unnecessary risk.
- [From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation](https://engineering-leadership.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/): Transforming legacy engineering practices to modern DevOps excellence is not a linear process but a series of tested hypotheses, with each change validated in real-world conditions. The journey begins by tackling the most complex product, such as migrating from Team Foundation Version Control to Git, exposing key challenges early. Involving everyone who signs off on releases uncovers essential requirements, which are then automated as far as possible to eliminate manual steps between code commit and production. Modernisation relies on trunk-based development, automated builds, approvals, and phased, audience-based rollouts that use real data, much like Microsoft and Google’s ring deployments. Building a culture of engineering excellence means adapting step by step and using what works on the hardest problems as a model for scaling change across the organisation.
- [Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience](https://engineering-leadership.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/): Azure DevOps provides more than just tools: it is a unified platform for engineering excellence, enabling transparency, traceability, and a collaborative developer experience. By linking work items directly to code changes, builds, test cases, and deployment environments, teams gain full lifecycle visibility and can answer precise questions about what is shipped and where. Automated and manual testing are integrated, with features like exploratory testing and instant bug association eliminating "bug ping pong" between testers and developers. This end-to-end traceability simplifies audits, supports risk analysis, and fosters trust among teams and stakeholders. Used fully, Azure DevOps improves both product quality and the day-to-day developer experience.
- [Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success](https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/): Engineering excellence is not about achieving perfection or creating exhaustive, unchangeable plans. Instead, it centres on continuous improvement, rapid feedback, and adaptive systems that allow teams to deliver high-quality products quickly. Practices like trunk-based development, clean code, automation, and observability are crucial, and barriers such as manual processes or legacy infrastructure must be addressed. A concrete example shows the Azure DevOps team reducing their test suite runtime from up to 72 hours to just three and a half minutes by gradually improving their systems over 80 sprints. The core message is to focus on shortening feedback loops and continuous adaptation, not on perfect plans.
- [Futureproof Leadership: How CTOs Can Cut Through the Noise and Lead with Clarity, Confidence, and Culture](https://engineering-leadership.hinshelwood.com/videos/futureproof-leadership-how-ctos-can-cut-through-the-noise-and-lead-with-clarity-confidence-and-culture/): CTOs face overwhelming pressure from rapid technological change, constant new frameworks, and high expectations from both leadership and teams. The solution is not to chase every trend but to focus on what matters: gain clarity by making end-to-end systems visible, use evidence and real data to drive confident decisions, and foster a resilient culture that encourages experimentation and learning from failure. Leadership is less about heroics and more about building robust systems and supportive teams. Navigating this landscape is easier with an experienced partner who can help guide through the noise and uncertainty.
- [Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win](https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/): Most teams struggle not with building, but with finishing work in a way that genuinely benefits the business. Treating the definition of done as a mere technical checklist misses its true power as a strategic tool that drives customer satisfaction, reduces costly defects and rework, and builds confidence in delivery. Done should mean the product is valuable, usable, and maintainable, not just that it compiles or is deployed. To unlock this advantage, teams should keep their definition of done visible, review and evolve it regularly, involve everyone in shaping it, and ensure it connects to real outcomes. The shift from "it works" to "it wins" begins with how teams finish, not just what they build.
- [Legacy Systems Aren’t the Enemy, Friction Is: How to Unblock Innovation and Accelerate Agile Delivery](https://engineering-leadership.hinshelwood.com/videos/legacy-systems-aren-t-the-enemy-friction-is-how-to-unblock-innovation-and-accelerate-agile-delivery/): Legacy systems are not inherently a problem; the real obstacle to innovation and agile delivery is friction in your software environment. Friction comes from neglected systems, clunky deployment processes, and opaque codebases, slowing lead times, sapping morale, and making change risky. Windows, despite its age, is not seen as "legacy" because it is actively maintained and evolves; the key difference is attention and continuous improvement. A system becomes a legacy system when friction accumulates and holds your organisation back. Identifying friction points, prioritising ongoing maintenance, and clearly communicating the value of reducing friction are crucial steps to unlock faster delivery and support future growth.
- [From Burnout to Breakthrough: How CTOs Can Lead with Clarity, Resilience, and Real Innovation](https://engineering-leadership.hinshelwood.com/videos/from-burnout-to-breakthrough-how-ctos-can-lead-with-clarity-resilience-and-real-innovation/): Tech leaders cannot drive real innovation if they are overwhelmed and burned out, yet many CTOs find themselves stuck in constant firefighting and survival mode rather than true leadership. Leading effectively starts with stepping back to gain clarity on what is slowing you down, understanding what your teams actually need, and recognising which systems and processes hinder progress instead of helping it. Sustainable tech leadership requires focusing on what matters most—building clear, actionable strategies aligned with business goals, supporting deliberate decision-making rather than panicked reactions, and consistently doing the right things. Burnout is not a sign of commitment but a barrier to effectiveness; resilience and clarity enable better leadership. Working intelligently, with purpose, leads to lasting innovation and healthier teams, moving from chaos to consistent, long-term success.
- [Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar](https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/): A vague definition of “done” limits product quality, agility, and trust by encouraging teams to focus on task completion instead of real outcomes. “Done” should be an objective, measurable standard where the product increment is tested across the whole system, deployed to a production-like environment, monitored in real-world use, and validated against an explicit business hypothesis. This approach raises quality by reducing defects and rework, speeds time to value, and builds stakeholder trust. Teams that adopt this shared, concrete standard for “done” learn and improve faster and consistently deliver valuable software to users. The difference is striking: those who raise the bar on “done” deliver true outcomes, not just completed checklists.
- [Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership](https://engineering-leadership.hinshelwood.com/videos/stop-chasing-tech-hype-how-evidence-based-decisions-empower-real-leadership/): Chasing technology trends because competitors or vendors urge it is not real strategy; it is simply yielding to pressure. Many organisations end up with flashy technologies like Kubernetes that do not solve their actual problems, leading to demotivated teams and wasted resources. The key to strong leadership is making current challenges and processes visible, relying on data to guide decisions, and evaluating technology based on whether it genuinely fits the business need rather than its popularity. Walking into meetings with clear evidence and alignment to business goals builds credibility and sustainable success. True leadership means resisting reactive decisions and focusing on choices that move the business forward on its own terms.
- [The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team](https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/): The Open Guide to Kanban is a community-driven, living document built on GitHub to make Kanban accessible and practical for any team or industry, not just software or experts. Its open approach encourages real contributions from practitioners, focusing on clear language and real-world value rather than jargon or rigid dogma. Distinctively, it emphasises visualising workflow—“work that’s started but not finished”—and centres on delivering meaningful outcomes, not just optimising flow for its own sake. Kanban and Scrum are presented as allies, with practical advice to start where you are, improve visibility, and adapt as you learn. The guide is both a resource and an invitation for everyone to participate, challenge, and improve it together.
- [Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster](https://engineering-leadership.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/): Acceptance criteria are the specific, testable conditions each backlog item must meet, serving as a unique checklist to clarify what “done” means for that particular feature or story. In contrast, the definition of done is the organisation-wide quality baseline that every piece of work must meet, covering requirements such as security checks, deployment readiness, and compliance. Confusing these leads to missed expectations, technical debt, and damaged trust; a feature might pass acceptance criteria but still lack essential quality. Teams must make their definition of done visible and explicit, and treat acceptance criteria as the contract for each item, but not as a replacement for quality standards. Clear distinction and regular review of both enable faster delivery, higher quality, and stronger trust between teams and stakeholders.
- [Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams](https://engineering-leadership.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/): Building true agility means creating systems and teams that are genuinely adaptable, rather than constantly chasing the latest frameworks or tools. Resilience comes from using DevOps and agile to reduce friction, enable smoother paths to production, and establish robust feedback loops, so teams can handle change without disruption. Adopting shiny new technologies is worthless if delivery pipelines are fragile or teams overloaded, as this only adds complexity. Adaptability must become part of the organisation's foundation, shaping culture, processes, and technology so that change is an opportunity rather than a threat. Focusing on connecting people, practices, and systems ensures teams move from reacting to leading, thriving instead of merely surviving.
- [How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum](https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/): A Definition of Done should start simple and practical, focusing on delivering something usable rather than trying to achieve perfection from the outset. High-performing teams evolve their Definition of Done over time, first ensuring features work and can be demonstrated, then gradually adding automated tests, telemetry, security checks, and ultimately continuous deployment as confidence builds. Trying to cover every compliance and quality standard from day one can stall progress and demotivate teams. Each improvement should be adopted when the team is ready, so momentum and value delivery are never lost. The journey to an effective Definition of Done is incremental and should prioritise progress and learning over immediate completeness.
- [Engineering Culture That Thrives: How to Build Teams Ready for Change, Not Just the Next Fire Drill](https://engineering-leadership.hinshelwood.com/videos/engineering-culture-that-thrives-how-to-build-teams-ready-for-change-not-just-the-next-fire-drill/): Engineering teams cannot thrive by simply reacting to new technologies or treating every wave of change as a crisis; the key is building a culture that expects, supports, and measures adaptation. The most effective teams do not chase every shiny tool, but instead reflect, learn, and improve their practices based on evidence while aligning with business goals. Deliberate investment in a learning organisation means training people to embrace change, embedding continuous improvement into daily work, and measuring what truly matters. Instead of betting on new frameworks, invest in people and culture to ensure the team is resilient and relevant, no matter how fast the technology landscape evolves. Ask whether your culture is ready for change, not just the next emergency.
- [Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth](https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/): A robust definition of done is a strategic lever that drives real business impact and agile growth. When "done" means features are live, usable, gathering telemetry, and having their outcomes validated, teams achieve faster time to value, lower risk, and genuine adaptability. Too often, teams mark code as "done" when it is merely merged but not deployed or validated, leading to wasted effort that delivers no measurable result. Making your definition of done visible, linking it directly to business outcomes, measuring impact, and continuously adapting it ensures that every increment truly moves the needle for your organisation. Done should not be a checklist but the engine of value and growth.
- [CTO Leadership Isn’t About Knowing Everything, It’s About Knowing What Matters Most](https://engineering-leadership.hinshelwood.com/videos/cto-leadership-isn-t-about-knowing-everything-it-s-about-knowing-what-matters-most/): CTOs do not need to keep up with every new technology or trend; effective leadership is about identifying and focusing on what truly matters for your business and teams. By mapping how value flows through your organization and filtering out distractions, you can make better decisions and lead with clarity. Prioritize understanding your key constraints and empower your teams to deliver value rather than trying to know everything yourself.
- [Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done](https://engineering-leadership.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/): 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.
- [Modernising Legacy Systems: A Practical, Low-Risk Strategy for Real Business Transformation](https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-a-practical-low-risk-strategy-for-real-business-transformation/): Modernising legacy systems should be a strategic, low-risk process focused on understanding both technical and workflow bottlenecks, not a risky full replacement. Incremental changes, targeted automation, and addressing process issues often deliver the best results while minimising disruption. Development managers should map how work flows through their systems, prioritise fixes that offer the most value, and shift from reactive firefighting to proactive improvement.
- [Stop Chasing the Hottest Tech Stack: Why Context-Driven Choices Win Every Time](https://engineering-leadership.hinshelwood.com/videos/stop-chasing-the-hottest-tech-stack-why-context-driven-choices-win-every-time/): 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.
- [Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation](https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/): 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.
- [DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over](https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/): 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.
- [How to Stop Chasing Tech Hype and Start Making Smarter, Evidence-Based Decisions](https://engineering-leadership.hinshelwood.com/videos/how-to-stop-chasing-tech-hype-and-start-making-smarter-evidence-based-decisions/): Chasing every new technology trend wastes resources, demoralises teams, and creates technical debt. Instead, use structured, evidence-based frameworks to evaluate tech choices based on strategic fit, ROI, team capability, and timing. Make disciplined decision-making a repeatable part of your process so you lead with intent rather than react to hype.
- [Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence](https://engineering-leadership.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/): 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.
- [How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward](https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/): 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.
- [From Firefighting to Focus: How CTOs Can Lead with Clarity Instead of Chasing the Next Big Thing](https://engineering-leadership.hinshelwood.com/videos/from-firefighting-to-focus-how-ctos-can-lead-with-clarity-instead-of-chasing-the-next-big-thing/): 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.
- [Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results](https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/): 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.
- [Breaking Free from Vendor Lock-In: How to Regain Control and Future-Proof Your Business](https://engineering-leadership.hinshelwood.com/videos/breaking-free-from-vendor-lock-in-how-to-regain-control-and-future-proof-your-business/): Vendor lock-in from legacy contracts and proprietary systems limits your team’s ability to adapt, often forcing you to work around outdated decisions and maintain inflexible vendor models. To regain control, identify your real constraints, map dependencies, and enable transparent decision-making that prioritises your business needs. Focus on building flexibility into your systems and processes rather than simply replacing tools, and start by challenging existing assumptions and mapping where you are truly locked in.
- [How CTOs Can Cut Through the Noise: Building Real Clarity and Confidence in a World of AI Hype and Microservices Madness](https://engineering-leadership.hinshelwood.com/videos/how-ctos-can-cut-through-the-noise-building-real-clarity-and-confidence-in-a-world-of-ai-hype-and-microservices-madness/): CTOs face constant pressure to adopt new technologies like AI and microservices, but chasing every trend often leads to confusion and technical debt. The key is to focus on understanding your organisation’s real challenges, build decision-making capability at all levels, and invest in clarity rather than hype. Partnering with experts who help you see your true constraints and strengths can enable you to set your own pace and lead with confidence.
- [Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/): 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.
- [Modernising Legacy Systems: How to Tackle Security Risks Without Breaking Your Business](https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/): 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.
- [Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery](https://engineering-leadership.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/): 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.
- [Cloud Migration Without the Mayhem: How to Move Legacy Systems Safely and Set Your Teams Up for Success](https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/): 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.
- [Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation](https://engineering-leadership.hinshelwood.com/videos/unlocking-legacy-systems-how-to-embrace-automation-and-drive-innovation/): Legacy systems can and should be automated, with the main barrier being mindset rather than technology. By encouraging a culture that questions old processes and starting with small, incremental automation efforts, teams can reduce bottlenecks and unlock significant efficiency gains. Development managers should identify manual pain points and begin automating them to drive innovation and continuous improvement.
- [Navigating the Shift: Key Strategies for a Successful Transition to Microservices](https://engineering-leadership.hinshelwood.com/videos/navigating-the-shift-key-strategies-for-a-successful-transition-to-microservices/): 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.
- [Navigating the Legacy System Dilemma: Balancing Stability and Innovation for Modernisation Success](https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-dilemma-balancing-stability-and-innovation-for-modernisation-success/): Balancing stability and innovation in legacy systems is challenging, as rapid changes can cause technical debt and confusion, while inaction leads to stagnation. Gradual, collaborative modernisation focused on engineering best practices allows for progress without disrupting what works. Consider incremental improvements to maintain resilience and competitiveness while modernising.
- [Navigating the Legacy System Labyrinth: Strategies for Modernisation Success](https://engineering-leadership.hinshelwood.com/videos/navigating-the-legacy-system-labyrinth-strategies-for-modernisation-success/): 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.
- [Mastering Sustainable Scaling: Overcoming Product Development Challenges with Naked Agility](https://engineering-leadership.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/): 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's needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth.
- [Scaling Teams: How to Foster Innovation Without Falling into Bureaucracy](https://engineering-leadership.hinshelwood.com/videos/scaling-teams-how-to-foster-innovation-without-falling-into-bureaucracy/): Scaling teams does not automatically lead to more innovation; it often results in bureaucracy, slower decision-making, and communication issues. To avoid this, focus on empowering teams, streamlining processes, and improving communication so growth enhances agility and innovation rather than stifling it. Development managers should reassess their scaling strategies to prioritize adaptability and team ownership for better outcomes.
- [Embrace Simplicity: How to Transform Complexity into Continuous Delivery Success](https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/): 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.
- [Mastering the Art of Scaling Agile: Strategies to Maintain Agility Across Multiple Teams](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/): 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.
- [Scaling Smart: How to Tackle Technical Debt for Sustainable Growth](https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/): 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.
- [Unlocking Sustainable Growth: Why Leadership is the Key to Successful Scaling](https://engineering-leadership.hinshelwood.com/videos/unlocking-sustainable-growth-why-leadership-is-the-key-to-successful-scaling/): Successful scaling in software development depends more on effective leadership than on technical solutions. Empowering teams, removing bottlenecks, and decentralising decision-making are key to sustainable growth. Development managers should focus on shaping leadership behaviours to create an environment where teams can scale effectively.
- [Why the Concept of a "Junior Scrum Master" is a Misguided Myth](https://engineering-leadership.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/): The idea of a "junior Scrum Master" 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.
- [Why More Teams Won't Speed Up Delivery: The Truth About Scaling Effectively](https://engineering-leadership.hinshelwood.com/videos/why-more-teams-wont-speed-up-delivery-the-truth-about-scaling-effectively/): Adding more teams does not automatically speed up software delivery; it often creates more dependencies, coordination overhead, and technical debt, which can slow progress. Effective scaling focuses on reducing friction, structuring teams to minimize dependencies, and prioritizing quality over quantity. Development managers should ensure teams are set up to work independently and efficiently rather than simply increasing headcount.
- [Is Your Engineering Culture Ready to Scale with Your Technology?](https://engineering-leadership.hinshelwood.com/videos/is-your-engineering-culture-ready-to-scale-with-your-technology/): Scaling technology is easy compared to scaling engineering culture, which is often overlooked but critical for sustainable growth. If your culture does not evolve, issues like poor collaboration, superficial DevOps practices, and lack of continuous learning can undermine progress, and more tools alone will not fix this. Development managers should focus on fostering genuine collaboration, integrating DevOps as a mindset, and making continuous learning part of daily work to ensure culture keeps pace with technology.
- [Scaling Smart: How to Build Sustainable Growth Without the Chaos](https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-build-sustainable-growth-without-the-chaos/): Scaling should focus on building sustainable value, not just growing quickly, and simply adopting frameworks without addressing underlying issues will only make problems worse. Effective scaling requires understanding constraints, simplifying processes, and ensuring teams are aligned to deliver value. Before scaling, assess whether your approach will truly improve outcomes and use agile methods to enable smarter, not just faster, growth.
- [Mastering the Art of Scaling Product Development: Why Adding More Developers Isn't the Answer](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-product-development-why-adding-more-developers-isnt-the-answer/): Adding more developers does not solve scaling challenges in product development; without fixing underlying system issues, it can actually slow progress. Key problems include lack of alignment, unmanaged technical debt, and slow feedback loops, which all hinder effective scaling. Focus on clarifying priorities, reducing process bottlenecks, and enabling fast, coordinated team movement before increasing headcount.
- [Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy](https://engineering-leadership.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/): Unrealised value, or the features your users need but you have not built or identified yet, is often overlooked but crucial for product success. To unlock this value, focus on understanding your users, validate assumptions with small experiments before full development, and increase deployment frequency to speed up feedback and learning. Make it a priority to continuously learn from your market and adapt your product strategy to stay relevant and maximise impact.
- [Navigating the Balance: How Lean Governance Can Boost Agility and Innovation in Your Organisation](https://engineering-leadership.hinshelwood.com/videos/navigating-the-balance-how-lean-governance-can-boost-agility-and-innovation-in-your-organisation/): Excessive or siloed governance can slow down your organisation and stifle innovation, often leading to unnecessary processes that do not add value. Focusing on lean governance by regularly reviewing policies, integrating compliance into your tools, and eliminating waste helps maintain agility and efficiency. Review your current governance practices and remove or streamline anything that does not directly support compliance or business value.
- [Avoiding the Local Optimisation Trap: How to Ensure Your Governance Drives Organisational Success](https://engineering-leadership.hinshelwood.com/videos/avoiding-the-local-optimisation-trap-how-to-ensure-your-governance-drives-organisational-success/): Focusing on optimising individual teams or processes without considering their impact on the whole organisation can create inefficiencies and misalignment. Integrating governance into daily work and encouraging cross-team collaboration helps ensure decisions support overall business goals. Development managers should prioritise system-wide alignment over isolated improvements to drive lasting organisational success.
- [Unlocking Product Value: Why Real User Feedback is Your Best Asset](https://engineering-leadership.hinshelwood.com/videos/unlocking-product-value-why-real-user-feedback-is-your-best-asset/): Product value is only proven when real users interact with your product, so early and ongoing user feedback is essential to validate assumptions and guide development. Engaging users early, testing with prototypes or MVPs, and iterating based on feedback help ensure your product meets real needs and delivers genuine value. Prioritise getting your product in front of users quickly to maximise impact and avoid wasted effort.
- [Empowering Leadership: Driving Cultural Change for Agile Success](https://engineering-leadership.hinshelwood.com/videos/empowering-leadership-driving-cultural-change-for-agile-success/): Leadership is crucial for enabling agile success by setting a clear vision, investing in automation, supporting architectural improvements, fostering continuous learning, and breaking down silos. These actions help teams align with organisational goals, deliver more reliably, and adapt to change. Development managers should prioritise these areas to create a culture that supports frequent, high-quality delivery and ongoing improvement.
- [Embracing Change: How Architectural Adaptation Fuels Software Development Success](https://engineering-leadership.hinshelwood.com/videos/embracing-change-how-architectural-adaptation-fuels-software-development-success/): Adapting software architecture to meet changing demands is essential for long-term product success. Investing in teams, enabling incremental changes, and maintaining a long-term vision, like the Azure DevOps team’s four-year transformation, help reduce risk and support continuous improvement. Development managers should foster adaptability, prioritize architectural health, and clearly communicate long-term goals to ensure sustained progress.
- [Mastering Market Leadership: The Power of Frequent Product Releases](https://engineering-leadership.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/): Frequent product releases help you lead the market by allowing rapid response to user feedback and emerging trends. Teams that adopt this approach see higher user engagement and improved morale, as they can quickly deliver value and adapt to change. To stay competitive, focus on releasing updates regularly and listening closely to your users.
- [Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments](https://engineering-leadership.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/): Azure DevOps transformed from two-year release cycles to 880,000 deployments per year by adopting continuous delivery, shortening feedback loops, and using real-time data to guide decisions. This shift enabled rapid response to customer needs and market changes, helping them stay ahead of competitors. Development managers should focus on frequent, small releases and data-driven improvements to maximise value and agility.
- [Balancing Speed and Stability: Why Quality Should Always Come First in Delivery Management](https://engineering-leadership.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/): Rushing to meet deadlines often leads to poor-quality products that can damage your brand and erode customer trust, so prioritising stability and quality is essential even if it means missing deadlines or incurring fines. The long-term costs of sacrificing quality far outweigh any short-term gains from speed, as seen in real-world cases like Zoom. Development managers should educate stakeholders about these risks and always choose quality over speed to protect both reputation and customer relationships.
- [Rethinking Continuous Delivery: Why Best Practices Don't Exist in Complex Environments](https://engineering-leadership.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-dont-exist-in-complex-environments/): 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.
- [Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success](https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/): 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.
- [Unlocking Continuous Delivery: How Feature Flags Transform Software Development](https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/): 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.
- [Unlocking the Future of Software Development: Why Automation is Your Key to Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/): 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.
- [Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence](https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/): 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.
- [Unlocking Code Quality: The Transformative Power of Frequent Deployments](https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/): 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.
- [Transforming Organisational Culture: Unlocking Engineering Excellence Through System Optimisation](https://engineering-leadership.hinshelwood.com/videos/transforming-organisational-culture-unlocking-engineering-excellence-through-system-optimisation/): To achieve engineering excellence, focus on understanding and measuring your current delivery system, then use those insights to optimise for maximum value rather than just cutting costs. Transparent metrics and iterative improvements help control costs and drive technical leadership. Start by assessing your workflows and processes to identify where changes will have the most impact.
- [Mastering Product Development Costs: Empower Your Team for Financial Success](https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-costs-empower-your-team-for-financial-success/): Understanding and managing product development costs, especially people and infrastructure, is essential for financial success. Empowering teams with financial awareness helps them make better decisions, align work with value, and focus on profitable outcomes. Development managers should foster a culture where teams track costs, measure value delivered, and continuously improve processes to drive profitability and innovation.
- [Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency](https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/): 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.
- [Why Embracing Automation is Essential for Reducing Human Error in Software Development](https://engineering-leadership.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/): 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.
- [Transforming Waste into Value: How to Boost ROI with Agile Metrics](https://engineering-leadership.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/): 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.
- [Transforming Chaos into Clarity: How Optimising Systems Fuels Engineering Excellence](https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/): 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.
- [Maximising ROI in Software Development: Unlocking Value Through Quality and Expertise](https://engineering-leadership.hinshelwood.com/videos/maximising-roi-in-software-development-unlocking-value-through-quality-and-expertise/): Maximising ROI in software development requires treating code as a valuable asset, investing in quality, and ensuring regular reviews to maintain standards. Bridging the gap between business and technical expertise is essential, so equip your leadership with the right knowledge and consider external coaching if needed. Prioritise quality, technical skill, and hypothesis-driven practices to ensure your teams deliver the most value for your investment.
- [Empowering Teams with Financial Insights: The Key to Maximising ROI and Fostering Ownership](https://engineering-leadership.hinshelwood.com/videos/empowering-teams-with-financial-insights-the-key-to-maximising-roi-and-fostering-ownership/): Giving your teams clear financial insights and ownership over their work leads to better decision-making and higher returns. When teams understand both the value they create and the costs involved, they align their efforts with business goals and are more motivated to improve. Start sharing financial context and encourage team-level profit and loss analysis to drive accountability and smarter product decisions.
- [Maximising Product Value: The Power of Hypothesis-Driven Engineering](https://engineering-leadership.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/): 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.
- [Navigating the Unknown: How to Fund Your Product Like a Venture Capitalist](https://engineering-leadership.hinshelwood.com/videos/navigating-the-unknown-how-to-fund-your-product-like-a-venture-capitalist/): Treat product funding like a venture capitalist by running small, low-risk experiments to validate ideas before committing significant resources. Require clear business plans, proof of concept, and ongoing iteration based on real user feedback to manage risk and maximize learning. Balance data-driven decisions with vision and passion, and be prepared to discard failed experiments while investing further in those that show promise.
- [Rethinking Budgeting: How to Break Free from Traditional Constraints and Maximise Value](https://engineering-leadership.hinshelwood.com/videos/rethinking-budgeting-how-to-break-free-from-traditional-constraints-and-maximise-value/): Traditional annual budgeting creates rigidity, discourages innovation, and often leads to missed opportunities and wasted resources. Adopting a more flexible, value-driven approach like Beyond Budgeting allows teams to allocate funds dynamically, respond quickly to changing needs, and focus on delivering real value. Development managers should consider shifting to iterative funding models to maximise impact and avoid costly missed opportunities.
- [Unlocking the True Power of Continuous Delivery: How Automation Transforms Software Development](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/): 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.
- [Rethinking Software Estimation: Embrace Probabilistic Forecasting for Agile Success](https://engineering-leadership.hinshelwood.com/videos/rethinking-software-estimation-embrace-probabilistic-forecasting-for-agile-success/): 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.
- [Transforming Scope Creep into Success: Embrace Agility and Deliver Value in a Changing Market](https://engineering-leadership.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/): 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.
- [Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration](https://engineering-leadership.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/): To build a high-performing software delivery team, focus on developing both technical and business competence across all members, encouraging everyone to think like product developers rather than just coders. Embrace Agile, DevOps, Lean, and Scrum philosophies, adapt practices as needed, and ensure due diligence before making structural changes. Prioritise collaboration, open communication, and continuous improvement to maximise value delivery and drive business success.
- [Navigating the Unpredictability of Software Development: Embrace Agile for Success](https://engineering-leadership.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/): 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.
- [Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership](https://engineering-leadership.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/): 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.
- [Cultivating a Culture of Quality: Lessons from Boeing and Volkswagen for Engineering Excellence](https://engineering-leadership.hinshelwood.com/videos/cultivating-a-culture-of-quality-lessons-from-boeing-and-volkswagen-for-engineering-excellence/): A strong culture of quality and technical excellence is essential for building reliable and valuable software products, as shown by the negative consequences at Boeing and Volkswagen when profit was prioritised over quality. Relying solely on frameworks like Agile is not enough; the real difference comes from collective commitment to quality, ethical leadership, and applying sound engineering principles. Development managers should focus on fostering this culture within their teams to ensure long-term success and avoid costly mistakes.
- [Mastering Technical Debt: Strategies to Transform Challenges into Opportunities for Your Development Team](https://engineering-leadership.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/): Technical debt results from choosing quick fixes over robust solutions, leading to future costs and risks that can hinder your team's productivity. Proactively paying down technical debt, as shown by the Azure DevOps team'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.
- [Code Reviews for Quality Assurance](https://engineering-leadership.hinshelwood.com/videos/code-reviews-for-quality-assurance/): 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.
- [Cultivating a Culture of Engineering Excellence: The Essential Role of Technical Leadership](https://engineering-leadership.hinshelwood.com/videos/cultivating-a-culture-of-engineering-excellence-the-essential-role-of-technical-leadership/): Technical leadership is essential for building a culture of engineering excellence, which requires clear expectations, continuous learning, and practical application of knowledge. Leaders should tailor strategies to their organisation’s context, model desired behaviours, and foster collaboration and improvement. Prioritising these actions helps teams adapt, innovate, and achieve better results in a fast-changing environment.
- [Confronting Incompetence: How to Stop Shipping Bad Code and Tackle Technical Debt Effectively](https://engineering-leadership.hinshelwood.com/videos/confronting-incompetence-how-to-stop-shipping-bad-code-and-tackle-technical-debt-effectively/): Shipping bad code is not just technical debt but a sign of deeper issues that teams must address by committing to quality and accountability. Key actions include enforcing thorough code reviews, investing in automated testing, and making regular refactoring a habit, while also actively identifying, prioritising, and allocating time to pay down technical debt. Development managers should ensure their teams distinguish between technical debt and poor practices, and dedicate resources to maintain a healthy, sustainable codebase.
- [Security by Design Building Secure Software](https://engineering-leadership.hinshelwood.com/videos/security-by-design-building-secure-software/): Shifting left in software engineering means embedding quality and security into development from the very beginning, not just checking for issues after code is written or released. Teams should own the entire process—developers write and run tests, support features in production, and work alongside specialists in security, testing, and UX. Techniques like test-driven development, pair programming, and fast feedback loops help prevent problems and support innovation. The Azure DevOps team, for example, shifted left over four years and increased their yearly feature delivery sixfold without growing the team. Building secure, reliable software from the start may feel slower initially but leads to stronger teams, happier customers, and far greater long-term value.
- [NKD Agility: Your partner in developing engineering excellence](https://engineering-leadership.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/): 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.
- [Unlocking the Superpower of Software Development: How Shifting Left Transforms Quality Assurance](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/): 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.
- [Building a culture of Quality](https://engineering-leadership.hinshelwood.com/videos/building-a-culture-of-quality/): Building a culture of quality in an organisation cannot be accomplished by any single person; everyone must demonstrate technical excellence and leadership, setting behaviour others will want to follow. The downfall of quality at Boeing after its acquisition of McDonnell Douglas, when revenue took precedence over engineering, shows the destructive impact of neglecting quality culture—a Boeing engineer joked they would only fly in their own plane if they had a death wish. The true issue is not Agile frameworks or tools themselves, but rather the organisational culture that governs how these tools are used, for good or ill. A genuine culture of quality prevents actions like writing deceptive code that cheats emissions tests, as happened at Volkswagen. Focusing on engineering excellence, technical leadership, and a strong theoretical foundation is essential to consistently making sound engineering decisions and building valuable, safe products.
- [Transforming Technical Debt: Unlocking Innovation and Value Through Quality Product Delivery](https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/): 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.
- [Technical Debt Management for Long-Term Quality](https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/): Technical debt arises when teams prioritise quick solutions over robust, long-term approaches, leading to inevitable future costs. It can be introduced knowingly by cutting corners or unknowingly as once-adequate architectural choices become outdated, such as when the Azure DevOps team hit SQL limits on work item fields and had to refactor their data model. Addressing technical debt should be prioritised, as it is an uninsured liability—no one else will fix it or cover losses if left unmanaged. By deliberately paying back technical debt and shortening feedback loops, the Azure DevOps team increased their delivery rate from 25 to 360 features per year over eight years, with a significant jump even in their first year of focused debt reduction. Managing technical debt directly improves a team's ability to deliver value and adapt their product.
- [Transforming Technical Debt: Unlocking Opportunities for Innovation and Value](https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/): 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's full potential.
- [Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/): 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.
- [Shifting Left. Quality from the Start](https://engineering-leadership.hinshelwood.com/videos/shifting-left-quality-from-the-start/): 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.
- [Transform Your Software Architecture: The Game-Changing Impact of TDD and Pair Programming](https://engineering-leadership.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/): 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.
- [The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower](https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/): 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.
- [Mastering Azure DevOps Migration: Expert Insights for a Seamless Transition](https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-migration-expert-insights-for-a-seamless-transition/): Migrating to Azure DevOps is complex and often a one-time event, so most teams lack the necessary in-house expertise. Key challenges include database validation, unexpected data issues, and the need for deep tool knowledge, making external experts or targeted training highly valuable. To ensure a smooth and successful migration, consider bringing in specialists or upskilling your team with expert support.
- [Mastering Cloud Migration: Overcoming the Fear of Incomplete Data Transfers](https://engineering-leadership.hinshelwood.com/videos/mastering-cloud-migration-overcoming-the-fear-of-incomplete-data-transfers/): Concerns about incomplete data transfers during cloud migration are often overstated; with proper planning, use of Microsoft’s migration tools, and clear communication about limitations, data loss is highly unlikely. Key steps include assessing your data, understanding cloud constraints like attachment size, and engaging Microsoft support for complex cases. To ensure a smooth migration, involve stakeholders early, plan for contingencies, and address potential issues before starting the move.
- [Navigating the TFS to Azure DevOps Migration: Overcoming Compatibility Concerns with Confidence](https://engineering-leadership.hinshelwood.com/videos/navigating-the-tfs-to-azure-devops-migration-overcoming-compatibility-concerns-with-confidence/): Migrating from TFS on-premises to Azure DevOps is generally straightforward, with most compatibility concerns affecting older on-prem versions rather than the cloud. Key considerations include planning for the loss of unsupported customisations, ensuring code security during the transition, and evaluating how existing extensions will work in Azure DevOps. To ensure a smooth migration, assess your current setup, identify potential gaps, and proactively address customisation needs.
- [Mastering Data Migration: How to Minimise Downtime and Keep Your Engineers Productive](https://engineering-leadership.hinshelwood.com/videos/mastering-data-migration-how-to-minimise-downtime-and-keep-your-engineers-productive/): 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.
- [Mastering Data Integrity: The Key to Successful DevOps Migrations](https://engineering-leadership.hinshelwood.com/videos/mastering-data-integrity-the-key-to-successful-devops-migrations/): Maintaining data integrity is crucial during DevOps migrations, especially when moving from database-centric systems like TFS to Azure DevOps Services. You must balance full database migration, which preserves all data but may be impractical, against selective migration, which offers flexibility but risks data loss and added complexity. Assess your teams' needs, use the right tools, communicate clearly, and test thoroughly to ensure a smooth and effective migration.
- [Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability](https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-role-moving-beyond-misconceptions-to-true-accountability/): 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.
- [The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI](https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/): Organisations often fail to realise the expected return on investment from Scrum Masters due to a lack of competence, especially in understanding the team context, product owner needs, and organisational dynamics. A skilled Scrum Master improves delivery, fosters innovation, reduces defects, and prevents stagnation. Key metrics to assess their impact include innovation rate, on-product index, usage index, and installed version index; for every dollar spent on development, as little as six cents may yield real value if these areas lag. For example, a bank uncovered that only 8% of its features were actually used, despite assumptions of 80%. Continually measuring these metrics and holding Scrum Masters accountable is vital to driving meaningful improvement in ROI.
- [The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success](https://engineering-leadership.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/): 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.
- [The Competence Crisis in Scrum Master Roles: A Call for Excellence](https://engineering-leadership.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/): There is a widespread competence gap among Scrum Masters, largely created by the rapid adoption of agile practices that outpaced the supply of skilled professionals. Many entered the role through short courses, often lacking essential experience with IT, software engineering, and modern product practices. The analogy is made to passing a driving test versus racing in Formula 1; foundational exposure is not mastery. Direct experience is vital, as illustrated by the author's work training police officers in Ghana, where lack of domain expertise limited their effectiveness. With economic pressures, organisations are now letting go of unqualified Scrum Masters and shifting hiring toward those with deep, contextual skills and real-world understanding.
- [The Importance of Competence in Organizations: Building a Culture of Learning and Growth](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-competence-in-organizations-building-a-culture-of-learning-and-growth/): Competence is essential for any organisation seeking to create valuable products and services, as it fuels innovation, problem-solving, and customer satisfaction. Unhappy or disengaged people build mediocre products, so fostering learning, experimentation, and well-being leads to happier, more effective teams. Practical ways to cultivate competence include offering ongoing training, supporting risk-taking and passion projects, recognising skill development, and prioritising self-care and feedback. Hiring should focus on proven ability and a drive for improvement rather than only culture fit. The core insight is that sustained investment in team competence enables organisations to thrive and exceed customer expectations.
- [Where Agile Went Wrong: Understanding the Competence Crisis](https://engineering-leadership.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/): Agile’s early promise was undermined by the founders’ assumption that future practitioners would be as competent and driven as they were, but most organisations have struggled to maintain these high standards. A striking example of the competence gap is that 39% of Scrum Masters have never read the Scrum Guide, and over 60% are not capable of fulfilling the role effectively, even with years of experience. This shortage of true Agile expertise has been worsened by hiring practices that prioritise filling roles over developing deep, context-specific knowledge and a culture of lifelong learning. Effective Agile teams are compared to Special Operations units, requiring continual practice, adaptation, and a commitment to experimentation. To reverse the competence crisis, companies must prioritise deep expertise, continuous learning, and investment in people who understand their specific product, team, and organisational context.
- [Focusing Beyond "Agile": Building True Capability in Organizations](https://engineering-leadership.hinshelwood.com/videos/focusing-beyond-agile-building-true-capability-in-organizations/): Focusing on "Agile" as a label misses the real goal: building genuine capability, maximising value, and enhancing effectiveness in organisations. Many teams struggle because Product Owners and Scrum Masters are hired for their titles rather than their skills, leading to "backlog barons" and "Scrum stumblers" who lack expertise or a learning mindset. True capability grows when organisations hire and promote those who demonstrate potential, context-specific leadership, and a commitment to continuous learning—such as business analysts or testers who organically become respected Scrum Masters within the team. Scrum Masters do not need to be coders, but they must understand the principles and context of their teams to enable success. By hiring for competence, promoting from within, and valuing learning, organisations create environments that drive real value and adaptability.
- [Agile is Not New: A Journey Back to the Basics](https://engineering-leadership.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/): Agile is not a new trend, but a return to how work was done before mass production: through personal connection, empathy, and adaptation, like a local cobbler making shoes for each customer. Industrial-era efficiency and Taylorist thinking eroded this human connection, leading to rigid work environments. Agile principles resurfaced in the 1990s as a response to excessive waste, complexity, and demotivation in failing software projects known as "Death Marches." Despite widespread adoption, many Agile efforts fall short due to a lack of competence in key roles, resulting in high costs and little impact. A reset is emerging where organisations demand true value, focus on real skills, and return to pragmatic, adaptive, and people-centred Agile practices.
- [How to Achieve Predictability in Business through Agile Principles](https://engineering-leadership.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/): Predictability is essential for businesses aiming to consistently achieve goals, but it is often challenged by uncontrollable factors like market volatility as well as controllable issues such as unclear goals and operational inefficiencies. Defining and optimising internal systems, alongside aligning teams around clear objectives, improves consistency and performance. Agile methodologies enable predictability by promoting adaptable planning, team empowerment, and principles over rigid rules; for example, Microsoft plans 18 months ahead in flexible cycles and rewards staff based on customer usage, not just sales. There is no one-size-fits-all solution; businesses gain the most by tailoring agile practices to their unique context and fostering collaboration both internally and with customers. Ultimately, a commitment to continuous improvement and bespoke processes leads to greater predictability, competitive advantage, and long-term resilience.
- [Navigating Complexity: How to Foster Agility and Innovation in Business Decision-Making](https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-how-to-foster-agility-and-innovation-in-business-decision-making/): There are no universal rules for making good business decisions in complex environments, so teams must focus on adaptability, creativity, and continuous learning to stay competitive. Relying on standard tools or processes can lead to bureaucracy and stifle innovation, so regularly reassess what adds value and be ready to change approaches as needed. Encourage a culture that questions the status quo and adapts quickly to new information or challenges.
- [Mastering Evidence-Based Management for Agile Success](https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/): Evidence-Based Management (EBM) uses data-driven decisions to ensure teams deliver real value to customers while staying competitive and adaptable. EBM focuses on four key value areas: current value delivered to customers, unrealised value in potential improvements, ability to innovate, and time to market. Gathering data—like customer satisfaction surveys, innovation rates, technical debt tracking, and telemetry—enables teams to spot trends and prioritise actions. A specific example details reducing time to market by 40 percent through continuous integration. Data should inform, not dictate, decisions, supporting both rapid adjustment and long-term improvement.
- [Advanced PSM II Immersive Learning Classes](https://engineering-leadership.hinshelwood.com/videos/advanced-psm-ii-immersive-learning-classes/): If you want your Scrum Masters to deliver better results, consider a private Advanced Professional Scrum Master immersive learning class. This training can help improve team performance and outcomes. Visit the provided link to learn more and take action.
- [Mastering the Agile Balance: Navigating Flexibility and Inflexibility for Project Success](https://engineering-leadership.hinshelwood.com/videos/mastering-the-agile-balance-navigating-flexibility-and-inflexibility-for-project-success/): 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.
- [Mastering Cloud Migration: How to Leverage Microsoft’s Tool for a Seamless Transition](https://engineering-leadership.hinshelwood.com/videos/mastering-cloud-migration-how-to-leverage-microsoft-s-tool-for-a-seamless-transition/): Using Microsoft’s migration tool helps identify and address potential issues with your systems and customisations before moving to the cloud, reducing post-migration problems. Review all customisations for compatibility, plan necessary rewrites, and track tasks to ensure nothing is missed. Proactively using these steps will make your cloud migration smoother and more reliable.
- [Evidence-Based Management: The Four Key Value Areas in Scrum](https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/): Evidence-based management in Scrum relies on four key value areas to ensure decisions are guided by real data and offer a holistic system view. These areas are current value, unrealised value, ability to innovate, and time to market. Measuring telemetry data and customer satisfaction scores gives insight into current value, while analysing backlogs and market gaps identifies unrealised value, much like how launching a new TV series taps new audiences more effectively than adding to an existing one. Organisational capability is tracked through metrics such as technical debt ratio and cycle time, with examples like Facebook’s 12.5-minute code-to-production cycle highlighting the impact of operational efficiency. Balancing these metrics enables teams to stay innovative while maintaining stability, supporting sustainable product development and more effective, data-driven decisions.
- [Mastering Outcomes: How Evidence-Based Management Transforms Your Project Success](https://engineering-leadership.hinshelwood.com/videos/mastering-outcomes-how-evidence-based-management-transforms-your-project-success/): Defining clear, measurable outcomes and using both leading and lagging metrics are essential for project success. Evidence-based management helps teams make informed decisions by consistently collecting and analyzing data, then iterating based on insights. Development managers should focus on setting SMART goals, tracking the right metrics, and using data to guide continuous improvement.
- [Understanding the Difference: Traditional Management vs. Evidence-Based Management](https://engineering-leadership.hinshelwood.com/videos/understanding-the-difference-traditional-management-vs-evidence-based-management/): Traditional management relies on experience, authority, and top-down decisions, often basing choices on intuition or hierarchy instead of data. Evidence-based management shifts this mindset, requiring managers to collect and analyse data, validate outcomes, and focus on metrics that reflect true organisational progress rather than vanity metrics like story points or velocity. An example illustrates how focusing only on velocity can look impressive but fail to ensure a product is delivering real value, much like judging a race by speed instead of direction. Adopting evidence-based management takes time and persistence but leads to stronger outcomes, clearer problem detection, and better alignment with organisational goals. This approach encourages asking “why” before deciding and demands constant learning and adjustment to drive meaningful improvement.
- [Unlocking Team Potential: How Measurement Influences Engagement and Collaboration](https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-how-measurement-influences-engagement-and-collaboration/): How you measure people shapes their behaviour, so focusing on individual output can reduce collaboration and engagement. Aligning metrics with team goals, encouraging open discussion about measures, and rewarding collective outcomes can boost teamwork and morale. Review your current metrics to ensure they promote the behaviours you want to see in your teams.
- [Mastering Evidence-Based Management in Agile: Inform, Don’t Control](https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/): Evidence-Based Management (EBM) is about using data to inform decisions and understand team behaviours, rather than letting numbers dictate every move. The metrics chosen directly influence how teams act and respond, so clearly define the outcomes you want, then select both leading and lagging indicators to measure progress. For example, tracking the number of live site incidents lasting more than three sprints highlights where issues may persist and when to dig deeper into underlying causes. Data should prompt conversations and understanding, not rigid control, since external dependencies and context often affect results. The ultimate aim is to use data as a guide, aligning strategic goals with team actions and focusing on meaningful value delivery.
- [Seamless Migration to Azure DevOps: Unlocking Enhanced Collaboration and Productivity](https://engineering-leadership.hinshelwood.com/videos/seamless-migration-to-azure-devops-unlocking-enhanced-collaboration-and-productivity/): Migrating to Azure DevOps can boost your team's collaboration and productivity by centralising project management and scaling with your needs. You can choose between self-service migration tools or a managed import service, both designed to ensure a smooth and accurate transition. Careful planning and assessment are essential for a successful migration, so consider expert support to avoid common pitfalls and maximise the benefits.
- [Empowering Employees: The Crucial Link Between Financial Awareness and Motivation](https://engineering-leadership.hinshelwood.com/videos/empowering-employees-the-crucial-link-between-financial-awareness-and-motivation/): Employees often lack awareness of the financial impact of their work, which can lead to missed opportunities and poor decisions. Promoting financial literacy and open discussions about costs helps teams make better choices, increases motivation, and drives accountability. Development managers should actively foster financial awareness to empower teams and improve business outcomes.
- [The Importance of Validation in Product Development: A Strategic Approach](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/): Prioritising sales-driven features in product development can lead to product fragmentation, hidden support costs, and a misalignment between short-term deals and long-term value. For example, Microsoft improved outcomes by shifting Azure sales incentives from hours sold to actual customer usage, which aligned sales goals with customer value. Adopting a hypothesis-driven approach, where each feature’s value is defined, measured, and validated with the right telemetry, ensures that development effort is invested wisely. Only 35 percent of software features are typically used, so rigorous validation reduces wasted effort and keeps the product aligned with user needs. Product managers should use data to inform decisions, ensuring features support both the product’s vision and customer value.
- [Boosting Team Morale and Engagement Through Effective Mentorship Programs](https://engineering-leadership.hinshelwood.com/videos/boosting-team-morale-and-engagement-through-effective-mentorship-programs/): Team morale has a direct impact on engagement and the success of an organisation, with unhappy or disengaged teams delivering lower quality work and collaborating less effectively. Intrinsic motivation, driven by autonomy, mastery, and purpose, is essential for deep engagement and cannot be replaced by salary alone. A 10-week mentorship programme for product managers at a UK company led to unexpectedly high excitement and sustained discussion—even at dinner with the CEO—prompting expansion of the approach to engineering teams. These long-term mentorships delivered increased collaboration, enhanced problem-solving, and stronger alignment with business goals, with visible improvements to product delivery. Unlike brief training sessions, extended programmes provide continuous engagement, actionable outcomes, and real-world application, making them far more effective at driving lasting organisational change.
- [Transform Your Product Development: Unlock User Value, Reduce Waste, and Enhance Collaboration with Structured Learning](https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unlock-user-value-reduce-waste-and-enhance-collaboration-with-structured-learning/): A structured learning course in product development can help your teams better understand user needs through experimentation, reduce waste by making evidence-based decisions, and improve collaboration with stakeholders using data-driven discussions. The course also encourages creative problem-solving and provides practical tools you can apply immediately. Consider investing in this training to boost user value, efficiency, and team alignment.
- [Understanding Product Discovery: Why It Matters More Than Ever](https://engineering-leadership.hinshelwood.com/videos/understanding-product-discovery-why-it-matters-more-than-ever/): Product Discovery is the intentional process of identifying how to make a product more valuable and appealing, going beyond routine backlog refinement to address both known needs and unknown opportunities. It involves strategic planning at both the organisational and team levels, as shown by Microsoft’s Azure DevOps team, which aligned over 90 teams through a shared vision while each engaged in its own discovery work. A key example is Microsoft’s Creators Update, where the pressure levels of digital pens were increased from 255 to 1024 to better serve creative users, illustrating how cross-team coordination and ongoing feedback drive meaningful product improvements. Product Discovery delivers value by aligning the whole organisation, enabling more innovative solutions through broader participation, and ensuring that product investments lead to measurable outcomes. Consistent and deliberate focus on discovery is essential for achieving a significant return on development efforts.
- [The Power of Kaizen: Continuous Improvement in Scrum and Beyond](https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/): Kaizen, meaning continuous improvement, is a principle that encourages making small, incremental changes to processes, which over time lead to significant results. In Scrum, Kaizen fits naturally into Sprint Retrospectives, where teams reflect and identify actionable improvements for the next sprint. One team improved collaboration between developers and testers by simplifying handoffs, leading to fewer bugs and shorter cycle times. Practicing Kaizen involves starting with small changes, measuring their impact, fostering a culture of improvement, and staying adaptable. Committing to ongoing, step-by-step improvement is positioned as the key to success in Scrum and beyond.
- [Navigating DevOps: Crafting Unique Solutions for Unique Organizations](https://engineering-leadership.hinshelwood.com/videos/navigating-devops-crafting-unique-solutions-for-unique-organizations/): DevOps success depends on recognising that every organisation faces unique challenges, so no single approach fits all. The most effective DevOps strategies are those adapted to a team’s specific context, sometimes requiring external expertise to bring new perspectives and solutions. For instance, a team that initially resisted outside help found that an external expert not only solved tough problems but also inspired innovation and direction within the group. Sustained progress relies on ongoing improvement, long-term engagement, and a tailored philosophy that grows with the organisation. The key is to embrace your organisation’s uniqueness, stay flexible, and continue learning and refining your approach.
- [The Limits of Self-Taught Learning: Why External Perspectives Matter](https://engineering-leadership.hinshelwood.com/videos/the-limits-of-self-taught-learning-why-external-perspectives-matter/): Self-taught learning is common in software development, but it comes with limitations, as engineers often stop searching for better solutions once they find one that works—like stopping the search after finding lost keys, even though more keys may be hidden. Most engineers lack formal training, which narrows their experience and restricts exposure to alternative methods. Bringing in external expertise provides fresh perspectives, illuminates hidden problems, and introduces new tools or approaches that teams might not find on their own. This outside guidance helps align progress with organisational goals and ensures institutional knowledge grows in the right direction. Balancing internal learning with external guidance enables teams to innovate and achieve more effective long-term outcomes.
- [The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps](https://engineering-leadership.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/): Organisations often seek DevOps consulting when existing problems with technical debt and complexity become unmanageable. In one case, a $50,000-per-licence product was managed by 90 teams in 13 locations, requiring 11,000 daily builds and massive workstations just to function. Years of integrating acquired technologies without proper refactoring had created layers of legacy debt, which made development slow and chaotic. By consolidating source control and prioritising continual refactoring, outcomes improved: build times shortened, delivery of features accelerated, and developer satisfaction increased. Real DevOps transformation demands patient simplification and ownership from teams themselves, not just external fixes.
- [The Common Challenges of Adopting DevOps Practices](https://engineering-leadership.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/): Adopting DevOps presents organisations with major challenges, the most common being "regression," where progress is often met with unexpected setbacks. Unlike the old waterfall model, DevOps demands rapid delivery, continuous risk management, and a strong focus on closing feedback loops. The only true validation of software is in production, as illustrated by Microsoft's investment in user studies for Windows 8 that failed to guarantee success until the product was in users' hands. In this fast-paced environment, gathering and acting on immediate feedback is crucial, and managing risk means adapting quickly with every release. Embracing this mindset allows teams to achieve higher quality, flexibility, and continuous improvement in their products.
- [Mastering Assumptions: Unlocking Success in Product Development Through Hypothesis-Driven Strategies](https://engineering-leadership.hinshelwood.com/videos/mastering-assumptions-unlocking-success-in-product-development-through-hypothesis-driven-strategies/): Success in product development depends on identifying, prioritising, and validating assumptions through structured hypotheses and targeted experiments. Focusing on the most critical assumptions, using data-driven testing, and avoiding attachment to unproven ideas leads to better decision-making and outcomes. Development managers should foster a culture of learning and adaptability by encouraging teams to challenge assumptions and iterate based on evidence.
- [Unlocking Continuous Improvement: How Metrics and Visualisation Drive Workflow Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/): Continuous improvement relies on using the right metrics and clear visual tools to identify patterns, increase transparency, and drive meaningful workflow changes. Teams should focus on measuring what truly matters and ensure their visualisations support understanding and collaboration. Regularly reviewing and adjusting processes based on these insights is essential for ongoing success.
- [Transform Your Team's Efficiency: The Three Core Principles of Caman Workflow Management](https://engineering-leadership.hinshelwood.com/videos/transform-your-teams-efficiency-the-three-core-principles-of-caman-workflow-management/): Caman workflow management focuses on three principles: clearly defining and visualising your team's workflow to improve understanding and spot bottlenecks, actively managing tasks through regular check-ins and prioritisation, and continuously improving processes with feedback and experimentation. Applying these principles can boost team efficiency, collaboration, and adaptability. Consider mapping your workflow and setting up regular reviews to start seeing immediate benefits.
- [DevOps: Elevating Your Organization’s Performance Through Bespoke Solutions](https://engineering-leadership.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/): DevOps must be tailored to each organisation’s unique needs, starting with a clear understanding of current practices through a State of DevOps Report. Evaluating areas like release processes, tooling, and on-the-ground workflows exposes inefficiencies, such as one case where 13 different source control systems were used for a single product. Streamlining tools and automating processes, along with educating teams about compliance myths, enables more frequent, higher-quality deliveries without sacrificing regulatory requirements. Empowering teams to take ownership across the software lifecycle fosters continuous improvement, while controlled, strategic deployments—deploying to a small group before full rollout and avoiding Friday releases—minimise risk and ensure stability. By focusing on assessment, streamlining, and team ownership, organisations can achieve efficient, compliant, and effective DevOps outcomes.
- [Mastering Your Kanban Board: A Practical Guide to Visualising and Optimising Your Workflow](https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-and-optimising-your-workflow/): A Kanban board should accurately reflect your real workflow, not an idealised version, so regularly review and adapt its columns to match how work actually moves through your team. Involve your team in these updates to spot bottlenecks and improve efficiency. The key takeaway is to use your board as a tool for ongoing improvement rather than aiming for perfection.
- [Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow](https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/): Using clear metrics and visual tools helps teams identify improvement areas, increase transparency, and make better decisions. Regularly reviewing processes, experimenting with small changes, and focusing on relevant, actionable data are key to ongoing improvement. Development managers should ensure their teams use these practices to drive meaningful and continuous workflow enhancements.
- [Harnessing Evidence-Based Management: Transform Your Decision-Making with Data-Driven Insights](https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/): Evidence-based management helps you make better decisions by using data to inform, not control, your actions and team behaviours. Focus on choosing the right metrics that align with your business goals, understand the context behind the numbers, and engage with teams to uncover root causes. Use data as a guide for continuous improvement and be ready to adapt your strategies as new insights emerge.
- [Embrace Kaizen: Unlocking Continuous Improvement for Personal and Team Success](https://engineering-leadership.hinshelwood.com/videos/embrace-kaizen-unlocking-continuous-improvement-for-personal-and-team-success/): Kaizen is a philosophy of making small, ongoing improvements that can lead to significant gains in team performance, collaboration, and personal growth. By regularly observing, measuring, and refining processes, teams can boost productivity and quality while fostering a culture where everyone feels empowered to suggest changes. Development managers should encourage open communication, celebrate small wins, and be patient as continuous improvement is a long-term journey.
- [Unpacking Assumptions: How to Elevate Your Product Development Beyond the Feature Factory](https://engineering-leadership.hinshelwood.com/videos/unpacking-assumptions-how-to-elevate-your-product-development-beyond-the-feature-factory/): Many teams focus on delivering features quickly but often overlook the assumptions behind what users truly need, leading to wasted effort and misaligned products. The PPD V course helps product teams identify and challenge these assumptions through structured discovery, experimentation, and validation, fostering better collaboration and evidence-based decisions. Consider investing in approaches that prioritise learning and user value over simply shipping features.
- [Unlocking the Power of Caman: Why It’s the Perfect Companion to Scrum for Process Optimisation](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/): Caman is a strategy that complements Scrum by increasing transparency and providing deeper insights into workflows, helping teams identify bottlenecks and optimise processes. It is universally applicable across different systems and industries, not just software development. Development managers should use Caman alongside Scrum by mapping processes, involving teams in discussions, and iterating improvements to enhance value delivery.
- [Unlocking the Power of Immersive Learning for Product Management](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-for-product-management/): Immersive learning is a holistic approach that integrates extended learning periods, practical application, and outcome-based assignments to help product managers achieve real organisational change. Rather than relying on surface-level metrics such as velocity or story points, participants focus on identifying and using evidence-based metrics that genuinely reflect value delivery. In one programme for a Sri Lankan company, participants analysed their current metrics and sparked in-depth conversations within teams and with management, challenging existing assumptions and exploring potential improvements. Reflective sessions are used to share experiences, solve problems, and encourage continuous improvement, making each assignment a catalyst for sustained organisational growth. While resistance and challenges are common, the immersive approach emphasises persistence and adaptability, resulting in long-term transformation across teams.
- [Transform Your Product Development: Unleash the Power of Experimentation and Collaboration](https://engineering-leadership.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/): Maximise user value and ROI in product development by adopting deliberate experimentation, focusing on stakeholder collaboration, and embracing agile simplicity. Gain deeper insights into user needs through targeted experiments and evidence-based decisions, as shown when feature cuts of 30 percent freed resources for customer satisfaction gains. Streamlining processes and problem-focused thinking help unlock creativity, reduce waste, and enable quicker iterations, exemplified by a 25 percent reduction in time-to-market that beat competitors. Data-driven conversations build stakeholder trust, turning resistance into alignment. Practical tools and fresh perspectives make these improvements actionable from day one.
- [Mastering Product Development: From Assumptions to Hypotheses](https://engineering-leadership.hinshelwood.com/videos/mastering-product-development-from-assumptions-to-hypotheses/): Assumptions are present throughout every stage of product development, subtly shaping decisions about new products, future planning, and backlog items. Recognising these assumptions is critical, followed by prioritising which ones could severely impact outcomes if wrong and focusing efforts on validating them. The course teaches how to turn key assumptions into testable hypotheses, such as “If we add feature X, user engagement will increase by 20%,” and stresses the need to balance the desired confidence from experiments with the costs involved. Emphasis is placed on using data and critical thinking, not emotional attachment, to guide product decisions and responses to customer feedback. By mastering this structured approach, teams can navigate uncertainty, adapt quickly, and base strategic choices on evidence rather than guesswork.
- [Unlocking User Insights: The Key to Meaningful Software Development](https://engineering-leadership.hinshelwood.com/videos/unlocking-user-insights-the-key-to-meaningful-software-development/): To deliver real value, development managers need to go beyond what users say and use data to understand their true needs, avoid copying competitors without clear alignment to user goals, and foster strong collaboration with stakeholders. Focus on evidence-based decisions and ongoing engagement to ensure your team builds solutions that genuinely matter. Make it a priority to regularly question assumptions and validate user needs with data and stakeholder input.
- [Unlocking the Power of Assumptions in Product Development: Why the PPDV Course is a Game-Changer](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-assumptions-in-product-development-why-the-ppdv-course-is-a-game-changer/): Building products is about more than just delivering features; real value comes from solving the right problems, which demands challenging and validating assumptions throughout the product development process. Unconscious assumptions often cause teams to fall into the "Feature Factory" trap, where stakeholder-driven demands, insufficient understanding of user needs, and misaligned metrics lead to features with little real impact. The PPDV course helps teams avoid these pitfalls by guiding them through an end-to-end empirical cycle of Discovery, Delivery, and Validation, reinforced by a hands-on case study. Participants learn to consciously surface and test their assumptions, create a culture of experimentation, and base decisions on evidence. This approach empowers teams to innovate purposefully and continuously improve, ensuring their work truly meets user needs.
- [The Strategic Imperative: Empowering Teams with Vision, Goals, and Direction](https://engineering-leadership.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/): Teams often work hard without understanding their organisation’s value, direction, or goals, leading to wasted effort and frustration. Like being dropped in a wide-open field with no map or compass, over 90% of teams consulted lack clarity on what they are trying to achieve or how their work connects to business strategy. Clear vision and well-articulated goals act as a map, while evidence-based management functions as a compass, enabling teams to measure progress and stay aligned. Rigid procedures hinder adaptability in complex environments; intent-based leadership empowers teams to make informed, independent decisions that support the wider strategy. Building product ownership capabilities, fostering empathy, and engaging everyone with the organisation’s vision help teams move in the right direction and create meaningful impact.
- [Understanding the Power of Kanban in Scrum](https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/): Kanban is not an alternative to Scrum but a strategy that complements and enhances any workflow, including Scrum. By introducing a Kanban board, teams can visualise their work, set limits on work in progress, and identify bottlenecks, which leads to greater transparency and more effective sprint management. In practice, combining Kanban with Scrum allows teams to consistently meet goals; for example, one team struggling with missed sprints began hitting their targets after integrating Kanban to visualise their workflow and limit tasks in progress. Kanban promotes ways to improve flow, encourage continuous improvement, and support better decision-making and collaboration across any type of team. Teams are encouraged to experiment with both approaches together to experience the benefits firsthand.
- [Detecting Agile BS: Lessons from the Department of Defense](https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/): Implementing Agile development practices is not enough to achieve true organisational agility if the surrounding processes remain slow or bureaucratic. True agility requires a fully integrated ecosystem that enables continuous delivery, removing manual handoffs and unnecessary steps like User Acceptance Testing when consistent quality is achieved. High product quality, built in from the start, should make additional manual checks redundant, as seen in a team developing firmware for pacemakers where rigorous external tests were always expected to succeed. The Department of Defense’s six-question litmus test helps assess whether your organisation’s Agile practices are genuinely end-to-end or merely a facade. Regular self-assessment, automation, and eliminating bureaucratic barriers are essential for moving closer to authentic, sustainable agility.
- [Product Ownership vs. Product Management: Busting the Myth That They're Separate Roles](https://engineering-leadership.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-theyre-separate-roles/): Product ownership and product management are not distinct roles; effective product ownership is actually a focused form of product management within the Scrum framework. The product owner's core accountability is to maximise value delivered by the Scrum team, rather than being distracted by unrelated administrative tasks. As organisations move from long-term delivery cycles to shorter, iterative ones, understanding and delivering true value—not just shipping features—becomes essential. Scrum highlights organisational strengths and weaknesses in product management, acting as a mirror; if the product owner cannot deliver value, deeper organisational issues may exist. In volatile markets, the product owner’s ability to continually reassess and adapt ensures products remain relevant and aligned with strategic goals.
- [Navigating the Complex World of Azure DevOps Data Migration](https://engineering-leadership.hinshelwood.com/videos/navigating-the-complex-world-of-azure-devops-data-migration/): Migrating to Azure DevOps is complex, particularly when dealing with legacy systems like Visual SourceSafe or older TFS versions. The order of migration steps is critical; for example, importing historical Visual SourceSafe data must happen before upgrading TFS to avoid losing access, since imports are only supported up to TFS 2015. Identity alignment is a key challenge—if user accounts are not matched correctly, users may end up with duplicate identities and lose access to their work, as seen when a migration from a workgroup to domain environment broke assignment links. Database size and cleanliness matter, so cleaning obsolete data is necessary before moving to Azure DevOps, which imposes size limits. Reliable migration requires following Microsoft’s backup procedures and marking transaction logs across all databases, since standard SQL Server backups can leave TFS migrations incomplete and hamper disaster recovery. With careful planning and attention to detail in these areas, migrations usually succeed, but mistakes in any critical step can cause major setbacks.
- [Mastering the Migration: Seamlessly Transitioning from TFS to Azure DevOps](https://engineering-leadership.hinshelwood.com/videos/mastering-the-migration-seamlessly-transitioning-from-tfs-to-azure-devops/): Migrating from Team Foundation Server (TFS) to Azure DevOps brings significant benefits such as enhanced collaboration, cloud capabilities, and continuous updates, but the process can be complex, especially with older TFS versions that have custom configurations like increased max attachment sizes. Migration requires careful preparation, including updating TFS, running validation tools, and resolving issues such as misaligned accounts that can prevent users from accessing repositories post-migration. There are two main migration strategies: targeted migration of specific components using Azure DevOps Migration Tools, or a comprehensive managed import of the entire TFS environment. Post-migration testing is crucial, as custom workflows or permissions may not transition properly and can disrupt development if not identified early. Leveraging the right tools and expert support ensures a smooth, efficient migration that safeguards operations and project continuity.
- [Mastering Azure DevOps Migration: Navigating Challenges, Solutions, and Best Practices](https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-migration-navigating-challenges-solutions-and-best-practices/): Migrating to Azure DevOps offers companies a modern, cloud-based platform with features like automatic updates, built-in disaster recovery, and scalability, all at affordable pricing from $4 per user per month. Common reasons for migration include splitting or consolidating projects, upgrading “crusty and old” servers, and complying with organisational changes. Migrations are often complex due to legacy systems, custom code, and resistance to change, but thorough planning, clear communication, and rigorous testing help overcome these challenges. Specific scenarios include moving from Team Foundation Server (TFS) to Git, as well as less typical moves like GitHub to TFS. Leveraging experienced professionals ensures a smooth transition and helps align migration outcomes with business needs.
- [The Evolution of My Journey with Azure DevOps: Lessons and Insights](https://engineering-leadership.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/): Azure DevOps has evolved from its origins as Team Foundation Server, consistently aiming to help teams improve by providing powerful tools. Real-world experience with large-scale migrations, such as moving 2.7 terabytes of data for Slumber, highlights both the capabilities and complexities of the platform. Migrating to Azure DevOps requires careful assessment, choosing between Microsoft’s built-in tools for straightforward cases or custom solutions for intricate needs like selective migration or splitting projects. PowerShell prototyping and custom adapters have proven essential for handling unique requirements. Upskilling teams and expert support are key to leveraging Azure DevOps’ full potential, especially in complex or regulated environments.
- [Is Your Project Ecosystem Truly Agile?](https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/): Agile success depends on more than just fast-moving development teams; without streamlined deployment and delivery, projects remain slow and bureaucratic. Manual approvals and linear processes create delays, frustrate teams, and diminish the value delivered to stakeholders as needs shift over time. Automation, especially with CI/CD pipelines, removes bottlenecks and shortens deployment from days to hours, as seen when a Scrum team adopted automation and boosted morale and customer impact. Short feedback loops and frequent releases are essential to keep products aligned with stakeholder expectations and maintain momentum. Focusing on end-to-end automation, quick feedback, and consistent stakeholder engagement transforms your ecosystem into one that delivers maximum value quickly and reliably.
- [Maximizing Transparency and Improvement in Software Engineering with Kanban](https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/): Kanban unlocks transparency in software engineering teams, allowing them to clearly see their workflows and identify hidden complexities that can slow progress. By visualising work on a Kanban board, teams can spot bottlenecks—such as discovering that code reviews were delaying delivery in a real project—and use key metrics like lead time, cycle time, and throughput to guide improvement. With clear work-in-progress limits and explicit workflow policies, Kanban empowers teams to make data-driven decisions and adapt quickly. This transparency fosters continuous delivery and a culture of ongoing improvement, making changes based on real insights rather than guesswork.
- [Empowering Teams to Tailor Their Processes: A Path to True Agility](https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/): True agility requires empowering teams to adapt their processes based on their unique challenges and what they learn, rather than enforcing rigid, one-size-fits-all standards. Imposing company-wide procedures can create waste and hinder innovation, as shown by the Merrill Lynch example where a small CRM project for 20 salespeople faced $20,000 pentest costs and $33,000 monthly infrastructure overhead due to rules designed for high-risk systems. Empowered teams can better maximise value, minimise waste, and foster innovation. Key signals of real agility include support for continuous delivery, a culture of experimentation, and a focus on delivering value over simply following process. Organisations should reflect on whether they truly allow teams the freedom to adapt in pursuit of better outcomes.
- [The Synergy Between Product Management and Product Development in Agile Environments](https://engineering-leadership.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/): Product Management and Product Development are distinct but closely linked, with Product Management defining what to build by focusing on market value, strategy, and vision, and Product Development focusing on how to build it through innovation, fast delivery, and engineering excellence. These functions must overlap and collaborate continuously, exchanging feedback and data to refine both direction and execution. A core insight is that maintaining user engagement and growth requires balancing support for existing features with bold moves into new markets, much like Netflix continually developing new content to sustain interest. Agile processes, rapid feedback loops, and experimentation drive a continuous cycle of improvement, ensuring products remain valuable in fast-changing markets. Success depends on integrating strategic leadership with robust delivery, creating a synergy that maximises current and future value.
- [Empowering Teams to Maximize Value and Return on Investment](https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/): Empowering Agile teams to adapt their processes is crucial for maximising value and return on investment. Teams that can tailor their workflows to their unique challenges deliver better outcomes than those forced into rigid, one-size-fits-all approaches. For example, two teams tackling similar projects had vastly different results: the team allowed to change its methods delivered higher-quality results on time, while the team that followed a prescribed process struggled with delays and frustration. Building a culture of continuous improvement, supporting experimentation, and encouraging knowledge sharing across teams enables this empowerment. Leaders are encouraged to trust teams’ decisions, support change, and focus on value delivered rather than strict process adherence.
- [Why Limiting Work in Progress is Key to Success in Kanban](https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/): Limiting work in progress (WIP) is essential for effective Kanban, enabling teams to control their workflow, focus on delivering value, and maintain a sustainable pace. Too much WIP leads to task switching, hidden bottlenecks, slower delivery, and reduced quality, as seen when one team took on every request and ended up overwhelmed with customer satisfaction declining. By introducing clear WIP limits, teams quickly improve flow, boost quality, and make bottlenecks visible and actionable. Setting WIP limits should be based on team capacity, regularly monitored, and adjusted with the team's involvement to ensure buy-in and encourage continuous improvement. Ultimately, limiting WIP turns Kanban from a visual aid into a powerful tool for consistent, high-quality delivery.
- [Empowering Agile Teams: The Critical Role of User Feedback in Requirement Changes](https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/): True Agile practice depends on empowering teams to change requirements in response to real user feedback, not just collecting feedback. Rigid contracts, locked-in requirements, or complex change request systems often block necessary pivots, leaving teams unable to respond when a significant business decision changes what is needed. A striking example is a B2B team with a three-week cadence that, upon learning mid-project that part of their product no longer fit user needs, was empowered to reprioritise and save time and money. Agile organisations need simple change processes, contractual flexibility, and a culture of trust so teams are not forced to deliver features that are suddenly irrelevant. Real agility is measured by a team's ability to adapt requirements quickly and autonomously as the market shifts.
- [The Evolution of Product Management in the Agile Era](https://engineering-leadership.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/): Maximising business value remains the goal of product management, but Agile methods have transformed how it is achieved. Traditionally, teams like Azure DevOps operated on two-year release cycles, which delayed feedback, increased the risk of building irrelevant features, and required complex change request systems. With Agile, teams shifted to three-week delivery cycles, enabling rapid feedback, more frequent delivery of value, and the elimination of cumbersome processes. Building quality in from the start, using practices like a strong Definition of Done, continuous integration, and continuous delivery, reduces production issues. This agility offers a strategic advantage by making teams more responsive to market shifts, enhancing customer satisfaction, and improving return on investment.
- [Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile](https://engineering-leadership.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/): Agility means empowering teams to adapt requirements in response to user feedback, rather than sticking rigidly to an initial plan. Product teams, when deeply engaged, gain unique insights and can suggest valuable changes, such as when one team discarded a feature after realising through user feedback that it added little value, ultimately leading to a stronger product. Maintaining an agile backlog requires constant updates, including adding, reprioritising, or deleting items based on new insights or shifting market needs. Deleting unnecessary requirements prevents feature creep, maximises resources, and ensures the product stays aligned with user needs. True agility relies on valuing team expertise, fostering open communication, and enabling the team to influence how products evolve.
- [Does Your Team Truly Understand Your Product Vision and Goals?](https://engineering-leadership.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/): True agility depends on whether every team member understands and internalises the product vision and strategic goals, and knows how their daily work contributes to them. A simple test is to ask anyone on the team to explain these points; if they cannot, the vision might as well not exist. Lack of shared understanding leads to misaligned decisions, wasted effort, and reduced value for customers, while clarity empowers better decision-making and collaboration. Practical steps like regular vision workshops, visible roadmaps, and leadership Q&A sessions help maintain alignment. The ultimate measure of Agile maturity is whether this connection between vision and daily work is real, not just stated.
- [The Fallacy of Equating Agility with Speed: What Agile Really Means](https://engineering-leadership.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/): Agile is frequently misunderstood as simply making teams work faster, when in fact its true purpose is to help teams spend their time on what matters most. Agility means focusing on high-value tasks, embracing trial and error to identify what truly works, and repeatedly testing ideas, which can take longer up front but leads to better outcomes. For example, Zoom.ai had to pivot from its original AI scheduling tool to become CalendarHero after learning what customers actually valued. Agile exposes unnecessary work and helps teams avoid building the wrong product, unlike fixed methods that risk obsolete or ill-fitting outcomes, as seen in the FBI’s Sentinel project where success came only after Agile adoption refocused efforts on delivering immediate value. Ultimately, Agile is not about speed but about regularly reassessing priorities to ensure the results closely match real user needs.
- [Turning User Feedback into Actionable Work: A Guide to Maximizing Product Value](https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/): Transforming user feedback into actionable work rapidly is central to delivering value in Agile development. True agility means reducing the time it takes to incorporate feedback, sometimes from weeks or months down to within a single Sprint. Regular engagement with users, strict prioritisation, integrating feedback into planning, and using visual feedback boards or KPIs all help close the gap between feedback collection and action. One team improved a retail app by swiftly streamlining the checkout process based on user feedback, which immediately reduced cart abandonment by 25 percent. Continually reviewing and acting on user input keeps your product in sync with user needs and maximises business outcomes.
- [Mastering Your Kanban Board: A Practical Guide to Visualising Workflows for Maximum Efficiency](https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/): A clear and accurate Kanban board is essential for understanding and improving your team'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.
- [Why Cost-Cutting During Recessions Is Counterproductive](https://engineering-leadership.hinshelwood.com/videos/why-cost-cutting-during-recessions-is-counterproductive/): Cutting costs during recessions, especially in areas like agile coaching and training, may seem prudent but often harms long-term organisational health. Companies such as Capital One have eliminated roles like agile coaches in downturns, only to later rehire and realise the loss in effectiveness. Investing in efficiency, productivity, and people during tough times creates a foundation for thriving after recovery, rather than merely surviving. Empowering employees with training budgets and autonomy, as seen in a Spanish company, fosters a resilient culture of continuous learning and experimentation. Prioritising value creation and internal improvement over short-term revenue extraction ensures the business is ready for market surprises and future growth.
- [Empowering Agile Teams: Why Understanding Product Vision is Key to Success](https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-why-understanding-product-vision-is-key-to-success/): Teams that clearly understand the product vision and strategic goals are more aligned, empowered, and able to make decisions that deliver greater value. Regularly communicating the vision, involving the team in its development, and providing context and feedback opportunities foster ownership and agility. Development managers should ensure their teams know and connect with the product vision to maximize effectiveness and adaptability.
- [Mastering Kanban: A Simple Guide to Its Core Principles](https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/): Kanban is a simple yet powerful method for managing workflow that helps teams increase efficiency by making work visible, proactively managing tasks, and focusing on continuous improvement. The three key principles are to define and visualise your workflow, actively manage work items, and continuously improve your process. An example is using a Kanban board with columns like “To Do,” “In Progress,” and “Done” to spot bottlenecks; in one team, introducing a limit on tasks in progress led to a marked boost in delivery speed and quality. Teams are encouraged to regularly review their board, adjust priorities, and make incremental changes. By embracing these principles, teams foster better communication, transparency, and ongoing learning.
- [Detecting Agile BS: Lessons from the US Department of Defense](https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/): Agile practices are often claimed but not truly followed, with many organisations labelling themselves Agile without changing culture or processes. The US Department of Defense created a guide with six questions to help organisations determine if they are genuinely Agile, emphasising points like delivering real working software to users every iteration and regularly releasing to production. True Agile teams act on user feedback, have a clear product vision, are empowered to make decisions, and commit to continuous improvement. Achieving this level of agility is challenging but greatly improves product quality and customer engagement, and no organisation has chosen to revert after reaching it. Honest self-assessment using these questions drives meaningful progress and helps foster a mindset needed for lasting Agile transformation.
- [The Power of Technical Excellence in Agile Development](https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/): Technical excellence is essential in Agile development because it ensures a usable, working product at the end of every iteration, which is key for reducing risk in high-variance environments. Attempting to deliver faster by sacrificing quality results in increased technical debt and makes products harder to maintain. The transformation of the Azure DevOps team at Microsoft is a striking example: after shifting to Agile practices and paying back technical debt, they increased their delivery from 24 to 280 features per year without expanding the team. Establishing a robust Definition of Done, which sets clear standards for quality and usability, is fundamental to achieving technical excellence. Focusing on quality and continuous improvement allows teams to deliver more value, respond quickly to feedback, and innovate, rather than being stuck in firefighting mode.
- [The Importance of Delivering Working Software Every Iteration](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/): Delivering working software to real users every iteration, starting from the very first, is crucial to being truly Agile. Agile's core is in closing feedback loops quickly and engaging directly with customers, which allows teams to validate their assumptions and make course corrections early. Practical actions such as launching a minimal viable product, ruthless prioritisation of user stories, involving stakeholders through regular demos, automating testing and deployment, and holding retrospectives support this approach. A key example is a project where several sprints were spent perfecting a feature that users ultimately found confusing; an earlier release would have surfaced this sooner and saved effort. Early and regular delivery of working software ensures progress, builds trust, and helps deliver genuine value.
- [Understanding Kanban: A Tool for Transparency and Continuous Improvement](https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/): Kanban is a tool for gaining transparency and enabling continuous improvement in any existing workflow, rather than a process or methodology itself. By visualising every stage of your team’s work on a Kanban board—with columns such as To Do, In Progress, Blocked, and Done—teams can easily spot bottlenecks and blocked tasks. Kanban also uses metrics like cycle time and throughput to provide insights into team performance, helping teams address slowdowns and improve over time. For example, one team resolved long delays in their "Review" stage after Kanban revealed the bottleneck, then improved delivery by introducing work-in-progress limits. Starting with a simple board, setting WIP limits, and regularly reviewing metrics fosters clarity and drives steady team growth.
- [Unlocking Naked Agility: How Happy Teams Drive Exceptional Products](https://engineering-leadership.hinshelwood.com/videos/unlocking-naked-agility-how-happy-teams-drive-exceptional-products/): Happy, engaged teams are essential for building exceptional products; when people have autonomy, opportunities for growth, and a clear sense of purpose, their motivation and output improve significantly. Managers should empower decision-making, invest in skill development, and clearly communicate the vision to foster this environment. Prioritising team well-being leads to better products and more satisfied customers, so focus on creating a culture where your teams can thrive.
- [Empowering Your Team: Why Quick Fixes in Agile and DevOps Are a Myth](https://engineering-leadership.hinshelwood.com/videos/empowering-your-team-why-quick-fixes-in-agile-and-devops-are-a-myth/): 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.
- [Transforming Training: The Power of Immersive Learning in Scrum](https://engineering-leadership.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/): Traditional two-day Scrum workshops offer poor retention and limited practical impact, as participants remember little and struggle to apply what they've learned under daily pressures. Immersive learning replaces this with eight half-day sessions, hands-on assignments, and collaborative debriefs that create a compounding knowledge effect and directly address real organisational challenges. This approach mirrors Scrum's iterative cycle: participants learn, apply in their own environments, review as a group, and continuously improve. One team, for example, secured stakeholder buy-in by reframing a difficult change as a small experiment, a tactic learned from another participant. With extended support and peer collaboration over weeks or months, immersive learning delivers deeper understanding, immediate value, and fosters a culture of continuous improvement across organisations.
- [Empowering Teams for Success: The Key to Thriving Product Development](https://engineering-leadership.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/): 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.
- [Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation](https://engineering-leadership.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/): 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.
- [Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management](https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/): 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.
- [Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility](https://engineering-leadership.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/): 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.
- [Mastering Azure DevOps: Avoiding Common Pitfalls for Agile Success](https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/): 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.
- [From Chaos to Clarity: My Journey Through DevOps and the Three Key Challenges to Overcome](https://engineering-leadership.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/): DevOps represents the union of people, processes, and products to enable continuous delivery of value. The three primary challenges in adopting DevOps are shifting culture to prioritise collaboration and automation, integrating tools to optimise deployment pipelines, and fostering continuous learning across teams. Real-world failures, like Knight Capital Group's financial loss from a manual deployment error, highlight the necessity of these changes. Emphasising systems thinking, maximising feedback loops, and encouraging experimentation underpin lasting improvements. Moving from early-day chaos to a mature DevOps approach empowers teams to deliver high-quality products efficiently.
- [Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success](https://engineering-leadership.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/): 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's structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team'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.
- [How Azure DevOps board columns decide your lead time and cycle time](https://engineering-leadership.hinshelwood.com/videos/how-azure-devops-board-columns-decide-your-lead-time-and-cycle-time/): Azure DevOps lets you customise board columns without changing the underlying work item states, so several teams can share a project and still visualise their own workflow. That separation matters because the state boundaries, not the columns, are what start the lead time timer and the cycle time timer. Configuring columns, WIP limits, split doing and done lanes, card style rules and a definition of workflow gives a team a board that matches how it really works. Agree those rules with everyone in the workflow, then refine them as you learn.
- [Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery](https://engineering-leadership.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/): 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.
- [Illuminate Your Workflow: Harnessing Candan Strategies for Continuous Improvement and Transparency](https://engineering-leadership.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/): Adopting a Candan strategy helps teams achieve continuous improvement and greater transparency by using flow metrics to identify workflow issues and inefficiencies. Visualising these metrics enables more informed decisions and motivates action, especially for Scrum teams that lack built-in measurement tools. To maximise benefits, integrate flow metrics into your processes and seek expert support or training if needed.
- [The Importance of Visualizing Your Work in a Kanban Strategy](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/): Visualising work is essential for a successful Kanban or Scrum system because it brings clarity, transparency, and accountability to software teams. Using digital boards in tools like Azure DevOps or Jira lets everyone easily track tasks and see where items are in the workflow. However, without clear team agreements about what goes on the board and how work moves through each stage, teams can become misaligned—like playing a board game without shared rules, leading to confusion. The most effective Kanban systems are defined collaboratively, with documented workflows and a shared "rulebook" for how work should flow. Alignment on these basics matters more than pure optimisation, setting the foundation for better collaboration and measurable improvement.
- [The Key to a Kanban Strategy: Understanding WIP Limits](https://engineering-leadership.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/): A Kanban strategy depends on setting clear Work-In-Progress (WIP) limits at each stage in the workflow, not just overall. WIP limits help avoid bottlenecks by ensuring the team is neither overloaded nor underutilised, aiming for the "Goldilocks zone" where work moves smoothly. The ideal is single-piece flow, but in real projects, teams should experiment with different limits, starting small and adjusting based on feedback and team capacity. Practical tips include beginning with a WIP limit one less than the number of people working on a stage. Visualising and discussing WIP limits leads to better team understanding and improved systems.
- [Mastering Kanban: Creating a Pull-Based System for Workflow Efficiency](https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-creating-a-pull-based-system-for-workflow-efficiency/): Kanban is a pull-based workflow management system that helps teams visualise their process, manage bottlenecks, and improve efficiency. Implementing Kanban means more than just designing workflow columns; teams must also set explicit work-in-progress (WIP) limits and make waiting states visible. The example of a hospital waiting room illustrates how exceeding capacity leads to longer wait times, demonstrating the need to adjust work limits. In Kanban, teams regularly review their boards, pause work when bottlenecks form, and can even shift team members to help clear overloaded stages. Continuous improvement is central, with teams encouraged to analyse constraints and adapt using flow metrics, making Kanban suitable not only as a standalone system but also as a complement to Scrum practices.
- [3 best ways to wreck Kanban. Sweep problems under the rug](https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/): Ignoring problems in your Kanban process leads to bigger issues, workflow blockages, and potential crises like project delays or cost overruns. Teams should regularly identify, visualize, and address problems, foster transparency, and take prompt action to prevent issues from escalating. Make it a priority to surface and resolve problems early to keep your workflow effective and avoid costly setbacks.
- [3 best ways to wreck Kanban. Don't have a working agreement](https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-dont-have-a-working-agreement/): Not having a working agreement causes chaos, misalignment, and inefficiency in teams using Kanban or similar frameworks. Clear agreements on roles, goals, processes, and workflows are essential for team alignment and success. Development managers should ensure their teams regularly create and review working agreements to avoid confusion and improve outcomes.
- [3 best ways to wreck Kanban. Use vanity metrics](https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/): 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.
- [3 Core Practices of Kanban: Improving a Workflow](https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/): 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.
- [Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency](https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/): 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.
- [3 core practices of Kanban. Actively managing work items in a workflow](https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/): 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.
- [My journey with Kanban and why I actively recommend it to clients](https://engineering-leadership.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/): Kanban is a practical strategy for improving workflow and predictability by making work processes more transparent and data-driven, which builds trust and enables better decision-making. Integrating Kanban with Scrum helps teams deliver more consistently and reduces stakeholder uncertainty. Development managers should consider adopting Kanban to optimize team performance and deliver greater value across any context.
- [Overview of the 'scaling with portfolio Kanban' course](https://engineering-leadership.hinshelwood.com/videos/overview-of-the-scaling-with-portfolio-kanban-course/): The "Scaling Portfolio Kanban" course helps development leaders move from team-level to organization-wide workflow management, enabling better visibility, predictability, and value delivery across multiple teams. Key outcomes include improved forecasting, data-driven decision-making, and optimized flow of high-value projects. If your current workflow lacks predictability or efficiency, consider applying these Kanban strategies to drive measurable improvement.
- [Overview of Applying Professional Kanban course](https://engineering-leadership.hinshelwood.com/videos/overview-of-applying-professional-kanban-course/): 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's processes and deliver more value quickly.
- [Overview of 'applying metrics for predictability' Kanban course](https://engineering-leadership.hinshelwood.com/videos/overview-of-applying-metrics-for-predictability-kanban-course/): The "Applying Metrics for Predictability" 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.
- [Overview of 'applying flow metrics for Scrum' course](https://engineering-leadership.hinshelwood.com/videos/overview-of-applying-flow-metrics-for-scrum-course/): The "Applying Flow Metrics for Scrum" 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.
- [How long does it take to transition from project management to Kanban?](https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/): 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.
- [Does Kanban integrate into a Scrum environment?](https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/): 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.
- [Getting started with Kanban](https://engineering-leadership.hinshelwood.com/videos/getting-started-with-kanban/): Kanban helps teams improve workflow and productivity by visualizing work, setting clear processes, and using metrics like cycle time and throughput to drive continuous improvement. Start with a small, willing team, define and visualize your workflow, and use data to identify and address bottlenecks. Begin with a pilot, focus on collaboration and regular feedback, and use metrics to build credibility and guide ongoing enhancements.
- [Why is Kanban becoming increasingly popular in creative industries?](https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-becoming-increasingly-popular-in-creative-industries/): Kanban is becoming popular in creative industries because it offers flexibility, allows teams to start from their current workflow, and supports both individual and team needs. Key benefits include minimizing disruption, enabling continuous improvement through data, and preventing overload with work-in-progress limits. To succeed, document your workflow, set clear limits, and regularly review progress to optimize efficiency.
- [What is Kanban?](https://engineering-leadership.hinshelwood.com/videos/what-is-kanban/): Kanban is a flexible strategy for improving existing workflows by making processes visible, tracking data, and enabling continuous, incremental improvements. Key steps include documenting your current workflow, visualizing work to spot issues, and using metrics to guide changes. Start by mapping your team's process and use the insights to drive efficiency and effectiveness.
- [The Power of Immersive Learning: Bridging Theory and Experience](https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-bridging-theory-and-experience/): Immersive learning for Agile and Scrum goes beyond traditional classroom methods by combining theory with hands-on, practical experience guided by trainers who have real industry expertise. Participants engage in simulated real-world scenarios, tackling challenges like team conflict, sprint planning, and stakeholder engagement and receiving tailored advice and immediate feedback. This approach builds both competence and confidence, enabling learners to apply new skills right away and adapt Scrum practices to their unique organisational contexts. One example saw a struggling team transform and confidently run their own sprints after immersive, scenario-driven sessions. Immersive learning also fosters networking among peers facing similar challenges, creating a valuable ongoing support network.
- [Immersive Learning in Scrum: Why Theory and Experience Must Go Hand in Hand](https://engineering-leadership.hinshelwood.com/videos/immersive-learning-in-scrum-why-theory-and-experience-must-go-hand-in-hand/): Theory and experience must be combined in Scrum training for true learning and continuous improvement. Without theory, experiences lack context and meaning, making it difficult to ask the right questions or replicate success across teams. Immersive learning should be interactive, reflective, and hands-on, creating space for participants to anchor their understanding in Scrum principles such as transparency, inspection, and adaptation. For example, a team struggling with the definition of "Done" found clarity by simulating a Sprint that required them to define "Done" upfront, turning theory into impactful practice. Asking better, theory-rooted questions after each experience enables teams to critically reflect, adapt, and grow.
- [The Power of Peer Feedback in Immersive Learning](https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/): Immersive learning transforms Scrum and Agile training by replacing lectures with hands-on activities that mirror real-world challenges. The peer feedback loop is central, as participants implement assignments in their organisations, then share experiences and insights in structured debriefs where everyone contributes ideas and reflections. These debriefs go beyond reviewing success or failure, fostering collaborative problem-solving and building a shared pool of knowledge rooted in actual practice. Peer feedback provides diverse perspectives and actionable advice, supporting continuous improvement and helping learners retain information and implement Scrum effectively. A trainer facilitates rather than directs, empowering participants to take ownership of their development.
- [The Power of Building Relationships Through Immersive Learning in Scrum](https://engineering-leadership.hinshelwood.com/videos/the-power-of-building-relationships-through-immersive-learning-in-scrum/): Immersive learning in Scrum is about more than just gaining knowledge; it centres on building lasting relationships among learners, which significantly enhances the experience. Engaging over several weeks lets practitioners reflect, apply Scrum practices in real contexts, and develop trust and support within their group. In one memorable cohort, participants from diverse industries began hesitant but ultimately formed connections so strong they continue to collaborate and attend each other's Sprint Reviews years later. These relationships foster diverse perspectives, constructive feedback, and collaborative problem-solving, which are vital for effective Scrum practice and continuous improvement. The network built during immersive learning becomes a valuable long-term asset, supporting professional growth and lifelong learning in Scrum.
- [Unlocking the Power of Immersive Learning in Agile: Overcoming Cognitive Bias](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/): Immersive learning in Agile is vital for overcoming the Dunning-Kruger effect, where practitioners overestimate their knowledge of Scrum and Agile principles. Many experienced team members realise through real-world simulations and hands-on activities that they have gaps, such as never having read the Agile Manifesto or Scrum Guide despite years in the field. Immersive learning continuously challenges assumptions with practical application and constant feedback, fostering humility and genuine growth. Focused effort, regular reflection, and engagement with peers drive real improvement. Embracing failure and staying open to learning by doing are presented as essential to becoming more effective in Agile environments.
- [The Power of Immersive Learning in Agile Training](https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-in-agile-training/): Immersive learning stands out in Agile training by focusing on active participation, real-world application, and continuous feedback, enabling real change rather than passive knowledge transfer. Participants experiment with new ideas, gather feedback, and adjust their approach, creating a cycle that fosters continuous improvement—a core value of Agile. For example, one Scrum Master introduced new sprint planning techniques, iterated based on team feedback, and saw significant improvement after several sprints. Immersive learning builds confidence as learners solve real organisational problems and helps spread a culture of ongoing growth. True Agile transformation happens not by getting it right the first time, but by learning, adapting, and improving together.
- [Unlocking the Power of Immersive Learning in Agile](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile/): Immersive learning transforms Agile adoption by engaging teams in hands-on, experience-based scenarios that mirror real organisational challenges, rather than relying on passive instruction. This approach allows individuals to experiment, reflect, and naturally shift their mental models, moving past rote rituals towards truly living Agile principles. A telling example is a team that only recognised and shed their old, hierarchical habits when they worked through a simulated project reflecting their actual struggles. Immersive learning begins with experience before theory, linking Agile practices directly to day-to-day work and encouraging adaptation through real feedback. Allowing teams to make mistakes and reflect on outcomes leads to lasting, meaningful change in Agile transformation.
- [The Power of Immersive Learning in Scrum Training](https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training/): Immersive learning in Scrum training leads to reduced cognitive load, greater engagement, and higher energy compared to traditional long-form video sessions, which can cause fatigue and low retention. By breaking content into shorter, focused, interactive sessions and using tools like group activities and real-life Scrum scenarios, learners better absorb material and stay motivated. The improvement is clear when switching from 8-hour training days to multiple brief sessions, as participants return more alert and involved. Time for reflection between sessions enhances retention and real-world relevance, making immersive learning a more effective approach for today’s Scrum teams.
- [Why Immersive Learning Keeps Scrum Students Excited and Engaged](https://engineering-leadership.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/): Immersive learning in Scrum sustains high excitement and engagement by turning education into a journey of discovery, rather than simply transferring information. Students explore new topics each session and immediately try techniques, such as experimenting with a new retrospective format with their teams. Spaced, hands-on sessions give time for real-world application and feedback, allowing students to reflect and improve on their experiences week by week. This cycle of practical experimentation, peer feedback, and anticipation keeps learning impactful and lively, making continuous improvement feel like an adventure, not a chore.
- [The Power of Immersive Learning in Scrum Training: Why Less Is More](https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training-why-less-is-more/): Intensive Scrum training often overwhelms students, leaving them drained and struggling to retain knowledge, much like being “hit with a fire hose” of information. Breaking learning into bite-sized, immersive modules allows time for reflection, discussion, and practical application, leading to deeper understanding and higher engagement. One student from a fast-paced industry finished an immersive day saying they felt energised rather than exhausted, sensing everything falling into place. Applying Scrum principles such as iteration, reflection, and adaptation to training fosters better retention and day-to-day use of Scrum in the workplace. Taking breaks, reflecting regularly, and linking theory to real-world examples further enhance learning outcomes.
- [Stop Starting and Start Finishing: The Key to Team Success](https://engineering-leadership.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/): Multitasking reduces productivity, as each additional task in progress causes around a 20 percent productivity loss due to context switching. Teams that juggle multiple priorities tend to deliver less value and experience burnout, inefficiency, and delayed delivery. Scrum mitigates this with a single Product Owner who funnels work and Lean reinforces it by limiting work in progress; both approaches help teams finish tasks instead of constantly starting new ones. Monitoring the gap between work started and finished—for example, using a Cumulative Flow Diagram—helps maintain swift delivery and business value. Focusing on value-based prioritisation and limiting work in progress enables teams to finish more work, deliver faster, and provide stakeholders with predictability and confidence.
- [Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery](https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/): Evidence-Based Management (EBM) provides product owners with a framework to make informed, value-driven decisions using four key metrics: Unrealised Value, Current Value, Ability to Innovate, and Time to Market. By regularly reviewing these metrics, product owners can assess if new features deliver expected results, identify hidden opportunities, and know when to pivot strategies. Involving development teams in metric discussions transforms them from feature builders to product developers invested in success. Regular alignment with stakeholders, backed by EBM data, ensures efforts consistently maximise value and support long-term goals. One concrete example is using EBM metrics to realise when a new feature fails to increase engagement, prompting a strategic shift.
- [The Power of Metrics: Why PAL-EBM is Essential for Your Organization](https://engineering-leadership.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/): Understanding and choosing the right metrics is crucial for leaders who want to guide their organisation toward long-term success. The Professional Agile Leadership - Evidence-Based Management (PAL-EBM) class helps leadership teams see beyond numbers on dashboards, focusing on how metrics influence behaviour and outcomes. Participants learn through real stories, including Microsoft’s widely criticised use of stack ranking, which led to competition and fear rather than collaboration. PAL-EBM stresses the value of transparency and using empirical data for decision-making, helping leaders avoid negative consequences from poorly chosen metrics. Leadership teams often find the class creates space for honest, strategic conversations that lead to more effective and people-focused measurement of success.
- [How Do You Know How Long It Takes to Deliver Value?](https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/): Efficiently delivering value to customers is vital for Agile teams, and measuring how long it takes is essential for business success. Evidence-Based Management highlights Time to Market as a key value area, tracking metrics such as lead time (from request to delivery), cycle time (task completion), time to pivot, time to learn, and time to fix. For example, one Scrum team reduced lead time from two months to three weeks by removing bottlenecks and improving communication. Using these metrics allows better forecasting, decision-making, and continuous improvement. Ultimately, speed matters, but delivering true customer value is the primary goal.
- [Evidence-Based Management: The Key to Agile Success](https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-key-to-agile-success/): Organisations often mistake implementing agile frameworks for achieving business success, but real improvement comes from focusing on measurable business outcomes rather than agile processes alone. Evidence-based management (EBM) allows organisations to adapt and thrive by making data-driven decisions that respond to market changes, as seen in startups that constantly experiment, pivot, and scale using market data. Success hinges on monitoring key metrics beyond just revenue, including unrealised value, ability to innovate, and time to market. Businesses that use EBM restructure leadership, workflows, and decision-making based on concrete evidence. True agility is about adapting quickly and effectively to both risks and opportunities, guided by continuous measurement and strategic use of data.
- [How to Measure Your Organization's Ability to Improve Value Through Innovation](https://engineering-leadership.hinshelwood.com/videos/how-to-measure-your-organizations-ability-to-improve-value-through-innovation/): Organisational capability is defined by the collective skills, processes, and resources that enable goal achievement, with innovation as a critical component. Evidence-based management uses key metrics—such as the number of active branches in software products, technical debt, innovation rate, and complexity overhead—to provide a clear picture of the organisation’s innovation capacity. For example, tracking active branches can signal whether teams are experimenting productively or creating inefficiencies. Setting clear innovation goals, regularly monitoring these metrics, and fostering a culture of continuous improvement helps organisations make better decisions and sustain long-term value delivery through innovation.
- [Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership](https://engineering-leadership.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/): Evidence-based management helps leaders make better decisions by focusing on meaningful metrics that drive real business value, such as current and unrealised value, time to market, and ability to innovate. Regularly reviewing and tailoring these metrics to your organisation enables data-driven strategies and a clear competitive advantage. Consider adopting this approach to move beyond gut feelings and ensure your team delivers measurable results.
- [How to Discover Unrealized Value in Your Product](https://engineering-leadership.hinshelwood.com/videos/how-to-discover-unrealized-value-in-your-product/): Unrealised value in a product is the gap between its current state and its untapped potential based on customer needs, market trends, or business opportunities. Evidence-Based Management (EBM) offers a framework for finding these gaps using metrics like customer satisfaction, market share, churn rate, and innovation. For example, a team used customer surveys and Net Promoter Score to identify usability issues, prioritised user interface improvements in their backlog, and saw a 15% drop in churn and greater user satisfaction. By adding such insights to the product backlog and engaging stakeholders, continuous improvement drives the product closer to its full potential.
- [Addressing Systemic Issues in Agile Organizations](https://engineering-leadership.hinshelwood.com/videos/addressing-systemic-issues-in-agile-organizations/): Most organisations adopting Agile struggle to address the root causes of inefficiency, focusing instead on surface-level rituals like daily stand-ups and sprint planning. Relying on these ceremonies does not lead to real change; meaningful improvement depends on measuring the right outcomes such as ROI, profit per team member, cost to deliver, and time to learn. Addressing tough questions about untapped market opportunities and being ready to pivot are crucial for survival, as shown by the high rate of startup failure. Incremental change is often not enough—sometimes the right move is to “rip off the Band-Aid” and make bold, decisive reorganisations when current systems clearly do not work, even if it is uncomfortable. Agile brings value only when leaders have the courage to confront systemic issues and transform the entire business, not just its processes.
- [How Do You Know the Value Currently Delivered in Your Organization?](https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/): Evidence-Based Management (EBM) helps organisations measure and improve the value they deliver by relying on factual data rather than intuition. Key metrics such as customer satisfaction (like NPS scores and feedback), employee engagement, revenue per employee, product cost ratio, and customer usage index provide concrete ways to evaluate performance. In one transformation project, introducing EBM metrics revealed low product usage despite high customer satisfaction; this insight led to a targeted feature improvement and a subsequent surge in both usage and satisfaction. EBM encourages regular metric review, team involvement, and adapting metrics over time, making evidence central to decision-making and continuous improvement.
- [Unlocking Agile’s Core: Questioning to Create Value](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-s-core-questioning-to-create-value/): Agility in business is about continuously questioning current practices and seeking ongoing improvement, not just following fixed processes. The essence of Agile and Scrum lies in relentless self-examination, with Scrum serving as a mirror that exposes organisational inefficiencies without directly fixing them. Organisations gain a competitive edge by empowering everyone to challenge rules, suggest better ways of working, and act on feedback to avoid team frustration. Creating open forums and regular retrospectives allows all team members to drive experimentation and continuous improvement. When dynamic change and curiosity are valued across all levels, businesses put themselves in position to spot opportunities and adapt faster than competitors.
- [The Importance of Evidence-Based Management in Agile Environments](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/): Evidence-based management is vital in Agile environments to ensure that process changes truly create business value. By tracking key metrics such as current value, time to market, ability to innovate, and unrealised value, teams can measure the real impact of their decisions rather than acting on assumptions. A specific example describes how a team, after introducing a new tool expecting faster delivery, instead saw increased delays and frustration until they tracked evidence and discovered the tool was slowing them down. Regularly collecting and analysing data supports informed decision-making, transparency, and ongoing improvement. Starting small and involving the team in monitoring metrics leads to more effective and confident changes.
- [Redefining Agile’s Core: Beyond Rituals and Procedures](https://engineering-leadership.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/): Agile is not about the rituals of stand-ups or Sprint reviews, but about building products and delivering value in new, adaptive ways. Many teams fall into "zombie Scrum," mechanically following Agile procedures without understanding or believing in their purpose, which undermines continuous improvement. True Agile focuses on outcomes—maximising value and responding flexibly to change—rather than rigidly following processes. Automation can simplify repetitive tasks, but complex systems such as Toyota’s production line succeed because they combine automation with human judgment and oversight. Adopting an Agile mindset means questioning rituals, adapting approaches, and recognising that every organisation's path to value is unique.
- [There’s No Such Thing as an Agile Transformation: Why You Should Focus on the System, Not the Culture](https://engineering-leadership.hinshelwood.com/videos/there-s-no-such-thing-as-an-agile-transformation-why-you-should-focus-on-the-system-not-the-culture/): Culture cannot be changed directly because it is an outcome of an organisation’s system, not a starting point. Focusing on altering the rules, procedures, and decision-making frameworks within which people operate is the most effective way to drive lasting change. For example, when performance metrics reward teamwork and decision-making is decentralised, behaviours and culture shift naturally over time. Begin with small, incremental tweaks to processes, monitor how these affect behaviour, and adjust continually, with leadership playing an active and supportive role. Ultimately, changing the system leads to the cultural transformation many seek.
- [The Importance of Evaluating Direction: Are You Heading the Right Way?](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evaluating-direction-are-you-heading-the-right-way/): Continuously evaluating direction is essential at every level, from individual developers to entire organisations. Developers must not only deliver features, but also regularly question if their code and approach match product vision and address risks like security flaws—a team once built a feature-rich but insecure product, leading to customer dissatisfaction and extra work. Product owners should challenge whether the features built actually solve users' problems rather than just adding complexity; ignoring this can result in unused features and wasted effort. At the organisational level, stubbornly sticking with an original plan—like persisting with a chatbot few customers used—increases risk, while the willingness to pivot and adapt to actual customer behaviour can drive success. The story of Olympian Dick Fosbury, who revolutionised high jumping with a new technique only widely adopted after a decade, shows that clinging to old ways or comfort can block innovation. Routinely gathering feedback, holding retrospectives, and fostering adaptability are vital to avoid heading in the wrong direction and missing better outcomes.
- [Continuous Adaptation: The Key to Success in a Dynamic Market](https://engineering-leadership.hinshelwood.com/videos/continuous-adaptation-the-key-to-success-in-a-dynamic-market/): Success in today’s fast-moving markets depends on a business’s ability to adapt continuously to changing conditions. Flexibility is essential, as rigid rules can stifle innovation and prevent organisations from responding quickly to shifts like new competitors or global events. For example, during the COVID-19 pandemic, businesses that had already adopted remote work and modern security adapted smoothly, while those with outdated systems struggled. Guiding principles, rather than fixed rules, provide a framework that empowers teams to make decisions and respond creatively to challenges. Continuous adaptation leads to greater competitiveness, improved customer satisfaction, and long-term profitability.
- [The Agile Bandit: How to Spot and Combat Project Management Mindsets in Product Owners](https://engineering-leadership.hinshelwood.com/videos/the-agile-bandit-how-to-spot-and-combat-project-management-mindsets-in-product-owners/): Product Owners who act like project managers and focus on tasks and control rather than value and collaboration can harm team morale, stifle innovation, and lead to ineffective products. To avoid these issues, encourage Product Owners to prioritize user value, foster close team collaboration, and empower teams to take ownership. Development managers should watch for these behaviors and actively support a shift toward a more value-driven and collaborative approach.
- [How to Overcome Agile Banditry: A Product Owner’s Journey](https://engineering-leadership.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/): Agile Banditry happens when Product Owners act as project managers, obsessing over detailed plans and task lists instead of focusing on vision, value, and outcomes. This micromanagement stifles creativity, disengages teams, and leads to poor results, as shown by a team burdened with Gantt charts that lost motivation and failed to innovate. Product Owners should step back from rigid planning, trust their skilled team members, and focus on setting clear goals and priorities. Empowered and engaged teams, not unhappy ones, deliver successful products. Letting go of control and fostering collaboration unlocks the team’s full potential.
- [The Pitfalls of Agile Burndowns: Stop Being Agile Bandits](https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/): Burndown charts, often used by Agile teams to track sprint progress, actually undermine true Agility by encouraging excessive upfront planning and creating a false sense of security. Attempting to meticulously plan every sprint detail leads teams to spend hours making task lists that are outdated almost immediately, wasting time and burdening developers with unnecessary admin. Most software products change significantly over time, and only a small fraction of features are ever used, making rigid planning futile. Teams should instead focus on minimal, just-in-time planning—such as only plotting the first 24 hours—then review and adapt daily, keeping backlogs lean. A switch to continuous flow boosts productivity and morale, as shown by teams who abandoned burndowns and achieved happier developers, faster delivery, and more satisfied customers.
- [Rethinking Sprint Planning: Why Burndown Charts Are Agile Banditry and What to Do Instead](https://engineering-leadership.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/): 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.
- [Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team's Success](https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-teams-success/): 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.
- [Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics](https://engineering-leadership.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/): Story points and velocity are often misused in Agile teams, leading to a focus on accumulating points rather than delivering value to customers. Tracking these metrics can cause teams to manipulate estimates, prioritise the wrong work, and waste time debating numbers instead of solving real problems. A striking case describes a team required by contract to deliver a set number of story points, resulting in inflated estimates, dishonesty, and stress. Instead, teams should measure throughput and cycle time, which reflect actual progress and value delivery. Story points can support team discussions but should never be used as performance measures or included in contracts.
- [Ditch the Agile Bandit Mentality: How to Prioritise Value Over Estimates for Team Success](https://engineering-leadership.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/): 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.
- [Say-Do Metrics: Avoiding Agile Banditry in Your Organization](https://engineering-leadership.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/): Say-do metrics, which track what teams promise versus what they actually deliver, often result in manipulated or vanity data that undermines real progress and psychological safety. A striking example recounts a project where reported estimates and actual hours matched exactly, only because managers retrospectively adjusted estimates to avoid leadership's scrutiny. This type of metric encourages data gaming, disconnects leadership from real issues, and pushes teams to prioritise looking good over delivering value. Focusing on outcomes, like the value delivered to customers, is vital; success lies in impact, not in meeting arbitrary targets. Organisations should promote transparency, psychological safety, and adaptability rather than fixating on outputs or rigid metrics.
- [Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products](https://engineering-leadership.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/): 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.
- [Special Sprints: Agile Banditry or Risk Management?](https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/): Special sprints like Sprint Zero, bug-fix sprints, or hardening sprints undermine Agile principles by allowing teams to defer work and dilute their focus on delivering usable, working products every sprint. The Azure DevOps team experienced this problem firsthand when a planned safety net sprint resulted in a mountain of undone work that could not be completed. By eliminating the safety net and requiring each sprint to end with a product ready for production, they improved quality and reduced technical debt. Relying on special sprints creates hidden risks and encourages teams to take shortcuts, whereas true Agile practice demands continuous delivery, immediate handling of technical debt, and no deferral of responsibility. Every sprint must count; treating them as anything less is labelled "agile banditry" and should be avoided.
- [The Pitfalls of Routine Agile Questions: Avoiding the Ghosts of Agile Past](https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/): Relying solely on the usual three daily Scrum questions—what was done yesterday, what is being worked on today, and what's blocking progress—can turn Agile meetings into unthinking routines that miss the real point: delivering value. When meetings focus on individual updates, teams risk losing sight of progress toward the sprint goal and fall into dysfunctional habits, such as redundant updates and ignoring stuck tasks. Using a banana peel analogy, the content highlights how tasks that linger on boards become harder to complete and attract more issues, just as old banana peels attract fruit flies. To improve, teams should track work item ageing, set clear rules for handling old tasks, focus updates on group progress toward the sprint goal, and actively discuss stuck items every day. Evolving Agile ceremonies beyond rote routines keeps the focus on value and continuous improvement, helping teams avoid bottlenecks and ineffective habits.
- [Overcoming the Ghost of Agile Certifications](https://engineering-leadership.hinshelwood.com/videos/overcoming-the-ghost-of-agile-certifications/): In Agile, certifications are often mistaken as proof of expertise, but relying solely on them can hinder true learning and professional growth. Passing a two-day course or exam is only the starting point, much like getting a driving licence does not make you an expert behind the wheel. The most effective Scrum Masters are those recognised for the real value they bring to their teams, not just for holding a certificate. Deep experience, hands-on problem-solving, and team endorsement are crucial for genuine professional development. Certifications should support your learning journey, not define your competence.
- [The Ghosts of Agile Past: Why Burndown Charts Might Be Holding You Back](https://engineering-leadership.hinshelwood.com/videos/the-ghosts-of-agile-past-why-burndown-charts-might-be-holding-you-back/): Burndown charts, once seen as essential for tracking Agile team progress, actually hinder adaptability by relying on fixed scope and upfront task planning that do not match how Agile teams operate. The belief that scope can be fully defined at the start of a sprint is unrealistic, as teams consistently discover new work and challenges during execution. Planning every task and estimating hours in advance leads to false certainty and missed realities; it is common to realise you only understand the true effort when deeply involved in the work. The key is to manage progress empirically, focusing on consistent flow of value rather than arbitrary burndown targets. Teams that thrive in Agile adapt their plans on the fly, respond to technical debt and production issues, and prioritise the delivery of value over adherence to outdated charts.
- [Story Points: A Ghost of Agile Past](https://engineering-leadership.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/): Story points, once introduced to replace rigid hours-based estimates in Agile, have become a persistent source of dysfunction in software teams. Rather than focusing on delivering real value, teams often fixate on accumulating points or chasing targets, even to the extent of pushing incomplete work to future sprints. The use of story points for comparing teams or contract compliance leads to false equivalences and damaging incentives, as seen in a team penalised for deviating more than 15% from point targets. Story points are subjective and can be manipulated, while flow metrics like cycle time, work item ageing, and throughput provide objective, cross-team insights based on actual performance. To achieve better outcomes, focus should shift from arbitrary point tallies to tracking how work moves through the system and the real value delivered.
- [Introduction to Agility’s Ghosts: Shedding Dogma and Embracing Pragmatism](https://engineering-leadership.hinshelwood.com/videos/introduction-to-agility-s-ghosts-shedding-dogma-and-embracing-pragmatism/): Agile thrives on flexibility, adaptation, and collaboration, not rigid rule-following. Dogmatic approaches can harm team effectiveness, as shown in the story of a Scrum Master fired for insisting that everyone stand during daily meetings, even when a team member used a wheelchair and the group chose to sit in solidarity. While it is important to be precise when teaching frameworks, teams should prioritise outcomes, respect, and value delivery over strict adherence to rules. True agility means responding to change and the unique needs of the team, letting pragmatism override dogma to foster innovation and inclusivity. Teams succeed when they are free to adjust processes based on feedback and context.
- [Stay Ahead of the Curve: How Continuous Learning Keeps You in the Top 10%](https://engineering-leadership.hinshelwood.com/videos/stay-ahead-of-the-curve-how-continuous-learning-keeps-you-in-the-top-10/): Continuous learning is essential for staying relevant and competitive in software development, as it helps you adapt to rapid changes, seize new opportunities, and grow personally. Regular reading, exploring diverse topics, engaging with the community, experimenting with new tools, and reflecting on what you learn are key habits. Make time for ongoing learning to maintain your edge and open up more opportunities for your team and yourself.
- [The Power of Continuous Learning for Product Owners](https://engineering-leadership.hinshelwood.com/videos/the-power-of-continuous-learning-for-product-owners/): Continuous learning is the most important factor for product owners aiming for success, as it keeps you ahead in a constantly evolving industry. Rather than chasing every new tool or trend, focus on building a broad set of effective techniques such as evidence-based management, A/B testing, OKRs, hypothesis-driven engineering, and even using tools like Mechanical Turk for quick feedback. Engaging with the product owner community, reading both modern and classic texts like Crossing the Chasm, and investing in professional training all help you stand out among your peers. Only a small percentage of professionals commit to continuous learning, so maintaining this habit puts you in the top 10%. Ultimately, learning is an ongoing journey that maximises the value you bring to your team and organisation.
- [Mastering the Art of Understanding: Essential Skills for Product Owners to Foster Team Clarity](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-understanding-essential-skills-for-product-owners-to-foster-team-clarity/): Product owners should focus on actively gauging team understanding by observing non-verbal cues, asking open-ended questions, and creating a safe environment for honest communication. Tailoring language to the audience and encouraging curiosity helps bridge knowledge gaps. Regular check-ins and fostering openness are key actions to ensure everyone is aligned, which is essential for project success.
- [Mastering Product Backlog Management: Essential Skills for Product Owners](https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/): Effective product backlog management is central to delivering maximum value as a product owner, requiring constant focus on risk, value, size, and learning. Accountability for value delivery remains with the product owner, even if backlog management is delegated. Ensuring backlog items are refined, manageable within a sprint, and clearly understood by both team and stakeholders is crucial, as misunderstandings can lead to disengagement and missed feedback. Techniques like Kanban and regular refinement sessions help maintain flow and alignment. Success depends on continuous improvement, open communication, and a readiness to break down high-risk or vague items, as failing to do so can hide uncertainty and cause costly errors.
- [Transforming Sprint Reviews: How to Engage Stakeholders and Secure Meaningful Feedback](https://engineering-leadership.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/): 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.
- [Mastering the Art of Product Ownership: The Power of Marketing Your Vision](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-the-power-of-marketing-your-vision/): Effective product ownership goes beyond backlog management; it requires marketing a compelling vision to engage the development team, stakeholders, and customers emotionally. Crafting and consistently communicating a strong product story is key to boosting participation in Sprint Reviews and generating meaningful feedback, rather than facing empty rooms where tumbleweeds roll by. Techniques like sharing personalised previews and inviting stakeholders to use the product during reviews can increase engagement by as much as 60 percent. Aligning everyone with a shared vision streamlines feedback loops, prioritises value, and keeps the backlog focused on high-impact features. As Product Owners become visionaries and collaborators, marketing skills are essential for rallying diverse perspectives behind a unified product direction.
- [Filling the Understanding Gap: A Product Owner's Guide to Vision, Engagement, and Value](https://engineering-leadership.hinshelwood.com/videos/filling-the-understanding-gap-a-product-owners-guide-to-vision-engagement-and-value/): Product Owners must clearly understand and communicate the product vision, engage teams and stakeholders with passion and clarity, and ensure all work aligns with delivering measurable value. Fostering open feedback and using visuals can boost engagement and ownership. Development managers should prioritize shared understanding and alignment to drive successful product outcomes.
- [Vision, Value, and Validation: The Keys to Successful Product Management](https://engineering-leadership.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/): When moving from project management to product management, it is essential for Product Owners to fill the gap left by traditional planning tools by focusing on vision, value, and validation. Clearly define and communicate the product vision, ensure all work aligns with delivering real value, and continuously validate progress through feedback and measurement. Prioritize these pillars to keep teams aligned and maximize product impact; consider seeking support if challenges arise.
- [Mastering Negotiation: Essential Skills Every Product Owner Needs from *Never Split the Difference*](https://engineering-leadership.hinshelwood.com/videos/mastering-negotiation-essential-skills-every-product-owner-needs-from-never-split-the-difference/): Negotiation is a critical but often overlooked skill for product owners, and the book Never Split the Difference offers practical techniques like empathy, active listening, and strategic questioning that can improve outcomes with stakeholders and teams. Understanding the impact of decisions and preparing thoroughly are key to successful negotiations. Development managers should encourage their teams to practice these skills and consider using this book as a resource to strengthen negotiation capabilities.
- [The Art of Negotiation for Product Owners: Essential Skills to Master](https://engineering-leadership.hinshelwood.com/videos/the-art-of-negotiation-for-product-owners-essential-skills-to-master/): Strong negotiation skills are essential for Product Owners to balance stakeholder demands, technical realities, and leadership requests, ensuring the product delivers maximum value. Key techniques include active listening, asking probing questions, and guiding others to see the bigger picture, which helps avoid unnecessary features and maintain focus. Development managers should encourage Product Owners to build these skills through training, reflection, and coaching to improve outcomes and stakeholder relationships.
- [Empathy in Agile: Building Trust and Stronger Relationships for Success](https://engineering-leadership.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/): Empathy, modesty, and respect are essential for building trust and strong relationships in agile teams, leadership, and with customers, leading to better collaboration and outcomes. Avoiding assumptions and seeking diverse perspectives through open questions and feedback helps prevent bias and supports continuous improvement. Development managers should prioritise empathy and active listening to create a culture where everyone feels valued and engaged.
- [The Power of Humility in Agile: A Core Virtue for Success](https://engineering-leadership.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/): Humility is crucial for Agile teams because it enables better collaboration, trust, and openness to feedback, leading to stronger products and happier teams. Recognizing that not all ideas are right, listening to others, and being willing to change course based on data and feedback are key to success. Development managers should foster a culture where team members check their egos, seek diverse perspectives, and use data thoughtfully to continuously improve.
- [Empowering Users: Transforming Products from Burdens to Essential Tools](https://engineering-leadership.hinshelwood.com/videos/empowering-users-transforming-products-from-burdens-to-essential-tools/): Products succeed when users see them as empowering tools rather than burdens, which requires empathy, clear communication of value, and proactive support. Open feedback channels and acting on user input help build trust and drive continuous improvement. Development managers should prioritize user relationships and feedback loops to ensure products are seen as essential and beneficial.
- [The Power of Kindness in Agile: A Core Virtue for Success](https://engineering-leadership.hinshelwood.com/videos/the-power-of-kindness-in-agile-a-core-virtue-for-success/): Kindness is a strategic advantage in Agile, driving both customer loyalty and effective team collaboration by building trust through empathy and compassion. Focusing on employee well-being and understanding customer needs leads to better products and stronger relationships. Development managers should model kindness in daily interactions to foster a culture where teams and customers feel valued, directly impacting long-term success.
- [Cultivating Patience: The Secret Ingredient for Thriving Agile Teams](https://engineering-leadership.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/): Patience is essential for agile teams to build trust, avoid blame, and support growth, leading to better collaboration and outcomes. Leaders should set realistic expectations, encourage open communication, and model patient behavior to foster a healthy team environment. Take time to invest in team development and celebrate progress to enable long-term success.
- [The Importance of Patience and Trust in Building Agile Organizations](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-patience-and-trust-in-building-agile-organizations/): Building a successful Agile organization requires patience and trust, as these enable teams to experiment, learn from failures, and innovate without fear of blame. Impatience leads to a blame culture, reduced quality, and stifled creativity, while patience supports empiricism and continuous improvement. Development managers should foster a culture that values learning from mistakes, sets realistic expectations, and avoids blame to strengthen trust and drive better outcomes.
- [Bridging the Gap: Understanding the True Meaning of "Done" in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/): Many Agile teams misunderstand what "done" really means, leading to gaps in quality and unmet expectations. Clearly defining "done" 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's definition of done to align with evolving business needs and maintain high standards.
- [The Overlooked Virtue of Agility: Diligence](https://engineering-leadership.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/): 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.
- [Unlocking Success: Join Me for a Virtual Coffee to Tackle Your Agile and Technical Challenges](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-join-me-for-a-virtual-coffee-to-tackle-your-agile-and-technical-challenges/): If you are facing agile or technical challenges, I am offering free virtual coffee chats to help you find practical solutions tailored to your organisation. This approach focuses on empowering teams, sharing knowledge, and creating positive impacts beyond your company. Book a session to discuss your issues and walk away with actionable ideas that support both your team's and the wider community's success.
- [The Power of Charity in Agile: How Helping Others Elevates Teams and Organizations](https://engineering-leadership.hinshelwood.com/videos/the-power-of-charity-in-agile-how-helping-others-elevates-teams-and-organizations/): Charity, or helping others without expecting anything in return, is a key driver of Agile team and organizational success because it builds trust, collaboration, and a shared sense of purpose. Encouraging this behavior leads to higher motivation, better product quality, and long-term growth. Development managers should actively foster a culture of giving and collective achievement to unlock these benefits.
- [Mastering Agile: The Power of "Just Enough and No More" for Optimal Efficiency](https://engineering-leadership.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/): Applying the principle of "just enough and no more" 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.
- [Temperance in Agile: Why Less is More](https://engineering-leadership.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/): 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.
- [Engaging Your Team: The Secret to Successful Organisational Change](https://engineering-leadership.hinshelwood.com/videos/engaging-your-team-the-secret-to-successful-organisational-change/): Successful organisational change depends on actively engaging your team by aligning their goals with the change, involving them in the process, and maintaining open communication. Empowering team members through participation and celebrating progress builds trust and motivation. To drive effective transformation, focus on shared purpose, regular updates, and continuous feedback so your team feels invested and valued.
- [Embracing Chastity in Agile: Why Taking Your Time is Key to True Transformation](https://engineering-leadership.hinshelwood.com/videos/embracing-chastity-in-agile-why-taking-your-time-is-key-to-true-transformation/): Rushing into agile practices without fully understanding their impact can lead to shallow adoption and missed opportunities. True transformation requires involving your team in decision-making, aligning organisational and individual goals, and using inclusive tools to support cultural change. Take a deliberate, thoughtful approach to implementing agile and seek expert guidance if needed to ensure lasting results.
- [The Importance of Product Backlog Management in Today's Agile Landscape](https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-todays-agile-landscape/): Effective product backlog management is essential for team focus, stakeholder alignment, and delivering real value, yet many organizations neglect it, leading to confusion and wasted effort. Key issues include oversized or outdated backlogs, lack of regular refinement, insufficient detail, and poor stakeholder involvement. To improve, keep the backlog lean, refine it regularly with the whole team, ensure transparency and clarity, and use data to guide priorities; making this a priority will boost team performance and stakeholder satisfaction.
- [Mastering Product Backlog Management: Key Strategies for Agile Success](https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/): 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.
- [Mastering Product Backlog Management: Insights from the New Scrum.org Course](https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/): 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.
- [Transform Your Leadership: The Power of Evidence-Based Management in Agile](https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/): 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.
- [Agile Leadership: Empowering Managers with the Right Skills](https://engineering-leadership.hinshelwood.com/videos/agile-leadership-empowering-managers-with-the-right-skills/): Managers often struggle to transition into effective leadership roles without proper training, especially in agile environments where servant leadership and data-driven decision making are key. Investing in Professional Agile Leadership and Evidence-Based Management training helps managers empower teams, align work with organizational goals, and make informed decisions. Consider prioritizing these training programs to boost both team performance and organizational success.
- [Mastering Scrum: Essential Insights for New Teams from a Scrum Master's Journey](https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-essential-insights-for-new-teams-from-a-scrum-masters-journey/): 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.
- [Understanding the True Role of a Scrum Master](https://engineering-leadership.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/): 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.
- [Mastering Prioritisation: How Product Owners Can Drive Value and Accountability](https://engineering-leadership.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/): Product Owners play a crucial role in ensuring resources are spent wisely by prioritising the most valuable work, aligning development with business goals, and maintaining stakeholder trust through clear communication. Effective prioritisation maximises value delivery, keeps teams focused, and adapts to changing needs. Development managers should support Product Owners in understanding users, collaborating closely, and staying flexible to drive successful outcomes.
- [The Real Scope of a Product Owner: Beyond the Backlog](https://engineering-leadership.hinshelwood.com/videos/the-real-scope-of-a-product-owner-beyond-the-backlog/): 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.
- [How to Choose the Right Agile Coach for Your Business Success](https://engineering-leadership.hinshelwood.com/videos/how-to-choose-the-right-agile-coach-for-your-business-success/): To get the most value from Agile coaching, choose someone who is adaptable, experienced across multiple frameworks, and committed to continuous learning rather than a coach who only uses one method. A versatile coach will tailor their approach to your team's unique needs and challenges, leading to better outcomes. When hiring, ask about their experience with different industries and how they customize solutions so you get guidance that truly fits your business.
- [How Immersive Learning Transforms Aspiring Agile Leaders](https://engineering-leadership.hinshelwood.com/videos/how-immersive-learning-transforms-aspiring-agile-leaders/): Immersive learning experiences like the PAL-E class help aspiring agile leaders overcome common barriers by providing time, practical assignments, and peer feedback to apply and reflect on agile practices in real-world settings. Leaders gain actionable tools to empower teams, foster collaboration, and focus on value delivery rather than just process. Consider enrolling your leadership team in such a program to drive sustainable agile transformation and maximize organizational impact.
- [Hiring the Right Agile Coach: What You Need to Know](https://engineering-leadership.hinshelwood.com/videos/hiring-the-right-agile-coach-what-you-need-to-know/): Hiring the right Agile coach is crucial for successful transformation, so focus on candidates with a proven track record, relevant experience in organizations similar to yours, and strong references. Look for coaches who demonstrate empathy, adaptability, and clear communication, and ensure they fit your culture and can tailor their approach to your needs. Involve key stakeholders in the selection process to maximize the chances of finding a coach who will drive lasting agility and continuous improvement.
- [The Future of Scrum Training: Immersive Learning for Lasting Change](https://engineering-leadership.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/): 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.
- [Hiring an Agile Coach: What You Need to Know](https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-you-need-to-know/): 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.
- [The Power of Immersive Learning: Elevating Scrum Mastery in Your Organization](https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-elevating-scrum-mastery-in-your-organization/): Immersive learning is more effective than traditional training for developing Scrum Masters because it emphasizes hands-on assignments, real-world application, and knowledge sharing, which lead to lasting improvements in team performance. Teams immediately apply what they learn, receive real-time feedback, and benefit from collective insights, making Scrum practices like the Definition of Done part of daily work. To boost Scrum mastery and see real impact, prioritize immersive learning for your organization’s training programs.
- [Hiring an Agile Coach: What to Look For in Both Technical and Leadership Engagement](https://engineering-leadership.hinshelwood.com/videos/hiring-an-agile-coach-what-to-look-for-in-both-technical-and-leadership-engagement/): 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.
- [Why Every Scrum Master Needs an Immersive Training Experience](https://engineering-leadership.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/): 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.
- [The Key to Hiring the Right Agile Coach: Building Credibility with Teams and Leadership](https://engineering-leadership.hinshelwood.com/videos/the-key-to-hiring-the-right-agile-coach-building-credibility-with-teams-and-leadership/): When hiring an Agile coach, prioritize candidates who can build credibility with both teams and leadership by demonstrating hands-on technical experience, strong communication skills, and emotional intelligence. Coaches who understand your tools and culture, and who can balance support across all levels, are more likely to drive real and lasting Agile transformation. Focus your search on those who have proven they can foster trust, adapt to your environment, and bridge gaps between teams and executives.
- [Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/): Immersive Professional Scrum Master training enables deeper learning by encouraging participants to question existing practices, apply new strategies, and collaborate with peers from diverse backgrounds. This approach helps Scrum Masters tackle real-world challenges, uncover organisational barriers, and continuously improve their methods. Consider enrolling in immersive training to foster a culture of reflection and shared problem-solving within your teams.
- [The Key to Being an Effective Agile Coach: Understanding the Team’s Context](https://engineering-leadership.hinshelwood.com/videos/the-key-to-being-an-effective-agile-coach-understanding-the-team-s-context/): Effective Agile coaching requires understanding your team's specific work and context, not just Agile frameworks. Coaches with domain experience or those who actively learn about their team's challenges can offer more relevant, practical advice and build trust. Development managers should ensure their coaches engage deeply with teams' day-to-day realities to maximize impact.
- [Mastering Azure DevOps Migration: A Step-by-Step Guide for Seamless Project Transfers](https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-migration-a-step-by-step-guide-for-seamless-project-transfers/): 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.
- [The Power of Community: Becoming an Awesome Agile Coach](https://engineering-leadership.hinshelwood.com/videos/the-power-of-community-becoming-an-awesome-agile-coach/): To be an effective Agile coach, it is essential to engage with a diverse community that challenges your thinking and provides honest feedback, rather than staying in a comfortable echo chamber. Growth comes from seeking out different perspectives, embracing critique, and continuously evolving your approach, which ultimately leads to delivering greater value to your teams and customers. Development managers should encourage their coaches to actively participate in varied Agile communities and prioritize learning and feedback to drive continuous improvement.
- [Mastering Agile: 3 Essential Strategies to Boost Your Team's Sprint Success](https://engineering-leadership.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-teams-sprint-success/): To improve your team's Sprint outcomes, clearly define what "done" 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.
- [Unlocking Agile Success: The Essential Knowledge Every Coach Needs](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-the-essential-knowledge-every-coach-needs/): 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.
- [Mastering Complexity in Scrum: Transform Your Team with Agile Product Strategy Insights](https://engineering-leadership.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/): 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's grasp of these principles to boost effectiveness.
- [How to Be an Effective Agile Coach: Agnosticism in Practice](https://engineering-leadership.hinshelwood.com/videos/how-to-be-an-effective-agile-coach-agnosticism-in-practice/): 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.
- [Why 'Definition of Done' is Crucial for Success in Scrum](https://engineering-leadership.hinshelwood.com/videos/why-definition-of-done-is-crucial-for-success-in-scrum/): The Definition of Done sets clear quality standards for all work, ensuring every deliverable meets your organization's expectations regardless of the specific feature or project. It aligns teams, reduces defects, and protects your brand by making sure nothing is released before it is truly ready. Regularly review and adapt your Definition of Done with your team to maintain high quality and customer satisfaction.
- [Before You Call Yourself an Agile Coach: The Importance of Real Experience](https://engineering-leadership.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/): 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.
- [Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/): 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.
- [Breaking the Silence: How to Combat the Hidden Dangers in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-the-hidden-dangers-in-agile-teams/): Silence in Agile teams can lead to poor communication, lack of accountability, and misleading commitments, which undermine value delivery, erode trust, and stall growth. Managers should actively foster open communication, model vulnerability, and set clear expectations to prevent these issues. Prioritising honest dialogue and celebrating those who speak up will help teams deliver better results and maintain a healthy, agile culture.
- [Taming the Chaos Factor: How to Align Your Agile Teams for Success](https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/): 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.
- [Navigating the Judgment Trap: How to Foster a Healthy Agile Environment](https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/): Judgment in Agile teams, such as rigid rules and unhealthy metric comparisons, can lower morale, stifle innovation, and create a culture of blame. To avoid this, set meaningful goals, use adaptive metrics that encourage improvement, and foster open dialogue focused on learning. Development managers should prioritize creating a safe, collaborative environment where teams feel empowered to innovate and grow.
- [Overcoming the Plague of Rigidity: Embracing True Agility in Your Team](https://engineering-leadership.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/): 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.
- [Combatting the Agile Apocalypse: How to Overcome the Famine of Feedback and Engagement](https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/): 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.
- [Navigating Team Conflict: From Healthy Disagreement to Agile Harmony](https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/): Team conflict is normal and can drive innovation, but if disagreements escalate unchecked, they can harm team dynamics and project outcomes. Managers should watch for signs of unhealthy conflict and use open communication, objective discussions, mediation, and clear team norms to de-escalate issues early. Addressing conflict directly helps maintain productivity and keeps teams focused on delivering value together.
- [Beware the Fake Agilists: How to Protect Your Team from the Agile Apocalypse](https://engineering-leadership.hinshelwood.com/videos/beware-the-fake-agilists-how-to-protect-your-team-from-the-agile-apocalypse/): Relying on leaders with only Agile certifications but no real software development experience can harm team trust, stifle growth, and lead to ineffective processes. To protect your teams, prioritize practical experience over credentials, encourage ongoing learning, and focus on delivering value rather than just following procedures. Ensure Agile leadership is grounded in genuine expertise to maintain team effectiveness and resilience.
- [Taming the Chaos: How to Align Your Agile Team for Success](https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/): 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.
- [Breaking the Silence: How to Combat Communication Gaps in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/): 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.
- [Navigating the Agile Apocalypse: How to Combat Judgment and Foster Team Growth](https://engineering-leadership.hinshelwood.com/videos/navigating-the-agile-apocalypse-how-to-combat-judgment-and-foster-team-growth/): Judging teams by metrics like velocity, bug counts, or code volume can create fear and stifle growth, undermining Agile principles. Instead, focus on goals that reflect real progress, encourage open discussion about challenges, and regularly review metrics to ensure they support a healthy team environment. Review your current metrics and team culture to ensure they foster collaboration and innovation rather than fear or competition.
- [Breaking Free from the Plagues of Agility: How to Cultivate Flexibility and Innovation in Your Team](https://engineering-leadership.hinshelwood.com/videos/breaking-free-from-the-plagues-of-agility-how-to-cultivate-flexibility-and-innovation-in-your-team/): Teams often lose true agility by becoming too attached to specific tools and processes, which leads to stagnation, inefficiency, and lower morale. Encouraging experimentation, holding regular retrospectives to review practices, and empowering teams to adapt workflows are key to maintaining flexibility and innovation. Development managers should regularly assess whether current methods still serve the team's needs and foster a culture of continuous improvement.
- [Combatting Famine in Agile: How to Foster Stakeholder Engagement and Boost Team Morale](https://engineering-leadership.hinshelwood.com/videos/combatting-famine-in-agile-how-to-foster-stakeholder-engagement-and-boost-team-morale/): 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.
- [Navigating Team Conflict: How Scrum Masters Can Prevent 'War' in Agile Projects](https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-how-scrum-masters-can-prevent-war-in-agile-projects/): Team conflict can quickly escalate from healthy debate to destructive arguments that harm collaboration and project outcomes. Scrum Masters play a key role in preventing this by fostering open communication, keeping discussions focused on issues rather than individuals, and de-escalating tensions early. Development managers should watch for early signs of conflict and support Scrum Masters in maintaining a productive team environment.
- [The Antichrist of Agile: How Fake Agilists Are Undermining True Innovation](https://engineering-leadership.hinshelwood.com/videos/the-antichrist-of-agile-how-fake-agilists-are-undermining-true-innovation/): Relying on certified but inexperienced Agile practitioners can harm teams by leading to poor leadership, stifled innovation, and loss of trust. Real-world experience and ongoing learning are more important than credentials alone. Development managers should prioritize hiring Agile coaches with proven practical backgrounds and foster open communication to maintain genuine Agile practices.
- [How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/): 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.
- [Training: A Bridge to Knowledge and Growth](https://engineering-leadership.hinshelwood.com/videos/training-a-bridge-to-knowledge-and-growth/): Investing in training and continuous learning is key to team growth and long-term success, helping teams stay relevant and engaged while demonstrating organizational commitment. Leaders should focus on creating a supportive environment that encourages experimentation, celebrates small wins, and addresses systemic barriers to learning. Prioritize ongoing development and adapt to new technologies to boost morale, performance, and retention.
- [What Should a Product Owner Do with an Incompetent Team?](https://engineering-leadership.hinshelwood.com/videos/what-should-a-product-owner-do-with-an-incompetent-team/): Before labeling a team as incompetent, assess whether the issue is a lack of knowledge or experience and provide training, support, and feedback to help them improve. If the team is truly incompetent, malicious, or fails to improve after support, act quickly to replace them to protect your product and organization. Invest in developing your team, but do not tolerate behavior that puts your business at risk.
- [Scrum is like communism, it doesn't work. Myth 5](https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesnt-work-myth-5/): Scrum does not mean abandoning governance; instead, it requires teams to balance agility with necessary regulatory and organizational standards. Applying "just enough governance" ensures compliance and quality without stifling innovation, especially in regulated or complex environments. Development managers should regularly review and adapt governance practices to support both compliance and Agile delivery.
- [Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum](https://engineering-leadership.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/): 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.
- [Scrum is like communism, it doesn't work. Myth 3](https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesnt-work-myth-3/): 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.
- [Scrum is like communism, it doesn't work. Myth 2](https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesnt-work-myth-2/): Story points are not required by Scrum and are often misused, leading to confusion and pressure on teams. Their real value is in sparking conversations about uncertainty during backlog refinement, not as ongoing metrics or time proxies. Development managers should focus on open dialogue, use story points only as needed for understanding, and consider alternative estimation methods to better support team effectiveness and value delivery.
- [Scrum is like communism, it doesn't work. Myth 1](https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesnt-work-myth-1/): 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.
- [7 Harbingers of the Agile apocalypse - Silence](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/): 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.
- [7 Harbingers of the Agile apocalypse - Chaos](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-chaos/): 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.
- [Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling](https://engineering-leadership.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/): 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.
- [7 harbingers of the Agile apocalypse - Judgement](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/): 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.
- [7 Harbingers of the Agile Apocalypse - Plague](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-plague/): 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.
- [7 Harbingers of the Agile Apocalypse - Famine](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-famine/): Resource scarcity in Agile organizations, such as lack of trust, funding, training, and tools, often stems from rigid, top-down management and can severely limit team performance and growth. Empowering teams with decision-making authority, flexible budgets, and a culture of trust and continuous learning leads to better outcomes and avoids costly mistakes. Development managers should prioritize investing in people and resources to enable agility and long-term success.
- [7 harbingers of the Agile apocalypse- War](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-war/): Unchecked conflict in agile teams can escalate from healthy debate to destructive infighting, undermining collaboration and progress. Leaders must foster open communication, empathy, and clear conflict resolution processes to keep disagreements constructive and aligned with shared goals. Proactively managing conflict is essential to prevent team dysfunction and support ongoing innovation and growth.
- [7 Harbingers of the Agile apocalypse - Organizational Structure](https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-organizational-structure/): Traditional top-down management structures block true agility by centralizing decision-making and limiting team empowerment, especially for key roles like Product Owner. To become more agile, organizations need to decentralize authority, promote transparency, and adopt servant leadership, allowing teams closer to the customer to make decisions. Leaders should drive this shift by supporting teams and gradually implementing changes that focus on delivering customer value.
- [Does 'starting with why' - Simon Sinek - really matter?](https://engineering-leadership.hinshelwood.com/videos/does-starting-with-why-simon-sinek-really-matter/): Starting with a clear purpose is essential for Agile teams because it boosts motivation, engagement, and alignment. Focusing on intrinsic motivators like autonomy, mastery, and purpose leads to better results than relying on financial incentives. Development managers should ensure their teams understand the broader vision and regularly connect daily work to that purpose for sustained success.
- [Are there any Scrum courses that teach you how to scale Scrum?](https://engineering-leadership.hinshelwood.com/videos/are-there-any-scrum-courses-that-teach-you-how-to-scale-scrum/): 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.
- [What is the one thing that no Agile team can survive?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-that-no-agile-team-can-survive/): No Agile team can survive a culture of contempt, which arises when team input is ignored and decisions are made without their involvement, leading to low morale and poor productivity. Leaders must foster open communication, include teams in decision-making, and address disconnects to build a positive, engaged workforce. If change is not possible, individuals may need to seek healthier environments to maintain well-being and performance.
- [7 deadly sins of Agile: Wrath](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/): Wrath in Agile teams shows up as blame and fear of mistakes, which stifles innovation and learning. Shifting from blame to shared accountability creates a safer environment for risk-taking and continuous improvement. Development managers should encourage open discussion of mistakes and support a culture where learning from errors is valued over perfection.
- [Quotes: Dictatorship vs Democracy](https://engineering-leadership.hinshelwood.com/videos/quotes-dictatorship-vs-democracy/): Effective Agile leadership requires balancing clear direction from leaders with empowering teams to collaborate and make decisions. Relying solely on top-down control limits innovation and engagement, while pure democracy can slow progress. Leaders should set the vision, encourage open dialogue, and trust teams to act, creating a more innovative and committed environment.
- [Quotes: Less is More. True or False?](https://engineering-leadership.hinshelwood.com/videos/quotes-less-is-more-true-or-false/): 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.
- [Quotes: You can't connect the dots looking forward; you can only connect them looking backwards. Steve Jobs](https://engineering-leadership.hinshelwood.com/videos/quotes-you-cant-connect-the-dots-looking-forward-you-can-only-connect-them-looking-backwards-steve-jobs/): 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.
- [7 deadly sins of Agile: Pride](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-pride/): 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.
- [Quotes: In the past the man has been first; in the future the system must be first. Frederick Winslow Taylor](https://engineering-leadership.hinshelwood.com/videos/quotes-in-the-past-the-man-has-been-first-in-the-future-the-system-must-be-first-frederick-winslow-taylor/): The Industrial Revolution shifted focus from individuals to systems for productivity, but in Agile environments, it is essential to balance effective systems with the needs of people. Systems should empower teams and not become obstacles, so regularly review and adapt them based on team feedback. Development managers should ensure systems support collaboration and productivity rather than hinder them.
- [When is an APS course appropriate for a scrum team?](https://engineering-leadership.hinshelwood.com/videos/when-is-an-aps-course-appropriate-for-a-scrum-team/): 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.
- [7 deadly sins of Agile: Lust](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-lust/): Agile transformation is not a quick fix or something that can be bought off the shelf; it requires genuine commitment, adaptation, and alignment with your organisation’s unique context. Many companies make the mistake of seeking instant results or copying generic models, which often leads to disappointment. Development managers should focus on building a tailored Agile journey through ongoing learning, experimentation, and a willingness to evolve.
- [Quotes: Fake it until you make it](https://engineering-leadership.hinshelwood.com/videos/quotes-fake-it-until-you-make-it/): "Fake it till you make it" can help build confidence and support learning in Agile teams, but it is not a replacement for real expertise and should not be used in roles that require proven skills. Use this approach only to bridge minor knowledge gaps and encourage learning by doing, while ensuring experts handle critical tasks and mentor others. Focus on creating a culture of continuous learning and valuing genuine expertise.
- [7 Deadly Sins of Agile: Greed](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/): 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.
- [7 deadly sins of Agile: Gluttony](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/): 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.
- [Quotes: Don't scale Scrum! Pragmatic or defeatist?](https://engineering-leadership.hinshelwood.com/videos/quotes-dont-scale-scrum-pragmatic-or-defeatist/): 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.
- [7 deadly sins of Agile: Envy](https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-envy/): Avoid copying Agile models like Spotify without considering your team'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.
- [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](https://engineering-leadership.hinshelwood.com/videos/quotes-i-estimate-that-75-of-those-organisations-using-scrum-will-not-succeed-in-getting-the-benefits-that-they-hope-for-from-it-ken-schwaber/): 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.
- [Why is Lego a shit idea for a scrum trainer - Part 3](https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-3/): Lego is avoided in Scrum training because its simplicity fails to reflect the real complexity and chaos of software development, while Minecraft is sometimes used for specific scenarios to better simulate overwhelming and collaborative environments. The choice of tool should support realistic learning experiences and evoke the pressures teams actually face. Focus on selecting training tools that mirror real-world challenges rather than just simplifying concepts.
- [Why is Lego a shit idea for a Scrum trainer - Part 2](https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-2/): Using Lego in Scrum training oversimplifies the real complexity of software development, as Lego pieces fit together too easily and do not reflect the integration challenges teams actually face. This can create unrealistic expectations and trivialize the difficulties of real projects. Development managers should choose training tools that better represent the unpredictable and varied nature of software work.
- [What are the barriers that prevent developers from fully accepting a Product Owner as the final decision maker?](https://engineering-leadership.hinshelwood.com/videos/what-are-the-barriers-that-prevent-developers-from-fully-accepting-a-product-owner-as-the-final-decision-maker/): Developers may not fully accept the Product Owner as the final decision maker when stakeholders undermine the Product Owner’s authority, send mixed messages, or fail to consistently support their decisions. This leads to confusion, lack of trust, and developers second-guessing decisions. To address this, ensure stakeholders back the Product Owner publicly, document agreements, and foster open communication to build trust and accountability.
- [Why is Lego a shit idea for a Scrum Trainer - Part 1](https://engineering-leadership.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-1/): Using Lego in Scrum training can undermine the seriousness of the message, create a mismatch between the training method and professional context, and risk disengaging senior participants. The playful approach may trivialize key concepts and reduce credibility with experienced professionals. Development managers should choose training tools that align with the professional environment and reinforce the importance of cultural transformation.
- [Cutting Through the Red Tape: How Eliminating Committees Can Boost Your Time to Market](https://engineering-leadership.hinshelwood.com/videos/cutting-through-the-red-tape-how-eliminating-committees-can-boost-your-time-to-market/): Committees often slow down decision-making and stall teams, leading to missed business opportunities and delayed time to market. Empowering teams to make decisions and adopting modern collaboration tools can significantly improve speed, accountability, and innovation. Review your current processes and consider reducing committee involvement to stay competitive and agile.
- [Transforming Agile: How to Shift from Blame to Systemic Solutions for Better Team Dynamics](https://engineering-leadership.hinshelwood.com/videos/transforming-agile-how-to-shift-from-blame-to-systemic-solutions-for-better-team-dynamics/): Problems in agile teams are usually caused by flawed measurement systems and processes, not individual intent. Metrics drive behavior, so focusing on changing how people are evaluated and incentivized is more effective than trying to change culture directly. Review your team’s metrics and processes to remove barriers and foster adaptability, which will lead to better collaboration and innovation.
- [Unlocking Agility: How Decentralisation Empowers Teams to Maximise Value in Any Organisation](https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-decentralisation-empowers-teams-to-maximise-value-in-any-organisation/): Decentralising decision-making empowers teams to respond faster, innovate more, and feel greater ownership, which leads to higher value delivery. Involving team members in shaping the organisation’s goals and connecting their skills to outcomes boosts engagement and collaboration. Development managers should focus on pushing responsibility to teams and fostering a shared sense of purpose to maximise results.
- [Unlocking Organisational Value: The Transformative Power of Engagement in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/unlocking-organisational-value-the-transformative-power-of-engagement-in-agile-teams/): Organisations deliver the most value when they focus on engaging their teams, not just managing them. Empowering people through decentralised decision-making, inclusivity, and clear principles leads to higher morale, innovation, and better results. Development managers should prioritise creating an environment where everyone feels trusted, aligned with the vision, and motivated to contribute.
- [Unlocking Success: The Essential Role of Product Ownership in Lean Product Delivery](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-the-essential-role-of-product-ownership-in-lean-product-delivery/): Strong product ownership is essential for aligning product vision with business goals, fostering team collaboration, and enabling quick adaptation to change. Lean product delivery helps teams focus on delivering customer value, encourages continuous improvement, and empowers teams to take ownership of their work. Development managers should invest in training, promote experimentation, and establish feedback loops to enhance product ownership and stay competitive.
- [Unlocking Success: How Lean Product Development Transforms Decision-Making and Value Creation](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-lean-product-development-transforms-decision-making-and-value-creation/): Lean product development is gaining traction because it helps teams make better decisions, reduce risk, and create more value with fewer resources. Adopting this mindset enables organisations to focus on building products that truly meet customer needs and avoid wasted effort. Development managers should consider exploring lean practices to improve product outcomes and maximise return on investment.
- [Why Azure DevOps is the Ultimate Game Changer for Scrum Masters and Agile Teams](https://engineering-leadership.hinshelwood.com/videos/why-azure-devops-is-the-ultimate-game-changer-for-scrum-masters-and-agile-teams/): Azure DevOps stands out for Scrum Masters and agile teams because it offers a simple, user-friendly interface, provides integrated tools for full project visibility, and empowers teams through collaboration and real-time feedback. These features help reduce overhead, streamline workflows, and support continuous improvement. Development managers should consider adopting Azure DevOps to enhance team performance and deliver greater value.
- [Scrum doesn't solve problems, it reveals them. How, and why is that valuable?](https://engineering-leadership.hinshelwood.com/videos/scrum-doesnt-solve-problems-it-reveals-them-how-and-why-is-that-valuable/): 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.
- [Embracing Asynchronous Communication: Transform Your Collaboration and Boost Productivity](https://engineering-leadership.hinshelwood.com/videos/embracing-asynchronous-communication-transform-your-collaboration-and-boost-productivity/): Asynchronous communication increases flexibility, reduces pressure, and improves collaboration by allowing team members to contribute on their own schedules and providing clear documentation. Shifting away from constant meetings can boost productivity and lead to more thoughtful input. Development managers should set clear expectations, use the right tools, and balance async work with occasional check-ins to get the most benefit.
- [Where is consensus valuable and where does it kill great product development?](https://engineering-leadership.hinshelwood.com/videos/where-is-consensus-valuable-and-where-does-it-kill-great-product-development/): Consensus is essential in product development but can slow progress if overused, especially in fast-moving markets where quick decisions are needed. Building trust and involving the team in decision-making helps achieve effective consensus, but leaders must know when to seek agreement and when to act decisively. Development managers should balance collaboration with timely leadership to drive successful outcomes.
- [Signs You're Failing as a Product Owner: How to Take Control and Deliver Real Value](https://engineering-leadership.hinshelwood.com/videos/signs-youre-failing-as-a-product-owner-how-to-take-control-and-deliver-real-value/): A failing product owner is marked by poor product quality, inconsistent delivery, lack of vision, and not taking true ownership of the product. To deliver real value, product owners must make decisions, communicate a clear vision, and focus on actual outcomes rather than vanity metrics. Development managers should ensure their product owners are empowered to lead, make tough calls, and stay aligned with user and business needs.
- [Unlocking Team Potential: Why Every Scrum Master Needs a Quality Camera for Effective Engagement](https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-why-every-scrum-master-needs-a-quality-camera-for-effective-engagement/): Using a high-quality camera in remote meetings helps Scrum Masters better read team members' body language and emotions, which leads to stronger engagement and more effective communication. Investing in good equipment, maintaining a professional background, and encouraging camera use can foster a more open and collaborative team environment. Development managers should ensure their teams have access to quality video tools to maximize virtual collaboration.
- [Harnessing Your Entrepreneurial Spirit: Key Strategies for Product Owners to Drive Team Success](https://engineering-leadership.hinshelwood.com/videos/harnessing-your-entrepreneurial-spirit-key-strategies-for-product-owners-to-drive-team-success/): Product owners should connect their teams to the value they create by clearly communicating vision and goals, and foster evidence-based decision-making using data and user feedback rather than intuition. Focusing on metrics like time to market and balancing innovation with maintenance helps teams deliver better results faster. Encourage regular dialogue and rapid prototyping to keep teams engaged and responsive to user needs.
- [Unlocking Team Potential: The Essential Role of Digital Whiteboards in Agile Collaboration](https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-digital-whiteboards-in-agile-collaboration/): 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.
- [What are the top 3 things a Scrum Master needs to bear in mind when adopting the coaching stance?](https://engineering-leadership.hinshelwood.com/videos/what-are-the-top-3-things-a-scrum-master-needs-to-bear-in-mind-when-adopting-the-coaching-stance/): A Scrum Master adopting a coaching stance should focus on guiding teams toward self-organisation, building trust and influence through expertise and empathy, and adapting their approach to the team’s unique context and culture. Key outcomes include stronger collaboration, empowered decision-making, and higher team satisfaction. To be effective, Scrum Masters should actively listen, foster a positive environment, and continuously develop their own skills.
- [Why the Scrum Master’s True Power Lies in Influence, Not Authority](https://engineering-leadership.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/): 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.
- [5 tools that Scrum Masters love. Part 1](https://engineering-leadership.hinshelwood.com/videos/5-tools-that-scrum-masters-love-part-1/): 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.
- [How do you decide whether to pivot or stay the course? (Nokia story)](https://engineering-leadership.hinshelwood.com/videos/how-do-you-decide-whether-to-pivot-or-stay-the-course-nokia-story/): 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.
- [How does a Scrum Master or Agile coach motivate a Scrum Team?](https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/): 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.
- [What should you do if your Sprint Review delivers harsh, scathing feedback?](https://engineering-leadership.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/): 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.
- [Agile Training versus Agile Consulting](https://engineering-leadership.hinshelwood.com/videos/agile-training-versus-agile-consulting/): Agile training builds a shared understanding and foundational skills across teams, while Agile consulting focuses on solving specific problems with tailored solutions in a short timeframe. Both approaches are effective but serve different needs. Consider using training for broad knowledge and consulting for targeted improvements.
- [Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success](https://engineering-leadership.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/): 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's next steps.
- [Mastering Product Ownership: Unlocking the Secrets to Effective Product Management in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/mastering-product-ownership-unlocking-the-secrets-to-effective-product-management-in-agile-teams/): Effective product management, especially through a strong product owner, is essential for agile teams to stay focused, align with goals, and deliver value. Key practices include providing clear vision, engaging stakeholders, prioritising work, fostering collaboration, and continuous learning. Development managers should prioritise investing in skilled product owners to drive team success and product quality.
- [What should be top of mind when a Scrum team prepare for a Sprint review?](https://engineering-leadership.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/): 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.
- [Unlocking Organisational Agility: How to Empower Your Team for Rapid Market Response](https://engineering-leadership.hinshelwood.com/videos/unlocking-organisational-agility-how-to-empower-your-team-for-rapid-market-response/): Organisational agility is about enabling your teams to respond quickly to market changes by empowering those closest to the customer to make decisions and reducing communication bottlenecks. Focusing on speed, clear context, and ownership helps capture opportunities faster than competitors. Review your decision-making processes and give teams the information and authority they need to act swiftly.
- [One thing an Agile Coach MUST do to be successful?](https://engineering-leadership.hinshelwood.com/videos/one-thing-an-agile-coach-must-do-to-be-successful/): An Agile Coach must deeply understand the team's processes, practices, and technologies to be effective, not just Agile theory. This knowledge allows coaches to guide, challenge, and help teams improve rather than simply supervise. Development managers should ensure their coaches are familiar with the team's tools and context to drive real progress.
- [What is empiricism and why is it so critical to great Agile?](https://engineering-leadership.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/): 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.
- [Unlocking Agile Mastery: How the Minecraft Case Study Transforms Training and Team Dynamics](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-how-the-minecraft-case-study-transforms-training-and-team-dynamics/): The Minecraft case study developed by Simon offers an engaging and practical way for teams to experience Agile concepts, closely mirroring real project challenges and improving team collaboration. Participants report higher engagement, better understanding of complexity, and stronger teamwork compared to traditional training. Development managers should consider innovative, interactive training methods like this to boost Agile adoption and team effectiveness.
- [What has the initial response been to the immersive learning experiences, how do you see that evolving?](https://engineering-leadership.hinshelwood.com/videos/what-has-the-initial-response-been-to-the-immersive-learning-experiences-how-do-you-see-that-evolving/): Immersive learning is quickly replacing traditional two-day workshops, with businesses reporting better knowledge retention, higher engagement, and greater return on investment as employees apply new skills in real time. This approach uses ongoing sessions, real-time collaboration, and continuous feedback, allowing for tailored and incremental development. Development managers should consider adopting immersive learning formats to foster deeper skill growth and more sustainable professional development within their teams.
- [Why is Kanban such a popular approach for people in creative industries?](https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/): Kanban is popular in creative industries because it adapts to existing workflows, reduces chaos, and helps teams align on priorities without stifling creativity. It improves efficiency by visualising work, shortening cycle times, and encouraging collective decision-making. Development managers should consider mapping their team's current process with Kanban to enhance collaboration and deliver creative work more predictably.
- [Why do you trust Russell to deliver the PSPO course for NKD Agility?](https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-russell-to-deliver-the-pspo-course-for-nkd-agility/): Russell is a highly experienced and versatile PSPO trainer whose background spans both technical and strategic aspects of product development, including work in aerospace and mentoring Product Owners. His teaching focuses on maximizing product value through practical, real-world insights and engaging, comprehensive learning experiences. Development managers looking to elevate their teams' product ownership skills should consider his course for actionable strategies and proven results.
- [Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/): 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.
- [Why do you trust Joanna to deliver Scrum.Org classes for NKD Agility?](https://engineering-leadership.hinshelwood.com/videos/why-do-you-trust-joanna-to-deliver-scrum-org-classes-for-nkd-agility/): 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.
- [If a client hasn't considered DevOps consulting as part of their Agile Consulting needs, why should they?](https://engineering-leadership.hinshelwood.com/videos/if-a-client-hasnt-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/): Relying on Agile alone limits your team'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's benefits, development managers should invest in DevOps consulting to create a truly high-performing, adaptable software delivery process.
- [1 thing that sinks a consulting engagement before it starts gaining traction?](https://engineering-leadership.hinshelwood.com/videos/1-thing-that-sinks-a-consulting-engagement-before-it-starts-gaining-traction/): Overly detailed contracts that specify exact deliverables, timelines, and costs can undermine consulting engagements because they do not account for the unpredictable nature of software development. Focusing on outcomes and the value delivered, rather than rigid outputs, leads to better results. Development managers should prioritize flexibility in contracts to adapt to changing requirements and ensure project success.
- [Harnessing the Power of Empiricism: Transform Your Decision-Making with Data-Driven Insights](https://engineering-leadership.hinshelwood.com/videos/harnessing-the-power-of-empiricism-transform-your-decision-making-with-data-driven-insights/): Using data to guide decisions helps teams make better choices, improve continuously, and build trust with stakeholders. The key is to ensure access to relevant data, act deliberately, and monitor results in a cycle of experimentation and learning. Development managers should foster a culture where decisions are based on evidence, not assumptions, and regularly review outcomes to adapt and improve.
- [Unlocking Agility: How EPS Immersive Learning Transforms Your Team's Performance](https://engineering-leadership.hinshelwood.com/videos/unlocking-agility-how-eps-immersive-learning-transforms-your-teams-performance/): 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.
- [What are 3 key takeaways for a scrum team after attending an APS immersive learning experience course?](https://engineering-leadership.hinshelwood.com/videos/what-are-3-key-takeaways-for-a-scrum-team-after-attending-an-aps-immersive-learning-experience-course/): 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.
- [How effectively does an APS prepare a team to do a solid, professional Scrum?](https://engineering-leadership.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/): 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 "Barnacle Exercise," 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.
- [Dogma versus Empiricism in a consulting engagement](https://engineering-leadership.hinshelwood.com/videos/dogma-versus-empiricism-in-a-consulting-engagement/): Rigid adherence to fixed methods limits innovation and effectiveness in consulting; instead, teams should move from strict training routines to flexible, evidence-based approaches that adapt to changing needs. Building relationships through empathy and mutual respect is key, and embracing continuous learning and empirical adaptation leads to better outcomes. Development managers should encourage adaptability and ongoing learning to stay responsive and successful.
- [Znaczenie znajomości terenu](https://engineering-leadership.hinshelwood.com/videos/znaczenie-znajomo%C5%9Bci-terenu/): Understanding your environment, much like knowing the terrain when foraging for mushrooms, is crucial for agile teams to adapt and succeed. Fostering a creative and collaborative workforce leads to better customer experiences and continuous improvement. Consider investing in agile training or coaching to help your teams perform at their best.
- [Harvesting Agility: What Mushroom Foraging Taught Me About Scrum and Team Dynamics](https://engineering-leadership.hinshelwood.com/videos/harvesting-agility-what-mushroom-foraging-taught-me-about-scrum-and-team-dynamics/): Applying Agile and Scrum effectively requires understanding your team's environment, being willing to step outside your comfort zone, and having patience for gradual improvement. Success comes from researching your context, iterating carefully, and focusing on continuous learning rather than just quick wins. Development managers should invest time in understanding team dynamics and encourage steady, mindful progress for lasting results.
- [Czym różni się zwinne przywództwo od tradycyjnego zarządzania](https://engineering-leadership.hinshelwood.com/videos/czym-r%C3%B3%C5%BCni-si%C4%99-zwinne-przyw%C3%B3dztwo-od-tradycyjnego-zarz%C4%85dzania/): Agile leadership differs from traditional management by focusing on building creative, collaborative, and high-performing teams that drive better customer experiences. Empowering and inspiring teams leads to continuous improvement and stronger results. Consider agile training or coaching to help your teams evolve and perform at their best.
- [From Control to Empowerment: Embracing Agile Leadership in a Complex World](https://engineering-leadership.hinshelwood.com/videos/from-control-to-empowerment-embracing-agile-leadership-in-a-complex-world/): Traditional management works well for predictable problems but falls short in today’s complex, fast-changing environment. Agile leadership empowers teams, encourages collaboration, and fosters innovation by shifting focus from control to enabling people. Development managers should move from directing every detail to creating environments where teams can adapt and thrive.
- [Part 2: Most influential people in Agile](https://engineering-leadership.hinshelwood.com/videos/part-2-most-influential-people-in-agile/): Simon Randell is highlighted as a key influence in Agile due to his exceptional facilitation skills, clear communication, and practical embodiment of Agile principles. His approach inspires others to emulate his clarity and effectiveness in both teaching and practice. Development managers should consider learning from leaders like Simon to strengthen their own Agile transformations.
- [How will the immersive learning experience help coach people on the job?](https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-help-coach-people-on-the-job/): Immersive learning spreads Agile training over several weeks, allowing participants to apply lessons directly to their work and receive valuable feedback in each session. This approach leads to deeper understanding, practical skill development, and stronger collaboration among team members. Development managers should consider immersive learning to foster real-world growth and continuous improvement within their teams.
- [5 critical Skills to master as an Agile Consultant?  Part 1](https://engineering-leadership.hinshelwood.com/videos/5-critical-skills-to-master-as-an-agile-consultant-part-1/): To be effective as an Agile consultant, it is crucial to recognize that fully understanding a client's context is rarely possible, so rely on experience, embrace trial and error, and continuously adapt your approach. Success comes from learning from setbacks, identifying universally effective strategies, and maintaining a commitment to ongoing learning. Development managers should foster a culture of experimentation and adaptability within their teams.
- [1 thing you wish you knew at the start of your Scrum journey?](https://engineering-leadership.hinshelwood.com/videos/1-thing-you-wish-you-knew-at-the-start-of-your-scrum-journey/): Integrating Lean principles with Scrum from the start can significantly boost team success by combining effective collaboration with data-driven insights. Many only discover the benefits of Lean years into their Scrum journey, but adopting both early leads to better outcomes and deeper understanding. Development managers should consider exploring and applying Lean alongside Scrum now rather than waiting, to maximize team performance and innovation.
- [3 reasons why you should level up your knowledge and skills?](https://engineering-leadership.hinshelwood.com/videos/3-reasons-why-you-should-level-up-your-knowledge-and-skills/): Continually improving your knowledge and skills is essential for sustained professional success, as it keeps you adaptable and respected in a changing industry. Embracing ongoing learning, trial and error, and genuine care for your craft builds resilience and drives innovation. Make continuous development a core part of your team's culture to maintain excellence and stay ahead.
- [Hardest part of becoming a professional Scrum Master?](https://engineering-leadership.hinshelwood.com/videos/hardest-part-of-becoming-a-professional-scrum-master/): The biggest challenge in becoming a professional Scrum Master is the widespread lack of true professionalism in the role, as many focus on titles rather than mastering the underlying principles and continuous learning. Success requires a deep understanding of Scrum theory and its real-world application, not just surface-level knowledge. Development managers should encourage their teams to prioritize professionalism and ongoing skill development to raise industry standards.
- [How will the Immersive Learning experience change the game for people with a couple of years experience in the field?](https://engineering-leadership.hinshelwood.com/videos/how-will-the-immersive-learning-experience-change-the-game-for-people-with-a-couple-of-years-experience-in-the-field/): Immersive learning helps experienced Agile practitioners deepen their expertise by connecting real-world challenges with advanced theory and practical assignments, leading to more meaningful breakthroughs. It leverages their existing knowledge, encourages nuanced questions, and tailors learning to specific needs. Development managers should consider immersive learning to accelerate team growth and address complex, real-world problems more effectively.
- [Transform Your Team's Skills: The Power of Immersive Learning in the Workplace](https://engineering-leadership.hinshelwood.com/videos/transform-your-teams-skills-the-power-of-immersive-learning-in-the-workplace/): Immersive learning is more effective than traditional training because it focuses on applying concepts directly to real work, encourages feedback and reflection, and helps teams challenge old habits. Including coaching and group support makes the learning more relevant and impactful for each participant. Consider adopting immersive learning to build stronger, more adaptable teams.
- [From Product Owner to Systemic Leader: Embracing the Evolution in Agile Leadership](https://engineering-leadership.hinshelwood.com/videos/from-product-owner-to-systemic-leader-embracing-the-evolution-in-agile-leadership/): Experienced Product Owners often grow into broader leadership roles, taking on more accountability and influencing organisational culture and systems. This transition requires a shift from managing backlogs to creating environments that empower teams and foster innovation. Development managers should support Product Owners in developing leadership skills and consider training like Agile Leadership Essentials to help them drive positive change across the organisation.
- [Why is the Professional Agile Leadership - Essentials course a natural evolution for an experienced Scrum Master?](https://engineering-leadership.hinshelwood.com/videos/why-is-the-professional-agile-leadership-essentials-course-a-natural-evolution-for-an-experienced-scrum-master/): The Professional Agile Leadership - Essentials course helps experienced Scrum Masters understand leadership perspectives and challenges, preparing them to move from team-level to broader organizational leadership. It equips them with new insights and language to better serve and influence at multiple levels. Consider this course if you are looking to expand your impact beyond your current Scrum Master role.
- [Why is Johanna a great teacher for the Professional Agile Leadership - Essentials course?](https://engineering-leadership.hinshelwood.com/videos/why-is-johanna-a-great-teacher-for-the-professional-agile-leadership-essentials-course/): Johanna is an engaging and passionate instructor for the Professional Agile Leadership course, bringing extensive real-world experience with organizational leaders. Her sessions are dynamic due to both her enthusiasm and the active participation of decision-makers in the class, leading to valuable discussions and practical insights. Consider enrolling in the course or reaching out for a conversation to enhance your agile leadership skills and drive transformation in your organization.
- [Unlocking Growth: The Transformative Power of Poly Immersive Learning Experiences](https://engineering-leadership.hinshelwood.com/videos/unlocking-growth-the-transformative-power-of-poly-immersive-learning-experiences/): Poly immersive learning experiences help teams adapt to complexity by encouraging learning from real-world feedback, fostering collaboration, and providing time for reflection. They reinforce knowledge through structured assignments and practical experiments, which build habits of continuous improvement. Development managers should integrate these approaches to drive ongoing learning and accountability within their teams.
- [Unlocking Potential: How Immersive Learning Transforms Careers and Organisations](https://engineering-leadership.hinshelwood.com/videos/unlocking-potential-how-immersive-learning-transforms-careers-and-organisations/): Immersive learning delivers immediate, practical skills that employees can apply to drive real improvements and continuous growth in your organisation. Teams benefit from ongoing support and multiple opportunities to implement new knowledge, while individuals gain confidence and job readiness. Investing in immersive training accelerates both organisational agility and individual career impact, making it a high-value development strategy.
- [Transforming Leadership: Embrace the Immersive Journey to Agile Mastery](https://engineering-leadership.hinshelwood.com/videos/transforming-leadership-embrace-the-immersive-journey-to-agile-mastery/): Switching from traditional two-day workshops to shorter, regular agile leadership modules helps managers absorb information better, apply new skills in real time, and build stronger relationships with trainers. This immersive approach supports continuous growth and adaptation, making it easier for leaders to transition to agile practices. Consider adopting or supporting ongoing, modular training to empower your teams and improve leadership effectiveness.
- [Unlocking Agile Mastery: Why Spaced Learning Outshines Traditional Courses](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-mastery-why-spaced-learning-outshines-traditional-courses/): Spaced learning, where Agile and Scrum training is spread over several weeks, leads to better retention, real-world application, and ongoing support compared to traditional short courses. Participants can practice and apply concepts in their actual work, get guidance as challenges arise, and benefit from peer collaboration. Development managers should consider longer, cohort-based training formats to achieve more lasting and practical results for their teams.
- [Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support](https://engineering-leadership.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/): 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.
- [Unlocking the True Power of Agile: Embracing Change and Collaboration for Team Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-agile-embracing-change-and-collaboration-for-team-success/): 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.
- [Reasons to do a PSM II Course in 60 seconds](https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-a-psm-ii-course-in-60-seconds/): The PSM II course helps experienced Scrum Masters deepen their expertise, empower teams, and better support product owners, leading to higher team performance and organizational agility. It offers practical tools, advanced facilitation techniques, and access to a professional community, all aimed at driving real change. Consider enrolling to accelerate your career growth and make a greater impact in your organization.
- [Reasons to do a PSPO-A Course in 60 Seconds](https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-a-pspo-a-course-in-60-seconds/): The PSPO-A course helps product managers and product owners master Agile and Scrum principles, improving their ability to manage products efficiently and respond to change. It offers practical insights to boost collaboration, innovation, and effectiveness in product management. Consider enrolling to enhance your skills and drive better results for your team and business.
- [Reasons to do an APS Course in 60 Seconds](https://engineering-leadership.hinshelwood.com/videos/reasons-to-do-an-aps-course-in-60-seconds/): 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.
- [Why have you decided to go all in on immersive learning experiences?](https://engineering-leadership.hinshelwood.com/videos/why-have-you-decided-to-go-all-in-on-immersive-learning-experiences/): Immersive learning experiences lead to deeper understanding, better retention, and stronger engagement than traditional methods by providing hands-on practice, ongoing support, and a collaborative community. This approach encourages continuous growth and adaptation, making learning a sustained journey rather than a one-time event. Development managers should consider adopting immersive learning to build resilient, high-performing teams and ensure lasting knowledge transfer.
- [Part 2: Common Mistakes that Scrum Masters Make](https://engineering-leadership.hinshelwood.com/videos/part-2-common-mistakes-that-scrum-masters-make/): Scrum Masters often fall into the trap of handling administrative tasks for their teams, which distracts from their real role of improving team effectiveness. Taking on these duties can undermine both the Scrum Master’s impact and the team’s growth. Focus on enabling the team rather than doing their work for them, and avoid becoming the team’s secretary.
- [Do you think we are on the slope of enlightenment in Gartner's Hype Cycle?](https://engineering-leadership.hinshelwood.com/videos/do-you-think-we-are-on-the-slope-of-enlightenment-in-gartners-hype-cycle/): Most organizations are still struggling with Agile due to unrealistic expectations and a focus on process over people, but a growing number are starting to see real benefits by prioritizing human interactions and learning from successful pioneers. The shift toward true Agile maturity is underway, though widespread enlightenment has not yet been reached. Development managers should focus on setting realistic goals, fostering a people-first culture, and learning from those who have achieved genuine Agile success.
- [Most influential people in Agile: Simon Reindl](https://engineering-leadership.hinshelwood.com/videos/most-influential-people-in-agile-simon-reindl/): Many Product Owners feel they lack control over key decisions like backlog order and product goals, often being excluded from strategic discussions. Recognizing this gap is the first step toward gaining more influence and accountability. Product Owners should proactively seek involvement in important meetings and build relationships to elevate their role within the organization.
- [What more needs to happen before traditional organisations consider Agile?](https://engineering-leadership.hinshelwood.com/videos/what-more-needs-to-happen-before-traditional-organisations-consider-agile/): 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.
- [How AI is Revolutionising Our Work: Embrace the Future of Productivity and Creativity](https://engineering-leadership.hinshelwood.com/videos/how-ai-is-revolutionising-our-work-embrace-the-future-of-productivity-and-creativity/): AI is rapidly transforming work by boosting productivity and creativity, acting as a supportive tool for idea generation, content creation, and automating repetitive tasks. Teams that adopt AI can work more efficiently and gain a competitive advantage. Development managers should start exploring and integrating AI tools now to stay ahead in a changing landscape.
- [What is the Sprint Review workshop and how will it help organisations?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/): 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.
- [Most Common Thing You Hear in a PSPO Course?](https://engineering-leadership.hinshelwood.com/videos/most-common-thing-you-hear-in-a-pspo-course/): Many Product Owners feel they lack control over key aspects like backlog order, product goals, and strategic discussions, which limits their impact. Recognizing this gap is the first step toward greater empowerment and influence. Product Owners should proactively seek involvement in important meetings, build relationships, and demonstrate competence to earn more accountability and elevate their role.
- [Unlocking the Power of Sprint Planning: Transform Your Agile Approach for Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/): Effective Sprint planning can transform your team'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.
- [Most Common Thing You Hear in a PSM 1 Course?](https://engineering-leadership.hinshelwood.com/videos/most-common-thing-you-hear-in-a-psm-1-course/): Many PSM 1 students justify compromising transparency with clients by citing "real world" pressures, especially around upfront estimates. The course stresses that maintaining honesty and moral integrity with customers is essential, even when it feels difficult. Development managers should prioritize truth and transparency over convenience to build lasting trust and avoid misleading clients.
- [Agile Scotland 2023: Why does this matter to you and why should people come to the event?](https://engineering-leadership.hinshelwood.com/videos/agile-scotland-2023-why-does-this-matter-to-you-and-why-should-people-come-to-the-event/): Agile 2023 in Scotland is a growing event that brings together passionate Agile professionals to share knowledge, connect with thought leaders, and discuss the latest trends in Agile practices. The conference highlights the importance of community, collaboration, and continuous learning in driving innovation within the tech sector. Development managers should consider engaging with local Agile events to gain fresh insights and foster a culture of improvement in their teams.
- [Scrum Master versus seasoned Agile Coach?](https://engineering-leadership.hinshelwood.com/videos/scrum-master-versus-seasoned-agile-coach/): A Scrum Master and a seasoned Agile Coach both support Agile practices, but an Agile Coach brings deeper knowledge and extensive experience across multiple frameworks like Scrum, Lean, and Kanban. Agile Coaches have a proven track record of guiding organizations through complex challenges and embedding Agile at a deeper level. If your goal is to drive significant Agile transformation and long-term success, consider engaging a seasoned Agile Coach.
- [Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment](https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/): 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.
- [Agile Coach Versus Professional Coach](https://engineering-leadership.hinshelwood.com/videos/agile-coach-versus-professional-coach/): An Agile coach offers deep expertise in Agile methods and brings new tools and perspectives that can significantly boost team effectiveness, while a professional coach helps teams work through challenges they already understand. For teams aiming to improve their Agile practices and innovate, bringing in an Agile coach provides added value beyond general coaching. Consider engaging an Agile coach if your goal is to advance Agile and Scrum capabilities within your organisation.
- [Why Are a Scrum Team Better Served by an Agile Consultant than a Professional Coach?](https://engineering-leadership.hinshelwood.com/videos/why-are-a-scrum-team-better-served-by-an-agile-consultant-than-a-professional-coach/): 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.
- [Most Rewarding Part of Being a Scrum Developer?](https://engineering-leadership.hinshelwood.com/videos/most-rewarding-part-of-being-a-scrum-developer/): The most rewarding part of being a Scrum developer is building software that truly matters to people, which gives purpose and fuels passion for the work. When developers see their efforts making a real impact, it drives higher quality and creativity. Managers should encourage teams to focus on meaningful outcomes to boost motivation and results.
- [Why Is It So Important that Senior Leadership Teams are Engaged During an Agile Consulting Engagement?](https://engineering-leadership.hinshelwood.com/videos/why-is-it-so-important-that-senior-leadership-teams-are-engaged-during-an-agile-consulting-engagement/): Active involvement from senior leadership is essential for successful Agile transformation because systemic change and faster market response require alignment and participation at all levels. Without leadership engagement, teams face barriers to adaptability and meaningful change. Development managers should ensure senior leaders are directly involved to enable organisation-wide transformation and maximise the value of Agile initiatives.
- [How Hard is it to Transition from Being a Developer to a Scrum developer?](https://engineering-leadership.hinshelwood.com/videos/how-hard-is-it-to-transition-from-being-a-developer-to-a-scrum-developer/): 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.
- [Rethinking the Statement of Work: How to Truly Meet Client Needs Beyond the Contract](https://engineering-leadership.hinshelwood.com/videos/rethinking-the-statement-of-work-how-to-truly-meet-client-needs-beyond-the-contract/): Focusing strictly on the statement of work often fails to address clients' real problems, leading to temporary fixes and dissatisfaction. Building trust, adapting to actual needs, and prioritising value over rigid contract terms result in better outcomes and lasting change. Development managers should emphasise relationships and flexibility to deliver solutions that truly matter to clients.
- [Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success](https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/): 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.
- [How Does Your Consulting Experience Manifest in the Training Environment?](https://engineering-leadership.hinshelwood.com/videos/how-does-your-consulting-experience-manifest-in-the-training-environment/): Training is most effective when led by someone with real consulting experience, as it brings practical, relatable examples that bridge the gap between theory and real-world challenges. Sharing authentic stories from consulting helps teams engage, learn, and apply concepts like Agile and Scrum more effectively. Consider choosing training programs led by experienced consultants to ensure your teams gain actionable insights they can use immediately.
- [What Does an Ineffective Scrum Master's Day Look Like?](https://engineering-leadership.hinshelwood.com/videos/what-does-an-ineffective-scrum-masters-day-look-like/): An ineffective Scrum Master spends too much time on reports instead of supporting the team, treats daily meetings as status checks rather than collaboration opportunities, and blocks communication between developers and the business. These behaviors hinder progress and team growth. Recognizing and addressing these habits is crucial for improving team effectiveness.
- [What is the Single Most Valuable Outcome a Consulting Engagement Can Produce?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-single-most-valuable-outcome-a-consulting-engagement-can-produce/): The most valuable outcome of a consulting engagement is achieving systemic change that leads to lasting improvements in how the organization operates. This enables teams to work faster and respond to the market more effectively, but it requires overcoming resistance to change and fostering a culture of experimentation. Development managers should focus on building an environment where people are willing to try new approaches and continuously evolve.
- [What Does a Poor Product Backlog Look Like?](https://engineering-leadership.hinshelwood.com/videos/what-does-a-poor-product-backlog-look-like/): 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.
- [What Does the Assessment Phase of a Consulting Engagement Look and Feel Like?](https://engineering-leadership.hinshelwood.com/videos/what-does-the-assessment-phase-of-a-consulting-engagement-look-and-feel-like/): The assessment phase in consulting should be minimal and flexible, with consultants continuously learning and adapting as they engage with teams rather than relying on a rigid upfront evaluation. Starting to help right away and adjusting based on real-time insights leads to better understanding and outcomes. Development managers should focus on early collaboration and ongoing adaptation instead of lengthy initial assessments.
- [Hardest Part of Adopting Scrum?](https://engineering-leadership.hinshelwood.com/videos/hardest-part-of-adopting-scrum/): The hardest part of adopting Scrum is overcoming the false belief that success will happen automatically without real effort or change. The real challenge is shifting mindsets and building a culture of continuous learning and adaptability. Development managers should focus on addressing these ingrained expectations to achieve genuine Scrum transformation.
- [Unlocking Agile Consulting: Transform Your Organisation with Diverse Strategies and Continuous Learning](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-consulting-transform-your-organisation-with-diverse-strategies-and-continuous-learning/): Agile consulting helps organisations improve by offering a range of strategies beyond a single framework, focusing on real-world challenges and maximising value through better feedback and collaboration. Success depends on engaging people at all levels, understanding the current state through interviews and reports, and fostering continuous learning and internal change. Development managers should consider diverse approaches and invest in building skills and relationships to drive meaningful transformation.
- [Can you align DevOps and Software Engineering Teams Through Scrum?](https://engineering-leadership.hinshelwood.com/videos/can-you-align-devops-and-software-engineering-teams-through-scrum/): 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.
- [DevOps Consulting Overview](https://engineering-leadership.hinshelwood.com/videos/devops-consulting-overview/): DevOps consulting focuses on driving real improvement by aligning culture, processes, and tools to deliver better software faster and more reliably. Key outcomes include tailored workshops, leadership alignment, and hands-on technical support across various platforms, not just Microsoft. To get the most value, approach DevOps as an ongoing journey of cultural and operational change rather than a one-time tool implementation.
- [How Much of An Impact can Scrum Have in a DevOps Environment?](https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-scrum-have-in-a-devops-environment/): 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.
- [Unlock £20 Rewards: Join Our Exciting Referral Program for Collaborative Learning!](https://engineering-leadership.hinshelwood.com/videos/unlock-gbp20-rewards-join-our-exciting-referral-program-for-collaborative-learning/): A new referral program offers £20 rewards for both you and your colleagues when you invite them to join classes, encouraging collaborative learning and community building. By sharing a unique code, you both receive discounts or credits, making professional development more cost-effective. Visit the website to get your code and start inviting your team to enhance learning together.
- [Why is DevOps such a Critical Element of Software Engineering?](https://engineering-leadership.hinshelwood.com/videos/why-is-devops-such-a-critical-element-of-software-engineering/): 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.
- [Under employed - 30% upfront, balance when you are employed](https://engineering-leadership.hinshelwood.com/videos/under-employed-30-upfront-balance-when-you-are-employed/): A new training program offers underemployed professionals affordable access by requiring only 30% upfront payment, with the balance due after securing suitable employment. The approach is built on trust, focuses on practical upskilling, and encourages networking and a positive mindset to turn underemployment into a career springboard. Development managers can consider this model to support team members’ growth while minimizing financial barriers.
- [How do DevOps and Agile integrate?](https://engineering-leadership.hinshelwood.com/videos/how-do-devops-and-agile-integrate/): DevOps and Agile are closely connected, each offering a different but complementary focus: DevOps emphasizes engineering and continuous delivery, while Agile centers on people and process. Combining both approaches helps teams achieve better results by leveraging their unique strengths together. Development managers should encourage their teams to integrate both mindsets for optimal performance.
- [Biggest contribution from a Product Owner that you know of](https://engineering-leadership.hinshelwood.com/videos/biggest-contribution-from-a-product-owner-that-you-know-of/): 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.
- [30% Discount for Existing Alumni Overview](https://engineering-leadership.hinshelwood.com/videos/30-discount-for-existing-alumni-overview/): Existing alumni are being offered a 30 percent discount on future courses to recognize their dedication and support their continued growth in Agile and DevOps. This offer aims to help committed professionals deepen their expertise, transition to consultant roles, and stay competitive. Take advantage of this opportunity to further develop your skills and advance your career.
- [Unlocking the Product Owner Potential: Bridging Theory and Practice in Agile Leadership](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-product-owner-potential-bridging-theory-and-practice-in-agile-leadership/): The Product Owner role requires moving beyond theory to practical leadership, taking on broader responsibilities like marketing, sales, and contract negotiation, and influencing key business areas. An immersive, collaborative learning approach helps product owners apply new strategies, share real-world experiences, and learn from peers to drive better outcomes. Development managers should support ongoing learning and cross-functional engagement for their product owners to maximize their impact.
- [Why Validate Your Advanced Product Ownership Skills with a PSPO-A](https://engineering-leadership.hinshelwood.com/videos/why-validate-your-advanced-product-ownership-skills-with-a-pspo-a/): Validating your skills with a PSPO-A demonstrates advanced product ownership abilities that go beyond the basics, positioning you as a visionary leader who can bridge departments and drive product success. Advanced Product Owners act like mini-CEOs, integrating business, strategy, and Agile leadership to deliver greater value. Consider pursuing the PSPO-A to elevate your impact and lead innovation within your organization.
- [Transform Your Agile Training: The Power of Immersive Learning for Lasting Impact](https://engineering-leadership.hinshelwood.com/videos/transform-your-agile-training-the-power-of-immersive-learning-for-lasting-impact/): Immersive learning in Agile training connects theory directly to participants' 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.
- [2-day PSPO Versus 8-week PSPO](https://engineering-leadership.hinshelwood.com/videos/2-day-pspo-versus-8-week-pspo/): Both the 2-day and 8-week Product Owner courses provide the same core knowledge, practical insights, and a recognized credential, but differ in pace and depth. The 2-day option offers fast, focused learning, while the 8-week course allows for deeper integration with real work and ongoing feedback. Choose the format that best fits your team's learning style and how you want to apply new skills on the job.
- [DevOps Demystified: Why It's More Than Just Tools and How to Embrace Its True Value](https://engineering-leadership.hinshelwood.com/videos/devops-demystified-why-its-more-than-just-tools-and-how-to-embrace-its-true-value/): 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'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.
- [Worst Contribution from a Product Owner that You Know Of](https://engineering-leadership.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/): A product owner publicly blamed the development team during a sprint review instead of supporting them when stakeholders questioned product decisions, undermining trust and collaboration. Product owners should balance accountability to stakeholders with support for their teams, especially under pressure. Development managers should ensure product owners are prepared to defend team decisions and foster a collaborative environment.
- [How big is the gap between an average developer and a great Agile Developer?](https://engineering-leadership.hinshelwood.com/videos/how-big-is-the-gap-between-an-average-developer-and-a-great-agile-developer/): The main difference between an average and a great Agile developer is deep engagement and a commitment to continuous learning and practice. Great Agile developers are proactive, embrace setbacks as learning opportunities, and thrive in environments that support self-directed and interactive learning. To close the gap, managers should foster a culture that encourages ongoing practice, flipped learning, and autonomy in professional development.
- [8-Week Immersive Learning Course in 60 Seconds](https://engineering-leadership.hinshelwood.com/videos/8-week-immersive-learning-course-in-60-seconds/): Scrum.org’s 8-week immersive learning courses combine theory with hands-on practice, blending classroom and offline work to help participants apply new skills directly in their organizations. Learners benefit from practical assignments, collaborative feedback, and a structure designed to drive real change. Consider enrolling to quickly gain actionable strategies and improve your team’s Agile performance.
- [Best Scrum advice you ever received?](https://engineering-leadership.hinshelwood.com/videos/best-scrum-advice-you-ever-received/): The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team'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.
- [How do you know if you've got a great Sprint Goal?](https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-if-youve-got-a-great-sprint-goal/): 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.
- [How does a Scrum team decide on a Sprint goal?](https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/): 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.
- [How does a Scrum team create a sprint goal?](https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/): 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.
- [How does a Scrum team estimate what can be delivered in a Sprint?](https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-estimate-what-can-be-delivered-in-a-sprint/): 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.
- [What is a sprint goal?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-goal/): 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.
- [How critical is a Product Owner in developing a great Product Backlog?](https://engineering-leadership.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/): 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.
- [What is a product goal?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-goal/): 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.
- [How do you select the most valuable items for the sprint backlog?](https://engineering-leadership.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/): 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.
- [What is a product vision?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision/): A product vision gives your team clear direction by defining the long-term goal and desired outcome for your product, serving as a guiding reference beyond short-term objectives. It aligns everyone toward a shared future state and inspires both the team and stakeholders. Make sure your team understands and uses the product vision to guide decisions and maintain focus on the big picture.
- [What is a Sprint Backlog?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-sprint-backlog/): 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.
- [Mastering Sprint Planning: Key Principles for Agile Success](https://engineering-leadership.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/): 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.
- [What is the best application of Scrum in the world?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-best-application-of-scrum-in-the-world/): Microsoft'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.
- [What is the most common mistake in sprint planning?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/): The most common mistake in sprint planning is failing to define a clear and tangible sprint goal, which is essential for guiding the team'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.
- [Is a Product Owner an Agile Project Manager?](https://engineering-leadership.hinshelwood.com/videos/is-a-product-owner-an-agile-project-manager/): A Product Owner is not an Agile Project Manager; the Product Owner focuses on delivering product value, while an Agile Project Manager is concerned with project success. These roles have different objectives and responsibilities, and their priorities may not always align. Development managers should ensure clear role definitions to avoid confusion and maximize both product and project outcomes.
- [What is Sprint Planning?](https://engineering-leadership.hinshelwood.com/videos/what-is-sprint-planning/): 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.
- [From Control to Collaboration: How Project Managers Can Embrace Agility and Thrive](https://engineering-leadership.hinshelwood.com/videos/from-control-to-collaboration-how-project-managers-can-embrace-agility-and-thrive/): Project managers need to move from controlling every detail to supporting and collaborating with their teams to succeed with agile approaches. Embracing uncertainty, focusing on outcomes instead of outputs, and fostering open communication are key to this shift. To thrive, managers should let go of the need to have all the answers, encourage continuous learning, and be patient as their teams adapt.
- [What is a product owner?    Why are they essential?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-owner-why-are-they-essential/): A product owner is essential because they are accountable for maximizing the value delivered by the Scrum team, not just managing the backlog. They ensure alignment between stakeholders, customers, and developers by setting a clear vision and strategy based on market and user insights. To succeed, make sure your product owner is empowered to lead, deeply understands your market, and keeps everyone focused on shared goals.
- [Why does project management not work in complex environments?](https://engineering-leadership.hinshelwood.com/videos/why-does-project-management-not-work-in-complex-environments/): Traditional project management is not effective in complex environments because it relies on predictability and low variance, while complex projects involve many unknowns and frequent surprises. In these situations, traditional methods struggle to adapt and deliver results. Development managers should consider adopting Agile or Scrum approaches that are better suited to handling uncertainty and change.
- [Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/): 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.
- [What is Project Management?](https://engineering-leadership.hinshelwood.com/videos/what-is-project-management/): Project management began in the early 1900s with tools like the Gantt chart and was designed to help teams plan and deliver work efficiently. Its core principles remain relevant today, having evolved to support the fast pace of modern business. Consider exploring Agile and Scrum approaches to further enhance your team's project management skills.
- [What is Scrum?](https://engineering-leadership.hinshelwood.com/videos/what-is-scrum/): 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's productivity and adaptability.
- [What is a product backlog?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-backlog/): 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.
- [What is a product vision, and why does it matter?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-product-vision-and-why-does-it-matter/): A clear product vision is essential because it aligns teams, prevents chaos, and ensures everyone understands the direction and purpose of their work. Without it, efforts become fragmented and counterproductive. Development managers should prioritize creating and communicating a shared vision so teams can work cohesively toward common goals.
- [#1 tip for a new Scrum Master](https://engineering-leadership.hinshelwood.com/videos/1-tip-for-a-new-scrum-master/): 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.
- [Unlocking Startup Success: Why Every Entrepreneur Needs to Master Product Management Value](https://engineering-leadership.hinshelwood.com/videos/unlocking-startup-success-why-every-entrepreneur-needs-to-master-product-management-value/): Mastering product management value is critical for startup success, as it helps ensure you deliver what customers truly need and avoid common causes of failure. Key actions include focusing on value, communicating a clear vision, using practical tools, and regularly engaging with your team and customers to adapt based on feedback. Investing in product management training like the PSPO course can strengthen your foundation and support long-term growth.
- [Momentum](https://engineering-leadership.hinshelwood.com/videos/momentum/): 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.
- [What is the one thing a PSPO course forces you to focus on?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-one-thing-a-pspo-course-forces-you-to-focus-on/): The PSPO course centers on understanding and defining value, which goes beyond just financial outcomes and varies by organization. Product Owners are expected to lead in clarifying and championing what value means for their teams and stakeholders. Development managers should ensure their teams have a shared, well-communicated definition of value to guide decisions and priorities.
- [Discipline versus motivation?](https://engineering-leadership.hinshelwood.com/videos/discipline-versus-motivation/): Motivation gets Agile transformations started, but discipline is what sustains progress and ensures teams stick to Scrum practices and values. Both are essential for lasting success; motivation inspires teams to begin, while discipline keeps them committed through challenges. Development managers should foster both to drive effective Agile adoption and continuous improvement.
- [Redefining the Scrum Master: From Misconceptions to Empowering Leadership](https://engineering-leadership.hinshelwood.com/videos/redefining-the-scrum-master-from-misconceptions-to-empowering-leadership/): 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.
- [What do people love most about the 4-day training format?](https://engineering-leadership.hinshelwood.com/videos/what-do-people-love-most-about-the-4-day-training-format/): The four-day training format, which spreads sessions over four half-days instead of two full days, is popular because it prevents exhaustion, allows time for reflection, and leads to deeper learning and better questions. Participants appreciate the breaks between sessions, which help them absorb and internalize content more effectively. Consider adopting this format to improve engagement and learning outcomes in your team's training programs.
- [No go zone for Agile consultants](https://engineering-leadership.hinshelwood.com/videos/no-go-zone-for-agile-consultants/): Agile consultants should go beyond coaching by actively teaching, guiding, and sometimes directing clients to try new approaches rather than just supporting existing methods. The real value lies in driving meaningful change and growth for organizations, not just prolonging engagements. Development managers should expect Agile consultants to challenge the status quo and encourage experimentation to achieve better results.
- [How did you come to be a preferred Scrum training supplier for Microsoft?](https://engineering-leadership.hinshelwood.com/videos/how-did-you-come-to-be-a-preferred-scrum-training-supplier-for-microsoft/): Becoming a preferred Scrum training supplier for Microsoft was achieved through long-term relationship building, deep expertise in both DevOps and Scrum, and consistently delivering value that led to strong referrals and repeat clients. Engaging directly with Microsoft’s teams and culture further strengthened credibility and visibility. Development managers should focus on building trust, developing dual-domain expertise, and maintaining ongoing client relationships to achieve similar recognition.
- [Worst agile advice you've ever heard?](https://engineering-leadership.hinshelwood.com/videos/worst-agile-advice-youve-ever-heard/): 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.
- [In WIP, less is more.  Why?](https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/): Limiting work in progress leads to higher productivity because multitasking and context switching reduce efficiency and slow down progress. Keeping tasks small and focusing on finishing before starting new work helps teams deliver more in less time. Development managers should encourage teams to reduce simultaneous tasks and prioritize completing work to improve outcomes.
- [One limitation of reading a book vs attending a course](https://engineering-leadership.hinshelwood.com/videos/one-limitation-of-reading-a-book-vs-attending-a-course/): Reading books provides valuable knowledge, but they cannot answer your questions or offer interactive discussions like a course can. Courses enable active engagement, idea exchange, and collaborative learning, which are essential for deeper understanding and team growth. Consider supplementing reading with interactive training to maximize learning and team performance.
- [Mastering the Art of Product Ownership: Balancing Innovation, Customer Needs, and Team Dynamics](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-product-ownership-balancing-innovation-customer-needs-and-team-dynamics/): Effective product ownership requires balancing innovation with customer needs and team well-being, not just chasing new features. The Advanced PSPO course highlights the importance of data-informed decisions, ongoing customer engagement, and strong team collaboration. Development managers should ensure product owners focus on both delivering value and maintaining healthy team dynamics.
- [One thing a client can do to ensure a successful Agile consulting engagement](https://engineering-leadership.hinshelwood.com/videos/one-thing-a-client-can-do-to-ensure-a-successful-agile-consulting-engagement/): The most important thing a client can do for a successful Agile consulting engagement is to be open to being challenged and provoked to rethink their current ways of working. Allowing consultants to question established practices helps uncover hidden issues and drives meaningful change. Development managers should encourage honest dialogue and introspection to enable real improvement and agility.
- [How can companies derive greater benefits from training by investing in a private training course?](https://engineering-leadership.hinshelwood.com/videos/how-can-companies-derive-greater-benefits-from-training-by-investing-in-a-private-training-course/): Private training courses offer companies a safe environment for open discussion, enabling teams to address real challenges and discover untapped capabilities within their organisation. These sessions foster candid conversations and provoke valuable insights that often lead to meaningful change. Development managers should consider private training to unlock deeper team engagement and drive more effective Agile and DevOps adoption.
- [How did you know you were ready to transition from DevOps practitioner to DevOps Consultant?](https://engineering-leadership.hinshelwood.com/videos/how-did-you-know-you-were-ready-to-transition-from-devops-practitioner-to-devops-consultant/): Transitioning from DevOps practitioner to consultant often happens when your expertise is recognized by others, not just when you feel ready. Key signals include being noticed for your skills, sharing your insights publicly, and being sought out for advice, which can lead to opportunities to guide multiple organizations. To prepare, focus on demonstrating your expertise, sharing your knowledge, and engaging with the community to build visibility and influence.
- [Celebrating Jernimo Palacios: A Beacon of Mentorship and Community in Agile Practices](https://engineering-leadership.hinshelwood.com/videos/celebrating-jernimo-palacios-a-beacon-of-mentorship-and-community-in-agile-practices/): Jernimo Palacios has played a key role in advancing agile practices in Spain by sharing his expertise, building a collaborative community, and mentoring others. His openness and support have helped many navigate agile challenges and encouraged continuous improvement and knowledge sharing. Development managers should foster similar mentorship and collaboration within their teams to drive growth and adaptability.
- [Embracing Hierarchies of Competence: How Respect and Expertise Transform Workplaces](https://engineering-leadership.hinshelwood.com/videos/embracing-hierarchies-of-competence-how-respect-and-expertise-transform-workplaces/): Prioritising respect and expertise over authority creates a workplace where skilled team members are valued, leading to better collaboration, more innovative solutions, and a culture of continuous learning. Recognising and leveraging individual strengths helps teams solve complex problems more effectively. Development managers should foster environments that reward competence and encourage knowledge sharing to drive team and organisational success.
- [Why I love heirarchies of competence](https://engineering-leadership.hinshelwood.com/videos/why-i-love-heirarchies-of-competence/): Competence-based hierarchies improve decision-making by prioritising expertise over authority, encouraging teams to defer to those with proven knowledge. This approach leads to more effective solutions and a more engaged team. Development managers should consider shifting their leadership style to focus on recognising and leveraging competence within their teams.
- [Why Agile Success Lies in Principles, Not Tools: A Shift in Focus](https://engineering-leadership.hinshelwood.com/videos/why-agile-success-lies-in-principles-not-tools-a-shift-in-focus/): 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.
- [Agile leader versus traditional manager](https://engineering-leadership.hinshelwood.com/videos/agile-leader-versus-traditional-manager/): Traditional managers focus on control and task delegation, which can limit communication and slow decision-making. Agile leaders, on the other hand, empower teams, encourage open communication, and help organizations adapt quickly to change. Consider shifting from traditional management to Agile leadership to drive growth and market responsiveness.
- [Unlocking Value in DevOps: My Role as a Consultant in Driving Change and Overcoming Bottlenecks](https://engineering-leadership.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/): 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.
- [Must have trait in an Agile Consultant](https://engineering-leadership.hinshelwood.com/videos/must-have-trait-in-an-agile-consultant/): The most important trait for an Agile Consultant is tenacity, which means persistently focusing on what matters most for the organization and pushing through obstacles and resistance. Success depends on maintaining this determination after identifying key areas for change and not being discouraged by doubters. Development managers should look for consultants who demonstrate unwavering focus and resilience when driving transformation.
- [Unlocking Transformation: Why Embracing Difficult Conversations with Agile Consultants is Key to Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-transformation-why-embracing-difficult-conversations-with-agile-consultants-is-key-to-success/): Allowing agile consultants to ask tough questions and engage openly with teams is essential for real transformation, as it sparks critical thinking, learning, and accountability. Restricting dialogue stifles change and limits improvement. Development managers should foster a safe environment for open conversations and be ready to embrace discomfort to achieve lasting results.
- [Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success](https://engineering-leadership.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/): 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.
- [Unlocking Trust in Scrum: The Power of Openness and Transparency](https://engineering-leadership.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/): Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early.
- [Redefining the Scrum Master: From Boss to Empowering Facilitator](https://engineering-leadership.hinshelwood.com/videos/redefining-the-scrum-master-from-boss-to-empowering-facilitator/): 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.
- [What is Your Peeve in DevOps](https://engineering-leadership.hinshelwood.com/videos/what-is-your-peeve-in-devops/): A common misconception in DevOps is that continuous delivery is unattainable and developers cannot be trusted to deploy to production, but this belief is unfounded and limits innovation. With the right tools and mindset, teams can achieve continuous delivery and empower developers to lead the process. Development managers should challenge these myths and consider upskilling their teams to unlock faster, more reliable delivery.
- [Empowering Agile Teams: The Transformative Power of Teaching the "Why"](https://engineering-leadership.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/): 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 "why" behind processes to empower teams and boost performance.
- [Unlocking the Scrum Master's Potential: Embracing Broader Responsibilities for Agile Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-scrum-masters-potential-embracing-broader-responsibilities-for-agile-success/): 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.
- [Worst trait in unskilled scrum masters?](https://engineering-leadership.hinshelwood.com/videos/worst-trait-in-unskilled-scrum-masters/): The worst traits in unskilled Scrum Masters are acting like a boss, micromanaging, and allocating all work, which go against the true role of a Scrum Master as a facilitator who empowers and guides teams. Effective Scrum Masters enable self-organization and foster a supportive environment rather than controlling every detail. Development managers should ensure their Scrum Masters focus on facilitation and team empowerment, not command and control.
- [One critical skill for a Scrum Master and why?](https://engineering-leadership.hinshelwood.com/videos/one-critical-skill-for-a-scrum-master-and-why/): The most important skill for a Scrum Master is effective teaching, especially helping teams understand the reasons behind Agile practices rather than just the mechanics. When Scrum Masters focus on teaching the 'why,' teams become more engaged, motivated, and open to change. Development managers should encourage Scrum Masters to develop strong teaching abilities to drive successful Agile transformation.
- [Is a scrum master an agile micromanager?](https://engineering-leadership.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/): 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.
- [Transforming Agile Training into Action: Experimentation and Engagement in the Workplace](https://engineering-leadership.hinshelwood.com/videos/transforming-agile-training-into-action-experimentation-and-engagement-in-the-workplace/): Agile training is most effective when participants actively experiment with new tools and techniques in their own work environments, adapting them to fit their team’s context. Techniques like "One, Two, Four, All" foster inclusive engagement and help turn group ideas into actionable plans, even in virtual settings. Development managers should encourage their teams to try these approaches and create safe spaces for sharing, which leads to better collaboration and practical results.
- [Unlocking Rapid Delivery: Overcoming Common DevOps Challenges for Agile Success](https://engineering-leadership.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/): 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.
- [Unlocking the True Potential of Scrum: Why Professionalism Matters in Agile Teams](https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/): 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.
- [How would you like to be remembered as a Professional Scrum Trainer?  What 3 things matter most to you?](https://engineering-leadership.hinshelwood.com/videos/how-would-you-like-to-be-remembered-as-a-professional-scrum-trainer-what-3-things-matter-most-to-you/): The author wants to be remembered as a Scrum Trainer who values integrity, honesty, and approachability, always acting transparently and providing straightforward, fact-based advice. They prioritize being open and helpful, offering free consultations and building lasting relationships. Development managers should seek trainers who embody these qualities to foster trust and effective learning in their teams.
- [What is your favourite DevOps consulting outcome?](https://engineering-leadership.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/): 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 'One Engineering System' approach. Development managers should consider consolidating tools and processes to drive similar improvements in productivity and teamwork.
- [Is a PSM II certification validation of your skills, or does it develop your skill and capability as a Scrum Master?](https://engineering-leadership.hinshelwood.com/videos/is-a-psm-ii-certification-validation-of-your-skills-or-does-it-develop-your-skill-and-capability-as-a-scrum-master/): The PSM II course is designed to develop your skills and capabilities as a Scrum Master, not just validate what you already know. The class focuses on advanced facilitation techniques and deepens your understanding of Scrum Master accountability to the team, Product Owner, and organization. If you want to grow as a Scrum Master and apply practical tools with your teams, attending the course is recommended over just taking the assessment.
- [Essential Skills Every Agile Consultant Needs: Mastering Domain Knowledge, Active Listening, and Honest Communication](https://engineering-leadership.hinshelwood.com/videos/essential-skills-every-agile-consultant-needs-mastering-domain-knowledge-active-listening-and-honest-communication/): Agile consultants are most effective when they understand the business domain, actively listen to all team members to uncover gaps in transparency, and communicate difficult truths honestly, even to leadership. These skills help build trust and drive meaningful change. Development managers should ensure consultants are empowered to ask tough questions and share candid feedback to improve team performance.
- [What are the hierarchies of competence vs control?  Why does this matter?](https://engineering-leadership.hinshelwood.com/videos/what-are-the-hierarchies-of-competence-vs-control-why-does-this-matter/): Traditional hierarchies based on control slow down decision-making and often promote people beyond their competence, while hierarchies based on competence allow the most capable individuals to lead in real time, enabling faster and more effective responses to market changes. Shifting to a competence-based structure can create a more agile, engaged, and market-responsive organisation. Development managers should consider moving away from rigid top-down models and foster dynamic leadership based on expertise to improve speed and adaptability.
- [What does your dream agile consulting week look like?](https://engineering-leadership.hinshelwood.com/videos/what-does-your-dream-agile-consulting-week-look-like/): Applied Professional Scrum (APS) helps teams focus on delivering a working product every iteration and identify unhelpful practices that slow them down. The "Barnacle Exercise" is a practical tool for teams to shed unnecessary habits and create a clear roadmap for agile transformation. Development managers should consider APS to build more effective, authentic Scrum teams and drive continuous improvement.
- [Unlocking Effective Product Development: How a Hypothesis-Driven Approach Transforms User Experience](https://engineering-leadership.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/): 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.
- [Why Many Scrum Masters Stall at PSM1: The Crucial Role of Passion in Professional Growth](https://engineering-leadership.hinshelwood.com/videos/why-many-scrum-masters-stall-at-psm1-the-crucial-role-of-passion-in-professional-growth/): Many Scrum Masters do not progress beyond the PSM1 certification because they lack genuine interest and focus only on obtaining the certificate rather than improving their skills. Those who advance are passionate, actively seek knowledge, and practice their craft, which leads to greater team effectiveness and value creation. Development managers should encourage ongoing learning and engagement to foster deeper expertise and professional growth in their Scrum Masters.
- [What is the difference between a newbie scrum master and a professional Scrum Master?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-difference-between-a-newbie-scrum-master-and-a-professional-scrum-master/): There is no real distinction between a newbie and a professional Scrum Master; once someone takes on the role and is accountable for the team's effectiveness, they are expected to act professionally and add value. The key is to fully embrace the responsibilities, focus on improving team productivity, and avoid ineffective practices. Development managers should ensure Scrum Masters are empowered to take the role seriously and support their ongoing learning.
- [Is Your Scrum Master Struggling? Discover When to Choose an Agile Process Simulation Workshop](https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/): 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.
- [Navigating My Most Memorable Challenge as an Agile Consultant: Lessons in Readiness and Engagement](https://engineering-leadership.hinshelwood.com/videos/navigating-my-most-memorable-challenge-as-an-agile-consultant-lessons-in-readiness-and-engagement/): Organisations must be ready and willing to engage for agile consulting to be effective; without this, even the best advice will be ignored and no real progress will happen. Repeated experiences showed that lack of readiness and follow-through leads to wasted effort and stagnation. Development managers should ensure their teams are prepared to listen and act before bringing in external help.
- [How will a PSM II course challenge your assumptions the most?](https://engineering-leadership.hinshelwood.com/videos/how-will-a-psm-ii-course-challenge-your-assumptions-the-most/): The PSM II course challenges common misconceptions about the Scrum Master role, showing that it is much more than being a Jira admin or a problem solver; instead, it focuses on empowering teams to be self-sufficient and highlights the value of subtle, behind-the-scenes leadership. The course helps Scrum Masters evolve from basic task facilitators to advanced guides who foster team autonomy and sustainable practices. Development managers should consider this course to deepen their understanding of effective Scrum leadership and drive stronger team performance.
- [The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap](https://engineering-leadership.hinshelwood.com/videos/the-truth-about-newbie-vs-professional-scrum-masters-bridging-the-experience-gap/): 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.
- [Why is becoming a Scrum Master a great career option?](https://engineering-leadership.hinshelwood.com/videos/why-is-becoming-a-scrum-master-a-great-career-option/): Becoming a Scrum Master is a strong first step for team members aiming for leadership roles, as it allows you to demonstrate leadership by improving team effectiveness and taking on new responsibilities. The role is widely recognized and respected as a starting point on the leadership ladder, regardless of your current specialty. Consider pursuing Scrum Master training to build these skills and advance your career in software development leadership.
- [Can organisations run an Applying Professional Scrum workshop? How would that help them?](https://engineering-leadership.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/): 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.
- [When should an organisation consider a professional agile consultant?](https://engineering-leadership.hinshelwood.com/videos/when-should-an-organisation-consider-a-professional-agile-consultant/): Organisations should consider a professional agile consultant when facing significant project failure or when seeking continuous improvement, as an external expert can provide valuable perspective and help identify opportunities for change. It is important to avoid being swayed by consultants who lack real agile expertise and instead choose someone with proven experience. Whether recovering from setbacks or aiming to enhance performance, bringing in the right agile consultant can help teams evolve and deliver better results.
- [What was your best day as an Agile consultant?](https://engineering-leadership.hinshelwood.com/videos/what-was-your-best-day-as-an-agile-consultant/): A brief Agile and Scrum engagement with a Java development team led to lasting positive change, as confirmed by a team member’s email seven years later describing its ongoing impact on their team and organization. The experience showed that even short, focused workshops can be a catalyst for significant transformation. Consider investing in Agile and Scrum training to spark similar long-term improvements in your teams.
- [Mastering Scrum: Effective Planning and Prioritisation for Agile Success](https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/): Effective Scrum planning and prioritisation require aligning work with business goals, regularly communicating with stakeholders, and keeping the product backlog lean and focused on near-term priorities. Use a simple value, risk, and size formula to help order backlog items, and continuously adjust based on customer data and outcomes. Keep your backlog manageable and iterate often to ensure your team delivers meaningful results that support business objectives.
- [Would you recommend the APS course to a newbie scrum team, and Why?](https://engineering-leadership.hinshelwood.com/videos/would-you-recommend-the-aps-course-to-a-newbie-scrum-team-and-why/): The APS course is highly recommended for new Scrum teams because it simplifies Scrum concepts, helps teams identify and address necessary organizational changes, and empowers both team members and leaders to drive improvements. Key benefits include creating an actionable Organizational Change Backlog and fostering team engagement and alignment. Development managers should consider enrolling their teams to ensure a strong start with Scrum and ongoing alignment with agile principles.
- [How good is the APSPO course in helping leaders determine product direction and Why?](https://engineering-leadership.hinshelwood.com/videos/how-good-is-the-apspo-course-in-helping-leaders-determine-product-direction-and-why/): The APSPO course does not directly tell leaders how to set product direction, but it provides valuable tools and frameworks that help them identify gaps and strengthen their approach. It highlights six key roles for product owners, encouraging a balance between customer focus, innovation, collaboration, and decisive leadership. Leaders should use the course to broaden their skills and continuously improve their product ownership capabilities.
- [How does someone become an Agile consultant?](https://engineering-leadership.hinshelwood.com/videos/how-does-someone-become-an-agile-consultant/): Becoming an Agile consultant requires deep expertise in your own field first, then integrating Agile practices and building a reputation as an Agile expert within that context. Success comes from mastering your domain, learning to abstract Agile principles for broader application, and gradually expanding into new industries as your experience grows. Start by applying Agile in your area, gain recognition, and only then consider consulting in other sectors.
- [What is the most interesting outcome you have achieved as an agile consultant?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-interesting-outcome-you-have-achieved-as-an-agile-consultant/): The most interesting outcome as an agile consultant was seeing how full company-wide commitment to agile, from leadership to frontline staff, led to lasting transformation and improved ownership at Backcountry, while lack of buy-in at another company caused agile efforts to fail and key advocates to leave. Key insights are that success depends on broad engagement and leadership support, and that agile can create a ripple effect across organizations. Development managers should ensure all levels of the company are involved and committed to agile practices for meaningful and sustainable change.
- [What is your feeling on creating Agile apprenticeships?](https://engineering-leadership.hinshelwood.com/videos/what-is-your-feeling-on-creating-agile-apprenticeships/): Creating Agile apprenticeships is a natural next step from immersive learning, as ongoing engagement with trainees has organically formed a community of Agile learners. Key initiatives include open invitations for informal discussions, bonus consulting time, and a mentor-apprentice model that supports continuous growth and knowledge sharing. Development managers should consider fostering similar environments to encourage ongoing learning and mentorship within their teams.
- [Transforming Training: How Immersive Learning and DevOps Drive Real Value in Organisations](https://engineering-leadership.hinshelwood.com/videos/transforming-training-how-immersive-learning-and-devops-drive-real-value-in-organisations/): Shifting to immersive, hands-on training and spreading sessions over a longer period leads to better knowledge retention and practical application for teams, even if it means fewer classes and less immediate revenue. Prioritising value creation over short-term gains results in more satisfied clients and stronger organisational outcomes. Development managers should consider adopting training approaches that focus on real learning impact rather than volume.
- [What are immersive training courses?](https://engineering-leadership.hinshelwood.com/videos/what-are-immersive-training-courses/): Immersive training courses move beyond traditional or flipped classroom formats by having participants apply new concepts directly in their own work environments, then return to share and learn from real experiences. This approach, often spread over several weeks, leads to deeper engagement and more practical learning outcomes. Consider adopting immersive training to drive real change and knowledge retention within your teams.
- [Why do you prefer agile consulting over agile coaching?](https://engineering-leadership.hinshelwood.com/videos/why-do-you-prefer-agile-consulting-over-agile-coaching/): Agile consulting is preferred over coaching because it empowers internal leadership, avoids creating long-term dependencies, and leads to more sustainable change. Consultants work intensively for a short period to spark transformation, then step back so teams can take ownership and continue improving on their own. Development managers should consider consulting to build self-reliant teams and lasting results rather than relying on ongoing external support.
- [Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations](https://engineering-leadership.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/): 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.
- [Why do you think that 4 half days is a better format than 2 full days?](https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-that-4-half-days-is-a-better-format-than-2-full-days/): Spreading training over four half days instead of two full days leads to better knowledge retention, more opportunities for reflection, and improved practical application. This approach reduces cognitive overload and supports continuous learning and improvement. Consider adopting or experimenting with more flexible training formats to maximize learning outcomes for your teams.
- [What is the difference between resource efficiency and flow efficiency?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-difference-between-resource-efficiency-and-flow-efficiency/): Resource efficiency focuses on maximizing how much each team member produces, while flow efficiency looks at how smoothly work moves through the entire process. Overemphasizing resource efficiency can lead to burnout and bottlenecks, but balancing both approaches helps create a healthier, more productive workflow. Review your current processes to ensure you are not just keeping people busy but also delivering value efficiently across the system.
- [What is your best advice for becoming a Scrum Master outside software engineering?](https://engineering-leadership.hinshelwood.com/videos/what-is-your-best-advice-for-becoming-a-scrum-master-outside-software-engineering/): Certifications can help you get noticed as a Scrum Master outside software engineering, but real value comes from applying Scrum principles and building practical skills. Focus on validated learning through assessments, training, and hands-on experience to bridge the gap between knowledge and expertise. Invest time in mastering the material and demonstrating your understanding in real situations to advance your career.
- [Why Pursuing Agile Certifications is Your Key to Career Advancement](https://engineering-leadership.hinshelwood.com/videos/why-pursuing-agile-certifications-is-your-key-to-career-advancement/): Agile certifications help validate foundational knowledge and make it easier for employers to identify qualified candidates, but real career growth comes from applying what you learn and committing to continuous improvement. Certifications like PSM1 serve as a useful screening tool and provide targeted feedback for further development. To advance your career, use certifications as a starting point and invest in ongoing learning and practical experience.
- [Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course](https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-master-journey-key-insights-from-the-advanced-psm-course/): 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.
- [What is the most common Aha moment people have in a scrum course?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-common-aha-moment-people-have-in-a-scrum-course/): The most common realization in scrum courses is understanding the deep purpose behind each element of the scrum framework, especially its foundation in empiricism, rather than just following procedures. Many experienced practitioners discover they have been missing the true value of scrum by not connecting its events and artefacts to their intended outcomes. To unlock high performance, teams should focus on mastering the fundamentals and intentionally applying scrum’s principles, not just its mechanics.
- [From Developer to Agile Advocate: How My Journey Unveiled the Power of Scrum and DevOps](https://engineering-leadership.hinshelwood.com/videos/from-developer-to-agile-advocate-how-my-journey-unveiled-the-power-of-scrum-and-devops/): 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.
- [Navigating Client Needs: How Agile Consultants Can Uncover True Value Beyond Initial Requests](https://engineering-leadership.hinshelwood.com/videos/navigating-client-needs-how-agile-consultants-can-uncover-true-value-beyond-initial-requests/): Clients often think they know what they need, but the real value comes from consultants who dig deeper to uncover their true challenges and guide them toward solutions that deliver real benefits. Focusing on sustainable growth, quality over quantity, and selective project engagement helps avoid common pitfalls like overcommitment and declining standards. Development managers should look beyond surface requests and work with consultants to identify and address the root issues for lasting improvement.
- [Why is Scrum so easy to understand but incredibly hard to master?](https://engineering-leadership.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/): 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.
- [If you could teach just one thing about Scrum, what would it be?](https://engineering-leadership.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/): 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's ability to learn and adapt quickly, as Scrum reveals problems but does not solve them for you.
- [Why did you choose the Scrum.Org track rather than the Scrum Alliance track?](https://engineering-leadership.hinshelwood.com/videos/why-did-you-choose-the-scrum-org-track-rather-than-the-scrum-alliance-track/): The author chose Scrum.Org over Scrum Alliance due to its strong professionalism, integrity, and community focus, as well as its fair certification policies that avoid recurring fees and restrictive progression paths. Scrum.Org encourages continuous improvement and knowledge sharing among trainers, which benefits both individuals and organizations. Development managers should consider Scrum.Org for its flexible, value-driven approach to Scrum training and certification.
- [What is DevOps and how is it different to Agile?](https://engineering-leadership.hinshelwood.com/videos/what-is-devops-and-how-is-it-different-to-agile/): DevOps and Agile are fundamentally the same, both aiming to deliver value to customers and organizations by focusing on rapid feedback, continuous improvement, and systems thinking. The main difference is perspective, with each emphasizing different aspects of the delivery process, but both require the right tools and practices to optimize the whole system. Development managers should ensure Agile and DevOps work together to maximize value and improve outcomes across the organization.
- [What is Taylorism and how did it influence project management?](https://engineering-leadership.hinshelwood.com/videos/what-is-taylorism-and-how-did-it-influence-project-management/): Taylorism established command-and-control management focused on efficiency, standardization, and strict hierarchies, which shaped traditional project management and works well for simple or repeatable tasks. However, this approach fails in complex environments where creativity, collaboration, and adaptability are needed, leading to the rise of Agile methods. Development managers should recognize where traditional project management fits and adopt Agile practices for complex, uncertain projects to stay effective.
- [Why do you think the PSU course has become so popular for product development?](https://engineering-leadership.hinshelwood.com/videos/why-do-you-think-the-psu-course-has-become-so-popular-for-product-development/): 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.
- [How important is DevOps in continuous delivery of value to customers?](https://engineering-leadership.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/): 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.
- [What is a common mistake made by rookie agile consultants?](https://engineering-leadership.hinshelwood.com/videos/what-is-a-common-mistake-made-by-rookie-agile-consultants/): Rookie agile consultants often make the mistake of rigidly applying frameworks like Scrum without understanding or addressing the unique needs and goals of each team, believing that simply following the rules will guarantee success. This dogmatic approach overlooks the importance of context, empiricism, and helping teams understand the purpose behind agile practices. Development managers should ensure agile adoption is tailored to their team's specific challenges and objectives, focusing on continuous learning and adaptation rather than just process compliance.
- [What would you advise a scrum team to do in their first 4 weeks?](https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/): 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.
- [How do you think Agile is evolving since its inception in 2001?](https://engineering-leadership.hinshelwood.com/videos/how-do-you-think-agile-is-evolving-since-its-inception-in-2001/): 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.
- [2023 is predicted to be a very tough year. What do you think will be needed to win and improve?](https://engineering-leadership.hinshelwood.com/videos/2023-is-predicted-to-be-a-very-tough-year-what-do-you-think-will-be-needed-to-win-and-improve/): To succeed in a challenging year, organizations must clarify their strategy, focus on both customer and employee satisfaction, and invest in effective ways of working. Key actions include strengthening product ownership, conducting thorough market analysis, and providing agile training and practice for teams. Prioritizing these areas will help maintain competitiveness and performance even in tough market conditions.
- [In high competition markets, how does scrum product development help acquire and retain customers?](https://engineering-leadership.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/): 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.
- [How does scrum help leadership teams pick the most valuable work to focus on?](https://engineering-leadership.hinshelwood.com/videos/how-does-scrum-help-leadership-teams-pick-the-most-valuable-work-to-focus-on/): Scrum does not help leadership teams choose the most valuable work; it highlights issues and provides feedback to inform decision-making, but leaders must set priorities based on business understanding. Agile frameworks like Scrum are most effective when leaders have a clear vision and use them to validate ideas, improve feedback loops, and optimize delivery. Leadership should focus on defining strategic goals, while Scrum helps teams deliver and refine solutions that align with those goals.
- [Why are recessions a great time for organizations to evaluate the opportunity of agile?](https://engineering-leadership.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/): 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.
- [How would you help organizations pitch the opportunity of agile internally?](https://engineering-leadership.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/): 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.
- [What is the most valuable thing you have learned through training people?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-most-valuable-thing-you-have-learned-through-training-people/): 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.
- [Why did so many of the early agile transformations fail?](https://engineering-leadership.hinshelwood.com/videos/why-did-so-many-of-the-early-agile-transformations-fail/): 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.
- [What is the hardest part of working with a brand-new scrum team?](https://engineering-leadership.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/): 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.
- [Debunking the Scrum Myth: Why "Twice the Work in Half the Time" is a Misleading Promise](https://engineering-leadership.hinshelwood.com/videos/debunking-the-scrum-myth-why-twice-the-work-in-half-the-time-is-a-misleading-promise/): The idea that Scrum enables teams to do twice the work in half the time is misleading and sets unrealistic expectations; Scrum is about delivering greater value to customers, not just increasing output. Focusing on outcomes rather than the number of features helps teams avoid burnout and frustration, and practices should be adapted to each team's context rather than following so-called best practices. Development managers should prioritize value delivery and continuous improvement over chasing productivity slogans.
- [Why is Satya Nadella a better example of agile leadership than Steve Jobs?](https://engineering-leadership.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/): 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.
- [How effective is scrum training via digital delivery?](https://engineering-leadership.hinshelwood.com/videos/how-effective-is-scrum-training-via-digital-delivery/): While in-person Scrum training offers slightly more engagement and interaction, digital delivery is nearly as effective and brings unique advantages such as greater accessibility, exposure to global perspectives, and alignment with how remote teams now work. Online courses allow immediate application of learning, foster diverse collaboration, and introduce valuable digital tools. Development managers should consider digital training as a practical, effective option that fits modern team dynamics and broadens participation.
- [How much of an impact can a strong, skilled product owner have?](https://engineering-leadership.hinshelwood.com/videos/how-much-of-an-impact-can-a-strong-skilled-product-owner-have/): A strong, skilled product owner is critical for turning engineering output into valuable solutions that solve real customer problems and drive business impact. Great product owners look ahead, anticipate market and customer needs, and enable teams to deliver the right features at the right time, avoiding the trap of just building more features. To maximize effectiveness, empower your product owner to focus on strategic value and proactive discovery, not just backlog management.
- [What does a poor scrum team look, act and feel like?](https://engineering-leadership.hinshelwood.com/videos/what-does-a-poor-scrum-team-look-act-and-feel-like/): 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.
- [What would be an example of a great agile consulting outcome for a client?](https://engineering-leadership.hinshelwood.com/videos/what-would-be-an-example-of-a-great-agile-consulting-outcome-for-a-client/): A great agile consulting outcome is helping an organization become consistently adaptable to both unexpected opportunities and threats by removing barriers to responsiveness and fostering a culture of flexibility and decentralized decision-making. Key results include shifting from rigid, top-down management to empowered, autonomous teams and building resilience throughout the organization, not just in isolated groups. Development managers should focus on enabling this mindset and structure across all levels to achieve lasting agility and improved business results.
- [What are some big red flags when hiring an agile consultant?](https://engineering-leadership.hinshelwood.com/videos/what-are-some-big-red-flags-when-hiring-an-agile-consultant/): When hiring an agile consultant, watch out for those who are not active in the agile community, lack deep understanding of core agile concepts, or come from consultancies that prioritize volume over quality and expertise. These red flags suggest the consultant may not be able to adapt to your team's needs or deliver meaningful results. Take time to assess their community involvement, knowledge, and the consultancy's focus before making a decision.
- [Unlocking Organisational Potential: The Transformative Power of a Great Consultant](https://engineering-leadership.hinshelwood.com/videos/unlocking-organisational-potential-the-transformative-power-of-a-great-consultant/): A great consultant can quickly identify and address core organisational issues by providing an honest, external perspective and actionable recommendations, often leading to immediate improvements. Their value lies in bridging gaps between leadership and teams, catalysing cultural change, and helping organisations move beyond common challenges. If your teams are struggling with transformation or alignment, consider bringing in a consultant to accelerate progress and unlock your organisation’s potential.
- [Why does Agile focus on values and principles rather than a prescribed set of steps?](https://engineering-leadership.hinshelwood.com/videos/why-does-agile-focus-on-values-and-principles-rather-than-a-prescribed-set-of-steps/): 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.
- [From Software Engineer to Scrum Trainer: How My Journey Shapes Effective DevOps Training](https://engineering-leadership.hinshelwood.com/videos/from-software-engineer-to-scrum-trainer-how-my-journey-shapes-effective-devops-training/): 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.
- [What will you learn on the professional scrum master course?](https://engineering-leadership.hinshelwood.com/videos/what-will-you-learn-on-the-professional-scrum-master-course/): 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' ability to deliver value and navigate complexity.
- [How does the APS course help people apply scrum effectively?](https://engineering-leadership.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/): 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.
- [How is agile product development different to waterfall project management?](https://engineering-leadership.hinshelwood.com/videos/how-is-agile-product-development-different-to-waterfall-project-management/): 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.
- [Learn Scrum with Minecraft Education Edition](https://engineering-leadership.hinshelwood.com/videos/learn-scrum-with-minecraft-education-edition/): Using Minecraft Education Edition in Scrum training creates a more realistic and engaging environment for learning complex product development compared to traditional website-building exercises. This approach ensures full team participation, better simulates real-world complexity, and is accessible across devices. Development managers should ensure participants can install Minecraft Education on an unrestricted device and join sessions off VPN for the best experience.
- [Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft](https://engineering-leadership.hinshelwood.com/videos/embrace-the-chaos-transforming-scrum-learning-through-experience-and-minecraft/): 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.
- [In what circumstances is agile consulting appropriate?](https://engineering-leadership.hinshelwood.com/videos/in-what-circumstances-is-agile-consulting-appropriate/): Agile consulting is most effective when used for short-term engagements that build internal leadership and agile capabilities, rather than relying on long-term external coaches which can create dependency and erode core competencies. The main value lies in helping teams quickly identify and solve key problems, enabling sustainable improvement and momentum. Development managers should focus on developing internal agile leaders and use consultants to kickstart transformation, not as a permanent solution.
- [How does Naked Agility select associate Scrum Trainers?](https://engineering-leadership.hinshelwood.com/videos/how-does-naked-agility-select-associate-scrum-trainers/): Naked Agility selects associate Scrum Trainers based on real-world agile experience, proven problem-solving skills, and the ability to engage and inspire teams, not just theoretical knowledge. Trainers are evaluated through co-training and must demonstrate deep expertise as practitioners, coaches, or consultants who can address industry-specific challenges and empower teams to apply agile effectively. If you need agile training or coaching from experienced professionals who understand complex environments, consider reaching out to Naked Agility.
- [Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events](https://engineering-leadership.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/): 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.
- [Unlocking Agile Success: How Empirical Models Transform Project Outcomes](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/): 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.
- [Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development](https://engineering-leadership.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/): 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.
- [Transform Your Team with Flipped Learning: Unlocking Agility at Naked Agility Limited](https://engineering-leadership.hinshelwood.com/videos/transform-your-team-with-flipped-learning-unlocking-agility-at-naked-agility-limited/): Naked Agility Limited uses a flipped learning approach that combines self-paced study with interactive workshops, enabling teams to deeply understand agile concepts and prepare for certification. Participants receive personalised coaching and access to a supportive community, fostering a people-first culture and continuous improvement. Development managers can consider this training to boost team engagement, learning, and agility.
- [Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey](https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-the-professional-scrum-product-owner-course-transforms-your-agile-journey/): The Professional Scrum Product Owner course provides practical, hands-on training that helps product owners maximise product value, make effective decisions, and adopt modern agile practices. Participants benefit from interactive sessions, ongoing support, and access to a peer community, ensuring skills are applied and developed beyond the classroom. Development managers should consider this course to strengthen product leadership and drive better outcomes in their teams.
- [Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course](https://engineering-leadership.hinshelwood.com/videos/mastering-the-art-of-scaling-scrum-insights-from-the-scaled-professional-scrum-course/): 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.
- [Unlocking Your Potential: Transformative Training for Aspiring Scrum Masters](https://engineering-leadership.hinshelwood.com/videos/unlocking-your-potential-transformative-training-for-aspiring-scrum-masters/): 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.
- [Unlocking Business Agility: Join Our Dynamic Monthly Discussions for Real-World Insights](https://engineering-leadership.hinshelwood.com/videos/unlocking-business-agility-join-our-dynamic-monthly-discussions-for-real-world-insights/): Business Agility Raw is a monthly, participant-driven discussion forum where software development leaders can share real-world challenges and solutions related to business agility. The sessions use a collaborative format to ensure relevant, actionable insights and diverse perspectives, supporting continuous learning. Consider joining on the fourth Wednesday each month to connect with peers and gain practical ideas you can apply immediately.
- [Live Virtual Professional Scrum Product Owner in 5 minutes!](https://engineering-leadership.hinshelwood.com/videos/live-virtual-professional-scrum-product-owner-in-5-minutes/): This training offers a condensed overview of the Professional Scrum Product Owner course, covering four half-days in just five minutes. If you need more detail, free live-streamed workshops are available on their channel. Consider watching the timelapse or joining a workshop to quickly assess if the course fits your team's needs.
- [Free Workshop 04: Introduction to Sprint Reviews [Review & Retrospective]](https://engineering-leadership.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/): The workshop introduced key concepts of Sprint Reviews using interactive tools and received very positive participant feedback, despite technical audio issues during the live stream. The main learning was to check both music and voice before sessions to avoid similar problems, and future events will use a new community platform for easier access. Development managers should ensure thorough technical checks before virtual workshops and consider leveraging interactive formats for better engagement.
- [A view into the PSM Training from Scrum.org](https://engineering-leadership.hinshelwood.com/videos/a-view-into-the-psm-training-from-scrum-org/): The Scrum.org PSM training provides a practical overview of Scrum principles and how to apply them effectively in real projects. Key insights include the importance of understanding Scrum roles, events, and artifacts, and how to foster team collaboration for better outcomes. Development managers should consider this training to help their teams adopt Scrum practices more successfully.
- [Embracing Change: Why Agile Evolution is the Key to Thriving in a Rapidly Shifting World](https://engineering-leadership.hinshelwood.com/videos/embracing-change-why-agile-evolution-is-the-key-to-thriving-in-a-rapidly-shifting-world/): Agility is not a one-time transformation but an ongoing process of experimentation and adaptation, essential for surviving in today’s rapidly changing business environment. Traditional management practices from the industrial era are no longer effective; leaders must foster continuous learning, embrace failure, and evolve their organisations iteratively. To stay competitive, development managers should prioritise experimentation and empower teams to adapt quickly rather than relying on outdated processes.
- [Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism](https://engineering-leadership.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/): 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.
- [Unlocking Agile Leadership: Transform Your Skills with Scrum.org's Essentials Workshop](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-leadership-transform-your-skills-with-scrum-orgs-essentials-workshop/): The Scrum.org Professional Agile Leadership Essentials workshop helps leaders shift from traditional management to effective agile leadership by providing hands-on learning, practical coaching skills, and tools for driving cultural change. It emphasises organisational alignment and collaboration, enabling leaders to support agile teams and measure the impact of agility. Attending this workshop can help you guide your teams through agile transformation and improve your organisation’s responsiveness and performance.
- [Challenging the Tyranny of Taylorism: Embracing True Agility in the Workplace](https://engineering-leadership.hinshelwood.com/videos/challenging-the-tyranny-of-taylorism-embracing-true-agility-in-the-workplace/): Many organizations still follow outdated management styles that prioritize efficiency over creativity, which stifles innovation and true agility. Overemphasis on metrics, lack of team autonomy, and rigid processes are signs of this problem and can lead to superficial agile adoption. Development managers should focus on fostering genuine collaboration, flexibility, and a culture that values creativity to achieve real agility.
- [Transforming Enterprises: How DevOps Drives Collaboration and Continuous Improvement](https://engineering-leadership.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/): DevOps can transform enterprise software teams by fostering collaboration, encouraging continuous improvement, and enabling automation, which together lead to faster delivery and higher quality. Focusing on a customer-centric approach helps teams respond quickly to feedback and market changes. Development managers should prioritize building a culture that supports these principles to drive meaningful organizational change.
- [Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work](https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/): 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.
- [Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture](https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/): 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.
- [Unlocking Agile Success: Your Guide to the Professional Scrum Foundations Class and PSM I Assessment](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-your-guide-to-the-professional-scrum-foundations-class-and-psm-i-assessment/): 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.
- [Unlocking Agile Success: Embrace Continuous Forecasting and Transform Your Training Experience](https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/): 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.
- [Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective](https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/): 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.
- [Maximise Your Virtual Classroom Experience: Essential Tech Tips for Scrum Training](https://engineering-leadership.hinshelwood.com/videos/maximise-your-virtual-classroom-experience-essential-tech-tips-for-scrum-training/): Using Microsoft Teams for video conferencing and Mural for digital whiteboarding can significantly improve engagement and collaboration in virtual Scrum training. Ensuring participants are comfortable with these tools through a tech check before class helps reduce confusion and maximises learning time. Development managers should encourage their teams to familiarise themselves with these platforms ahead of training to ensure a smoother and more productive experience.
- [Transforming Management into Agile Leadership: The Power of Virtual Training](https://engineering-leadership.hinshelwood.com/videos/transforming-management-into-agile-leadership-the-power-of-virtual-training/): Virtual agile leadership training offers significant benefits, including fostering true leadership over traditional management, encouraging team self-organisation, and focusing on value delivery. Small, diverse virtual classes enable deeper engagement, richer learning, and cost-effective, flexible participation using effective technology. Development managers should consider virtual training to upskill teams, broaden perspectives, and support continuous learning in an evolving agile landscape.
- [Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape](https://engineering-leadership.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/): 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.
- [Navigating the Agile Landscape: Understanding the Key Differences Between Product Owners and Project Managers](https://engineering-leadership.hinshelwood.com/videos/navigating-the-agile-landscape-understanding-the-key-differences-between-product-owners-and-project-managers/): Product Owners focus on delivering product value and prioritising work based on user needs, while Project Managers concentrate on delivering projects on time and within budget; this distinction is key as organisations move to agile ways of working. Adopting Scrum impacts not just teams but also organisational structure, leadership style, and how value is delivered, requiring a shift from traditional hierarchies to empowered, cross-functional teams. As teams mature, they should move beyond story points to optimise flow and continuous delivery, so managers should support this evolution to improve agility and responsiveness.
- [10th April 2020 - Office Hours \ Ask me Anything](https://engineering-leadership.hinshelwood.com/videos/10th-april-2020-office-hours-ask-me-anything/): Martin, an expert in Scrum and Azure DevOps, is hosting an open Q&A session where you can ask about DevOps, agility, or related topics. You can submit questions publicly or privately. This is a chance to get expert advice on your current challenges, so consider preparing your key questions in advance.
- [Mastering Agile in a Distributed World: Tools and Strategies for Effective Team Management](https://engineering-leadership.hinshelwood.com/videos/mastering-agile-in-a-distributed-world-tools-and-strategies-for-effective-team-management/): 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.
- [30th March 2020 - Office Hours \ Ask Me Anything](https://engineering-leadership.hinshelwood.com/videos/30th-march-2020-office-hours-ask-me-anything/): Martin, an expert in Scrum and Azure DevOps, is hosting an open Q&A session where you can ask about DevOps, agility, or related topics. You can submit questions publicly or privately. This is a chance to get direct advice on your team’s challenges from a recognized industry professional.
- [Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World](https://engineering-leadership.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/): Remote work requires strong communication, the right tools, and a focus on delivering value, even when teams are not co-located. Improving feedback loops, observing team dynamics through activities like games, and integrating UX early in Agile processes all help teams collaborate better and build the right products. Development managers should prioritize open communication, continuous process improvement, and shared accountability for user experience to help their teams thrive in a digital environment.
- [Empowering Development Teams: Cultivating an Agile Mindset for Lasting Quality](https://engineering-leadership.hinshelwood.com/videos/empowering-development-teams-cultivating-an-agile-mindset-for-lasting-quality/): 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.
- [Navigating Agile Learning: Embrace Change and Community in Uncertain Times](https://engineering-leadership.hinshelwood.com/videos/navigating-agile-learning-embrace-change-and-community-in-uncertain-times/): 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.
- [Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape](https://engineering-leadership.hinshelwood.com/videos/mastering-agility-balancing-engineering-excellence-and-effective-processes-in-a-rapidly-changing-business-landscape/): Balancing strong engineering practices with effective processes is essential for thriving in today’s fast-changing business environment; neglecting either can lead to costly failures or products that miss user needs. Success with Agile requires more than process changes, it demands a culture of transparency, collaboration, and continuous learning, along with well-trained product owners and meaningful outcome-focused metrics. Development managers should invest in engineering excellence, support ongoing training, and adopt an experimental, evidence-based approach to drive real agility and business value.
- [Scaling Agility: Navigating the Dragons of Change in the Future of Work](https://engineering-leadership.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/): 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.
- [Unmasking Agile: How to Spot Genuine Practices Amidst the Myths](https://engineering-leadership.hinshelwood.com/videos/unmasking-agile-how-to-spot-genuine-practices-amidst-the-myths/): 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.
- [Mastering Azure DevOps Migration Tools: Your Ultimate Guide to Seamless Migrations](https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-migration-tools-your-ultimate-guide-to-seamless-migrations/): 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.
- [Mastering VSTS Sync Migration Tools: Your Ultimate Guide to Seamless TFS to VSTS Transitions](https://engineering-leadership.hinshelwood.com/videos/mastering-vsts-sync-migration-tools-your-ultimate-guide-to-seamless-tfs-to-vsts-transitions/): When migrating from TFS to VSTS, use Microsoft's migration service for full database moves, but choose VSTS sync migration tools if you need flexibility to migrate or restructure specific projects. The sync tools allow selective migration, field mapping, and bulk updates, and are supported by a strong community; install them via Chocolatey and always test with a small dataset first. Decide which approach fits your needs, and leverage available documentation and community support for a smooth migration.
- [Unlocking Human Potential: How Health and Perspective Fuel Innovation in Tech](https://engineering-leadership.hinshelwood.com/videos/unlocking-human-potential-how-health-and-perspective-fuel-innovation-in-tech/): Prioritising health and well-being boosts innovation and leadership in tech by improving perspective and fostering creativity. Supporting hands-on builders, embracing diverse viewpoints, and engaging with sceptics lead to stronger outcomes. Development managers should encourage healthy habits, value unique perspectives, and build deeper connections within their teams to drive better results.
- [Transforming Chaos into Collaboration: How a Common Framework Can Revolutionise Your Team's Dynamics](https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-teams-dynamics/): Introducing a common framework and structured backlog helped transform a chaotic team environment into one marked by better collaboration, clearer communication, and increased trust. Teams benefited from a shared language, improved confidence, and more effective problem-solving, while regular feedback channels boosted morale and engagement. Development managers should consider adopting structured frameworks and open communication practices to drive positive change and sustain team momentum.
- [Embracing Process Improvement: How Understanding Scrum Transformed a Developer's Mindset](https://engineering-leadership.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developers-mindset/): 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.
- [Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm](https://engineering-leadership.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/): 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.
- [Streamline Your Release Management Setup: A Step-by-Step Guide to Simplifying Server, Client, and Agent Installation](https://engineering-leadership.hinshelwood.com/videos/streamline-your-release-management-setup-a-step-by-step-guide-to-simplifying-server-client-and-agent-installation/): Learn how to quickly install and configure release management server, client, and deployment agent, including TFS integration and permission setup, using simple default settings.
- [Mastering Domain Controller Migration: A Step-by-Step Guide to Seamless Active Directory Transfers](https://engineering-leadership.hinshelwood.com/videos/mastering-domain-controller-migration-a-step-by-step-guide-to-seamless-active-directory-transfers/): Learn how to safely migrate Active Directory roles to a new domain controller, including setup, role transfer, and decommissioning the old server for minimal disruption.
- [Unlocking TFS: Mastering Permissions for Seamless Team Collaboration](https://engineering-leadership.hinshelwood.com/videos/unlocking-tfs-mastering-permissions-for-seamless-team-collaboration/): Learn how to configure Team Foundation Server (TFS) permissions and access levels to enable full feature access and improve team collaboration and project management.
- [Mastering TFS Installation on a Single Server: A Step-by-Step Guide for Beginners](https://engineering-leadership.hinshelwood.com/videos/mastering-tfs-installation-on-a-single-server-a-step-by-step-guide-for-beginners/): Learn how to install and configure Team Foundation Server (TFS) on a single server, including SQL Server setup, TFS installation, and creating your first team project.
- [A Step-by-Step Guide to Installing TFS 2013 on Windows Server 2012 R2](https://engineering-leadership.hinshelwood.com/videos/a-step-by-step-guide-to-installing-tfs-2013-on-windows-server-2012-r2/): Learn how to install Team Foundation Server 2013 on Windows Server 2012 R2, covering VM setup, system requirements, domain joining, SQL options, and step-by-step configuration.
- [Mastering Email Notifications in Release Management: A Step-by-Step Guide to Configuring Office 365 SMTP](https://engineering-leadership.hinshelwood.com/videos/mastering-email-notifications-in-release-management-a-step-by-step-guide-to-configuring-office-365-smtp/): Learn how to set up email notifications in release management systems using Office 365 SMTP, including server settings, account details, and best practices for team mailboxes.
- [Mastering TFS Release Management: A Step-by-Step Guide to Smooth Configuration](https://engineering-leadership.hinshelwood.com/videos/mastering-tfs-release-management-a-step-by-step-guide-to-smooth-configuration/): Learn how to configure release management in Team Foundation Server (TFS) with step-by-step setup, troubleshooting tips, and best practices for smooth deployment workflows.
- [Unlocking Project Management Potential: A Deep Dive into TFS Preview for Agile Teams](https://engineering-leadership.hinshelwood.com/videos/unlocking-project-management-potential-a-deep-dive-into-tfs-preview-for-agile-teams/): Explore how TFS Preview helps Agile teams manage projects with cloud-based source control, work tracking, Kanban boards, WIP limits, and early access to new features.
- [Harris Beach SDS Ultrabook Unbox](https://engineering-leadership.hinshelwood.com/videos/harris-beach-sds-ultrabook-unbox/): Unboxing and first impressions of the Harris Beach SDS Ultrabook, highlighting design, features, and initial setup. Includes video and detailed review link.

## Workshops

- [Customer Working Agreement](https://engineering-leadership.hinshelwood.com/workshops/customer-working-agreement/): A Customer Working Agreement workshop, lasting about 60 minutes, helps both parties define a clear Statement of Work and agree on the level of agility to apply. It ensures customers understand their responsibilities, such as providing a Product Owner, clear goals, and attending Sprint Reviews, while the development team commits to delivering usable increments and a dedicated team. Development managers should use this workshop early to clarify expectations, roles, and trade-offs for successful collaboration.
- [Definition of Done](https://engineering-leadership.hinshelwood.com/workshops/definition-of-done/): The Definition of Done (DoD) clarifies when work is truly complete, ensuring shared understanding and consistent quality across the team. Key steps include aligning on what "done" means, using exercises to explore the concept, and applying it to increments of work. Development managers should ensure their teams have a clear, agreed-upon DoD to improve delivery consistency and product quality.
- [Sprint Review #1](https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/): This Sprint Review workshop uses interactive methods to help teams and stakeholders inspect the product increment, gather feedback, and identify next steps based on recent changes and business needs. Key activities include networking to clarify expectations, hands-on product inspection, structured group reflection, and personal action planning. Development managers should ensure active participation, update the Product Backlog with new insights, and encourage team members to define concrete actions for the next Sprint.
- [The Importance of Batch to Optimise Flow](https://engineering-leadership.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/): Breaking large backlog items into smaller pieces helps teams deliver faster and more predictably. The workshop uses a hands-on coin game to show that smaller batch sizes improve flow and reduce delivery time. Development managers should encourage teams to split work into smaller, manageable batches to boost efficiency and predictability.