Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 1. Getting started with Agile AL... > Building blocks of Agile ALM - Pg. 17

Building blocks of Agile ALM 17 People Transparency Changes ALM Figure 1.7 Transparency, people, changes, risk, and concrete business value are essential factors that influence software engineering and that should be stressed in an ALM project. Business value Risk importance of transparency and on alignment with business value, as illustrated in figure 1.7. We'll learn more about concrete Agile strategies in chapter 2 and we'll discuss lightweight, primary open source tools throughout the rest of this book. Right now, we'll look at the building blocks of A gile ALM . This information will give you the nec- essary preparation for subsequent chapters. 1.3 Building blocks of Agile ALM What exactly is A gile ALM and what value does it add? In this section, we'll consider that question in the context of software releases and service orientation. We'll also discuss how important it is to be focused on the stakeholders' needs and to use a task-based approach. We'll consider configurable, pluggable systems and standards. Finally, we'll talk about what it means to use and cope with "polyglot" environments, with their many languages and technologies, and how to apply open source methods and automation. The tools we'll cover in this book will enable you to implement and support these build- ing blocks. Tools are important, but it's also important to start with a stakeholder focus. 1.3.1 Stakeholder focus Developing a software application isn't just about writing code. Once developed, code must be tested, approved, and deployed to the live environment where it must be maintained. Many programmers will expect their code to migrate to the live environ- ment as soon as it's completed to see that their deliverables are used, whereas others understand that the release will be promoted when it's tested and approved. INTERDISCIPLINARY ROLES In this book, the developer is a person who not only develops or programs code but also has an interdisciplinary skill set. Develop- ers are skilled in coding, but they should also know how to test, configure, and ship features. As a consequence, some people don't like to see the word