<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cross Functional Teams on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/</link>
		<description>Recent content in Cross Functional Teams 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.hinshelwood.com/tags/cross-functional-teams/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</link>
				<pubDate>Thu, 04 Jun 2020 02:05:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</guid>
				<description>The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust.</description>
			</item>
			<item>
				<title>Why Handoffs Are Killing Your Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</link>
				<pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/</guid>
				<description>Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness.</description>
			</item>
			<item>
				<title>Cross Functional Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/</guid>
				<description>Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise.</description>
			</item>
			<item>
				<title>Scrum Team</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/scrum-team/</guid>
				<description>A Scrum Team is a fundamental component of the Scrum framework, tasked with delivering value through iterative and incremental work. Comprising a Scrum Master, Product Owner, and Developers, the team operates collaboratively towards a unified Product Goal. Characterised by its self-managing and cross-functional nature, the Scrum Team eschews sub-teams and hierarchies, holding collective accountability for producing a usable Increment at the end of each Sprint. While individual members may have specific roles, the team&amp;rsquo;s shared responsibility encompasses all facets of product delivery, including stakeholder engagement, development, validation, and release. This structure empowers the Scrum Team to autonomously manage its work, making it a vital element in agile methodologies, DevOps practices, and effective organisational design. Understanding the dynamics and responsibilities of the Scrum Team is crucial for navigating complex and adaptive environments, as it highlights the importance of collaboration and accountability in achieving successful product outcomes.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/product-developer/</guid>
				<description>Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.</description>
			</item>
	</channel>
</rss>
