Home > Articles

  • Print
  • + Share This
This chapter is from the book

10.9 Specifying Features and Their Acceptance Criteria

Meet with business representatives, developers, and testers (sometimes called “the Triad”) to describe the feature in a way that clearly communicates the requirement. Chapter 8, “Seeding the Backlog—Discovering and Grading Features,” section 8.7, provides guidelines for specifying features using the Role-Feature-Reason (Connextra) template. Coach stakeholders and the team to use the template, but don’t force its use where the resulting wording is unnatural and impedes understanding.

Then, specify feature AC. AC play a central role in agile analysis: they serve as requirements and as the basis for user acceptance testing (UAT). For the first release of the feature, specify just enough AC to define an MMF—the minimum functionality required to deliver value that the customer would view as significant.

As an analyst, you support feature AC specification. You support ATDD guidance by ensuring AC are specified before work on the feature begins so that they can serve as specifications by example. The AC tell the developers how much functionality must be delivered for the item to be releasable—providing them with the information they need to estimate the feature for capacity planning. The AC also serve as test scenarios to validate the solution. These scenarios describe how the product must behave when user stories are strung together in a larger workflow or value stream. A common approach is to specify the AC in a feature file in the Gherkin syntax so they can be interpreted by a test automation tool such as Cucumber.

AC and estimates are so intertwined that you should encourage stakeholders to discuss them at the same time with developers and QA professionals so trade-offs can be explored. This is the principle behind the Triad approach, discussed in Chapter 13.

10.9.1 Specifying Epic Acceptance Criteria

Specify epic AC that communicate, at a high level, the minimum requirements for completion. In Chapter 7, we saw the following epic example. Its AC expresses the epic’s business objective, “legacy system can be retired.”

10.9.2 Specifying Feature Acceptance Criteria

Like epic AC, feature AC do not have to cover all possible scenarios. Instead, begin by specifying an MMF that includes only the minimum level of functionality needed for the feature to be seen as valuable by customers.

Following is an example of feature belonging to the epic we saw earlier: “As a planner I want to introduce dropship capability to increase top-line sales without the inventory ownership expense.” Its AC are specified in brief descriptive text, also known as scenario titles.

Following is an example we saw in Chapter 8.

10.9.3 The Analyst Contribution

As an agile analyst, you support ATDD by facilitating Triad conversations between stakeholders, QA, and developers about AC and by specifying AC, as discussed earlier. However, you should review and adjust your contribution over time based on experience. Options for your involvement in feature AC include the following:4

  • You own the feature files—or the team as a whole owns them.

  • You write the AC, scenario titles, and Gherkin given/when/then specifications—or you write AC and scenario titles, and QA professionals write the given/when/then specs.

10.9.4 Analyze AC During Triad Meetings

Analyze AC for epics and features incrementally, through collaborative sessions with business stakeholders (representing the customer), testers, and developers—the Triad.

Before committing a feature to development, facilitate Triad discussions to specify high-level AC in the language of the business. The AC and conversations clarify the requirements to stakeholders, testers, and developers. Continue to meet with the Triad to refine the AC with more specific test scenarios.

This chapter focuses on feature preparation, but you also need to prepare stories and their AC. Story preparation and AC are discussed in Chapter 13.

10.9.5 Specifying AC in the BDD Gherkin Syntax

The Gherkin syntax is widely used because it can be easily interpreted by stakeholders, testers, and test automation tools. Typically, you begin by writing story AC informally; then, as the story approaches development, you specify test scenarios in Gherkin feature files. Gherkin includes keywords such as given, when, and then to identify standardized aspects of test scenarios.

template.jpg

For example, you create the following feature to introduce dropship capabilities.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020