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
€15.99 €23.99
Paperback
€29.99
Subscription
Free Trial
Renews at €18.99p/m

What do you get with Print?

Product feature icon Instant access to your digital eBook copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
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
Estimated delivery fee Deliver to Slovenia

Premium delivery 7 - 10 business days

€25.95
(Includes tracking information)

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 Print?

Product feature icon Instant access to your digital eBook copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
Estimated delivery fee Deliver to Slovenia

Premium delivery 7 - 10 business days

€25.95
(Includes tracking information)

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
€18.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
€189.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 €5 each
Feature tick icon Exclusive print discounts
€264.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 €5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total 110.97
Scaling Scrum Across Modern Enterprises
€38.99
Managing Software Requirements the Agile Way
€29.99
Becoming an Agile Software Architect
€41.99
Total 110.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 the delivery time and cost of print book? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela
What is custom duty/charge? Chevron down icon Chevron up icon

Customs duty are charges levied on goods when they cross international borders. It is a tax that is imposed on imported goods. These duties are charged by special authorities and bodies created by local governments and are meant to protect local industries, economies, and businesses.

Do I have to pay customs charges for the print book order? Chevron down icon Chevron up icon

The orders shipped to the countries that are listed under EU27 will not bear custom charges. They are paid by Packt as part of the order.

List of EU27 countries: www.gov.uk/eu-eea:

A custom duty or localized taxes may be applicable on the shipment and would be charged by the recipient country outside of the EU27 which should be paid by the customer and these duties are not included in the shipping charges been charged on the order.

How do I know my custom duty charges? Chevron down icon Chevron up icon

The amount of duty payable varies greatly depending on the imported goods, the country of origin and several other factors like the total invoice amount or dimensions like weight, and other such criteria applicable in your country.

For example:

  • If you live in Mexico, and the declared value of your ordered items is over $ 50, for you to receive a package, you will have to pay additional import tax of 19% which will be $ 9.50 to the courier service.
  • Whereas if you live in Turkey, and the declared value of your ordered items is over € 22, for you to receive a package, you will have to pay additional import tax of 18% which will be € 3.96 to the courier service.
How can I cancel my order? Chevron down icon Chevron up icon

Cancellation Policy for Published Printed Books:

You can cancel any order within 1 hour of placing the order. Simply contact customercare@packt.com with your order details or payment transaction id. If your order has already started the shipment process, we will do our best to stop it. However, if it is already on the way to you then when you receive it, you can contact us at customercare@packt.com using the returns and refund process.

Please understand that Packt Publishing cannot provide refunds or cancel any order except for the cases described in our Return Policy (i.e. Packt Publishing agrees to replace your printed book because it arrives damaged or material defect in book), Packt Publishing will not accept returns.

What is your returns and refunds policy? Chevron down icon Chevron up icon

Return Policy:

We want you to be happy with your purchase from Packtpub.com. We will not hassle you with returning print books to us. If the print book you receive from us is incorrect, damaged, doesn't work or is unacceptably late, please contact Customer Relations Team on customercare@packt.com with the order number and issue details as explained below:

  1. If you ordered (eBook, Video or Print Book) incorrectly or accidentally, please contact Customer Relations Team on customercare@packt.com within one hour of placing the order and we will replace/refund you the item cost.
  2. Sadly, if your eBook or Video file is faulty or a fault occurs during the eBook or Video being made available to you, i.e. during download then you should contact Customer Relations Team within 14 days of purchase on customercare@packt.com who will be able to resolve this issue for you.
  3. You will have a choice of replacement or refund of the problem items.(damaged, defective or incorrect)
  4. Once Customer Care Team confirms that you will be refunded, you should receive the refund within 10 to 12 working days.
  5. If you are only requesting a refund of one book from a multiple order, then we will refund you the appropriate single item.
  6. Where the items were shipped under a free shipping offer, there will be no shipping costs to refund.

On the off chance your printed book arrives damaged, with book material defect, contact our Customer Relation Team on customercare@packt.com within 14 days of receipt of the book with appropriate evidence of damage and we will work with you to secure a replacement copy, if necessary. Please note that each printed book you order from us is individually made by Packt's professional book-printing partner which is on a print-on-demand basis.

What tax is charged? Chevron down icon Chevron up icon

Currently, no tax is charged on the purchase of any print book (subject to change based on the laws and regulations). A localized VAT fee is charged only to our European and UK customers on eBooks, Video and subscriptions that they buy. GST is charged to Indian customers for eBooks and video purchases.

What payment methods can I use? Chevron down icon Chevron up icon

You can pay with the following card types:

  1. Visa Debit
  2. Visa Credit
  3. MasterCard
  4. PayPal
What is the delivery time and cost of print books? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela