https://engineering.hinshelwood.com/concepts/practice/ Recent content in Practice on Engineering as a Leadership System Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ Wed, 14 May 2025 07:00:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering.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. https://engineering.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery. https://engineering.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Mon, 04 Aug 2025 07:00:00 +0000 https://engineering.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization. https://engineering.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Mon, 21 Jul 2025 06:00:00 +0000 https://engineering.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 plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success. https://engineering.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ Thu, 04 Jun 2020 02:05:28 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering.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. https://engineering.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Fri, 02 Aug 2024 06:45:02 +0000 https://engineering.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Adopting Agile development practices is not enough if the rest of your organization remains slow and bureaucratic; true agility requires continuous delivery, high product quality, and minimal manual or bureaucratic steps across the entire process. Use the Department of Defense’s six-question test to assess your real agility, and focus on automating testing, streamlining deployment, and building quality in from the start. Regularly review and improve your processes to eliminate bottlenecks and ensure your whole ecosystem supports rapid, reliable delivery. https://engineering.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Wed, 04 Jun 2025 06:00:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Wed, 28 May 2025 07:00:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ Mon, 02 Jun 2025 06:00:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Fri, 28 Mar 2025 16:30:04 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Wed, 20 Nov 2024 07:00:26 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ Mon, 19 Feb 2024 07:00:09 +0000 https://engineering.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. https://engineering.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Mon, 08 Sep 2025 09:00:00 +0000 https://engineering.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning. https://engineering.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/ Thu, 07 Dec 2023 11:00:05 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/ Sat, 18 Sep 2021 13:32:34 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Thu, 01 May 2025 15:30:38 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ Wed, 23 Apr 2025 15:30:47 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Fri, 04 Apr 2025 15:30:02 +0100 https://engineering.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. https://engineering.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Thu, 21 Sep 2023 08:00:00 +0000 https://engineering.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes. https://engineering.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ Sat, 05 Apr 2025 15:30:00 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Thu, 07 Mar 2024 07:00:10 +0000 https://engineering.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process. https://engineering.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Sun, 25 Aug 2024 22:00:34 +0000 https://engineering.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum. https://engineering.hinshelwood.com/videos/getting-started-with-kanban/ Wed, 14 Feb 2024 07:00:19 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Thu, 20 Feb 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Fri, 07 Feb 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/ Tue, 19 Nov 2024 16:55:41 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Tue, 04 Mar 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile. https://engineering.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/ Mon, 14 Apr 2025 15:30:31 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Mon, 07 Apr 2025 15:30:01 +0100 https://engineering.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. https://engineering.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/ Fri, 10 Apr 2020 18:30:42 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/too-much-refinement-wastes-time/ Tue, 29 Apr 2025 15:30:43 +0100 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/security-by-design-building-secure-software/ Tue, 26 Nov 2024 13:35:33 +0000 https://engineering.hinshelwood.com/videos/security-by-design-building-secure-software/ Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation. https://engineering.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Thu, 07 Dec 2023 07:00:02 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/reasons-to-do-a-psm-ii-course-in-60-seconds/ Wed, 12 Jul 2023 14:00:30 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/ Mon, 11 Sep 2023 07:00:17 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/ Thu, 16 Feb 2023 07:00:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Mon, 28 Apr 2025 15:30:55 +0100 https://engineering.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. https://engineering.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/ Thu, 23 Nov 2023 08:30:06 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/recipes/daily-scrum-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering.hinshelwood.com/recipes/daily-scrum-recipe/ Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals. https://engineering.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/ Thu, 06 Feb 2025 11:02:31 +0000 https://engineering.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. https://engineering.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/ Thu, 22 Aug 2019 12:55:28 +0000 https://engineering.hinshelwood.com/articles/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/ Estimation is valuable mainly for the team discussions it generates, not the numbers themselves. New Scrum Teams benefit from using Story Points and Velocity, but as they mature, they should shift to flow-based metrics like Cycle Time and Throughput and consider dropping traditional estimation. Teams should regularly review and adapt their process, moving toward simpler sizing and continuous improvement as they gain experience. https://engineering.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Mon, 29 Jul 2024 06:45:02 +0000 https://engineering.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement. https://engineering.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Mon, 03 Mar 2025 15:46:26 +0000 https://engineering.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. https://engineering.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Sun, 09 Feb 2025 16:30:00 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/ Tue, 07 Nov 2023 11:30:07 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training/ Fri, 02 Feb 2024 07:00:16 +0000 https://engineering.hinshelwood.com/videos/the-power-of-immersive-learning-in-scrum-training/ Immersive learning in Scrum training uses shorter, interactive sessions that reduce fatigue and boost engagement, leading to better retention and collaboration compared to traditional long-format training. Key benefits include lower cognitive load, higher energy, and more meaningful participation. Development managers should break up training into focused, hands-on segments to improve learning outcomes and team performance. https://engineering.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/ Mon, 20 Nov 2023 07:51:59 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Wed, 10 Jul 2024 06:45:01 +0000 https://engineering.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Turning user feedback into actionable work quickly is essential for delivering real product value and staying truly agile. Teams that engage users regularly, prioritize feedback effectively, and integrate it into each Sprint see higher satisfaction and better business results. Review feedback weekly, involve stakeholders, and empower your team to act fast so your product evolves in line with user needs. https://engineering.hinshelwood.com/videos/transform-your-career-how-to-become-a-confident-scrum-master-through-real-world-learning-and-community-support/ Thu, 13 Jul 2023 07:41:01 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/ Thu, 29 Feb 2024 07:00:09 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/why-many-scrum-masters-stall-at-psm1-the-crucial-role-of-passion-in-professional-growth/ Fri, 07 Apr 2023 07:00:20 +0000 https://engineering.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. https://engineering.hinshelwood.com/articles/getting-started-with-objectives-key-results/ Mon, 18 Aug 2025 09:00:00 +0000 https://engineering.hinshelwood.com/articles/getting-started-with-objectives-key-results/ OKRs only work when there is a clear strategy, a culture of transparency and adaptation, empowered teams, and a focus on outcomes over output. They help connect strategy to execution but require ongoing review, learning, and refinement to be effective. Before adopting OKRs, ensure your leadership, culture, and processes support these foundations or the framework will not deliver real value. https://engineering.hinshelwood.com/videos/mastering-product-ownership-unlocking-the-secrets-to-effective-product-management-in-agile-teams/ Tue, 05 Sep 2023 07:00:12 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/in-wip-less-is-more-why/ Tue, 09 May 2023 07:00:19 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/before-you-call-yourself-an-agile-coach-the-importance-of-real-experience/ Mon, 13 Nov 2023 11:00:29 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-agile-mastery-how-the-minecraft-case-study-transforms-training-and-team-dynamics/ Tue, 29 Aug 2023 07:00:14 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/ Mon, 04 Mar 2024 07:00:13 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Wed, 06 Mar 2024 07:00:17 +0000 https://engineering.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Setting work-in-progress (WIP) limits is essential for an effective Kanban strategy because it prevents overload, exposes bottlenecks, and improves workflow. The optimal WIP limit for each stage should be found through experimentation and regular adjustment, aiming for a balance that maximizes flow without causing idle time or bottlenecks. Start small, monitor results, and adjust limits as needed to boost team productivity and collaboration. https://engineering.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/ Wed, 29 Mar 2023 07:00:17 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/ Fri, 22 Nov 2024 14:04:14 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/ Mon, 26 Feb 2024 14:06:47 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/confronting-incompetence-how-to-stop-shipping-bad-code-and-tackle-technical-debt-effectively/ Tue, 26 Nov 2024 13:55:20 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/ Tue, 26 Mar 2024 10:56:26 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/ Thu, 01 Feb 2024 07:00:09 +0000 https://engineering.hinshelwood.com/videos/why-immersive-learning-keeps-scrum-students-excited-and-engaged/ Immersive learning keeps Scrum students engaged by making each session a hands-on journey of discovery, allowing them to apply new concepts in real time and reflect on their experiences. Spreading content over multiple sessions helps teams assimilate knowledge, experiment safely, and continuously improve through feedback. Development managers should break training into manageable pieces, encourage experimentation, and foster regular feedback to maintain excitement and drive ongoing growth. https://engineering.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/ Tue, 05 Dec 2023 07:00:10 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/ Tue, 27 Feb 2024 07:00:31 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Mon, 22 Jul 2024 06:00:19 +0000 https://engineering.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable. https://engineering.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/ Wed, 07 Feb 2024 07:00:27 +0000 https://engineering.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/ Peer feedback in immersive learning accelerates skill development by enabling participants to apply Scrum techniques in real situations, share experiences, and collaboratively solve problems. Facilitated debriefs deepen understanding and build a shared knowledge base, leading to better retention and real-world results. Encourage your teams to actively engage in peer feedback during training to drive continuous improvement and more effective Scrum adoption. https://engineering.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ Mon, 08 Jul 2024 06:00:07 +0000 https://engineering.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. https://engineering.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/ Mon, 05 Feb 2024 07:00:03 +0000 https://engineering.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-in-agile-overcoming-cognitive-bias/ Immersive learning is essential for Agile teams because it exposes knowledge gaps and helps overcome overconfidence, leading to real skill growth. By focusing on hands-on practice, continuous feedback, and regular reflection, teams can drive ongoing improvement and avoid common pitfalls. Development managers should encourage immersive, practical learning environments to ensure their teams keep evolving and truly master Agile principles. https://engineering.hinshelwood.com/tags/liberating-structures/ Mon, 14 Apr 2025 14:50:18 +0000 https://engineering.hinshelwood.com/tags/liberating-structures/ Liberating Structures are a modular toolkit of facilitation techniques used to structure team interactions, promote equal participation, and improve collaboration. Designed as plug-and-play alternatives to conventional meeting formats, each structure provides a clear pattern for group engagement, making them easy to learn and adapt. In Agile, Lean, and DevOps contexts, they support team self-organisation by enabling rapid idea generation, shared understanding, and collective decision-making. When applied intentionally, these methods enhance team effectiveness and help build a culture of trust and psychological safety, without requiring major changes to existing workflows. https://engineering.hinshelwood.com/concepts/practice/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering.hinshelwood.com/concepts/practice/ Practice refers to the consistent and repeatable techniques or habits that teams employ to improve their effectiveness, collaboration, and value delivery. Originating from Agile, Lean, and DevOps methodologies, practices such as Pair Programming, Continuous Deployment, and Retrospectives are integral to fostering ongoing, systematic routines that enhance team dynamics and performance. Unlike structured methods, which provide defined steps, practices focus on the habitual actions that teams incorporate into their workflows. For instance, Pair Programming not only boosts code quality but also promotes knowledge sharing, while Retrospectives allow teams to reflect on their processes and identify areas for improvement, thus supporting continuous enhancement. Although tools like Kanban boards can facilitate these practices, the essence lies in how teams manage their workflows and adapt their routines to evolving challenges. The long-term value of practices is evident in their ability to embed behaviours that lead to predictable and sustainable outcomes, such as the frequent and reliable software releases enabled by Continuous Deployment. Ultimately, practices are crucial for effective teamwork, as they shape collaboration, drive continuous improvement, and ensure responsiveness to both internal and external demands, making them essential in the fast-paced environments characteristic of modern product development and organisational design. https://engineering.hinshelwood.com/tags/test-first-development/ Tue, 25 Mar 2025 07:40:33 +0000 https://engineering.hinshelwood.com/tags/test-first-development/ Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts. https://engineering.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering.hinshelwood.com/tags/shift-left-strategy/ The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development. https://engineering.hinshelwood.com/tags/acceptance-test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/acceptance-test-driven-development/ Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users. https://engineering.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/automated-testing/ Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment. https://engineering.hinshelwood.com/tags/backlog-refinement/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/backlog-refinement/ Backlog Refinement is a fundamental practice within Agile methodologies that focuses on ensuring the product backlog is clearly defined, prioritised, and prepared for execution. Originating from the need for effective collaboration between product owners and development teams, this ongoing process involves clarifying requirements, estimating effort, and adjusting priorities based on evolving insights and stakeholder feedback. The importance of Backlog Refinement lies in its ability to enhance focus and alignment on delivering value, thereby enabling teams to deliver outcomes predictably and sustainably. By regularly refining the backlog, teams can reduce risks associated with ambiguity and miscommunication, facilitating smoother sprint planning and execution. This practice promotes a culture of continuous improvement, allowing teams to adapt to changing circumstances and customer needs while maintaining momentum. Additionally, it supports long-term planning by prioritising the most valuable items, optimising resource allocation, and enhancing overall productivity. By integrating Backlog Refinement into their workflows, organisations can foster a more responsive and agile environment, leading to improved product outcomes and greater stakeholder satisfaction. This systemic approach not only streamlines the development process but also encourages a proactive mindset among team members, empowering them to take ownership of their work and align with the organisation’s strategic objectives. https://engineering.hinshelwood.com/tags/behaviour-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/behaviour-driven-development/ Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality. https://engineering.hinshelwood.com/tags/continuous-integration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/continuous-integration/ Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development. https://engineering.hinshelwood.com/tags/cycle-time/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/cycle-time/ Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success. https://engineering.hinshelwood.com/tags/daily-scrum/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/daily-scrum/ The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint’s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity. https://engineering.hinshelwood.com/tags/definition-of-ready/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/definition-of-ready/ Definition of Ready (DoR) is a concept within the Scrum framework that outlines the criteria necessary for a Backlog Item to be considered ready for implementation by the development team. It emerges from the collaborative understanding among Developers, the Product Owner, and Stakeholders regarding what is required to proceed with a Backlog Item. The importance of DoR lies in its potential to enhance clarity and alignment within agile teams, yet it also presents challenges, such as creating a false sense of readiness, neglecting the need for ongoing refinement, and leading to misconceptions about its equivalence with the Definition of Done (DoD). Unlike the DoD, which is an absolute measure of completion, the subjective nature of DoR can result in partial implementation, risking the integrity of the development process. To mitigate these issues, it is suggested that teams adopt a more nuanced approach to defining readiness, ensuring that each Backlog Item meets specific criteria, such as having a clear outcome, hypothesis, and telemetry for evaluation. The INVEST criteria further guide the formulation of Product Backlog Items, emphasising their independence, negotiability, value, estimability, size, and testability. Ultimately, a well-defined DoR fosters effective communication and understanding within agile teams, contributing to successful product development and organisational design. https://engineering.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering.hinshelwood.com/tags/engineering-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/engineering-practices/ Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software’s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance. https://engineering.hinshelwood.com/tags/estimation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/estimation/ Estimation is a fundamental practice within Agile and Scrum methodologies that allows teams to predict the effort and time necessary to complete tasks or deliver features. Originating from the need to manage uncertainty in project management, estimation employs empirical data and collaborative techniques to align stakeholder expectations and foster a shared understanding of project scope and timelines. This practice transcends mere numerical assignment; it involves engaging the entire team in discussions that utilise collective knowledge and experience, thereby enhancing both accuracy and team buy-in. Effective estimation is crucial as it enables teams to deliver value in a predictable and sustainable manner, facilitating improved planning and resource allocation. It also supports continuous improvement through a feedback loop that compares past estimates with actual outcomes, refining future forecasting. This iterative process promotes a culture of transparency and accountability, which is vital for high-performing teams. Unlike broader concepts such as Agile Planning or Backlog Refinement, estimation focuses on the tactical execution of tasks, serving as a foundational element for successful Agile practices. By incorporating estimation into their workflows, organisations can improve their agility and responsiveness in a rapidly changing market, ultimately leading to better outcomes for customers and stakeholders. https://engineering.hinshelwood.com/tags/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/forecasting/ Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation. https://engineering.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/frequent-releases/ Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape. https://engineering.hinshelwood.com/tags/modern-source-control/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/modern-source-control/ Modern source control is a critical practice in software development that focuses on version control and branching strategies to manage codebase changes effectively. Originating from the need for collaborative coding, it utilises systems like Git to allow multiple developers to work simultaneously without conflicts, while also enabling the tracking of modifications, reverting to previous states, and maintaining a comprehensive development history. This practice is vital as it enhances a team’s ability to deliver value in a predictable and sustainable manner, facilitating the implementation of continuous integration and continuous delivery (CI/CD) pipelines that promote rapid feedback and reduced lead times. Such agility empowers organisations to swiftly adapt to market demands and customer feedback, fostering innovation. Additionally, modern source control encourages a systematic approach to development through branching strategies, such as feature branches or trunk-based development, which support parallel workstreams and minimise disruptions to the main codebase. This not only improves collaboration but also helps in managing technical debt by allowing teams to isolate and resolve issues more efficiently. By integrating these practices into their workflows, organisations can cultivate a resilient development environment that prioritises quality and efficiency, ultimately contributing to long-term success in product delivery. https://engineering.hinshelwood.com/tags/release-management/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/release-management/ Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty. https://engineering.hinshelwood.com/tags/remote-working/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/remote-working/ Remote working is a practice that enables teams to collaborate and deliver value from various locations, moving beyond the constraints of a physical office. This approach has gained prominence in today’s technology-driven landscape, allowing organisations to access a wider talent pool, improve employee satisfaction, and sustain productivity irrespective of geographical limitations. By utilising digital collaboration tools and nurturing a culture of trust and accountability, remote working empowers teams to function effectively, adapting quickly to market changes and customer demands. Its systemic nature fosters sustainable practices through continuous communication and feedback loops, which are crucial for iterative development. This flexibility supports agile methodologies and aligns with lean principles by reducing waste and optimising resource use. Additionally, remote working enhances team members’ sense of ownership, boosting engagement and motivation. As teams embrace this model, they cultivate resilience and agility, equipping them to tackle challenges and seize opportunities in a dynamic environment. Ultimately, the emphasis on delivering value ensures that organisations can thrive in a competitive landscape while promoting innovation and collaboration among dispersed teams. https://engineering.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/test-automation/ Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements. https://engineering.hinshelwood.com/tags/test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/test-driven-development/ Test Driven Development (TDD) is a software development methodology that prioritises the creation of automated tests prior to writing the actual code. Originating from the need for a structured approach to software design, TDD ensures that development is guided by the requirements specified in the tests, which clarifies the intended functionality of the software. This practice is crucial in the context of Agile and DevOps as it promotes a culture of quality and accountability, allowing teams to deliver consistent and sustainable value. By embedding testing into the development lifecycle from the beginning, TDD significantly reduces the risk of defects and simplifies the process of refactoring, with tests acting as a safety net. The long-term advantages of TDD extend beyond immediate improvements in code quality; it fosters a mindset of continuous improvement and adaptability among team members. This approach aligns seamlessly with Agile principles, enhancing collaboration and responsiveness to change while supporting technical excellence. By focusing on test coverage, teams can confidently introduce new features and enhancements, ensuring that existing functionalities remain intact. Ultimately, TDD not only improves individual projects but also cultivates a culture of reliability and trust within the organisation, leading to better outcomes for stakeholders and customers. https://engineering.hinshelwood.com/tags/value-stream-mapping/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/value-stream-mapping/ Value Stream Mapping is a visual tool designed to analyse and optimise workflows within an organisation by focusing on the flow of materials and information necessary for delivering a product or service. This method involves mapping each step of the process to identify inefficiencies, bottlenecks, and areas of waste, thereby enabling teams to streamline operations and enhance value delivery. Its importance lies in facilitating predictable and sustainable value delivery, empowering teams to make informed decisions based on empirical data, and allowing for adjustments that improve overall performance. By aligning processes with customer needs, Value Stream Mapping ensures that every step adds value towards the end goal. It is not a one-time exercise but a long-term, systemic practice that promotes ongoing reflection and adaptation, helping teams remain agile in response to changing demands and market conditions. This ultimately leads to improved customer satisfaction and organisational resilience. The insights gained from Value Stream Mapping can drive strategic initiatives and foster a culture of collaboration and shared understanding across cross-functional teams, which is essential for achieving sustained success in modern product development. https://engineering.hinshelwood.com/tags/working-agreements/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering.hinshelwood.com/tags/working-agreements/ Working agreements are foundational norms and principles that teams establish to improve collaboration and effectiveness in their work processes. Originating from the need for clear communication and decision-making frameworks, these agreements delineate how team members interact and fulfil their responsibilities, thereby fostering a shared understanding of expectations. Their importance is underscored in agile and DevOps environments, where accountability and trust are essential for delivering consistent value. By aligning on working agreements, teams can minimise interpersonal conflicts and distractions, allowing them to concentrate on their objectives and engage in continuous improvement. Furthermore, these agreements facilitate long-term systemic change within organisations by empowering teams to self-organise and adapt to challenges, enhancing resilience and agility. By embedding working agreements into the team’s culture, organisations can create an environment conducive to collaboration, ultimately leading to improved performance and value delivery. The clarity and commitment provided by working agreements are vital for navigating the complexities of modern product development, ensuring that teams remain aligned with their goals and values. https://engineering.hinshelwood.com/tags/metrics-and-learning/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering.hinshelwood.com/tags/metrics-and-learning/ Metrics and Learning is a fundamental concept that centres on the utilisation of data, metrics, and feedback to drive continuous improvement within teams and organisational processes. Originating from the need for empirical decision-making, this approach allows organisations to enhance their value delivery by systematically collecting and analysing performance metrics. By doing so, teams can pinpoint areas for enhancement, monitor their progress, and adjust their strategies in alignment with changing customer demands. The focus on learning through metrics fosters a culture of experimentation and adaptability, enabling teams to respond swiftly to feedback and pivot as necessary. This systemic approach not only facilitates immediate improvements but also lays the groundwork for sustained development and innovation. Unlike methodologies that may be prescriptive, Metrics and Learning empowers teams to take ownership of their performance, which is essential for maintaining agility in a fast-paced environment. By integrating metrics into everyday operations, organisations can establish a continuous feedback loop that informs practices and strategies, ultimately leading to more effective and resilient product development.