Deriving an outside-in agile process

Agile Development continues to grow in popularity, but if you've been using Agile Development, or a just beginning research, you've likely found that Agile Development is a general term referring to one of a number of specific approaches such as XP, Scrum, Crystal, Lean, and others. While there are a variety of specific ways to practice Agile development, they all follow a common rhythm. We'll talk about that here.

All these named Agile approaches currently share one shortcoming. They're heavy on engineering an project management practices - details on how to build software, but light or altogether silent on envisioning what to build. That's what this book is for.

We'll talk about a design process that starts far outside of the software, and works its way back in. We'll consider the reasons why we're building the software, the people the software will serve, and the ways they might use it. Modeling those concerns first will help us arrive at and validate our decisions on what to build.

Let's get started.

1. Agile's Iterative Development Incremental Release Rhythm
2. Designing outside-in
3. A conjoined Agile outside-in design and development process
4. Contextualizing an outside in process