Chapter 24: The Role of the Architect – Leadership in Projects

A core focus is the critical partnership between the software architect and the project manager, where the manager handles external factors like budget and schedule, while the architect drives the internal technical solution and design. The architect supports the manager across numerous Project Management Body of Knowledge (PMBOK) knowledge areas, including creating the design and managing dependencies for integration, estimating costs and risks for scope management, defining work breakdown structures for time management, designing for crucial quality attributes, and defining technical skill sets for human resource management. Furthermore, the chapter stresses that architecture must be delivered incrementally, not all at once, in a tempo that supports the overall project schedule. Early architectural increments should prioritize structures like the module decomposition view (to inform team structure) and the module uses structure (to enable planned functional extensions), while also tackling the most challenging quality attribute requirements upfront to prevent late-stage surprises. Addressing the integration with Agile methodologies, the text advocates for a balanced "Iteration 0" approach over relying solely on "Big Design Up Front" (BDUF) or unmanaged "emergent" architecture, especially for large, complex systems. This approach involves using initial Attribute-Driven Design (ADD) iterations to select major patterns and frameworks, and then employing technical spikes for managing subsequent requirement changes. While many Agile principles align with architectural practice, the text argues strongly against the idea that best architectures simply emerge from self-organizing teams or that face-to-face conversation negates the need for thorough documentation. For enterprise-scale applications, coordinating numerous small Agile teams is addressed by frameworks like the Scaled Agile Framework (SAFe), which balances purposeful "intentional architecture" with the necessity of "emergent design". Finally, the chapter discusses the growing challenge of distributed development, emphasizing that formal mechanisms, especially well-written documentation, and careful attention to minimizing module dependencies are vital for successful coordination across dispersed teams and time zones.