If you feel the need to improve your current Agile practice and are looking for practical ideas, this is the book for you. This book clears the air about Agile (a simple yet overloaded term in software industry) and explains the what/why/how of Agile - WHAT is Agile, WHY one must go for it and HOW to be Agile? For the 'how' part, the book shares the key essence of Agile in a framework agnostic manner, then provides condensed summary of two most popular approaches for implementing Agile - Scrum and Kanban.




If you feel the need to improve your current Agile practice and are looking for practical ideas, this is the book for you. This book clears the air about Agile (a simple yet overloaded term in software industry) and explains the what/why/how of Agile - WHAT is Agile, WHY one must go for it and HOW to be Agile? For the 'how' part, the book shares the key essence of Agile in a framework agnostic manner, then provides condensed summary of two most popular approaches for implementing Agile - Scrum and Kanban.
Besides giving a crisp overview of Agile, Scrum and Kanban, this book also answers some difficult questions like how to decide Sprint length, why use story point estimation, how to avoid waterfall in your Sprint, how to combine Scrum and Kanban, among others.
The core belief in this book is: 'process must subordinate to business outcomes, and not the other way around'. Which means that your process must enable better business outcomes and if it does not, you must be ready to alter it, evolve it or replace it. On the contrary, compromising business outcomes to ensure process compliance (per management order) is not only a ridiculous idea, it is against the idea of Agile itself.