Flexible working architectures: agile architecting using PPCs
ECSA'10 Proceedings of the 4th European conference on Software architecture
Towards a process for architectural modelling in agile software development
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
An architecture-centric approach for goal-driven requirements elicitation
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
A persona-based approach for exploring architecturally significant requirements in agile projects
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
| Hi-index | 0.00 |
Agile development delivers value quickly, using a series of short-term goals based on immediate priorities. Architecture grows value carefully, using a set of long-term objectives based on fundamental principles. The two seem at odds, but the architect can bring them together at four well-defined points in agile projects: during project initiation by setting architectural direction, through storyboarding by introducing specific architectural tasks, within sprints by close collaboration on challenging issues, and as working software gets delivered by performing direct inspection. This requires four critical skills: decomposing architectural work into iterative form, advocating the merits of architecture throughout development, tracking the architectural state of the project as it executes, and driving toward a broader enterprise architecture to which all agile projects contribute. When done effectively, this approach achieves a pragmatic balance between business and architectural priorities while delivering both with agility.