https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/ Recent content in Agile Planning on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Mon, 04 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work. https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Tue, 24 Nov 2020 13:00:01 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability. https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Wed, 02 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ Mon, 14 Oct 2019 13:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint. https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead. https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ Thu, 30 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success. https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/ Mon, 13 Jul 2020 18:42:03 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/ Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible. https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ Mon, 19 Feb 2024 07:00:09 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Thu, 04 Jan 2024 11:09:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk. https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/ Thu, 04 Jan 2024 12:14:45 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/ditching-the-myth-of-special-sprints-embrace-true-agile-practices-for-usable-products/ Relying on special Sprints like Sprint Zero or bug fix Sprints undermines true Agile practices by encouraging risky behavior, diluting focus, and creating a false sense of security. Teams should instead prioritize delivering a usable product at the end of every Sprint, foster accountability, and integrate quality assurance into regular work. Development managers should avoid safety nets and focus on continuous improvement and value delivery each Sprint. https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/ Thu, 21 Mar 2024 09:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/ Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ Thu, 16 Nov 2023 07:00:16 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ To improve your team’s Sprint outcomes, clearly define what “done” means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/ Thu, 29 Jun 2023 07:00:19 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-sprint-planning-transform-your-agile-approach-for-success/ Effective Sprint planning can transform your team’s Agile approach by building shared understanding, enabling hands-on practice with real-time coaching, and fostering continuous improvement through feedback. As teams gain confidence, they should adapt Sprint planning to fit their unique needs and culture. Consider structured workshops with flexible delivery to empower your team to run impactful Sprint planning sessions independently. https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/ Tue, 09 Jan 2024 07:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-sprint-planning-why-burndown-charts-are-agile-banditry-and-what-to-do-instead/ Relying on burndown charts leads to excessive upfront planning, which is ineffective given the high uncertainty and frequent changes in software development. Instead, start each Sprint with only enough planning to begin work, then reassess and adjust daily to stay flexible and focused on delivering value. Shift your team’s approach to minimal, just-in-time planning to reduce overhead and respond better to change. https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/ Wed, 03 Jan 2024 07:00:13 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/ Focusing daily meetings on routine status questions leads to disengagement and distracts from delivering real value. Instead, teams should use these meetings to track progress toward sprint goals, manage aging tasks before they become bottlenecks, and adapt ceremonies to support value delivery and continuous improvement. Review your Agile practices and shift the focus from individual updates to team outcomes for better results. https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/ Thu, 27 Jul 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/ If teams do not deliver a usable product at the end of each iteration, trust with stakeholders erodes, technical debt grows, adaptability slows, and expectations become misaligned. This also leads to lower team morale and a lack of feedback, making it hard to improve or stay on track. To avoid these issues, ensure every iteration results in a usable product so you maintain trust, alignment, and the ability to adapt quickly. https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Fri, 26 Jul 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Empowering teams to adapt their processes to their specific needs leads to greater value, less waste, and more innovation, while rigid, one-size-fits-all processes can cause delays, unnecessary costs, and frustration. Development managers should assess whether their teams have the freedom to experiment, minimize bureaucracy, and focus on delivering customer value rather than just following procedures. To achieve true agility, encourage teams to tailor their ways of working and continuously improve based on what they learn. https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/ Fri, 28 Apr 2023 09:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/ Focusing on Scrum rituals instead of its core principles, empiricism, transparency, and delivering value, can hinder true agile success. Overemphasis on mechanics leads to misplaced priorities, reduced creativity, and lower team engagement. Development managers should encourage open dialogue, support experimentation, and regularly assess whether practices are truly delivering value, adapting or discarding those that do not. https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ Thu, 17 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies. https://engineering-leadership-preview.hinshelwood.com/signals/too-much-refinement-wastes-time/ Tue, 29 Apr 2025 15:30:43 +0100 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/ Thu, 14 Sep 2023 14:25:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/ Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes. https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/ Thu, 08 May 2025 15:30:40 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/ Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives. https://engineering-leadership-preview.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/ Thu, 10 Oct 2024 15:48:56 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/agile-is-not-new-a-journey-back-to-the-basics/ Agile is rooted in centuries-old practices focused on human connection and adaptability, but mass production and Taylorism shifted work toward efficiency at the cost of empathy and craftsmanship. The Agile movement aimed to restore these values, yet many organizations now face a competence gap, hiring for Agile roles without ensuring the necessary skills, which leads to disappointing results. Development managers should prioritize building real competence and continuous learning in their teams to realize Agile’s true benefits and prepare for a coming reset that emphasizes value, empathy, and adaptability over rigid processes. https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Fri, 28 Jun 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense’s “Detecting Agile BS” guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation. https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/ Thu, 05 Jun 2025 15:30:54 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/ The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation. https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and critical evaluation questions. https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/ Sat, 14 Oct 2023 07:00:13 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/ Focusing on fewer, high-value tasks rather than trying to do everything leads to better productivity and higher quality in Agile teams. Regularly refining the backlog and planning sprints around essential work helps eliminate waste and ensures efforts align with project goals. Development managers should encourage teams to prioritize what matters most to maximize results. https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/ Fri, 02 Jun 2023 07:00:09 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/ A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable. https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/ Mon, 13 Jul 2020 08:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/ Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/ Tue, 05 Dec 2023 11:00:27 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/ Applying the principle of “just enough and no more” across backlog management, team size, refinement, and planning helps teams stay focused, efficient, and adaptable. Prioritising value, embracing simplicity, and iterating regularly reduces wasted effort and maximises productivity. Development managers should encourage teams to do only what is necessary to deliver value and continuously improve. https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/ Mon, 01 Feb 2010 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/ A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems. https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/ Wed, 26 Jun 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/ Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort. https://engineering-leadership-preview.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-leadership-preview.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-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/ Sun, 14 Apr 2024 12:17:16 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/ Achieving true agility requires more than adopting Agile practices; organisations often fall into seven common traps such as seeking quick fixes, overloading backlogs, focusing on resource utilisation over value, lacking accountability, fostering blame, copying others blindly, and letting pride block learning. These behaviours hinder innovation, value delivery, and team effectiveness. Development managers should regularly assess and address these pitfalls, tailor Agile to their context, and foster a culture of continuous improvement and honest reflection. https://engineering-leadership-preview.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Mon, 28 Apr 2025 15:30:55 +0100 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn't-work-myth-1/ Tue, 24 Oct 2023 06:50:42 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/scrum-is-like-communism-it-doesn't-work-myth-1/ Scrum events are not just meetings but purposeful activities designed to drive inspection, adaptation, and real progress. Misunderstanding them as empty ceremonies leads to missed opportunities for team alignment, stakeholder engagement, and continuous improvement. Development managers should focus on using Scrum events to foster transparency and action, not just to fill calendars. https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/ Wed, 18 Jan 2023 08:57:16 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/ The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption. https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/ Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/ Fri, 30 Jun 2023 07:00:18 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/ The Sprint Review workshop helps teams align product development with stakeholder needs, adapt to market changes, and drive continuous improvement. It offers practical guidance on running effective reviews, boosting stakeholder engagement, and turning feedback into actionable improvements. Development managers should consider this workshop to enhance team performance and ensure products deliver real value. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/ Mon, 30 Oct 2017 19:26:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-training-for-the-ghana-police-service/ The Ghana Police Service began grassroots Scrum training with its first Professional Scrum Foundations classes, introducing officers with little IT experience to agile practices through hands-on software sprints. Key outcomes included increased engagement, practical understanding of Scrum, and improved alignment between training and police work after adjusting the approach based on feedback. For future success, ensure participants receive clear pre-class communication about objectives and context, especially when introducing agile methods to non-technical teams. https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/ Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions. https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn't-solve-problems-it-reveals-them-how-and-why-is-that-valuable/ Wed, 27 Sep 2023 07:00:29 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/scrum-doesn't-solve-problems-it-reveals-them-how-and-why-is-that-valuable/ Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation. https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/ Tue, 18 Mar 2025 09:51:08 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/ Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability. https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/ Fri, 19 Jul 2024 06:45:03 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-critical-role-of-user-feedback-in-requirement-changes/ Empowering teams to change requirements based on real user feedback is essential for true agility, yet many organizations are held back by rigid contracts, complex change processes, and lack of team autonomy. Teams must be able to quickly adapt, discard outdated features, and act on feedback to keep products relevant and valuable. Development managers should streamline change processes, build flexibility into contracts, and foster a culture of trust so teams can respond rapidly to evolving business needs. https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/ Mon, 06 May 2024 14:12:53 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/debunking-the-top-5-myths-about-scrum-unlocking-agile-success-in-your-organisation/ Many common beliefs about Scrum, such as it being just meetings, requiring story points, encouraging micromanagement, lacking planning, or having no governance, are misconceptions that hinder its effectiveness. Scrum events are purposeful, story points are optional, teams should self-organise, planning is integral, and governance is flexible to business needs. Development managers should challenge these myths to help teams fully benefit from Agile and deliver greater value. https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/ Tue, 09 Jan 2024 11:00:51 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/ Relying on burndown charts leads to excessive upfront planning, false confidence, and wasted effort, as most plans quickly become outdated and only a fraction of features are actually used. Instead, focus on minimal, just-in-time planning and continuous flow to adapt quickly, reduce overhead, and deliver real value. Encourage your teams to plan only what is needed for the next day, adjust daily, and prioritize delivering value over maintaining detailed charts. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/ Fri, 26 May 2023 14:00:37 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/ Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/ Thu, 30 Nov 2023 11:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/ Effective product backlog management is crucial for Agile success; prioritising tasks, limiting work in progress, and holding regular refinement sessions help teams stay focused and deliver more value. Engaging stakeholders and using visual tools can further improve clarity and alignment. Development managers should regularly review their backlog practices to ensure they are working on the most valuable items and maintaining a manageable, focused backlog. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/ Fri, 24 Mar 2023 07:00:30 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/ Effective Scrum planning and prioritisation require aligning work with business goals, regularly communicating with stakeholders, and keeping the product backlog lean and focused on near-term priorities. Use a simple value, risk, and size formula to help order backlog items, and continuously adjust based on customer data and outcomes. Keep your backlog manageable and iterate often to ensure your team delivers meaningful results that support business objectives. https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/ Fri, 30 May 2025 15:30:41 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/ Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products. https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/ Fri, 08 Sep 2023 07:00:07 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/ Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process. https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/ Wed, 06 Sep 2023 07:00:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/ The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team’s next steps. https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/ Mon, 11 Jan 2021 14:36:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/ The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features. https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ Wed, 04 Jun 2025 15:31:05 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/ Sat, 24 May 2025 15:30:17 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/ Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries. https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/ Mon, 27 Feb 2023 07:00:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/if-you-could-teach-just-one-thing-about-scrum-what-would-it-be/ The most important thing to teach about Scrum is the principle of empiricism, which means making work transparent, inspecting progress frequently, and adapting based on what is learned. This approach helps teams navigate complex, uncertain environments where traditional project management falls short. Focus on building your team’s ability to learn and adapt quickly, as Scrum reveals problems but does not solve them for you. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/ Tue, 18 Oct 2022 16:13:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/ Scrum is a flexible framework that helps teams deliver value through transparency, clear roles, and structured events, all grounded in trust and five core values. Key elements include defined accountabilities, essential artifacts for decision-making, and regular events to inspect and adapt work. To get the most from Scrum, focus on building trust, maintaining transparency, and continuously improving team processes. https://engineering-leadership-preview.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/ Thu, 24 Aug 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/ Keep your product backlog minimal but sufficient, ensuring it is clear and transparent for all stakeholders while also considering future needs to avoid surprises. Regularly review and reflect on completed work and unexpected issues to refine your backlog and adapt to changing circumstances. Aim for a balance that supports both current priorities and readiness for what lies ahead. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/ Mon, 18 Dec 2023 07:00:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/ Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently. https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Wed, 11 Oct 2023 11:35:09 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Excessive backlog items, overambitious sprint plans, and unnecessary product features can slow teams down and reduce focus. Regularly prioritise and trim the backlog, set realistic sprint goals, and remove unused features to keep the team agile and deliver real value. Focus on quality and relevance rather than quantity to improve productivity and morale. https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/ Mon, 04 Sep 2023 07:00:13 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/ To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency. https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/ Mon, 05 Jun 2023 07:00:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/best-scrum-advice-you-ever-received/ The most valuable Scrum advice is to avoid rigidly following every rule and instead adapt Scrum principles to fit your team’s unique context. Flexibility and continuous improvement are more important than strict adherence to the framework, so use Scrum as a guide and modify it as needed to maximize value and innovation. Encourage your teams to experiment and iterate, focusing on what works best for your organization. https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/ Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/ Wed, 24 May 2023 14:00:36 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/ Sprint planning is a team meeting to align on what will be accomplished in the next sprint, ensuring everyone understands the goals and priorities, including new features, technical debt, and unexpected work. It provides clarity, flexibility, and a shared sense of direction, whether you use Scrum or Kanban. Make sure your team uses sprint planning to regularly evaluate priorities and maintain alignment for better outcomes. https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/ Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/ Wed, 04 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/ Scope creep is often a sign that traditional fixed-scope approaches are failing in today’s fast-changing market. Focusing on delivering customer value, embracing flexible planning, and actively seeking feedback helps teams adapt and succeed. Development managers should shift from rigid scope management to Agile practices that prioritize value and responsiveness to change. https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/ Thu, 11 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/ Agile is not about working faster but about focusing on delivering the most valuable outcomes by prioritizing, experimenting, and adapting based on real customer needs. Speed alone can lead to building the wrong product, while Agile helps teams avoid wasted effort by eliminating unnecessary work and bureaucracy. Development managers should ensure their teams use Agile to maximize value, not just to increase velocity. https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/ Wed, 25 Oct 2023 13:30:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/ Effective planning is essential for Agile and Scrum teams, not something to skip; key Scrum events like sprint planning, backlog refinement, and daily standups all revolve around planning. The goal is to find the right balance, plan enough to provide direction and coordination, especially in large teams, but avoid over-planning that wastes resources. Development managers should ensure their teams have clear goals, roadmaps, and themes to align efforts and adapt as needed. https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/ Thu, 17 Aug 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-product-backlog-navigating-through-the-weeds-of-complexity/ Relying on rigid hierarchies in the Product Backlog can hinder transparency and adaptability in complex product development. Instead, focus on a flat backlog that highlights valuable, deliverable items, supports team autonomy, and leverages emergent practices over fixed best practices. Empower your teams to structure the backlog in ways that foster learning, innovation, and resilience in changing environments. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/ Tue, 08 Oct 2024 10:33:32 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/ Predictability in software development is achieved by aligning teams around clear goals, optimizing systems, and adopting Agile principles that balance planning with adaptability. Key insights include the importance of well-defined processes, empowering teams to make decisions, and tailoring Agile frameworks to fit your unique business needs, as seen in Microsoft’s transformation. To improve predictability, focus on continuous improvement, effective communication, and collaboration both within teams and with customers. https://engineering-leadership-preview.hinshelwood.com/articles/what's-in-a-burndown/ Wed, 28 Mar 2012 03:52:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/what's-in-a-burndown/ Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility. https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/ Sun, 03 Apr 2011 21:44:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/ A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work. https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/ Thu, 10 Aug 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/ A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery. https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/ Mon, 06 May 2024 13:29:40 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/ Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/ Wed, 30 Aug 2023 07:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/ Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs. https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/ Fri, 27 Nov 2020 13:09:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-goal-is-a-commitment-for-the-sprint-backlog/ The Sprint Goal is a clear, single objective for each Sprint that guides the team’s focus and aligns their work toward the Product Goal. It is set during Sprint Planning, helps teams adapt their work as needed without losing sight of the main purpose, and should be specific to your business context. Ensure your Product Owner proposes a meaningful Sprint Goal for each Sprint to keep the team aligned and working toward valuable outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they're-separate-roles/ Thu, 01 Aug 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they're-separate-roles/ Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive. https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/ Wed, 03 Apr 2024 17:21:43 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/ Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team’s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team’s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results. https://engineering-leadership-preview.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-leadership-preview.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-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/ Tue, 30 May 2023 07:00:18 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-select-the-most-valuable-items-for-the-sprint-backlog/ Selecting the most valuable items for the sprint backlog requires input from business, product, and engineering perspectives, not just following the product backlog order. It is a collaborative process where the team and stakeholders align on priorities to ensure each sprint delivers real value. Development managers should facilitate open discussions to balance strategic goals and technical needs when planning sprints. https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/ Tue, 05 Dec 2023 07:00:10 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/videos/the-ghosts-of-agile-past-why-burndown-charts-might-be-holding-you-back/ Mon, 01 Jan 2024 07:00:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-ghosts-of-agile-past-why-burndown-charts-might-be-holding-you-back/ Burndown charts often hinder Agile teams by promoting rigid, upfront planning and fixed scopes, which do not reflect how real Agile work unfolds. Teams are more effective when they focus on delivering a steady flow of value, adapt plans as they learn, and make decisions based on actual progress rather than predictions. Consider moving away from burndown charts and instead prioritize flexibility, just-in-time planning, and empirical management to improve your team’s outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/ Wed, 10 Jan 2024 07:00:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/ Product Owners who micromanage and focus on rigid task planning undermine team engagement and product success. Shifting to a focus on vision, value, and outcomes while empowering teams leads to higher motivation, better collaboration, and improved results. Development managers should encourage Product Owners to let go of detailed control, trust their teams, and prioritize clear goals and customer value. https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Mon, 05 Aug 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery. https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/ Fri, 29 Sep 2023 12:12:59 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/ Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed. https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/ Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders. https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Fri, 01 Dec 2023 07:00:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Effective product backlog management is essential for team focus, stakeholder alignment, and delivering real value, yet many organizations neglect it, leading to confusion and wasted effort. Key issues include oversized or outdated backlogs, lack of regular refinement, insufficient detail, and poor stakeholder involvement. To improve, keep the backlog lean, refine it regularly with the whole team, ensure transparency and clarity, and use data to guide priorities; making this a priority will boost team performance and stakeholder satisfaction. https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/ Mon, 15 Mar 2010 13:08:59 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/ Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/ Mon, 29 May 2023 12:01:04 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-a-sprint-backlog/ The Sprint Backlog is a combination of the Sprint Goal, selected tasks, and a clear plan for achieving them, providing transparency on current work and progress. It should balance goal-driven work with essential tasks like bug fixes, remain flexible to adapt to new needs during the Sprint, and set teams up for achievable success. Development managers should ensure Sprint Goals are realistic and use the Sprint Backlog to maintain focus while staying adaptable. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/ Thu, 30 Nov 2023 07:00:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/ Scrum.org’s new Product Backlog Management course offers focused, practical training in backlog management, helping teams capture, prioritize, and break down work for better clarity and alignment. The compact 8-hour format teaches actionable techniques to minimize distractions, improve transparency, and ensure teams deliver high-value work that supports business goals. Development managers should consider this course to streamline their backlog processes and boost team efficiency. https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/ Thu, 01 Jun 2023 11:00:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-create-a-sprint-goal/ A Scrum team creates a sprint goal by combining the product’s strategic direction, the product owner’s tactical priorities, and current engineering challenges to identify the most valuable next step. The team then selects backlog items that best align with this goal to deliver clear value to stakeholders. Encourage your teams to invest time in understanding context before setting sprint goals for better alignment and outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/ Wed, 31 May 2023 07:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/ A strong product owner is essential for creating and maintaining a focused, valuable product backlog that aligns with strategy and avoids becoming an unmanageable list of requests. The product owner is fully responsible for prioritizing and communicating the backlog, using discernment to filter out items that do not support the product vision. Development managers should ensure their product owners are empowered and proactive to keep teams focused on delivering real value. https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/ Mon, 23 Nov 2020 14:01:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/ The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency. https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/ Sun, 11 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/ The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product’s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product’s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation. https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/ The Product Backlog is a dynamic and prioritised list of work items that acts as the definitive source for what needs to be accomplished in order to deliver a product. It includes features, enhancements, bug fixes, and technical tasks, providing teams with a clear understanding of their objectives. This concept is vital as it allows teams to deliver value in a predictable and sustainable manner by offering transparency regarding priorities and progress. Effective management of the backlog encourages collaboration among stakeholders and enables continuous refinement based on feedback and shifting market conditions. It empowers teams to make informed decisions about their next steps, aligning their work with strategic goals and customer needs. The Product Backlog is more than just a to-do list; it is a living artefact that captures the evolving understanding of the product and its context, promoting a culture of continuous improvement and adaptability. By maintaining a well-structured backlog, organisations can enhance agility, minimise waste, and optimise resource allocation, leading to more successful product outcomes. This systematic approach to backlog management supports long-term planning while remaining flexible enough to address new insights and challenges as they emerge. Ultimately, the Product Backlog is foundational to effective Agile practices, ensuring that teams focus on delivering high-quality, valuable products that meet user expectations and contribute to business success. https://engineering-leadership-preview.hinshelwood.com/tags/service-level-expectation/ Mon, 05 May 2025 09:46:11 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/service-level-expectation/ A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team’s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team’s ability to deliver reliably and respond to change. https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/ The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability. https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/ Fri, 21 Mar 2025 14:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/ Common Goals are a foundational principle for effective delivery within organisations, serving to align strategy with execution and ensuring that every decision, Sprint, and line of code contributes to a shared purpose. These goals are not mere aspirational statements; they represent the strategic objectives that unify efforts and connect individual contributions to meaningful outcomes. In the context of agile, DevOps, and product development, understanding and committing to common goals fosters ownership, clarity, and accountability among team members, enabling distributed decision-making and reducing friction in prioritisation. This alignment is crucial for creating adaptive and high-performing systems, as it allows teams to surface misalignments early and make informed trade-offs without waiting for permission. Furthermore, the integration of tactical commitments, such as Product Goals and Sprint Goals, ensures that strategic intent is operationalised at every level of delivery. By maintaining a focus on measurable outcomes and desired impacts, organisations can avoid the pitfalls of busywork and ensure that their efforts are directed towards achieving significant results. Ultimately, common goals provide the necessary framework for teams to understand their role in the larger organisational context, making it imperative for leaders to establish and communicate these objectives clearly. https://engineering-leadership-preview.hinshelwood.com/categories/scrum/ Tue, 04 Mar 2025 10:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/scrum/ Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum’s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum’s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment. https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/ Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development. https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning-tools/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning-tools/ Agile Planning Tools are vital resources that support effective backlog management, forecasting, and collaboration within Agile teams. Originating from the principles of Agile methodology, these tools enable teams to visualise their work, prioritise tasks, and monitor progress in real-time, ensuring alignment and focus on delivering value. Their importance lies in enhancing predictability and sustainability in value delivery, allowing teams to make informed decisions based on empirical data, which fosters a culture of continuous improvement and adaptability in dynamic environments. By providing a structured approach to planning, Agile Planning Tools help teams anticipate challenges and respond to changing requirements, streamlining workflows and promoting a collaborative atmosphere. Unlike Agile Project Management or Agile Product Management, which target specific project execution or product lifecycle aspects, these tools form the foundational layer that underpins all Agile practices. They facilitate not just task management but also the creation of an environment conducive to team innovation and customer satisfaction through effective planning and execution. Integrating Agile Planning Tools into daily operations enhances organisational agility and resilience, ultimately leading to improved outcomes and sustained success. https://engineering-leadership-preview.hinshelwood.com/tags/azure-boards/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/azure-boards/ Azure Boards is an integral component of the Azure DevOps suite, specifically designed to enhance the management of Agile projects. It provides teams with tools to track work items, manage backlogs, and optimise planning through visual boards that accommodate methodologies such as Scrum and Kanban. By offering a comprehensive view of tasks, progress, and team capacity, Azure Boards promotes collaboration and communication, ensuring that all team members are aligned on priorities and deliverables. Its importance lies in fostering transparency and accountability within teams, enabling them to deliver value in a predictable and sustainable manner. The tool supports continuous improvement by allowing teams to analyse workflows, identify bottlenecks, and adapt processes based on real-time data, which streamlines project management and enhances responsiveness to changing requirements and customer feedback. Unlike other tools that may focus solely on task management, Azure Boards integrates seamlessly with other Azure DevOps services, creating a unified environment for development, testing, and deployment. This integration is vital for maintaining a consistent workflow and ensuring that all facets of product development are interconnected, ultimately leading to improved outcomes and greater organisational agility. The long-term advantages of adopting Azure Boards extend beyond immediate project needs, as it fosters a culture of continuous delivery and improvement, reinforcing the principles of Agile and Lean methodologies across the organisation. https://engineering-leadership-preview.hinshelwood.com/tags/backlog-refinement/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/tags/daily-scrum/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/tags/definition-of-ready/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/tags/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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.