BOOKS ✮ Agile Software Requirements Author Dean Leffingwell –

Agile Software Requirements 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

10 thoughts on “Agile Software Requirements

  1. says:

    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.

  2. says:

    First of all, I think the book title sucks Dean Leffingwell s book is named Agile Software Requirements, but it is all about the Enterprise Agile model called Scaled Agile Framework a.k.a SAFe I don t understand why that couldn t have been the title of the book also.I have hands on experience about SAFe model, when it was invented at least partly at Nokia I was heavily involve

  3. says:

    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 ente

  4. says:

    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

  5. says:

    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.

  6. says:

    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, incl

  7. says:

    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 an

  8. says:

    Fantastic and a gotta have for any organization that is trying to bridge the impedance mismatch between teams doing agile development and an organizations portfolio management and release management functions.I frankly believe the title is slightly misleading because it is so muchthan a book on agile software requirements I suppose I understand why since Scaling Software Agility was already taken that was

  9. says:

    When reading other books about agile lean, it has always chafed me that they focus exclusicely on the development team level, and assume that stories magically appear in the backlog Instead, this book focus on what goes on in a large enteprise to put the stories into the backlog As such it is one of the few books I ve seen that shows how to scale agile lean methodologies.It is a bit wordy, but there are plenty

  10. says:

    A great book, but not particularly on requirement handling in an agile world, but on how to adopt agile in a large scale Sure, the book goes into the usual agile for dummies for one team, but it also covers every part of the agile process with clear examples for both team, program and enterprise It so far the only book I ve found that deals with the added complexity of running agile on a large scale with releases, a

Leave a Reply

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