BN.com Gift Guide

Requirements by Collaboration: Workshops for Defining Needs / Edition 1

Paperback (Print)
Buy New
Buy New from BN.com
$42.38
Used and New from Other Sellers
Used and New from Other Sellers
from $7.95
Usually ships in 1-2 business days
(Save 85%)
Other sellers (Paperback)
  • All (15) from $7.95   
  • New (10) from $26.05   
  • Used (5) from $7.95   

Overview

“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 presents a wealth of practical tools and techniques for facilitating requirements development workshops. It is suitable–no, essential reading–for requirements workshop facilitators. It will help both technical people and customer representatives participate in these critical contributions to software success.”

Karl Wiegers, Principal Consultant, Process Impact, author of Software Requirements

“The need for this particular book, at this particular time, is crystal clear. We have entered a new age where software development must be viewed as a form of business problem solving. That means direct user participation in developing ‘requirements,’ or more accurately, in jointly working the business problem. That, in turn, means facilitated sessions. In this book, Ellen Gottesdiener provides a wealth of practical ideas for ensuring that you have exactly the right stuff for this all-important area of professional art.”

Ronald G. Ross, Principal, Business Rule Solutions, LLC, Executive Editor, www.BRCommunity.com

“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 midlevel project manager. In addition to her technical experience, her knowledge of group dynamics balance 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...It is a required ‘handbook’ that will be referred to again and again.”

Kay Christian, ebusiness Consultant, Conifer, Colorado

Requirements by Collaboration is a ‘must read’ for any system stakeholder. End users and system analysts will learn the significant value they can add to the systems development process. Management will learn the tremendous return they may receive from making a modest time/people investment in facilitated sessions. Facilitators will discover ways to glean an amazing amount of high-quality information in a relatively brief time.”

Russ Schwartz, Computer System Quality Consultant, Global Biotechnology Firm

“In addition to showing how requirements are identified, evaluated, and confirmed, Ellen provides important guidance based on her own real-world experience for creating and managing the workshop environment in which requirements are generated. This book is an engaging and invaluable resource for project teams and sponsors, both business and IT, who are committed to achieving results in the most productive manner possible.”

Hal Thilmony, Senior Manager, Business Process Improvement (Finance), CiscoSystems, Inc.

“Project managers should read this book for assistance with planning the requirements process. Experienced facilitators will enrich their knowledge. New facilitators can use this book to get them up to speed and become more effective in less time.”

Rob Stroober, Competence Development Manager and Project Manager, Deloitte &Touche Consultdata, The Netherlands

“While many books discuss the details of software requirement artifacts (for example, use cases), Ellen’s new book zeros in on effective workshop techniques and tools used to gather the content of these artifacts. As a pioneer in requirements workshops, she shares her real-life experiences in a comprehensive and easy-to-read book with many helpful examples and diagrams.”

Bill Bird, Aera Energy LLC

Requirements by Collaboration is absolutely full of guidance on the most effective ways to use workshops in requirements capture. This book will help workshop owners and facilitators to determine and gain agreement on a sound set of requirements, which will form a solid foundation for the development work that is to follow.”

Jennifer Stapleton, Software Process Consultant and author of DSDM: The Methodin Practice

“This book provides an array of techniques within a clear, structured process, along with excellent examples of how and when to use them. It’s an excellent, practical, and really useful handbook written by a very experienced author!”

Jean-Anne Kirk, Director DSDM Consortium and IAF Professional Development

“Ellen has written a detailed, comprehensive, and practical handbook for facilitating groups in gathering requirements. The processes she outlines give the facilitator tools to bring together very different perspectives from stakeholders elegantly and with practical, useable results.”

Jo Nelson, Principal, ICA Associates, Inc., Chair, IAF (2001-2002)

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.

Read More Show Less

Product Details

  • ISBN-13: 9780201786064
  • Publisher: Addison-Wesley
  • Publication date: 4/28/2002
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 368
  • Sales rank: 1,083,670
  • Product dimensions: 7.30 (w) x 9.15 (h) x 0.79 (d)

Meet 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

Read More Show Less

Table of Contents

List of Figures.

List of Tables.

Preface.

The Organization of This Book.

Acknowledgments.

I. OVERVIEW OF REQUIREMENTS WORKSHOPS.

1. Getting Started with Requirements Workshops.

Essential Requirements.

Difficulties with Requirements.

Requirements Levels.

Surfacing User Requirements.

User Requirements Models.

Requirements Workshops.

Workshops and Collaboration.

Workshops and Facilitation.

How Workshops Differ from Typical Meetings.

Workshop Products.

Types of Requirements Workshops.

Other Uses for Workshops.

Workshops and Iterative Development.

Making the Business Case for a Requirements Workshop.

When Not to Use Requirements Workshops.

Summing Up.

For More Information.

2. Workshop Deliverables: Mining Coal, Extracting Diamonds.

The Evolution of Requirements.

Business Requirements.

User Requirements.

Software Requirements.

Model Views, Focuses, and Levels of Detail.

Model Views.

Model Focus.

Level of Detail.

Building the Models.

As-Is Models.

Multiple Models.

Model Briefings.

Actor Map.

Actor Table.

Business Policies.

Business Rules.

Context Diagram.

Decision Table or Decision Tree.

Domain Model.

Event Table.

Glossary.

Process Map.

Prototype.

Relationship Map.

Scenarios.

Stakeholder Classes.

Statechart Diagrams.

Use Cases.

Use Case Map.

Use Case Package.

User Interface Navigation Diagram.

For More Information.

3. Ingredients of a Successful Requirements Workshop.

A Shared Purpose.

The Right People.

Shared Space.

Wise Groups.

Pre-Work.

Focus Questions.

Serious Play.

Trust.

Process Variety.

Doneness Tests.

Collaborative Closure.

Flexible Structure.

Using Both Sides of the Brain.

Frequent Debriefs.

II. REQUIREMENTS WORKSHOP FRAMEWORK.

4. Purpose: Sharing a Common Goal.

Writing Your Workshop Purpose Statement.

Don't Assume Anything.

Seek the Stories.

Link Workshop Purpose with Project Vision.

Defining Project Scope.

Identifying the Workshop Sponsor.

Defining the Workshop Planning Team.

Sample Purpose Statements.

Purpose for Horizontal Top-Down Requirements Workshop.

Horizontal Middle-Out Requirements Workshop.

Horizontal Bottom-Up Requirements Workshop.

Vertical Strategy Requirements Workshop.

Zigzag Strategy Requirements Workshop.

Tips.

Questions to Ask Stakeholders.

Questions Related to Project Purpose.

Questions Related to Workshop Purpose.

For More Information.

5. Participants: Roles People Play.

Workshop Roles.

The Workshop Sponsor.

The Project Sponsor.

Having Sponsors in the Workshop.

Sponsor Kick-and-Close.

Content Participants.

Surrogate Users.

Ensuring Attendance.

The Recorder.

The Facilitator.

Facilitator as Planner and Designer.

Facilitator as Process Leader.

Facilitator Observation and Intervention Skills.

Other Facilitator Considerations.

Should You Hire an Outside Facilitator?

Observers.

On-Call Subject Matter Experts.

Tips.

Questions to Ask Stakeholders About Participant Roles.

For More Information.

6. Principles: Ground Rules for the Workshop.

Forming, Storming, Norming, and Performing.

Basic Ground Rules.

Special Ground Rules.

Values-Based Ground Rules.

Culturally Aware Ground Rules.

Introducing and Testing Ground Rules.

Hidden Agendas.

Decision-Making Ground Rules.

Product and Process Decisions.

Collaborative Decision Making.

Decision Rules.

Reaching Closure.

A Real-World Example.

Tips.

Questions to Ask Stakeholders About Ground Rules.

For More Information.

7. Products: Ending with the Beginning.

Output Products.

Making Deliverables Visually Rich.

Select Models Aligned with the Business Problem.

Use Multiple Models.

Mix Text and Diagrammatic Models.

Mix Focuses and Views.

Define the Level of Detail.

Iteratively Deliver Requirements.

Prioritize the Deliverables.

Partition Requirements Across Workshops.

Define Doneness Tests.

Metaphors.

Doneness Testing and Decision Making.

Intangible Output Products.

Input Products.

The Workshop Agenda.

Draft Models.

System and User Documentation.

Pre-Work.

Templates.

Workshop Aids.

The Workshop Repository.

Tips.

Questions to Ask Stakeholders About Products.

For More Information.

8. Place: Being There.

Workshop Logistics.

Room Setup.

Creating Sticky Walls.

Preparing the Workshop Room.

Different Time and Place Options.

Videoconferencing.

Collaborative Technology.

Collaborative Technology Variants.

Collaborative Technology: A Caveat.

Tips.

Place Checklists.

