Agile And Software Architecture . Marching Together ..

Agile and Software Architecture Marching Together Sujatha Dantuluri Software Architecture Karsun Solutions LLC Herndon, USA Abstract—Notion of faster to market and changing rapidly to the demands of the market has given a boost to Agile. Agile promotes iterative delivery and design as we go because of which many organizations are having tough time implementing proper architecture and developers are doing architecture as they go into their iterations. Without proper architecture, we will create silos and redundant artifacts and this may lead to lack of scalability, interoperability and performance. Architecture improves software quality and Agile enhances productivity. This paper addresses this issue and finds out a way where we†¦show more content†¦Zachman framework is used to derive the architecture artifacts and Togaf is used to define architecture processes which fit the agile methodology. II. DEFINITIONS A. Agile â€Å"Agile Software Development is an umbrella term for a set of methods and practices based on the values and principles expressed in the Agile Manifesto. Solutions evolve through collaboration between self-organizing, cross-functional teams utilizing the appropriate practices for their context† (Agile Alliance, 2015). â€Å"Agile Manifesto defines the importance of †¢ Individuals and interactions over processes and tools †¢ Working software over comprehensive documentation †¢ Customer collaboration over contract negotiation †¢ Responding to change over following a plan† (Agile Alliance, 2015) Scrum, Kanban, XP are some of the methodologies used to develop the software form the Agile.. B. Enterprise Architecture â€Å"An architecture is defined as system fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution† (ISO/IEC/IEEE 42010, 2011) It is important to have architecture defined for an organization so that we can produce repeatable quality products and to ensure we meet the scalability, interoperability, security and compliance factors derived from non-functional requirements of the project. As stated by Togaf documentation, Architecture is classified as †¢Show MoreRelatedProject Mgmt296381 Words   |  1186 Pagesresponses (.2–.1.2) 11.6 Risk register 7.1.2.5 PERT analysis 7.1.2.6.3 Contingency reserves 7.3.3.4 Change control management G.7 Culture awareness 1.4.4 Project offices 8.1.2 Continuous improvement 5.1 Requirements vs. actual [5.3] Chapter 17 Agile PM 6.1.2.2 Rolling wave This page intentionally left blank Project Management The Managerial Process The McGraw-Hill/Irwin Series Operations and Decision Sciences OPERATIONS MANAGEMENT Beckman and Rosenfield, Operations, Strategy:Read MoreExploring Corporate Strategy - Case164366 Words   |  658 Pagesdiscussion and not as an illustration of either good or bad management practice. They are not intended to be a comprehensive collection of teaching material. They have been chosen (or speciï ¬ cally written) to provide readers with a core of cases which, together, cover most of the main issues in the text. As such, they should provide a useful backbone to a programme of study but could sensibly be supplemented by other material. We have provided a mixture of longer and shorter cases to increase the ï ¬â€šexibility