Agile Software Requirements Lean Requirements Practices for Teams Programs and the Enterprise 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 practic

  • Title: Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
  • Author: Dean Leffingwell Don Widrig
  • ISBN: 9780321635846
  • Page: 371
  • Format: Hardcover
  • 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 isolation 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 isolation From the Foreword by Don Reinertsen, President of Reinertsen Associates author of Managing the Design Factory and 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 In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments.Part 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.

    • [PDF] Download å Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise | by ✓ Dean Leffingwell Don Widrig
      371 Dean Leffingwell Don Widrig
    • thumbnail Title: [PDF] Download å Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise | by ✓ Dean Leffingwell Don Widrig
      Posted by:Dean Leffingwell Don Widrig
      Published :2020-05-13T16:19:18+00:00

    About "Dean Leffingwell Don Widrig"

    1. Dean Leffingwell Don Widrig

      Dean Leffingwell Don Widrig Is a well-known author, some of his books are a fascination for readers like in the Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise book, this is one of the most wanted Dean Leffingwell Don Widrig author readers around the world.

    581 thoughts on “Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise”

    1. 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. 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 involved in taking it in to use in Multimedia area. I don't want to talk too much about SAFe model this time, I try to c [...]


    3. 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 re [...]


    4. 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.


    5. 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. 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 Test [...]


    7. 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 immed [...]


    8. 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 much more than a book on agile software requirements. I suppose I understand why since Scaling Software Agility was already taken - that was his list book :-)I really can't say enough about this book and the value found wit [...]


    9. 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 of explaining pictures (some of which are gratuitous) so you can read it quite sel [...]


    10. 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, architecture, NFR, different cadence etc). Truly recommended for anyone with an [...]


    11. Basically a book on SAFe framework, on how to scale Agile. A must read if you think about doing large scale Agile projects. The idea on team level, program level and portfolio level is spot on and can be a great tool. It maybe considered a bit prescriptive but I think everyone can customize and adopt what works for your organisation. What is lacking for me is that it is such a big book on requirement but it mentions nothing about business process reengineering or story maps.


    12. I was sceptical about SAFe but found the book really pragmatic. lots of practical approaches to the real challenges you face with agile in larger environments. In a perfect world you should not have to use some of these and could apply a "purer" agile approach but in many environments these may help you get benefit when you are not able to overcome resistance with other approaches.


    13. Agile Software Requirements read like an advertisement for the Agile development method -- it's more of a **how** guide, rather than something which gives justifications or substance as to **why**. Consider it a good resource if you're looking to implement a full agile process to your business, but not if you're looking for research into the value of agile development as a practice.


    14. Good for structuring Agile into the enterprise level. However, better take this as one of the many possibilities rather than applying it by the book. Agile is really about decentralization and an empowerment mindset. So having a book to "organize" agile seems a bit outdatedBut the concepts of programs are good. I'm using it in my company


    15. It should be required reading for anyone helping a company through an agile transformation. I read it cover to cover and marked up many of the pages. Quite a useful desk reference, at least until the next methodology comes along


    16. Good textbook on lean software requirements. It was instrumental in shaping a program level presentation on the performance and reliability of our systems. Most agile books focus on the team and Leffingwell focuses on a broader audience; teams, programs and enterprises.


    17. Excellent overview about working with Software Requirements. Not only good for POs but also Scrum Masters and Management to learn about how to deal with requirements beyond the team level (features, epics, themes). This book is the foundation of the later SAFe framework.


    18. This book was marketed as being useful for managing multiple agile teams within a portfolio. Instead, it was primarily (~80%) a rehash of how to do Agile, which plenty of other books have already addressed.



    19. A very good journey through the trade of defining and managing requirements in an agile context. A must read book.




    20. 3.5 stars.Could be shorter, but in general is a good overview of agile practices for large enterprises.



    Leave a Reply

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