For More Information.

9. Process: Plan the Work, Work the Plan.

Opening the Workshop.

The Opener.

Designing Activities.

Sequencing Activities.

Framing Activities.

Mini-Tutorials.

Elements of a Workshop Activity.

Sample Workshop Activity.

Estimating Activity Time.

Using Focus Questions.

Imagine This….

QA As You Go.

Collaborative Modes.

Collaboration Patterns.

Wall of Wonder.

Divide, Conquer, Correct, Collect.

Multi-Model.

Expand Then Contract.

The Sieve.

Combining Collaboration Patterns.

Collaborative Techniques.

Techniques for Guiding the Flow.

The Parking Lot.

Group Dynamics.

Conflict.

The Value of Conflict.

Group Dysfunction.

How to Deal with Difficult Participants.

Fun and Games.

Closing the Workshop.

The Show-and-Tell.

Addressing Parking Lot Items.

Final Debrief.

Tips.

Tools for the Workshop Process.

For More Information.

III. REQUIREMENTS WORKSHOP DESIGN STRATEGIES.

10. Workshop Navigation Strategies.

The Horizontal Strategy.

Picking Your Horizontal Strategy.

The Top-Down Approach.

The Middle-Out Approach.

The Bottom-Up Approach.

The Vertical Strategy.

Pick a Starting Model.

Pick a Primary Focus.

Start at the Scope Level or the High Level.

Move Over.

The Vertical Strategy with Multiple Workshops.

The Zigzag Strategy.

Comparing the Strategies.

11. Workshop Case Studies.

SalesTrak.

What Worked Well.

Pitfalls and Learning Points.

RegTrak.

What Worked Well.

Pitfalls and Learning Points.

HaveFunds.

What Worked Well.

Pitfalls and Learning Points.

BestClaims.

What Worked Well.

Pitfalls and Learning Points.

12. Moving Forward.

Making the Case to Management.

The Business Value of Requirements Workshops.

Critical Success Factors.

Surfacing Problems.

How to Evaluate Workshops.

What to Report.

Deliverable Data to Capture.

Cost-Benefit Data to Capture.

Happy Sheets.

The Post-Workshop Survey.

Improvement Data.

Regular Workshop Debriefs.

Integrating Workshops into the Requirements Phase.

Becoming a Skilled Requirements Workshop Facilitator.

The IAF.

How Much Must the Facilitator Know?

What Do Business Users Need to Know?

Ground Rules for the Facilitator.

Epilogue.

For More Information.

Appendix: Collaboration Patterns.

Glossary.

Bibliography.

Index. 0201786060T03262002

Read More Show Less

Preface

"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

Read More Show Less

Introduction

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

—sLao-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 andfacilitating 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 Imve 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.

Chapter 3, 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 become an effective working group.

Chapter 5, 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 zigzag.

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 12, Moving Forward, explains how to make workshops a best practice, including using data to improve workshops, selling workshops to management, integrating workshops into 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.



Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 5 Customer Reviews
  • Anonymous

    Posted December 2, 2011

    Highly Recommended

    Business analysis, and the requirements process, is never exactly as the formal process lays it out. However, anything goes better if there is a recipe to follow (and adapt). Gottesdiener is the best in the business at laying down a roadmap for how to handle business requirements. Anyone who uses this book as the standard will find it much easier to adapt to a particular client's unique needs. This is one of those deskside manuals that no business analyst should be without.

    Was this review helpful? Yes  No   Report this review
  • Posted July 8, 2009

    more from this reviewer

    Great resource

    A great resource and companion for anyone involved in software requirements capture. Introduces collaboration techniques - mainly workshops - in a structured yet human manor.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted November 2, 2005

    An extremely helpful and practical book

    Being in the challenging world of requirements I am extremely grateful to have this book at my fingertips. It is full of practical information and is easy to navigate to find answers to my questions.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted May 8, 2002

    New Insight Into An Old Process

    If you develop computer systems, you've heard your customers say, 'That may have been what we said we wanted, but it's not what we really meant'. Ellen's readable book offers a methodology that will help you reach 'what the customer really meant' and help you avoid many other problems that can and do occur in requirements development. Her collaborative analysis and decisionmaking workshop process is well-organized and illustrated with real world examples. In addition, there are online resources available for workshop participants, facilitators, planning teams and sponsors. This book is a must have, must read and must use for anyone that participates in developing user requirements.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted April 26, 2002

    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.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 5 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)