Agile Requirements Information Model (5) – For Agile Programs (b): Nonfunctional Requirements | Scaling Software Agility Agile Requirements Information Model (5) – For Agile Programs (b): Nonfunctional Requirements Posted on January 8, 2009 by Dean Leffingwell in Agile Requirements Note: This is the fifth in a series of posts describing, in more rigorous terms, A Lean, Scalable Requirements Information Model for the Agile Enterprise (AE RIM) that underlies the Big Picture Series. In this series, I’ve been collaborating with Juha-Markus Aalto, Director of Operational Development for Nokia S60 Software Unit, where a variant of the model is being developed and applied on a very large scale development project. In the last post, the Agile Requirements Information Model For Agile Programs we described those elements of the model, Features and Feature Backlog that are relevant to the Program Level of the Big Picture. Agile Enterprise Big Picture with Program Level Highlighted In this post, we complete that discussion with a discussion of Non-functional Requirements. Non-functional Requirements in Agile Development
DevOps « Scaled Agile Framework In order for you to keep up with customer demand, you need to create a deployment pipeline. You need to get everything in version control. You need to automate the entire environment creation process. You need a deployment pipeline where you can create test and production environments, and then deploy code into them, entirely on demand.– Erik To Grasshopper. The Phoenix Project DevOps is a pattern, not a team. Real, tangible software development value occurs only when the end-users are successfully operating the software in their environment. Deployment Operations is an Integral Part of the Software Value Stream The goal of software engineering is to deliver usable and reliable software products to the end users. However in most cases, development teams still deliver software to deployment in large batches. Deployment Operations Must be “On the Train” In SAFe, Value Streams cover all steps of software value creation and delivery. Figure 1. 3a: Deploy to Staging Every Sprint Summary