[Reading] ➮ Agile Software Requirements ➶ Dean Leffingwell – Peakpopa.info

Agile Software Requirements I have been told by agile practitioners that this is on the best books on the subject Being an agile enthusiast myself, I found it to be a real mind opener I loved how it explained the roles in agile on both team and program level I also loved how they suggested transition paths from traditional project managers to agile project managers Although it is a software methodology book, I would say it is and easy to moderate read The explanations are clear, lots tips and tricks that you can immediately apply in your organisation and the pictures are very well supporting the text I would recommend this book to newbies who might get a very nice overview of what Agile is, as well as experienced agilists who can always build a broader view. This book is not only about requirements but also about Agile per se It s rather long and detailed book and if you are familiar with SAFe some parts might be boring However, some parts of the book are truly inspiring including Product Owner role s in a large enterprise and what are Agile pitfalls Personally, my favorite chapters are about scaling the agile to a portfolio and how to set up large projects. We Need Better Approaches To Understanding And Managing Software Requirements, And Dean Provides Them In This Book He Draws Ideas From Three Very Useful Intellectual Pools Classical Management Practices, Agile Methods, And Lean Product Development By Combining The Strengths Of These Three Approaches, He Has Produced Something That Works Better Than Any One In IsolationFrom The Foreword By Don Reinertsen, President Of Reinertsen Associates Author Of Managing The Design Factoryand Leading Expert On Rapid Product Development Effective Requirements Discovery And Analysis Is A Critical Best Practice For Serious Application Development Until Now, However, Requirements And Agile Methods Have Rarely Coexisted Peacefully For Many Enterprises Considering Agile Approaches, The Absence Of Effective And Scalable Agile Requirements Processes Has Been A Showstopper For Agile Adoption InAgile Software Requirements,Dean Leffingwell Shows Exactly How To Create Effective Requirements In Agile EnvironmentsPart I Presents The Big Picture Of Agile Requirements In The Enterprise, And Describes An Overall Process Model For Agile Requirements At The Project Team, Program, And Portfolio Levels Part II Describes A Simple And Lightweight, Yet Comprehensive Model That Agile Project Teams Can Use To Manage Requirements Part III Shows How To Develop Agile Requirements For Complex Systems That Require The Cooperation Of Multiple Teams Part IV Guides Enterprises In Developing Agile Requirements For Ever Larger Systems Of Systems, Application Suites, And Product Portfolios This Book Will Help You Leverage The Benefits Of Agile Without Sacrificing The Value Of Effective Requirements Discovery And Analysis You Ll Find Proven Solutions You Can Apply Right Now Whether You Re A Software Developer Or Tester, Executive, Project Program Manager, Architect, Or Team Leader Es un libro muy amplio sobre SAFe en que describe a partir de como funcionan los requerimientos como funciona cada parte de ese marco de referencia Es un libro exhaustivo y en ciertas partes toma un modo acad mico, por lo que puede resultar a ser cansado si no se est acostumbrado a este tipo de lecturas.Es muy recomendable este libro si est s en una empresa que est adoptado SAFe o eres nuevo y no conoces nada de ello, incluso si no se sabe nada de m todos giles No s si pudiera ser referencia para alguna certificaci n, pero s para conocer a fondo la forma de trabajo. Pra que isso tudo Book title is a bit misleading, as this book covers not only requirements part of the agile, but all aspects of agile in software development at various levels of enterprise companies from investment themes, to epics features stories It has nearly 500 pages and lot of stuff is well known, but there are some goodies. Anyone wanting to learn and understand SAFe this is the book for you I absolutely loved it I was able to grasp and implement most of the things. This handbook provides a SAFe framework for scaling the product road map across many agile teams that supports both independent and coordinated release cycles It introduces an hierarchy of Epic Sub epic Feature Story Task order, where Epics are managed by a cross functional project management body and Features are owned by team leadership It supports many of the better agile practices today, including the practices spelled out in the Martin Fowler and Mike Cohen book series Both Agile Testing and Continuous Delivery books are explored, as well as the author s prior work on requirements management As we adopt these concepts at Constant Contact, using JIRA AGILE as our record of reference, we had to add the Structure plugin and other cross project capability to manage within this SAFe framework Atlassian acknowledged that they are working on features that will support the SAFe framework in the future. Good overview of how Agile fits into a very large enterprise Other agile books I read seemed only written for small teams This one scales it up all the way through the organization and gives a framework Gave a book club at work on this one. I expected a book on agile requirements, but this is not just about requirements Instead Dean has compiled the most comprehensive work on agile to date The book covers agile at team, programme and enterprise level expertly laying out practices and principles at all levels to guide an enterprise He provides an easy adaptable and lightweight blueprint of how to organise an agile enterprise from ideation and strategy down to daily operations in teams An amazing accomplishment This is a must read for anyone contemplating agile in any enterprise.


About the Author: Dean Leffingwell

Is a well-known author, some of his books are a fascination for readers like in the Agile Software Requirements book, this is one of the most wanted Dean Leffingwell author readers around the world.


Leave a Reply

Your email address will not be published. Required fields are marked *