Book Image

The Mini Book of Agile

By : Mauricio Rubio Parra
Book Image

The Mini Book of Agile

By: Mauricio Rubio Parra

Overview of this book

Think of this book as Agile for Dummies (or Agile for anyone and everyone). This Agile book will allow you to master the most important concepts of Agile development, Agile project delivery, and Agile project management. This mini book has been designed to enable you to manage your projects in an Agile way. This mini book will walk you through the fundamentals, principles, and key concepts of Agile, Agile project management, and Agile Delivery. The book includes valuable resources, graphics, and examples that will allow you to grasp the key essence of Agile, Agile rituals, Agile practices, Agile concepts, and the key differences between Agile and traditional project management. After reading this book, you will have a thorough understanding of Agile and how to put Agile into practice at work and in your personal projects.
Table of Contents (16 chapters)
1
Chaper 1: Introduction
Free Chapter
2
Chapter 2: What is Agile?
3
Chapter 3: Why go Agile?
4
Chapter 4: How it all began
5
Chapter 5: The Different Agile Methodologies
6
Chapter 6: Agile Principles
7
Chapter 7: The Agile Culture
8
Chapter 8: Agile Roles
9
Chapter 9: Agile Concepts
10
Chapter 10: Agile Artifacts
11
Chapter 11: Agile Rituals
12
Chapter 12: Agile Tools
13
Chapter 13: Agile vs. Waterfall
14
Chapter 14: Agile FAQs
15
Chapter 15: Agile Myths
16
Chapter 16: The Agile Knowledge Base | AgileKB.com

Chapter 13: Agile vs. Waterfall

https://cdn-images-1.medium.com/max/1600/1*x5q182L_noeMObXUvjk7pg.png

Agile is iterative. It's also time boxed. You deliver quickly and often & you iterate and improve regularly. In Agile you break down work into user stories (tasks) and work on those user stories during a short, set time frame or timebox called Sprint. So Agile projects tend to last from a few weeks to a few months. 

 

In Agile work isn't done in phases like in traditional Project Management but instead within the Sprints themselves and they can combine different types of tasks such as design, testing and deployment within the same Sprint. And you can repeat this (combining different types of activities) multiple times, pretty much as many times as needed or required. So in Agile, for example, testing isn't done only in a particular point in time, but actually regularly, when appropriate. 

In Agile, scope is flexible and can change throughout the lifecycle of the projects as new needs arise or as the Product Owner re...