Home > Articles > Programming

Testing the Big Picture on Agile Teams

One of the biggest problems on many agile teams is forgetting the real business value of the feature they are developing. Even with all the testing done for each story, the team may deliver a feature that has outstanding issues, or does not meet the customer’s expectations. This article covers how to balance the fast feedback of working in small increments and iterations with ensuring that the overall feature delivers adequate business value.
Like this article? We recommend


One of the top seven agile testing success factors that we talk about in the summary chapter of our book Agile Testing: A Practical Guide for Testers and Agile Teams is “Look at the Big Picture.” In that section we talk about using the agile testing quadrants to help think about all types of testing, and how to keep the customers’ point of view.

Risks of Losing the “Big Picture”

We use “feature” in this article to mean some business capability, perhaps an epic or theme in Scrum.  One of the biggest problems we’ve seen on many agile teams is forgetting the real business value of the feature they are developing. We call this risk “forgetting the big picture”. Teams break up a feature into tiny stories and then make sure they test the functionality on each individual story.  Even with all the testing done for each story, the team may deliver a feature that has outstanding issues, or does not meet the customer’s expectations. We have to balance the fast feedback of working in small increments and iterations with ensuring that the overall feature delivers adequate business value.

User stories should generally be small enough to complete in two or three days. During an iteration, the team focuses on their current stories, making decisions about acceptance tests and code design. However, these stories represent the tip of the iceberg – there’s probably a big feature lurking just out of view. In the process of slicing a feature into manageable stories, it’s easy to leave some gaps. We have to find ways to keep the end goal -- the purpose of the overall feature -- in mind.

Paradoxically, it’s hard to learn how to think in small chunks and thin slices when it comes to breaking up features and stories. Janet recently talked to a team that is still struggling to define a release scope. They haven’t gotten the idea of thin slices, delivering small complete pieces, and adding more incrementally until they get something that meets their needs. When you try to deliver a feature all at once, you’re likely to not finish it at all. But once you do master the art of incremental and iterative development, you must find ways to keep the overall feature visible.

An “Aha” Moment

Janet gained insights into “big picture testing” while on vacation at her family’s country cabin. Here’s her story.

I was relaxing at our cabin and pulled out a jigsaw puzzle. I dumped the fresh puzzle on to the table, looked at the picture on the box – my final goal, the release acceptance test if you like – and tried to decide how to sort the pieces.  There is no one correct way to do this and everyone has their own method. The only consistency that I have seen is everyone tries to make sure they get all the outside pieces separated.

As I began sorting puzzle pieces, I found that it was easier than normal even though there wasn’t a lot of difference among the pieces.  I realized it was because I was making all the decisions myself, and didn’t have to explain my thinking to anyone else ... and that got me thinking.    I started to think of this process as if I were a Product Champion. What was going to be in this release? My piles of pieces were pretty generic with little understanding of what the details were. I believe this is why I found it helpful to do it alone – I had no real idea of what I was doing, I was only starting to understand the bigger picture.

Once I got all the pieces into my initial six piles, I was able was ready to start collaborating with others to get more ideas in play. Was my thinking correct?  Did they understand my ideas and why I sorted them into those piles? Could I explain my vision so that others could help me put it together?

Since I was alone, I started by framing the puzzle, putting together the outside pieces. Of course, it did not work the first time. I desperately wanted someone to challenge my thinking – where did I go wrong? Instead, I got up, walked away and came back a bit later to see where my issues were.  All the pieces were there, just not quite in the right places. This is what I like to see in release planning sessions – looking at the big picture, where are the holes, what is missing.

 Once the frame was done, I looked at the other five piles trying to decide what the most important thing was.  To me, the most important part of a puzzle is the “core”, what makes the picture.

In this puzzle, I chose a simple well-defined area to start with. I started with the simplest “story”, the mirror. It was then easy to continue and add complexity.  There were some that didn’t belong to this feature, so I put them into a ‘backlog’ to be grabbed later when I found somewhere they belonged.

As I was going through this process, it dawned on me that this might be an easy way to think about creating stories. Don’t try to look at the whole picture at once, but tackle each section a bit at a time. Keep breaking it up smaller and smaller. It becomes much easier to deal with. Eventually, it gets put together and you have your big picture. It is important to keep the big picture in view at all times, but work on small chunks ... one piece at a time.

Identifying the “Big Picture”

These are various levels of precision: release (or project) / feature / story. We need to consider various tools to represent the levels. For example, we can use a context diagram to look at the interaction with other components or human interfaces at the project or feature level.

At the feature level, we need to understand what problem the customer is trying to solve. Ask your stakeholders how they will measure the success of the feature once it’s delivered to production. What are the hoped-for outcomes? How do we know when the feature is “DONE”? Turn these outcomes or examples into acceptance tests.  At the story level, ATDD (Acceptance Test Driven Development), BDD (Behavioural Driven Development) or Specification by Example are effective ways to define detailed business-facing tests so that developers can design the code. We can use a similar approach to define feature-level acceptance tests.

As testers, we sometimes want to dig into details right away, especially those smelly areas of the code where problems wait to be discovered. But we have to consider the context of each small increment of functionality that we test. Do break features into small stories, but don’t lose sight of the overall goal.

Defining “Big Picture” Tests

In specification or story elaboration workshops, we start with a feature, decompose it into stories, and write customer-facing acceptance tests to drive coding on each story. Too often, we lose or forget to keep that feature in mind when testing.  What if we created acceptance tests – both desired and undesired behaviour – at the feature level? These give us a way to test the “big picture”.

Let’s go a step further.  When decomposing a feature into stories, try creating an extra story to “Test Feature A,” which should include the corresponding feature acceptance tests.  In our experience, the idea of creating a “Feature DONE” definition is powerful. We can apply many tests that do not make sense at the story level, but do apply to the feature.

The “Test Feature” story is prioritized after all the individual stories are “done”. Tasks for this story might include: Test browser compatibility, Perform load test, Automate GUI tests, Complete user documentation, and Perform UAT (User Acceptance Test). Testing at the feature level enables us to run these tests at the appropriate time.  End users can be given the chance to test the complete feature and give timely feedback.

Adding acceptance tests to the feature and defining “Feature DONE” to include the tasks and tests that make sense at this higher level help teams to consider the big picture and the business problem that they are trying to solve.


When you start to test your next story, step back and think “big picture”. Consider not only the feature that it is part of, but the system as a whole.  What are the system impacts, the business workflows or scenarios? Think about who or what, is using this feature and what other pieces is it interacting with, or what data it uses. As your team, including your customers, plans upcoming features and user stories, work together to identify tests that show the desired value is delivered for each. There are many simple tools like mind mapping, drawing flow diagrams of scenarios on the whiteboard, or story mapping that help teams explore ideas and business needs. Use all the tools in your toolkit to help you remember to look beyond the story.



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.


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.


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.


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.


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


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


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.


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.


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