Cover of Fundamentals of Software Architecture by Mark Richards, Neal Ford - Business and Economics Book

From "Fundamentals of Software Architecture"

Author: Mark Richards, Neal Ford
Publisher: O'Reilly Media
Year: 2020
Category: Computers

🎧 Free Preview Complete

You've listened to your free 10-minute preview.
Sign up free to continue listening to the full summary.

🎧 Listen to Summary

Free 10-min Preview
0:00
Speed:
10:00 free remaining
Chapter 23: Negotiation and Leadership Skills
Key Insight 3 from this chapter

Effective Integration with Development Teams

Key Insight

For a software architect to be effective, it is crucial to allocate more time to the development team, despite a typical schedule often being filled with meetings. Architects must actively manage their meeting commitments to create this dedicated time. Meetings are categorized as 'imposed upon' (when an architect is invited) or 'imposed by' (when an architect calls a meeting). For 'imposed upon' meetings, consistently ask the organizer for the reason for attendance, as many invites are merely for informational purposes, a need often met by meeting notes.

Prior to accepting an 'imposed upon' meeting invitation, request the agenda. This allows the architect to evaluate their necessity for attendance and, if appropriate, optimize their time by joining only for relevant discussions or leaving once their contribution is complete. Architects can also 'take one for the team' by attending meetings in place of a technical lead or developer. This strategy keeps the development team focused on their tasks, boosting their overall productivity, even if it marginally increases the architect's own meeting time.

Meetings 'imposed by' the architect should be kept to a minimum and rigorously managed. Before scheduling a meeting, assess if an email could convey the necessary information, saving collective time. Always establish and adhere to a clear agenda to prevent discussions from veering off-topic for some participants. Architects must also be acutely aware of 'developer flow', a state of deep concentration. To avoid disrupting this, schedule meetings strategically: first thing in the morning, immediately after lunch, or at the end of the day, rather than during core working hours. Furthermore, physical integration, such as sitting with the development team rather than in a separate office or cubicle, signals accessibility, fosters respect, and facilitates mentorship. If co-location is not feasible, regularly walk around, engage in conversations, and offer assistance or coaching on both technical and non-technical matters to maintain presence and reinforce leadership.

📚 Continue Your Learning Journey — No Payment Required

Access the complete Fundamentals of Software Architecture summary with audio narration, key takeaways, and actionable insights from Mark Richards, Neal Ford.