Don’t fear change, embrace it
Advancing the case for agile methods in systems integration
Driven by a competitive and ever changing business landscape, our clients are looking for ways to meet their changing business needs through rapid technology implementations. They want to implement systems and system changes quickly and efficiently in order to realize business benefits early.
The need for speed and agility has led them to consider agile software development methods as alternatives to traditional approaches.
Agile software development methodologies consist of several methods that focus on reducing overhead and time to delivery. The various methods have different flavours of implementation approaches, but share common characteristics, including:
- Delivering tested software in short, time-boxed iterations
- Accepting and sometimes encouraging requirement changes between iterations in order to meet changing business needs
- Mandating extensive client involvement during each iteration to understand ambiguous requirements and increase development team productivity
However, many organisations struggle with perceived agile downfalls, such as limited planning, weaker controls, and less documentation. This is a common misconception because agile software development can be integrated within existing organizational boundaries of standardized processes. In fact, most agile methods do not prescribe a methodology for project management or quality control. Instead, they focus on simplifying the software development approach, embracing changing business needs, and producing working software as quickly as possible.
This paper will introduce the drivers and background for agile development methods, summarize agile impact on SDLC phases, outline project characteristics and challenges for agile adoption, and address common myths about agile software development.