Product Description

Many software development books teach you how to build the product right. This one focuses on building the right product. Ellen Gottesdiener introduces the breakthrough Requirements Workshop technique, and demonstrates how to use it to identify customer's needs far more effectively, and specify new software systems far more quickly and accurately. The authors begin by reviewing the challenges of specifying software requirements, showing how Requirements Workshops address these challenges, and explaining the process of designing and running workshops. Through practical examples and case studies, they identify the best approaches to workshop design, and thoroughly explain the deliverables that workshops generate. This is the first book to fully integrate coverage of user requirements modeling, including UML-based use cases, business rules, and collaborative techniques designed to strengthen the relationship between IT and the business. Author Ellen Gottesdiener also introduces her breakthrough collaboration patterns -- powerful collections of group behavior that can be reused in a wide variety of software projects. For every developer, analyst, architect, and manager involved with creating or utilizing requirements specifications.

---

Product Details

• Amazon Sales Rank: #221863 in Books
• Published on: 2002-04-20
• Original language: English
• Number of items: 1
• Binding: Paperback
• 368 pages

From the Back Cover
"I spend much time helping organizations capture requirements and even more time helping them recover from not capturing requirements. Many of them have gone through some motions regarding requirements, as if they were sleepworking. It's time to wake up, and do it right--and this book is going to be their alarm clock."
Jerry Weinberg, author of numerous books on productivity enhancement "In today's complex, fast-paced software development environment, collaboration--the intense peer-to-peer conversations that result in products, decisions, and knowledge sharing--is absolutely essential to success. But all too often, attempts to collaborate degenerate into agonizing meetings or ineffectual bull sessions. Ellen's wonderful book will help you bridge the gap--turning the agony of meetings into the ecstasy of effective collaboration."
Jim Highsmith, a pioneer in adaptive software development methods

Requirements by Collaboration: Workshops for Defining Needs focuses on the human side of software development--how well we work with our customers and teammates. Experience shows that the quality and degree of participation, communication, respect, and trust among all the stakeholders in a project can strongly influence its success or failure. Ellen Gottesdiener points out that such qualities are especially important when defining user requirements and she shows in this book exactly what to do about that fact.

Gottesdiener shows specifically how to plan and conduct requirements workshops. These carefully organized and facilitated meetings bring business managers, technical staff, customers, and users into a setting where, together, they can discover, evolve, validate, verify, and agree upon their product needs. Not only are their requirements more effectively defined through this collaboration, but the foundation is laid for good teamwork throughout the entire project.

Other books focus on how to build the product right. Requirements by Collaboration focuses instead on what must come first--the right product to build.

0201786060B02212002

About the Author

Ellen Gottesdiener is President of EBG Consulting, Inc., a firm providing facilitation, consulting, and training services for clients in a wide variety of industries. She is a pioneer in the use of facilitated workshops to elicit business rules and other user requirements. She is the author of numerous articles and several book contributions and is a highly regarded speaker at professional conferences.

0201786060AB02212002

Excerpt. © Reprinted by permission. All rights reserved.

"What is softest in the world drives what is hardest in the world."

Lao-Tzu

To be successful, software projects need solid requirements and collaborating teams. Problems with requirements are one of the primary causes of software project failure. To make matters worse, the rush to use technologies to collaborate over time and space, or to try to substitute fast development, has resulted in lots of bad software. Many people on both sides of the software divide--developers and users have complaints about their interrelationships.

Requirements by Collaboration explains how to plan and hold workshops to meet two essential needs: efficiently defining user requirements while building positive, productive working relationships. Similar structured workshops are called joint requirements, accelerated design, group design, or Joint Application Design or Development (JAD) sessions. These workshops are about getting the requirements accurately, quickly, and collaboratively, through shared vision and clear communications. By collaborating in this way, you establish relationships, achieve mutual understanding, and build trust.

Successful workshops don't just happen. Facilitating a requirements workshop is simple, but it's not easy. These workshops require forethought, planning, and design on the part of the workshop facilitator as well as its stakeholders.

This book focuses on the essential tools you need for planning and leading requirements workshops. It integrates user requirements modeling, including use cases, business rules, and collaborative techniques. It teaches you the basic principles of designing and facilitating requirements workshops and gives you an overview of the deliverables of these workshops. It also shows you workshop design strategies. This book is a complement to other books on requirements gathering as well as those that deal with software engineering, requirements, modeling, and facilitation. To guide your study of these related topics, most chapters include references and information about further reading.

The aim of this book is to be practical, not theoretical. It's based on my real-world experiences from the numerous projects I've facilitated for clients as well as a series of courses I've written and delivered to clients in a variety of industries. The goals of this book are to provide a focused perspective on user requirements elicitation and to promote techniques that enhance the ongoing relationship between software and business people.

