ABSTRACT

Objectives ◾ Revisit the popular role of Agility in the context of software development ◾ Discuss emergent information and communications technologies (ICT) as enablers of busi-

ness Agility ◾ Position Agile practices in the architecture, design, implementation, and deployment of a

software system ◾ Describe the enterprise architecture process map in Composite Agile Method and Strategy

(CAMS) together with its Agile practices ◾ Describe the system architecture process map in CAMS together with its Agile practices ◾ Discuss the importance of organizational Web portals in presenting agility to an end user

(customer) ◾ Discuss the importance of nonfunctional requirements specifications (NFRS) in projects

and their influence on business Agility ◾ Describe the system design process map in CAMS together with its Agile practices ◾ Describe the implementation process map in CAMS together with its Agile practices ◾ Describe the pure Agile elements (roles, artifacts, ceremonies) within the implementation

process map in practice ◾ Revisit user stories within the implementation process map ◾ Describe the deployment process map in CAMS together with Agile practices

Introduction is chapter discusses Composite Agile Method and Strategy (CAMS) in the context of software development and maintenance. e discussion herein is software centric, as compared with the ensuing chapters that deal with business and project management aspects of an organization and CAMS. is development-centric aspect of Agility is the one that made it quite popular. Agility in software development, highlighted in Chapter 2, is revisited in this chapter. e Agile practices, however, are placed within the process maps of CAMS. is provides for the formal, planned aspect of the development process. Developers, designers, and architects should find these CAMS process maps helpful as they provide process guidance corresponding to the respective roles. Embedding Agile practices within these process maps will substantially enhance the quality as well as throughput of the respective deliverables.