<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Common Goals on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</link>
		<description>Recent content in Common Goals on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</link>
				<pubDate>Thu, 08 May 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</guid>
				<description>Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives.</description>
			</item>
			<item>
				<title>How does a Scrum team decide on a Sprint goal?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</link>
				<pubDate>Fri, 02 Jun 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/</guid>
				<description>A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable.</description>
			</item>
			<item>
				<title>Everyone loves the idea of self-managing teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</link>
				<pubDate>Tue, 18 Mar 2025 09:51:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</guid>
				<description>Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability.</description>
			</item>
			<item>
				<title>Mastering Sprint Planning: Key Principles for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</link>
				<pubDate>Fri, 26 May 2023 14:00:37 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/</guid>
				<description>Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes.</description>
			</item>
			<item>
				<title>Empowering Agile Teams: Why Understanding Product Vision is Key to Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-why-understanding-product-vision-is-key-to-success/</link>
				<pubDate>Wed, 03 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-why-understanding-product-vision-is-key-to-success/</guid>
				<description>Teams that clearly understand the product vision and strategic goals are more aligned, empowered, and able to make decisions that deliver greater value. Regularly communicating the vision, involving the team in its development, and providing context and feedback opportunities foster ownership and agility. Development managers should ensure their teams know and connect with the product vision to maximize effectiveness and adaptability.</description>
			</item>
			<item>
				<title>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</link>
				<pubDate>Mon, 11 Jan 2021 14:36:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</guid>
				<description>The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.</description>
			</item>
			<item>
				<title>Does Your Team Truly Understand Your Product Vision and Goals?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</link>
				<pubDate>Fri, 12 Jul 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/</guid>
				<description>Many teams lack a true understanding of the product vision and strategic goals, which leads to misaligned decisions and reduced value for customers. Regularly communicating and reinforcing these goals helps team members see how their work contributes to the bigger picture, improving collaboration and decision-making. Development managers should frequently check team alignment and use practical strategies like workshops, visual roadmaps, and leadership engagement to ensure everyone is working toward shared objectives.</description>
			</item>
			<item>
				<title>Taming the Chaos: How to Align Your Agile Team for Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</link>
				<pubDate>Fri, 03 Nov 2023 05:11:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/</guid>
				<description>Chaos in Agile teams is usually caused by unclear goals, lack of direction, and poor communication, which leads to inefficiency and confusion. Aligning teams through clear goals, regular check-ins, open communication, and visualising progress increases motivation, collaboration, and productivity. Development managers should prioritise establishing and communicating shared objectives to reduce chaos and drive team success.</description>
			</item>
			<item>
				<title>Evidence-Based Portfolio Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-portfolio-management/</link>
				<pubDate>Wed, 16 Dec 2020 13:11:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-portfolio-management/</guid>
				<description>Explains how evidence-based portfolio management helps organisations extend agile practices beyond teams, enabling greater responsiveness and improved business outcomes.</description>
			</item>
			<item>
				<title>Getting Started with Objectives &amp; Key Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-objectives-key-results/</link>
				<pubDate>Mon, 18 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-objectives-key-results/</guid>
				<description>OKRs only work when there is a clear strategy, a culture of transparency and adaptation, empowered teams, and a focus on outcomes over output. They help connect strategy to execution but require ongoing review, learning, and refinement to be effective. Before adopting OKRs, ensure your leadership, culture, and processes support these foundations or the framework will not deliver real value.</description>
			</item>
			<item>
				<title>OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/okr-guide/</link>
				<pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/okr-guide/</guid>
				<description>Comprehensive guide to using OKRs for shared focus, measurable outcomes, and strategic learning, including roles, events, best practices, and common pitfalls.</description>
			</item>
			<item>
				<title>Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</link>
				<pubDate>Mon, 06 May 2024 13:29:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</guid>
				<description>Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes.</description>
			</item>
			<item>
				<title>The Strategic Imperative: Empowering Teams with Vision, Goals, and Direction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</link>
				<pubDate>Thu, 08 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</guid>
				<description>Many teams lack clarity on their organization’s vision, goals, and value, leading to inefficiency and misaligned efforts. To address this, leaders should clearly communicate strategic direction, empower teams with autonomy through intent-based leadership, and move beyond rigid procedures to foster engagement and continuous improvement. Ensure everyone understands how their work contributes to broader objectives so teams can make informed decisions and drive meaningful results.</description>
			</item>
			<item>
				<title>The Product Goal is a commitment for the Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</link>
				<pubDate>Mon, 23 Nov 2020 14:01:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/</guid>
				<description>The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency.</description>
			</item>
			<item>
				<title>Objective Key Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/objective-key-results/</link>
				<pubDate>Tue, 03 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/objective-key-results/</guid>
				<description>Objective &amp;amp; Key Results (OKR) are a structured method for translating strategic goals into measurable outcomes, enabling clarity, alignment, and accountability within teams and organizations. Originating from John Doerr&amp;rsquo;s &amp;ldquo;Measure What Matters,&amp;rdquo; this approach defines an Objective as a meaningful, directional goal, and Key Results as specific, measurable indicators of progress toward that goal. Rather than tracking tasks or individual efforts, Objective Key Results emphasize outcomes and evidence of actual progress. Their value lies in creating a transparent system that encourages teams to focus on critical priorities, align their efforts clearly, regularly inspect progress, and adapt accordingly. Properly implemented, Objective Key Results foster a culture of accountability and continuous improvement, pushing teams beyond comfort zones to achieve meaningful results. In agile, DevOps, product development, and organizational design contexts, Objective Key Results serve as a foundational practice for ensuring strategic alignment, outcome-driven decision-making, and iterative learning.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</link>
				<pubDate>Fri, 21 Mar 2025 14:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Daily Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/daily-scrum/</guid>
				<description>The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint&amp;rsquo;s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity.</description>
			</item>
	</channel>
</rss>
