xmas15 Öle & Betriebsstoffe für Ihr Auto Jetzt Mitglied werden bestsellers-of-the-year-2015 Cloud Drive Photos boseFly Learn More pantry Geschenkideen Hier klicken Fire Shop Kindle

An Ihren Kindle oder ein anderes Gerät senden


Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Keine Abbildung vorhanden

Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series) [Kindle Edition]

Dean Leffingwell
4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)

Kindle-Preis: EUR 30,69 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

  • Länge: 518 Seiten
  • Sprache: Englisch
  • Aufgrund der Dateigröße dauert der Download dieses Buchs möglicherweise länger.
  • Sie haben noch keinen Kindle? Hier kaufen oder mit einer unserer kostenlosen Kindle Lese-Apps sofort zu lesen anfangen.
Kostenlose Kindle-Leseanwendung Jeder kann Kindle Bücher lesen  selbst ohne ein Kindle-Gerät  mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.

Geben Sie Ihre E-Mail-Adresse oder Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Weitere Ausgaben

Preis Neu ab Gebraucht ab
Kindle Edition EUR 30,69  
Gebundene Ausgabe EUR 40,92  



Praise for Agile Software Requirements "In my opinion, there is no book out there that more artfully addresses the specific needs of agile teams, programs, and portfolios all in one. I believe this book is an organizational necessity for any enterprise." -Sarah Edrie, Director of Quality Engineering, Harvard Business School "Agile Software Requirements and Mr. Leffingwell's teachings have been very influential and inspiring to our organization. They have allowed us to make critical cultural changes to the way we approach software development by following the framework he's outlined here. It has been an extraordinary experience." -Chris Chapman, Software Development Manager, Discount Tire "This book supplies empirical wisdom connected with strong and very well-structured theory of succeeding with software projects of different scales. People new to agile, practitioners, or accomplished agilists-we all were waiting for such a book." -Oleksandr (Alex) Yakyma, Agile Consultant, www.enter-Agile.com "This book presents practical and proven agile approaches for managing software requirements for a team, collaborating teams of teams, and all across the enterprise. However, this is not only a great book on agile requirements engineering; rather, Leffingwell describes the bigger picture of how the enterprise can achieve the benefits of business agility by implementing lean product development flow. His 'Big Picture' of agile requirements is an excellent reference for any organization pursuing an intrinsically lean software development operational mode. Best of all, we've applied many of these principles and practices at Nokia (and even helped create some of them), and therefore we know they work. -Juha-Markus Aalto, Agile Change Program Manager, Nokia Corporation "This pragmatic, easy-to-understand, yet thought-provoking book provides a hands-on guide to addressing a key problem that enterprises face: How to make requirements practices work effectively in large-scale agile environments. Dean Leffingwell's focus on lean principles is refreshing and much needed!" -Per Kroll, author, and Chief Architect for Measured Improvements, IBM "Agile programming is a fluid development environment. This book serves as a good starting point for learning." -Brad Jackson, SAS Institute Inc. "Dean Leffingwell captures the essence of agile in its entirety, all the way from the discrete user story in the 'trenches' to complex software portfolios at the enterprise level. The narrative balances software engineering theory with pragmatic implementation aspects in an easy-to-understand manner. It is a book that demands to be read in a single sitting." -Israel Gat,


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


  • Format: Kindle Edition
  • Dateigröße: 15740 KB
  • Seitenzahl der Print-Ausgabe: 560 Seiten
  • Gleichzeitige Verwendung von Geräten: Bis zu 5 Geräte gleichzeitig, je nach vom Verlag festgelegter Grenze
  • Verlag: Addison-Wesley Professional; Auflage: 1 (27. Dezember 2010)
  • Verkauf durch: Amazon Media EU S.à r.l.
  • Sprache: Englisch
  • Text-to-Speech (Vorlesemodus): Aktiviert
  • X-Ray:
  • Word Wise: Nicht aktiviert
  • Verbesserter Schriftsatz: Aktiviert
  • Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: #90.579 Bezahlt in Kindle-Shop (Siehe Top 100 Bezahlt in Kindle-Shop)

  •  Ist der Verkauf dieses Produkts für Sie nicht akzeptabel?

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


4 Sterne
2 Sterne
1 Sterne
4.0 von 5 Sternen
4.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
1 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The Agile Enterprise ... 28. September 2013
Format:Gebundene Ausgabe|Verifizierter Kauf
Very good and a real practible view to a lean agile software organization/enterprise. Contains working ideas for software portfolio and program management interlinked with agiles teams. Use as additional reference and to stay uptodate: [...]
War diese Rezension für Sie hilfreich?
Missbrauch melden
0 von 3 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Not the best one 20. April 2015
Format:Gebundene Ausgabe|Verifizierter Kauf
There are other better books for learning the SAFe and Agile in general.

This is not just my view, I was told this by someone more experienced
War diese Rezension für Sie hilfreich?
Missbrauch melden
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.5 von 5 Sternen  44 Rezensionen
32 von 32 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The first complete book on what an enterprise level agile process should look like 26. November 2011
Von Tad Anderson - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
I still remember the first few pages of Managing Software Requirements: A Unified Approach (The Addison-Wesley Object Technology Series). I was in BWI waiting on my daughter's flight to arrive. The book opened with such a great beginning I knew I was going to love it. In a nutshell what I heard the authors say was we have years of experience that you don't, let us show you what we have learned so you don't have to repeat our mistakes. That is my number one reason for reading books. The message at the beginning of this book is the same.

I feel this is the first complete book on what an enterprise level agile process should look like. What baffles me is the number of enterprises I have been in that have not come close to implementing 10% of the process this book outlines, yet they call themselves agile and lean. The one thing this book brings to light is just how complex and advanced agile processes are. Like the book says, "it is not easy, it is agile".

This book has the caveat that certain skills are required for the agile teams to be successful. I agree with that completely. The thing I have a hard time with is the fact that agile processes assume such skill sets are readily available. They aren't. That is why I see such a mess in 90% of the attempts I have seen when enterprises attempt to go agile. Almost all of them will claim to be successful at implementing their agile processes, but budgets and bugs don't lie. Agile does not equate to simple or easy, actually the opposite is true.

So then does that mean agile methods should be avoided and this book is not worth reading? Absolutely not. It is one of the few books that may just help you implement a successful agile enterprise environment. If nothing else, it does not pull punches, so it will enlighten you as to just how difficult it is to pull it off. It is a must read for anyone out there claiming to be running an agile enterprise.

This book is unique in that it provides a complete view of all the roles throughout the enterprise that are involved with the process and does a great job of defining the activities they are involved with. The book calls the process Agile Enterprise Big Picture: Scaled Agile Delivery Model, or the Big Picture for short. The process has three levels, the Team level, the Program level, and the portfolio level.

The book starts out with a really cool overview of software development process models. The chapter goes from Waterfall to Spiral, RAD, RUP to Crystal, Scrum, XP, FDD, DSDM, Open UP, Kanban to Enterprise-Scale Adaptive Processes.

The rest of part one dedicates four more chapters to introducing the Agile Enterprise Big Picture: Scaled Agile Delivery Model (the Big Picture).

The book has three more parts, one for each process level. The Team level, the Program level, and the portfolio level. Each part has several chapters that drill deep into the details of each level.

One of the things I really like about the book is that it acknowledges the importance of software architecture. It does not go along with the common agile "emergent architecture" view. The book advocates intentional architecture. It also acknowledges project managers and doesn't just drop them from the picture.

Another thing I really like is that modernization is realized through the architectural epics. Modernization strategies are usually nonexistent in most enterprises until they find it is too late. Then they are implemented in a haphazard way creating so much more damage than necessary. This book makes modernization strategies first class citizens through architectural epics.

If you are in an enterprise environment and you are attempting to implement agile processes, this book is the book to have. Agile requires experience. This book is filled with experience from the trenches. The book is written well and the author's writing style makes it an easy read. As easy as you can make a topic that is so complex.

This books takes all the activities, artifacts, roles, responsibilities, and processes that have always made a successful software development project using classic software development processes such as the unified process and the RUP, and repositions them in their agile context.

All in all I highly recommend this book to anyone working in an enterprise level software development environment. The developer, project manager, tester, software architect, process engineer, business analyst, scrum master, product owner, project sponsor, CIO, CFO, and CEO could benefit from reading this book, even if you are not in an agile shop.
34 von 39 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Close, But Wrong Features 13. Oktober 2013
Von Earl Beede - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Verifizierter Kauf
I believe Dean Leffingwell has a solid grasp of the issues that face agile and, in particular, Scrum as it scales. He does well in basing his approach on the the thoughts of people like Donald Reinertsen. However, I can give the book only three stars as I disagree with Mr. Leffingwell in several important aspects.

First area is the people Mr. Leffingwell left out. If one is going to talk about scaling software development, one must at least engage Fred Brooks and his recent work, The Design of Design. Even if you disagree with Mr. Brooks' position that a single mind is required for conceptual integrity (at a given level of abstraction), you need to more than throw an agile principle at his well reasoned thought.

Then there is Tom Gilb. Mr. Gilb was agile for there was an agile. I feel that anybody who wants to talk seriously about scaling and agile needs to engage Mr. Gilb's position on requirements and their being testable at any level of abstraction. Again, you may disagree but not to consider it seems a huge oversight. His design impact estimation would be a perfect add to an architecture workshop.

A second area is the lack of testability at the higher levels of abstraction. Given a features approach, it seemed to me that Mr. Leffingwell had a hard time describing how to test things at the highest level. If, instead, he had the higher levels focus more on the problem and the (non-function) characteristics that made the client/customer/user feel the products would solve their problem, then coming up with tests is not that difficult. You can let an architecture "emerge" to the degree you have well designed tests that state that whatever emerges, must pass the tests!

A third area is Mr. Leffingwell's approach to requirements. I disagree with his features driven approach. I have worked as long in the field as Mr. Leffingwell and I have found that his approach, while perhaps letting the team be as efficient as possible in creating a thing, often leads to building the wrong thing. This isn't so bad on the small scale but large scale development really doesn't have the chance to fail fast AND cheap. If it does fail, it is always expensive. Fast feedback at the large end of development isn't a good substitute for building the right thing in the first place. I seek fast feedback, I just don't use it as a crutch for poor understanding of the clients problems/opportunities.

The main point is that "agility" is far more necessary when you take a features first approach as, to paraphrase the Cheshire Cat, "Any solution will work when you don't know the problem." When the problem is still not well understood, features (solutions) will fight to have their way, failing more often than succeeding, forcing the development organization to spin and flex. While Mr. Leffingwell will argue that requirements are not fully knowable at the start of a project (or if ever), that doesn't mean that the are not a least partially knowable. Given a reasonable approach to truly understanding the problem, I think practitioners will find that their business don't need to be as "agile" when they understand the customer's actual needs (not just their feature wants).

Even with those concerns, I have several action items to improve my seminars, writing, and coaching . I needed to remember the Cost of Delay more than I have. The idea of using the Kano model to talk about investment levels is great. If the concerns I listed don't bother you, you will probably get more bit more.
13 von 14 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen A detailed and extensive study of the agile gathering and management of requirements in enterprises 5. August 2011
Von Methods & Tools Software Development Magazine - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
Although many might tend to limit the concept of agile requirements to "user stories", this book reminds us that there could be more than just a post-it on an information radiator when we talk about requirements. The title of one of the initial chapters is "The Big Picture of Agile Requirements" and this book provides it, together with the small details that can help you write better stories.

Dean Leffingwell describes the general context of managing requirements in organizations based on a three levels view: portfolio, program and team. The concept of requirements is different at each of these levels: from the investment themes and epics of the enterprise strategy to the user stories implemented by teams during Scrum sprints. An interesting concept developed in the book is the Agile Release Train (ART) that aggregates user stories in features set. The goal is to adjust the team's capacity to produce software with the ability of customers to absorb it.

The book is very well written, achieving balance between a structured approach and easiness to read. It contains many case studies, templates and sample agenda that help relate the ideas expressed with the daily activities. Three appendixes at the end propose interviews and document templates, along with a release-planning checklist.

This book provides a detailed and extensive study of the agile gathering and management of requirements in enterprises and I will recommend it to everybody involved in some software requirement activity, from the business analyst to the project manager or developer.
6 von 6 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Fills in the Gaps / Addresses Key Challenges 3. Februar 2011
Von Mauricio Zamora - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
Agile Software Requirements: Lean Requirements for Teams, Programs and the Enterprise does a fantastic job of addressing the overall structure required to truly develop software in a manner that ultimately meets the end vision in mind while also establishing the proper transparency and visibility for internal stakeholders and external clients. There are many Agile books do a good job of defining the "process" behind the methodology or the right "technical" philosophy to enable Agile driven development. Several of these books will get folks new to Agile or folks without stakeholder pressure started quickly.

While Lean Requirements for Teams, Programs and the Enterprise will also give you a good grounding on Agile, it's focus is really on establishing the right vision, roadmap, requirements and execution structure to enable large scale development (large number of teams and/or long duration product investments) while remaining Agile from a development team standpoint.

For the longest time, Agile has suffered from myths / challenges including:
* Can't scale to meet a large # of practitioners or teams
* Won't enable software companies to communicate feature availability to clients in future releases
* Won't work for projects requiring upfront intentional / robust architecture
* Can't transform existing Product Management organizations to be effective Product Owners
* Can't enable the right level of visibility and understanding for senior executives
* Etc.

As a result, many large software development efforts have struggled to remain Agile. Lean Requirements for Teams, Programs and the Enterprise finally addresses these challenges and many others. Dean has worked closely with several large companies over the past few years to develop the framework described in his book. Leveraging the experience he gained, he has now described his proposed structure in a manner that will enable others to also successfully leverage Agile in large scale environments. His book is based on real experience vs. academia.

As others have referenced previously, the book addresses the appropriate structure for the various different audiences involved - the Team, the Program, the Portfolio, etc. What I also love about the book is that it can be used equally well for a small software development team of 10 that still has to communicate upcoming releases, etc. to end stakeholders and clients. The structure Dean describes in his book scales up and scales down

I have personally been able to leverage a lot of Dean's best practices that are now described well in this book successfully - both at small scale (team of ten) and large scale (12 teams of a total of 150 practitioners over a two year period). Dean's book is a fantastic and MUST read. I honestly believe it will help organizations get to the next level while also keeping Agile in the mainstream vs. another fad.
6 von 6 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen A Path for the Unforgiven 19. Januar 2013
Von Joe Butson - Veröffentlicht auf Amazon.com
Format:Kindle Edition|Verifizierter Kauf
It is difficult to improve on a review like the one Per Kroll wrote, but I do need to add my own opinion on the book.

While the book's title may be deceptive, it is likely the best way to gather an audience for what I found to be an excellent and accessible recipe for implementing agile at scale. Having led Agile Teams at the Feature and Component Level, I know how powerful and fundamental those concepts are in engaging a team of over 100 people in a large Program.

Most profitable organizations have bits and pieces of best practices within and readers will recognize this when they skim through the books later chapters where Leffingwell begins to synthesize the fundamentals of agility and lean practices "up the organization."

Most organizations I have worked within "foam the runway" for large projects/programs to land. It is never pretty how ugly these landing can be with traditional planning only able to set up the "triage" ward for the inevitable crashes. This book describes how portfolio managers can create an agile architecture using epics to create a smooth landing for programs and keep the architecture aligned with the portfolio vision epics. Using lean techniques at the portfolio level brilliantly increases flow/reduces waste and keeps the focus on business value.

The book is a breeze to read for the agile community but I also think the jargon is limited enough that any manager can grasp it's fundamental power, and implement basic ideas/concepts of the book within a week of picking it up. I certainly hope this is the case as I am delivering a handful to my local colleagues this week.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Erster Beitrag:
Eingabe des Log-ins

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen

Ähnliche Artikel finden