0915920514 cs@booksvn.com
EN VI JA KO ZH
Log in Sign up
BooksVN
Trang chủ › eBook › Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise, 1st edition
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise, 1st edition

Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise, 1st edition

BRAND: PEARSON
Publisher:
PEARSON
Author:
Dean Leffingwell
Edition:
(December 27, 2010) © 2011
eBook ISBN:
9780321685407
Print ISBN:
9780321635846
Type:
1 Year Subscription. Dành cho Cá nhân
eBook edition. 1 Year Subscription. Dành cho Cá nhân | Trường ĐH, Nhóm, Thư Viện: Gọi 0915920514 để báo giá Pearson, Vital Source eBook hoặc mua Sách In
Related Tags

Tổng quan sách

Phát hiện và phân tích yêu cầu hiệu quả là phương pháp thực hành quan trọng nhất để phát triển ứng dụng nghiêm túc. Tuy nhiên, cho đến nay, các yêu cầu và phương pháp Agile hiếm khi cùng tồn tại một cách hòa bình. Đối với nhiều doanh nghiệp đang xem xét các phương pháp tiếp cận Agile, việc thiếu các quy trình yêu cầu Agile hiệu quả và có thể mở rộng đã là yếu tố cản trở việc áp dụng Agile. Trong Yêu cầu phần mềm linh hoạt, Dean Leffingwell chỉ ra chính xác cách tạo ra các yêu cầu hiệu quả trong môi trường Agile. Phần I trình bày “bức tranh toàn cảnh” về các yêu cầu Agile trong doanh nghiệp và mô tả mô hình quy trình tổng thể cho các yêu cầu Agile ở cấp độ nhóm dự án, chương trình và danh mục đầu tư Phần II mô tả một mô hình đơn giản, nhẹ nhàng nhưng toàn diện mà các nhóm dự án Agile có thể sử dụng để quản lý các yêu cầu Phần III trình bày cách phát triển các yêu cầu Agile cho các hệ thống phức tạp đòi hỏi sự hợp tác của nhiều nhóm Phần IV hướng dẫn doanh nghiệp phát triển các yêu cầu Agile cho “hệ thống của hệ thống”, bộ ứng dụng và danh mục sản phẩm ngày càng lớn hơn
  1. Foreword xxiiiPreface xxviiAcknowledgments xxxiiiAbout the Author xxxv Part I: Overview: The Big Picture 1
  2. Chapter 1: A Brief History of Software Requirements Methods 3Software Requirements in Context: Decades ofPredictive, Waterfall-Like Processes 5Iterative and Incremental Processes 9Adaptive (Agile) Processes 12Requirements Management in Agile Is Fundamentally Different 16Enterprise-Scale Adaptive Processes 19Introduction to Lean Software 20Summary 28
  3. Chapter 2: The Big Picture of Agile Requirements 31The Big Picture Explained 32Big Picture: Team Level 34Big Picture: Program Level 38Big-Picture Elements: Portfolio Level 43Summary 45
  4. Chapter 3: Agile Requirements for the Team 47Introduction to the Team Level 47Agile Team Roles and Responsibilities 50User Stories and the Team Backlog 55Acceptance Tests 58Unit Tests 60Summary 61
  5. Chapter 4: Agile Requirements for the Program 63Introduction to the Program Level 63Organizing Agile Teams at Scale 64Vision 74Features 75Nonfunctional Requirements 77The Agile Release Train 80Roadmap 81Summary 82
  6. Chapter 5: Agile Requirements for the Portfolio 83Introduction to the Portfolio Level 83Investment Themes 84Portfolio Management Team 85Epics and the Portfolio Backlog 85Epics, Features, and Stories 87Architectural Runway and Architectural Epics 88Summary 91Summary of the Full, Enterprise Requirements Information Model 91 Interlude: Case Study: Tendril Platform 93Background for the Case Study 93System Context Diagram 95 Part II: Agile Requirements for the Team 97
  7. Chapter 6: User Stories 99Introduction 99User Story Form 102INVEST in Good User Stories 105Splitting User Stories 111Spikes 114Technical Spikes and Functional Spikes 114Story Modeling with Index Cards 116Summary 117
  8. Chapter 7: Stakeholders, User Personas, and User Experiences 119Stakeholders 119Identifying Stakeholders 122User Personas 126Agile and User Experience Development 129Summary 133
  9. Chapter 8: Agile Estimating and Velocity 135Introduction 135Why Estimate? The Business Value of Estimating 137Estimating Scope with Story Points 138Understanding Story Points: An Exercise 138An Alternate Technique: Tabletop Relative Estimation 145From Scope Estimates to Team Velocity 146Caveats on the Relative Estimating Model 147From Velocity to Schedule and Cost 148Estimating with Ideal Developer Days 149A Hybrid Model 151Summary 152
  10. Chapter 9: Iterating, Backlog, Throughput, and Kanban 155Iterating: The Heartbeat of Agility 155Backlog, Lean, and Throughput 169Software Kanban Systems 179Summary 180
  11. Chapter 10: Acceptance Testing 183Why Write About Testing in an Agile Requirements Book? 183Agile Testing Overview 184What Is Acceptance Testing? 187Characteristics of Good Story Acceptance Tests 188Acceptance Test-Driven Development 190Acceptance Test Template 192Automated Acceptance Testing 193Unit and Component Testing 196Summary 199
  12. Chapter 11: Role of the Product Owner 201Is This a New Role? 201Perspectives on Dual Roles of Product Owner and Product Manager 202Responsibilities of the Product Owner in the Enterprise 207Five Essential Attributes of a Good Product Owner 218Collaboration with Product Managers 220Product Owner Bottlenecks: Part-Time Product Owners, Product Owner Proxies, Product Owner Teams 221Seeding the Product Owner Role in the Enterprise 222Summary 224
  13. Chapter 12: Requirements Discovery Toolkit 227The Requirements Workshop 228Brainstorming 232Interviews and Questionnaires 237User Experience Mock-Ups 241Forming a Product Council 243Competitive Analysis 244Customer Change Request Systems 245Use-Case Modeling 247Summary 247 Part III: Agile Requirements for the Program 249
  14. Chapter 13: Vision, Features, and Roadmap 251Vision 251Expressing the Vision 252Features 255Estimating Features 257Testing Features 260Prioritizing Features 261The Roadmap 271Summary 273
  15. Chapter 14: Role of the Product Manager 275Product Manager, Business Analyst? 276Responsibilities of the Product Manager in a Product Company 276Business Responsibilities of the Role in the IT/IS Shop 278Responsibility Summary 279Phases of Product Management Disillusionment in the Pre-Agile Enterprise 280Evolving Product Management in the Agile Enterprise 283Responsibilities of the Agile Product Manager 287Summary 297
  16. Chapter 15: The Agile Release Train 299Introduction to the Agile Release Train 300Driving Strategic Alignment 304Institutionalizing Product Development Flow 305Designing the Agile Release Train 308Planning the Release 308Tracking and Managing the Release 309Release Retrospective 310Measuring Release Predictability 310Releasing 313Summary 317
  17. Chapter 16: Release Planning 319Preparing for Release Planning 319Release Planning Narrative, Day 1 322Release Planning Narrative, Day 2 328Stretch Goals 336Summary 338
  18. Chapter 17: Nonfunctional Requirements 339Modeling Nonfunctional Requirements 340Exploring Nonfunctional Requirements 342Persisting Nonfunctional Requirements 347Testing Nonfunctional Requirements 348Template for an NFR Specification 352Summary 354
  19. Chapter 18: Requirements Analysis Toolkit 355Activity Diagrams 357Sample Reports 358Pseudocode 358Decision Tables and Decision Trees 359Finite State Machines 361Message Sequence Diagrams 364Entity-Relationship Diagrams 365Use-Case Modeling 366Summary 366
  20. Chapter 19: Use Cases 367The Problems with User Stories and Backlog Items 368Five Good Reason to Still Use Use Cases 368Use Case Basics 369A Use Case Example 375Applying Use Cases 377Use Cases in the Agile Requirements Information Model 378Summary 379 Part IV: Agile Requirements for the Portfolio 381
  21. Chapter 20: Agile Architecture 383Introduction to the Portfolio Level of the Big Picture 383Systems Architecture in Enterprise-Class Systems 384Eight Principles of Agile Architecture 390Implementing Architectural Epics 399Splitting Architecture Epics 403Summary 405
  22. Chapter 21: Rearchitecting with Flow 407Architectural Epic Kanban System 408Overview of the Architectural Epic Kanban System 4091. The Funnel: Problem/Solution Needs Identification 4122. Backlog 4153. Analysis 4184. Implementation 423Summary 427
  23. Chapter 22: Moving to Agile Portfolio Management 429Portfolio Management 429When Agile Teams Meet the PMO: Two Ships Pass in the Night 431Legacy Mind-Sets Inhibit Enterprise Agility 432Legacy Mind-Sets in Portfolio Management 433Eight Recommendations for Moving to Agile Portfolio Management 436Summary: On to Agile Portfolio Planning 447
  24. Chapter 23: Investment Themes, Epics, and Portfolio Planning 449Investment Themes 450Epics 452Identifying and Prioritizing Business Epics: A Kanban System for Portfolio Planning 456Summary 467
  25. Chapter 24: Conclusion 469Further Information 470 Appendix A: Context-Free Interview 471 Appendix B: Vision Document Template 475 Appendix C: Release Planning Readiness Checklist 485 Appendix D: Agile Requirements Enterprise Backlog Meta-model 489 Bibliography 491Index 495
Chat Zalo