A unique aspect of this book is its discussion of collaboration patterns: reusable collections of group behavior applied to software projects. Collaboration patterns extend the idea of "process patterns"(work methods) by exploiting the power of software and customer groups working in tandem to achieve project goals.

You can think of collaboration as a continuous feedback loop that enhances both the quality and the speed of communication, and thereby of the products created in workshops. For this reason, the techniques described in this book use collaboration patterns coupled with clearly defined user requirements documentation and diagrams.

Anyone who participates in initiating, eliciting, analyzing, verifying, validating, or approving requirements for software will find this book useful. The focus is on perspectives, ranging from those of project sponsors to analysts, with the goal of providing a common understanding of user requirements from concept through specification. Readers of this book include people who will facilitate requirements workshops; project, product, and business managers overseeing the requirements process; and participants in requirements workshops. Project roles include analyst, project manager, product manager, developer, architect, quality assurance analyst, tester, and requirements engineer.

Like life itself, workshops are often surprising. You plan, and plan you must. But then unexpected things happen when people get together. A workshop rarely follows its original plan because when people get together, things get messy and sloppy; mistakes are made, discussions go off-track, the unexpected occurs. Yet this is when great ideas spring forth. With steady guidance from the facilitator, the group can achieve wonders.

The Organization of This Book

The body of this book contains 12 chapters within three parts.

Part One, Overview of Requirements Workshops, contains three chapters .

Chapter 1, Getting Started with Requirements Workshops, describes the problems associated with eliciting requirements and the basic concepts of the requirements workshop.

Chapter 2 , Workshop Deliverables: Mining Coal, Extracting Diamonds, provides a high-level overview of the various models that are the primary deliverables of a requirements workshop. Each of these models expresses a particular point of view, provides perspective on a certain focus, and achieves a varying level of detail. The chapter also explains how the workshop facilitator selects the most appropriate models for the workshop.

Chapter3, Ingredients of a Successful Requirements Workshop, describes the elements you need to achieve success with a requirements workshop.

Part Two, Requirements Workshop Framework, contains six chapters.

Chapter 4, Purpose: Sharing a Common Goal, describes how to specify why a given workshop is being held. A concise statement of purpose is the starting point for defining the other elements of a workshop: who, how, what, where, and when. Shared purpose is also an essential element for participants to ecome an effective working group.

Chapter5, Participants: Roles People Play, describes the various roles played by workshop attendees. It also explains what to do if surrogate or substitute users will attend your workshop and why the facilitator should be neutral and should have knowledge about requirements models. The chapter discusses the importance of participation by business subject matter experts, sponsors, and software stakeholders.

Chapter 6, Principles: Ground Rules for the Workshop, describes basic ground rules, special ground rules, ways to uncover hidden agendas, and decision-making ground rules.

Chapter 7, Products: Ending with the Beginning, discusses workshop products in detail. It describes how to determine the right level of precision, perform doneness tests, and divide a product across multiple sessions (or multiple products across a single session). It also shows how to promote efficiency by using pre - work and self - assigned post - work.

Chapter 8 , Place: Being There, describes same -time, same -place focus, recording modes (including posters and collaborative software tools) ,and location logistics.

Chapter 9, Process: Plan the Work , Work the Plan, describes the design and flow of workshop activities and shows you how to create a comprehensive agenda to serve as your roadmap. The chapter discusses how to open and close the workshop and defines collaborative modes, focus questions, collaboration patterns, sponsor "show and tell" group dynamics, and location logistics.

Part Three, Requirements Workshop Design Strategies, contains three chapters.

Chapter 10, Workshop Navigation Strategies , describes three roadmaps for structuring requirements workshops: horizontal, vertical, and zig zag.

Chapter 11, Workshop Case Studies, illustrates the book's principles and strategies with several case studies drawn from requirements workshops that I've facilitated.

Chapter 1 2, Moving Forward ,explains how to make workshops a best practice, including using data to improve workshops, selling workshops to management, integrating workshops in to your requirements process, ensuring that subject matter experts and the workshop facilitator have the needed knowledge and skills, and identifying helpful ground rules.

The book also includes a Glossary, which contains definitions for all terms introduced in the body of the text. The Bibliography lists books and articles that contain relevant material. Finally, the Appendix describes a set of collaboration patterns, referenced in the main body, that I have found helpful in facilitating requirements workshops.

0201786060P03262002

---

Customer Reviews

Synthesizes PD, RD and JAD
This ground breaking book blends the best of PD (Participatory Design), RD (Rapid Development) and JAD (joint application development). To this synthesis it adds modern elements such as business rules. To understand why this book is a ground breaking work a little history is in order. Participatory design (PD) began in England by Enid Mumford and was refined in Scandinavia by Pelle Ehn and Morten Kyng in the late 1970s. RD (Rapid Development) was first formalized by DuPont in mid 1980s and was then known as Rapid Iterative Production Prototyping (RIPP). JAD was first developed by Toby Crawford and Chuck Morris at IBM in 1977. Each of these approaches have one thing in common: participatory requirements elicitation accomplished in a workshop setting.

Most previous work about these approaches focused on general aspects of workshop management and requirements. Although this book certainly addresses these two aspects, it goes beyond.

This book is structured in three parts and 12 chapters. Part I covers the basics of constructing a workshop and provides a comprehensive list of deliverables. The author's web site that supports this book provides checklists and templates in Word and PDF format, which will save you time. The web site also has links to other resources that will prove extremely useful. Part II provides the workshop framework, covering logistics, managing roles and ground rules and the workshop process itself. Part III addresses the strategies for conducting the workshop. What I particularly like about this book are:

(1) It defines a process with inputs, tasks and defined outputs (deliverables).
(2) Adds structure by aligning business problems to model views, and by defining the deliverables that need to be produced to develop the model. The models views are: behavior, structural, dynamic and control. These cover the four basic business problem domains.
(3)Does not lock you into any single model (you can use multiple model types), and provides criteria for selecting the best model(s) to employ for capturing requirements.
(4) Introduces business rules, which is (in my opinion) one of the most powerful and effective means of capturing requirements.

The approach set forth is effective and thoroughly modernizes the approaches that were synthesized. More importantly it provides a structure in which to conduct participatory workshops, and clearly defines the types of goals you should be setting based on the business problem, and clear definitions of the deliverables that the workshop should produce. This book goes into my short list of best books read in 2002, and I suspect it will remain on my short list of recommended books for years to come.

Definitive Facilitation and Requirements Workshop Resource
Software development is approximately 50 percent about computing and 50 percent about communication. "Requirements by Collaboration" deals with the critical communication half of the problem. Ellen Gottesdiener presents a wealth of practical tools and techniques for facilitating collaborative requirements development workshops. The goal of such workshops is to arrive at a common vision of the product being specified, which gives all stakeholders confidence in achieving a successful project outcome.

This is a highly pragmatic book, not a theoretical treatise. Ellen describes in clear detail the nuts and bolts of planning and leading requirements workshops. Chapters address the Purpose, Participants, Principles, Products, Place, and Process of such workshops. Based on her extensive hands-on experience as a facilitator, Ellen presents several illustrative case studies and many tips that share her insights. These methods are broadly applicable to any type of facilitation, not just software requirements exploration.

Ellen describes some 20 different requirements models, organized ways to represent the diverse jumble of information that appears whenever people discuss their needs and the desired properties of a new product. These models provide a richness of representation that goes far beyond the list of functional requirements or even use cases that traditionally comes out of requirements workshops.

I especially like Ellen's collaboration patterns, with intriguing titles such as "Decide How to Decide," "Expand Then Contract," "The Sieve," and "Wall of Wonder." These describe recurring patterns of interaction among the members of a collaborative team. Skillful application of selected collaboration patterns can help any group achieve its objectives efficiently and with less friction than they might otherwise suffer.

"Requirements by Collaboration" is essential reading for all requirements workshop leaders. It will help both technical people and customer representatives participate effectively in these critical contributors to software success.

Ellen Gottesdiener achieves the complex through the simple.
Gottesdiener's down-to-earth writing style combined with her extensive knowledge of requirements gathering make Requirements by Collaboration a must-have book for Product and Project Managers, Technology Leads, Business Analysts and Information Architects.

Gottesdiener employs engaging side-bars, useful figures, and a bounty of experience to explain the complex process of eliciting and describing user needs. Her infusion of quiet wisdom with extensive workshop exercises and tools energizes the reader in planning their own projects.

She has designed the workshops and exercises in such a way that they can easily apply to traditional software applications, web applications or even a pure content project that addresses a diverse audience. Her narrative examples as well as the case studies effectively transfer the concepts into something tangible.

Gottesdiener's years of software development experience coupled with her straight-forward writing style make her book a perfect choice for either a senior developer or a mid-level project manager. In addition to her technical experience, her knowledge of group dynamics round out the book by educating the reader on how to manage conflict and personality differences within a requirements team - something that is missing from most requirements textbooks.

Software and web development teams can quickly and easily put Gottesdiener's book to practice. It's a required "handbook" that will be referred to again and again.