The Practical Guide to Agile Requirements Enginering
$9.99
Minimum price
$12.99
Suggested price

The Practical Guide to Agile Requirements Enginering

Tips for Communicating & Documenting Requirements

About the Book

Business analysis and requirements engineering in an agile environment has its own rules. The goal is clear: development teams can solve almost anything if they can just identify and communicate the requirements. This book explains the agile RE framework req42 and uses a complete product example to show how you can get to grips with requirements just-in-time and deliver successful products to your customers and users. Over 100 practical tips and answers to many FAQs make the book a useful companion for your product developments.

About the Authors

Peter Hruschka
Peter Hruschka

Dr. Peter Hruschka is co-founder and enthusiastic user of the (open source) req42 documentation template for requirements communication and documentation, as well as co-founder of the corresponding arc42 template for software and systems architects.

He is also a founding member of the International Requirements Engineering Board (IREB e.V.) and helped creating foundation and advanced level curricula for the certification of Business Analysts and Requiremetns Engineers worldwide.

Peter is a principal of the Atlantic Systems Guild, an international think tank that has influenced the systematic development of IT systems through numerous publications and presentations.

He lives betweeen Aachen, Germany and his holiday home in Austria with his wife Monika. When not working, he can usually be found in the most beautiful parts of the world, trying to hit little white balls into holes that are way too far away and way too small.

E-mail: peter@systemsguild.com or hruschka@b-agile.de 

Table of Contents

  • I. Overview
    • I.1 Basic Principles of req42
      • Agile, Lean and Pragmatic
      • Personal Responsibility for Product Success
      • Result-driven, not Process-driven
      • Agile is More than Scrum
    • I.2 Why this Book?
    • I.3 What this Book is NOT
    • I.4 Our Assumptions about You
    • I.5 Navigation Aid for People in a Hurry
    • I.6 Conventions
    • I.7 Thanks
  • II An Example to explain req42
    • II.1 Business Goals
      • Goals as PAM Cards
      • Goals as Product Box
    • II.2 Stakeholders
    • II.3 Scope
    • II.4 Product Backlog
      • Backlog at a very early point in the life cycle
      • Backlog after some refinement
      • Backlog after more refinement
    • II.5 Supporting Models
    • II.6 Quality Requirements
    • II.7 Constraints
    • II.8 Domain Terminology
    • II.9 Assets
    • II.10 Team Structure
    • II.11 Roadmap
    • II.12 Risks & Assumptions
      • 12.1 Risks
      • 12.2 Assumptions
    • II.13 Product Increments
  • III Basic rules for Effective Requirements Work
    •  
      • Requirements for the Requirements Documentation
      • Key Tips for Effective Documentation and Communication
  • IV. Effectively using req42
    • IV.1 Business Goals
      • Business Goals as “News from the Future”
      • Goals as Value-Propositions of the most Important Stakeholder
      • Further practical tips for the chapter “Business Goals/Visions”
    • IV.2 Stakeholders
    • IV.3 Scope
    • IV.4 Product Backlog
    • IV.5 Supporting Models
    • IV.6 Quality Requirements
    • IV.7 Constraints
    • IV.8 Domain Terminology
    • IV.9 Assets
    • IV.10 Team Structure
    • IV.11 Roadmap /Release Plan
    • IV.12 Risks /Assumptions
    • IV.13 Product Increments
  • V. req42 in Everyday Life
    • V.1 Good Start with req42
    • V.2 req42 for Existing Systems
    • V.3 Greenfield Development with req42
    • V.4 req42 in Agile Projects
    • V.5 req42 for Very Large Systems
  • VI Tools for req42
    • VI.1 Requirements for Tools
    • VI.1 Wikis
    • VI.2 Issue-Tracker
    • VI.3 Story-Mapping-Tools
    • VI.4 Requirements Management Tools
    • VI.4 Modeling tools
    • VI.5 Drawing Tools
    • VI.6 Text Processing
    • VI.7 Mindmapping
    • VI.8 Recommendations
  • VII Frequently Asked Questions
    • VII.1 General Questions
    • VII.2 Questions about req42 Methodology
    • VII.3 Questions about req42 Artifacts
      • VII.3.1. About Business Goals
      • VII.3.2. About Stakeholders
      • VII.3.3. About Scope
      • VII.3.4. About Product Backlog
      • VII.3.5. About Supporting Models
      • VII.3.6. About Quality Requirements
      • VII.3.7. About Constraints
      • VII.3.8. About Domain Terminology
      • VII.3.9. About Assets
      • VII.3.10. About Team Structure
      • VII.3.11. About Roadmaps
      • VII.3.12. About Risks
    • VII.4 Questions about Modeling
    • VII.5 Questions about Tools
    • VII.6 Questions about Versions and Variants
    • VII.7 Questions about Traceability
    • VII.8 Questions about Projects and Project Management
    • VII.9 Questions about Customizing req42
  • Literature and Other Sources
    • Other recommended books on agile practices
  • The Authors
    •  
      • Peter Hruschka
      • Markus Meuten
      • Dirk Fritsch
  • Notes

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $14 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub