The Power of Team Ownership When Defining and Implementing Architectural Decisions | Richard Coplan
Sep 23, 2024
auto_awesome
Richard Coplan, a seasoned Scrum Master with a wealth of experience in the banking sector, shares insights on the importance of team ownership in architectural decisions. He highlights the stark contrast between a high-performing API team that thrived on ownership and another that struggled with top-down approaches. Richard discusses the friction caused by architecture governance and emphasizes the need for teams to actively engage in defining their architecture, ultimately fostering collaboration and creativity in the development process.
Team ownership in architectural decisions enhances creativity and reduces friction, as demonstrated by Richard's experience with differing team dynamics.
Effective Scrum Mastering requires addressing team dynamics and fostering collaboration between roles for successful Agile implementation.
Deep dives
Richard Coplan's Journey into Scrum Mastery
Richard Coplan's transition from software developer to Scrum Master reflects an organic evolution of roles driven by his experiences in various contract positions. Initially working as a lead developer in the .NET space and later in data warehousing, he adopted Agile principles even before the term was widely recognized, focusing on rapid application development. As he shifted into the role of Scrum Master, he recognized the significance of fostering strong relationships between the product owner and the development team, which he views as fundamental to the Scrum framework. His journey emphasizes the importance of collaborative engagement in Agile environments, illustrating how proactive communication can drive successful project outcomes.
Challenges of Siloed Architectures in Agile Teams
The experience Richard had in a banking environment exposed the detrimental effects of siloed architectures on Agile teams. He observed two different teams: one effective in developing APIs with strong ownership of their tasks, and another struggling due to a lack of engagement from architects who dictated designs without collaboration. This disconnect led to limited ownership and accountability within the less competent team, while the API team faced friction due to their critical stance on architectural decisions. Richard argues that integrating architectural roles within teams can enhance creativity and reduce conflicts, urging for a more collaborative approach to design responsibilities.
The Need for Agile Coaching and Team Restructuring
Through his experiences, Richard recognized the necessity of Agile coaching in order to address the structural issues within organizations. He highlighted the limitations that arise when teams are not adequately organized, pointing out that merely implementing Scrum or Kanban methodologies would not lead to improvement without addressing underlying team dynamics. His time at the banking company reinforced the idea that reorganization was essential for fostering effective Agile practices, emphasizing team ownership and active participation in decision-making. By advocating for a transformation towards a coaching-centric approach, he aims to empower teams to take responsibility for their architectural and developmental processes.
Richard shares a story about his time working as a Scrum Master for two teams at a bank. While one team excelled at developing APIs and took ownership of architectural decisions, the other struggled to build a relationship with the architecture team. Richard discusses the friction that arose from a top-down imposition of architecture and highlights the key anti-pattern of architecture governance. How can teams take more ownership of their architecture, and what role should architects play in facilitating collaboration? Listen in to find out!
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Richard Coplan
Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures.