Along the (not so long) story of software engineering, we have experienced a continuous transformation for improvement, in terms of more industrialized, faster and higher quality development. We keep on continuously improving the way we develop software, as an intrinsic part of business and society, pushed by a changing context in the way we consume and access software. “Change is the only constant in life”. We need to respond to two main aims: Firstly, we need to deliver software faster. Secondly, we need to improve quality in a changing, challenging and more complex world, because software defects and low quality directly impact the business (reputation, business processes behavior and associated revenue, user experience, social consequences…).
In this context, agile is a development approach that inspires a transformation wave in almost all organizations, in conjunction with the DevOps vision. However, agile does not mean (only) going faster by doing (more or less) the same. We change because we want to work better. And if this is the aim, no agile implementation can be really agile unless (1) agile testing and continuous quality assurance are considered and applied as key activities of software development, and (2) teams become really one-team mind-shaped, with diverse profiles (developers, business, architecture experts, UX, testers,…) aimed at working together. And this usually requires cultural changes, and a plan to re-skill technical capabilities and cross-wise abilities.
In this whitepaper, let me explain you my top 10 tips for implementing agile development with a focus on delivering software continuously with quality. Download now!