[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242192-105":53,"doc-detail-242192-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","agile-software-requirements-book-table-of-contents-lean-requirements-practices-for-teams-programs-and-the-enterprise","Agile Software Requirements - Book Table of Contents - Lean Requirements Practices for Teams, Programs, and the Enterprise","","Table of Contents for Agile Software Requirements, structured to explain lean requirements practices across agile team, program, and portfolio levels. The outline covers the evolution of software requirements methods, the “big picture” of agile requirements, and roles, user stories, acceptance and unit testing, estimation, velocity, and Kanban throughput. It further addresses portfolio investment themes, epics and architectural runway, and a requirements discovery toolkit including workshops, interviews, questionnaires, customer change systems, competitive analysis, and use-case modeling.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/agile-software-requirements-book-table-of-contents-lean-requirements-practices-for-teams-programs-and-the-enterprise/242192/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/agile-software-requirements-book-table-of-contents-lean-requirements-practices-for-teams-programs-and-the-enterprise/242192.png","ImageObject",442,249,{"name":88,"@type":89},"Anda","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-12","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",8,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What does the book cover across team, program, and portfolio levels?","Question",{"text":109,"@type":110},"It presents agile requirements practices at the team level (user stories, backlog, acceptance testing), the program level (organization at scale, vision/features, release train, roadmap), and the portfolio level (investment themes, epics, architectural runway).","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How does the “Big Picture of Agile Requirements” relate to lean product development?",{"text":114,"@type":110},"The outline emphasizes the enterprise-wide “big picture” and how implementing lean product development flow helps achieve business agility through agile requirements.",{"name":116,"@type":107,"acceptedAnswer":117},"What requirements engineering techniques and workshop tools are included?",{"text":118,"@type":110},"The table of contents lists a requirements discovery toolkit such as requirements workshops, brainstorming, interviews and questionnaires, user experience mock-ups, forming a product council, competitive analysis, customer change request systems, and use-case modeling.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},242192,1791214844,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":79},962075006959,"https://ap-avatar.wpscdn.com/avatar/e0002397efbe92a78e?_k=1776741047341049297","PRAISE FOR AGILE SOFTWARE REQUIREMENTS  \n“In my opinion, there is no book out there that more artfully addresses the specific  \nneeds of agile teams, programs, and portfolios all in one. I believe this book is an  \norganizational necessity for any enterprise.”  \n—Sarah Edrie, Director of Quality Engineering, Harvard Business School  \n“Agile Software Requirements and Mr. Leffingwell’s teachings have been very influ  \nential and inspiring to our organization. They have allowed us to make critical  \ncultural changes to the way we approach software development by following the  \nframework he’s outlined here. It has been an extraordinary experience.”  \n—Chris Chapman, Software Development Manager, Discount Tire  \n“This book supplies empirical wisdom connected with strong and very well  \nstructured theory of succeeding with software projects of different scales. People  \nnew to agile, practitioners, or accomplished agilists—we all were waiting for such  \na book.”  \n—Oleksandr (Alex) Yakyma, Agile Consultant, [www.enter-Agile.com](www.enter-Agile.com)  \n“This book presents practical and proven agile approaches for managing software  \nrequirements for a team, collaborating teams of teams, and all across the enter  \nprise. However, this is not only a great book on agile requirements engineering;  \nrather, Leffingwell describes the bigger picture of how the enterprise can achieve  \nthe benefits of business agility by implementing lean product development flow. His ‘Big Picture’ of agile requirements is an excellent reference for any organization  \npursuing an intrinsically lean software development operational mode. Best of all,  \nwe’ve applied many of these principles and practices at Nokia (and even helped  \ncreate some of them), and therefore we know they work.  \n—Juha-Markus Aalto, Agile Change Program Manager, Nokia Corporation  \n“This pragmatic, easy-to-understand, yet thought-provoking book provides a  \nhands-on guide to addressing a key problem that enterprises face: How to make  \nrequirements practices work effectively in large-scale agile environments. Dean  \nLeffingwell’s focus on lean principles is refreshing and much needed!”  \n—Per Kroll, author, and Chief Architect for Measured Improvements, IBM  \nAgile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise  \nTable of Contents  \nContents Foreword Preface Acknowledgments About the Author  \nPart I: Overview: The Big Picture  \nChapter 1 A Brief History of Software Requirements Methods  \nSoftware Requirements in Context: Decades of Advancing Software Process Models  \nPredictive, Waterfall-Like Processes  \nIterative and Incremental Processes  \nAdaptive (Agile) Processes  \nRequirements Management in Agile Is Fundamentally Different  \nEnterprise-Scale Adaptive Processes  \nIntroduction to Lean Software  \nSummary  \nChapter 2 The Big Picture of Agile Requirements  \nThe Big Picture Explained  \nBig Picture: Team Level  \nBig Picture: Program Level  \nBig-Picture Elements: Portfolio Level  \nSummary  \nTable of Contents  \nChapter 3 Agile Requirements for the Team  \nIntroduction to the Team Level  \nAgile Team Roles and Responsibilities  \nUser Stories and the Team Backlog  \nAcceptance Tests  \nUnit Tests  \nSummary  \nChapter 4 Agile Requirements for the Program  \nIntroduction to the Program Level  \nOrganizing Agile Teams at Scale  \nVision  \nFeatures  \nNonfunctional Requirements  \nThe Agile Release Train  \nRoadmap  \nSummary  \nChapter 5 Agile Requirements for the Portfolio  \nIntroduction to the Portfolio Level  \nInvestment Themes  \nPortfolio Management Team  \nEpics and the Portfolio Backlog  \nEpics, Features, and Stories  \nArchitectural Runway and Architectural Epics  \nSummary  \nSummary of the Full, Enterprise Requirements Information Model Interlude: Case Study: Tendril Platform  \nBackground for the Case Study  \nSystem Context Diagram  \nPart II: Agile Requirements for the Team  \nTable of Contents  \nChapter 6 User Stories Introduction  \nUser Story Form  \nINVE","cbCaitmxPzXhDIuX","https://ap.wps.com/l/cbCaitmxPzXhDIuX","pdf",151017,10,"English","# Foreword\n# Preface\n# Acknowledgments\n# About the Author\n# Part I: Overview: The Big Picture\n## Chapter 1 A Brief History of Software Requirements Methods\n## Chapter 2 The Big Picture of Agile Requirements\n## Chapter 3 Agile Requirements for the Team\n## Chapter 4 Agile Requirements for the Program\n## Chapter 5 Agile Requirements for the Portfolio\n# Part II: Agile Requirements for the Team\n## Chapter 6 User Stories Introduction\n## Chapter 7 Stakeholders, User Personas, and User Experiences\n## Chapter 8 Agile Estimating and Velocity\n## Chapter 9 Iterating, Backlog, Throughput, and Kanban\n## Chapter 10 Acceptance Testing\n## Chapter 11 Role of the Product Owner\n## Chapter 12 Requirements Discovery Toolkit\n# Part III: Agile Requirements for the Program\n## Chapter 13 Vision, Features, and Roadmap","[{\"question\":\"What does the book cover across team, program, and portfolio levels?\",\"answer\":\"It presents agile requirements practices at the team level (user stories, backlog, acceptance testing), the program level (organization at scale, vision/features, release train, roadmap), and the portfolio level (investment themes, epics, architectural runway).\"},{\"question\":\"How does the “Big Picture of Agile Requirements” relate to lean product development?\",\"answer\":\"The outline emphasizes the enterprise-wide “big picture” and how implementing lean product development flow helps achieve business agility through agile requirements.\"},{\"question\":\"What requirements engineering techniques and workshop tools are included?\",\"answer\":\"The table of contents lists a requirements discovery toolkit such as requirements workshops, brainstorming, interviews and questionnaires, user experience mock-ups, forming a product council, competitive analysis, customer change request systems, and use-case modeling.\"}]","Agile Software Requirements - Book Table of Contents - Lean Requirements Practices for Teams, Programs, and the Enterprise | PDF",1789187679]