https://engineering-leadership-preview.hinshelwood.com/tags/transparency/ Recent content in Transparency on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system. 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/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Mon, 28 Jul 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality. https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Mon, 25 Aug 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible. https://engineering-leadership-preview.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-leadership-preview.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-leadership-preview.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/ Thu, 15 Aug 2024 07:04:39 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/ Using clear metrics and visual tools helps teams identify improvement areas, increase transparency, and make better decisions. Regularly reviewing processes, experimenting with small changes, and focusing on relevant, actionable data are key to ongoing improvement. Development managers should ensure their teams use these practices to drive meaningful and continuous workflow enhancements. https://engineering-leadership-preview.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Thu, 20 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-leadership-preview.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-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/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/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/ Fri, 08 Mar 2024 07:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/ Adopting a Candan strategy helps teams achieve continuous improvement and greater transparency by using flow metrics to identify workflow issues and inefficiencies. Visualising these metrics enables more informed decisions and motivates action, especially for Scrum teams that lack built-in measurement tools. To maximise benefits, integrate flow metrics into your processes and seek expert support or training if needed. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ Mon, 13 Nov 2023 06:56:47 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk. 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/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/ Tue, 21 Jul 2020 18:00:53 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/ Many teams claim to be agile but still operate with outdated management mindsets that stifle autonomy and engagement, leading to low adoption of core agile practices like short iterations and retrospectives. True agility requires transparency, regular feedback, and a focus on delivering value rather than just completing tasks. Development managers should assess whether their teams meet these criteria and actively foster a culture that supports genuine agile principles. 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/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/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Tue, 13 Feb 2024 15:44:53 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Using Blocked columns on Kanban boards hides the true status of work, encourages team disengagement, and leads to stale tasks and inflated work-in-progress limits. Instead, teams should tag blocked items within their current workflow stage and provide clear context, which maintains transparency and accountability. Managers should avoid Blocked columns and use tags or annotations to highlight issues without disrupting the flow or losing critical information. https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/ Mon, 04 Jan 2021 14:20:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/ Story points and velocity are not required by Scrum and relying on them long-term signals a team’s lack of maturity and adaptability. While they can help new teams start conversations and build shared understanding, they do not provide real predictability or confidence in delivery. Development managers should focus on transparency, concrete data, and metrics like cycle time to build true confidence and improve predictability for stakeholders. 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/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/ Wed, 15 Nov 2023 07:00:28 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-complexity-in-scrum-transform-your-team-with-agile-product-strategy-insights/ Understanding and managing complexity is essential for Scrum teams to plan and execute effectively, especially as unpredictability increases. Emphasizing transparency, inspection, and adaptation helps teams navigate complex work, improve processes, and foster continuous improvement. Consider investing in training or discussions that deepen your team’s grasp of these principles to boost effectiveness. 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/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/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/ Sat, 27 Jan 2024 07:00:19 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/ The PAL-EBM class helps leaders and teams understand how to use metrics effectively to drive organizational success by focusing on real data, transparency, and the human impact of measurement. Participants learn through real-world stories why some metrics fail, how to avoid negative behaviors like those seen with Microsoft’s stack ranking, and how to foster strategic conversations that lead to better outcomes. Leadership teams are encouraged to take the class together to align on measuring success, iteratively strategize, and make informed decisions that support long-term goals. https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/ Mon, 23 Oct 2023 11:00:23 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/ Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions. https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/ Wed, 06 Aug 2014 14:46:41 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/ Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers guidance for agile teams to avoid it. https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Mon, 29 Jul 2024 06:45:02 +0000 https://engineering-leadership-preview.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-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/guides/nexus-guide/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/ Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies. https://engineering-leadership-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/ Thu, 15 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/ Migrating a large, legacy blog to Hugo enabled the use of generative AI for automated tagging and categorisation, significantly improving content discoverability and editorial consistency while reducing manual effort. The system combines AI-driven suggestions with human oversight, using multi-factor scoring, penalty logic, and transparent reasoning to ensure quality and accountability. Development managers considering similar automation should maintain human control over final decisions and leverage AI to streamline, not replace, editorial processes. https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/ Fri, 05 Jan 2024 07:00:28 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/ Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change. https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/ Tue, 28 Feb 2023 07:00:18 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-is-scrum-so-easy-to-understand-but-incredibly-hard-to-master/ Scrum is challenging to master because true understanding and effective implementation require deep cultural change, transparency, and alignment with agile values, not just following the framework. Many teams struggle due to legacy mindsets, lack of comprehension, and misaligned organizational structures, leading to superficial adoption and missed opportunities for value creation. Development managers should focus on fostering a culture of transparency, learning, and value-driven collaboration to realize Scrum’s full benefits. 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/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/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/ Fri, 28 Apr 2023 07:00:30 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/ Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early. https://engineering-leadership-preview.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/ Fri, 23 Feb 2024 07:00:12 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/ Kanban is a practical strategy for improving workflow and predictability by making work processes more transparent and data-driven, which builds trust and enables better decision-making. Integrating Kanban with Scrum helps teams deliver more consistently and reduces stakeholder uncertainty. Development managers should consider adopting Kanban to optimize team performance and deliver greater value across any context. https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/ Thu, 19 Jun 2025 15:30:37 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/ Most transformation efforts fail because teams avoid honest conversations about real issues. Creating space for open dialogue leads to genuine improvement and transparency, which are essential for true agility. Development managers should ensure their teams regularly discuss tough topics to drive meaningful change. https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Thu, 15 Feb 2024 07:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions. https://engineering-leadership-preview.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/ Tue, 25 Jun 2024 11:37:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/ Scrum is meant to be flexible and adaptable, not rigid, despite some claims that it is “immutable.” The Scrum Guide’s reference to immutability applies to its definition, not to how teams must implement it, so teams can adapt Scrum as needed as long as they are transparent about changes. Development managers should focus on delivering value, getting feedback, adapting plans, and reflecting regularly rather than debating strict adherence to the Scrum Guide. https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/ Wed, 27 Sep 2023 09:59:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/ The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team’s delivery. https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ Thu, 03 Jul 2025 05:22:41 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Mon, 01 Jul 2024 07:00:24 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency. 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/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Mon, 24 Jun 2024 06:48:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/ Tue, 13 Aug 2024 07:04:49 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/ Caman is a strategy that complements Scrum by increasing transparency and providing deeper insights into workflows, helping teams identify bottlenecks and optimise processes. It is universally applicable across different systems and industries, not just software development. Development managers should use Caman alongside Scrum by mapping processes, involving teams in discussions, and iterating improvements to enhance value delivery. 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/rethinking-'user-stories'-a-call-for-clarity-in-product-backlog-management/ Thu, 31 Aug 2023 13:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-'user-stories'-a-call-for-clarity-in-product-backlog-management/ The author argues that using the term “User Stories” for all work items leads to confusion and unnecessary complexity, as not all tasks fit this format. Switching to a more generic term like “Product Backlog Item” allows teams to describe work more clearly and flexibly, improving communication and transparency. Development managers should consider updating their backlog terminology to better reflect the true nature of their work and support more effective product development. https://engineering-leadership-preview.hinshelwood.com/articles/online-is-the-new-co-located/ Mon, 16 Nov 2020 15:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/online-is-the-new-co-located/ With modern video technology and fast internet, online meetings can now provide the same level of non-verbal communication as being in the same room, so keeping cameras on is essential for team transparency and engagement. Development managers should encourage camera use during online events to maximize communication and adapt interactions, but also respect occasional needs for cameras off. If team members cannot use video reliably, consider in-person participation instead. https://engineering-leadership-preview.hinshelwood.com/tags/increment/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/increment/ Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices. https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery. 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/concepts/artifact/ Fri, 21 Mar 2025 13:59:46 +0000 https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/ An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change. 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/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/transparency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/transparency/ Transparency is the practice of fostering openness and visibility within agile processes, which is essential for building trust and accountability among team members. Originating from agile methodologies, transparency enables teams to share information freely, allowing all members to grasp project status, challenges, and progress. This clarity is vital for effective collaboration, empowering individuals to make informed decisions and contribute significantly to team objectives. By promoting transparency, organisations can more easily identify bottlenecks and inefficiencies, facilitating continuous improvement and creating a culture that values feedback and adaptability. This openness not only enhances team dynamics but also aligns efforts towards common goals, ensuring that all members work together to deliver value in a predictable and sustainable manner. Furthermore, transparency supports a long-term approach to organisational health by cultivating an environment of psychological safety, where team members feel secure in expressing concerns and proposing innovations without fear of retribution. This ultimately results in a more resilient organisation, capable of navigating the complexities and uncertainties inherent in product development. By embedding transparency into daily operations, teams can improve their performance and achieve meaningful outcomes that resonate with stakeholders and customers.