Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Managing Software Requirements the Agile Way
Managing Software Requirements the Agile Way

Managing Software Requirements the Agile Way: Bridge the gap between software requirements and executable specifications to deliver successful projects

eBook
Mex$447.98 Mex$639.99
Paperback
Mex$799.99
Subscription
Free Trial

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!
Product feature icon Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!
Product feature icon 50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.
Product feature icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Product feature icon Thousands of reference materials covering every tech concept you need to stay up to date.
Subscribe now
View plans & pricing
Table of content icon View table of contents Preview book icon Preview Book

Managing Software Requirements the Agile Way

Chapter 2: Impact Mapping and Behavior-Driven Development

As well as the initial capturing of requirements, as system builders, we also need to deal with changes in requirements. A project's requirements constantly evolve, and we need to react to each stage of their evolution in two steps. The first is to correctly understand what is changing in the requirements. The second is to act on that new information in a way that helps reflect these changes and that influences the design and implementation of our system. To achieve this, we need to have a model that is a meaningful representation of our requirements.

In the previous chapter, we began to explore some of the entities within the requirements domain, namely goals and stakeholders. In this chapter, we'll expand our domain knowledge to capabilities and features and learn how to represent these four domain entities in an impact map. An impact map containing all the goals, stakeholders, capabilities, and features for our...

Modeling requirements with impact maps

In Chapter 1, The Requirements Domain, we learned how to identify stakeholders and goals. This is a crucial step in our analysis process, but in order to store and share our analytical findings, we must be able to represent these entities and their associations in a simple yet understandable manner. In other words, we want to model our requirement entities, and a great way of doing that is by using impact maps.

Introduction to impact mapping

Back in 2012, Gojko Adjiz defined the concept of impact maps, a technique that he evolved from UX-based effect-mapping methods in order to improve communication, collaboration, and interaction in teams and organizations.

Simply put, an impact map is a tree graph with four levels, where each level of the tree represents an answer to some fundamental questions about our system:

  • Why are we building the system?
  • Who benefits from it?
  • How can the stakeholders achieve their goals?
  • ...

Identifying capabilities and features

In Chapter 1, The Requirements Domain, we identified two of the main entities in the requirements domain: stakeholders and goals. In the previous section about impact mapping, we saw how these entities slot perfectly into an impact map. It's time now to look at the other two main entities that constitute the requirements domain and how they are all represented within an impact map.

In the Introduction to impact mapping section earlier in this chapter, we saw how the third and fourth levels of an impact map correspond to the business and system impacts of a stakeholder's effort to accomplish their goal, respectively. We shall define the business impact as a capability. A capability is a stakeholder's required ability to do something with our system in order to reach their goal. We shall define the system impact as a feature. A feature is a system functionality or behavior required in order to support a capability. Let's now...

Introducing BDD

In this section, we will be introduced to BDD, as it forms an essential part of the methodology described in this book. BDD was first introduced as a concept by Dan North back in 2006 (refer to Further reading link #2), as a way to improve communication and collaboration and to facilitate behavior-based automated testing. BDD is often referred to as an outside-in development methodology, as it focuses on system behavior required by the stakeholders as the driving mechanism for developing software. This well-defined system behavior is referred to as a feature in BDD parlance.

Since North's original article, BDD has matured and evolved and now has a rich ecosystem supporting it, with tools such as Cucumber, SpecFlow, and JBehave appearing in many a developer's tool-belt. Gojko Adjiz (yes, him again) helped solidify BDD principles in his book Specification by Example (refer to Further reading link #4). As a result, some people actually use the terms BDD and...

Knowing the difference between functional and non-functional requirements

Let's now take a look at the main type of requirements we are going to encounter and how we will be dealing with them. In the use cases and examples we have used so far, we have encountered requirements that influence what the system should do or how it should behave. In our pizza example, we talked about the actors selecting toppings for the pizza, choosing a delivery slot, and other such functionalities or behaviors. These are commonly known as functional requirements and we've already seen how we can represent these in a requirements model by identifying goals, stakeholders, capabilities, and features. But let's now consider some different requirements that don't focus on interactions between the system and its actors but on internal system operations instead: Non-Functional Requirements (NFRs).

Let's suppose that the pizza company wants our system to display all 50 available toppings...

Summary

In this chapter, we defined and distilled two more requirement domain entities: capabilities and features. We learned how to use them alongside goals and stakeholders in order to model our requirements in a requirements model, using impact mapping. Knowing what these four entities are about and how they are related is the first step in the requirements management workflow that we'll be detailing in this book. We already started exploring the mental process we'll be using to analyze requirements and break them down into these four entities. We'll be delving in greater detail into how this mental process works in Chapter 5, Discovering and Analyzing Requirements, in the Discovering Requirements section, where we will also be applying effective techniques to help us discover and analyze requirements.

This chapter also introduced BDD. BDD is what we do after we have discovered and analyzed our requirements. Specifically, BDD will help us refine our requirements...

Further reading

  1. Gojko Adzic, Impact Mapping: Making a Big Impact with Software Products and Projects, ISBN-10: 0955683645
  2. Dan North, Introducing BDD: https://dannorth.net/introducing-bdd
  3. John Ferguson Smart, BDD in Action: Behavior-driven development for the whole software lifecycle, Manning Publications, 1st edition, ISBN-10: 161729165X
  4. Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software, Manning Publications, 1st edition, ISBN-10: 1617290084

    Mike Cohn, User Stories: https://www.mountaingoatsoftware.com/agile/user-stories

Left arrow icon Right arrow icon
Download code icon Download Code

Key benefits

  • Learn how to communicate with a project’s stakeholders to elicit software requirements
  • Deal every phase of the requirement life cycle with pragmatic methods and techniques
  • Manage the software development process and deliver verified requirements using Scrum and Kanban

Description

Difficulty in accurately capturing and managing requirements is the most common cause of software project failure. Learning how to analyze and model requirements and produce specifications that are connected to working code is the single most fundamental step that you can take toward project success. This book focuses on a delineated and structured methodology that will help you analyze requirements and write comprehensive, verifiable specifications. You'll start by learning about the different entities in the requirements domain and how to discover them based on customer input. You’ll then explore tried-and-tested methods such as impact mapping and behavior-driven development (BDD), along with new techniques such as D3 and feature-first development. This book takes you through the process of modeling customer requirements as impact maps and writing them as executable specifications. You’ll also understand how to organize and prioritize project tasks using Agile frameworks, such as Kanban and Scrum, and verify specifications against the delivered code. Finally, you'll see how to start implementing the requirements management methodology in a real-life scenario. By the end of this book, you'll be able to model and manage requirements to create executable specifications that will help you deliver successful software projects.

Who is this book for?

This book is for software engineers, business analysts, product managers, project managers, and software project stakeholders looking to learn a variety of techniques and methodologies for collating accurate software requirements. A fundamental understanding of the software development life cycle (SDLC) is needed to get started with this book. Although not necessary, basic knowledge of the Agile philosophy and practices, such as Scrum, along with some programming experience will help you to get the most out of this book.

What you will learn

  • Kick-start the requirements-gathering and analysis process in your first meeting with the client
  • Accurately define system behavior as features
  • Model and describe requirement entities using Impact Mapping and BDD
  • Create a feature-based product backlog and use it to drive software development
  • Write verification code to turn features into executable specifications
  • Deliver the right software and respond to change using either Scrum or Kanban
  • Choose appropriate software tools to provide transparency and traceability to your clients

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : Aug 14, 2020
Length: 214 pages
Edition : 1st
Language : English
ISBN-13 : 9781800206465
Concepts :
Tools :

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!
Product feature icon Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!
Product feature icon 50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.
Product feature icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Product feature icon Thousands of reference materials covering every tech concept you need to stay up to date.
Subscribe now
View plans & pricing

Product Details

Publication date : Aug 14, 2020
Length: 214 pages
Edition : 1st
Language : English
ISBN-13 : 9781800206465
Concepts :
Tools :

Packt Subscriptions

See our plans and pricing
Modal Close icon
$19.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
$199.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just Mex$85 each
Feature tick icon Exclusive print discounts
$279.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just Mex$85 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total Mex$ 2,995.97
Scaling Scrum Across Modern Enterprises
Mex$1066.99
Managing Software Requirements the Agile Way
Mex$799.99
Becoming an Agile Software Architect
Mex$1128.99
Total Mex$ 2,995.97 Stars icon

Table of Contents

11 Chapters
Chapter 1: The Requirements Domain Chevron down icon Chevron up icon
Chapter 2: Impact Mapping and Behavior-Driven Development Chevron down icon Chevron up icon
Chapter 3: Writing Fantastic Features with the Gherkin Language Chevron down icon Chevron up icon
Chapter 4: Crafting Features Using Principles and Patterns Chevron down icon Chevron up icon
Chapter 5: Discovering and Analyzing Requirements Chevron down icon Chevron up icon
Chapter 6: Organizing Requirements Chevron down icon Chevron up icon
Chapter 7: Feature-First Development Chevron down icon Chevron up icon
Chapter 8: Creating Automated Verification Code Chevron down icon Chevron up icon
Chapter 9: The Requirements Life Cycle Chevron down icon Chevron up icon
Chapter 10: Use Case: The Camford University Paper Publishing System Chevron down icon Chevron up icon
Other Books You May Enjoy Chevron down icon Chevron up icon

Customer reviews

Rating distribution
Full star icon Full star icon Full star icon Full star icon Half star icon 4.7
(3 Ratings)
5 star 66.7%
4 star 33.3%
3 star 0%
2 star 0%
1 star 0%
Mohith Kumar Oct 12, 2020
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This is well written! One of the keys skills for any good business consultant or a solution architect is managing business requirements! This books provides best practices around this topic which is a rare find!Author documents in a plain English with examples making this a great read
Amazon Verified review Amazon
Maureen L-L Jan 15, 2021
Full star icon Full star icon Full star icon Full star icon Full star icon 5
I have been working in the software industry for over 20 years and am very familiar with traditional software development and modern agile methodologies such as Scrum, Kanban, eXtreme Programming, etc. This book was a provides a great practical approach to managing the chaos of requirements that many agile practitioners have unleashed on us. Too many people in our industry are either agile "purists" who think only in terms of user stories (which results in a giant mess of unstructured requirements) or are peddling overblown methodologies like SAFe that require over 50 different artifact types and seem to be anything but agile (IMHO). This book was great in clearly distinguishing between different types of requirement (goal vs. capability vs. specification) and how you can put them together to make sense of a software project. Also it is a great primer on BDD and using gherkin syntax as a way to write requirements. I would say you should buy this book for either its overall approach to requirements elicitation and/or its great intro to using BDD, in many ways two books in one. In summary, a great book for anyone in the software field, and one that offers some unique, new fresh insights.
Amazon Verified review Amazon
Govindadas PAI Nov 02, 2022
Full star icon Full star icon Full star icon Full star icon Empty star icon 4
Very relevant for todays digital innovation and acceleration of faster development of software solutions. Some of the key aspects are not new to me but the way these are articulated reinforced my views as well. A must read for Business Analyst.
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

What is included in a Packt subscription? Chevron down icon Chevron up icon

A subscription provides you with full access to view all Packt and licnesed content online, this includes exclusive access to Early Access titles. Depending on the tier chosen you can also earn credits and discounts to use for owning content

How can I cancel my subscription? Chevron down icon Chevron up icon

To cancel your subscription with us simply go to the account page - found in the top right of the page or at https://subscription.packtpub.com/my-account/subscription - From here you will see the ‘cancel subscription’ button in the grey box with your subscription information in.

What are credits? Chevron down icon Chevron up icon

Credits can be earned from reading 40 section of any title within the payment cycle - a month starting from the day of subscription payment. You also earn a Credit every month if you subscribe to our annual or 18 month plans. Credits can be used to buy books DRM free, the same way that you would pay for a book. Your credits can be found in the subscription homepage - subscription.packtpub.com - clicking on ‘the my’ library dropdown and selecting ‘credits’.

What happens if an Early Access Course is cancelled? Chevron down icon Chevron up icon

Projects are rarely cancelled, but sometimes it's unavoidable. If an Early Access course is cancelled or excessively delayed, you can exchange your purchase for another course. For further details, please contact us here.

Where can I send feedback about an Early Access title? Chevron down icon Chevron up icon

If you have any feedback about the product you're reading, or Early Access in general, then please fill out a contact form here and we'll make sure the feedback gets to the right team. 

Can I download the code files for Early Access titles? Chevron down icon Chevron up icon

We try to ensure that all books in Early Access have code available to use, download, and fork on GitHub. This helps us be more agile in the development of the book, and helps keep the often changing code base of new versions and new technologies as up to date as possible. Unfortunately, however, there will be rare cases when it is not possible for us to have downloadable code samples available until publication.

When we publish the book, the code files will also be available to download from the Packt website.

How accurate is the publication date? Chevron down icon Chevron up icon

The publication date is as accurate as we can be at any point in the project. Unfortunately, delays can happen. Often those delays are out of our control, such as changes to the technology code base or delays in the tech release. We do our best to give you an accurate estimate of the publication date at any given time, and as more chapters are delivered, the more accurate the delivery date will become.

How will I know when new chapters are ready? Chevron down icon Chevron up icon

We'll let you know every time there has been an update to a course that you've bought in Early Access. You'll get an email to let you know there has been a new chapter, or a change to a previous chapter. The new chapters are automatically added to your account, so you can also check back there any time you're ready and download or read them online.

I am a Packt subscriber, do I get Early Access? Chevron down icon Chevron up icon

Yes, all Early Access content is fully available through your subscription. You will need to have a paid for or active trial subscription in order to access all titles.

How is Early Access delivered? Chevron down icon Chevron up icon

Early Access is currently only available as a PDF or through our online reader. As we make changes or add new chapters, the files in your Packt account will be updated so you can download them again or view them online immediately.

How do I buy Early Access content? Chevron down icon Chevron up icon

Early Access is a way of us getting our content to you quicker, but the method of buying the Early Access course is still the same. Just find the course you want to buy, go through the check-out steps, and you’ll get a confirmation email from us with information and a link to the relevant Early Access courses.

What is Early Access? Chevron down icon Chevron up icon

Keeping up to date with the latest technology is difficult; new versions, new frameworks, new techniques. This feature gives you a head-start to our content, as it's being created. With Early Access you'll receive each chapter as it's written, and get regular updates throughout the product's development, as well as the final course as soon as it's ready.We created Early Access as a means of giving you the information you need, as soon as it's available. As we go through the process of developing a course, 99% of it can be ready but we can't publish until that last 1% falls in to place. Early Access helps to unlock the potential of our content early, to help you start your learning when you need it most. You not only get access to every chapter as it's delivered, edited, and updated, but you'll also get the finalized, DRM-free product to download in any format you want when it's published. As a member of Packt, you'll also be eligible for our exclusive offers, including a free course every day, and discounts on new and popular titles.