Home > Articles

This chapter is from the book

Knowledge Artifacts

The following has been adapted from a project that your authors are involved in called NucleusThe Minimum Viable Knowledge. As its name suggests, the intention is to specify the absolute minimal amount of documentation that enables the project to succeed. We are equating documentation with knowledge on the basis that as you learn things during business analysis, you record them. This is the knowledge that must be gained and recorded for the duration of the project and longer.

What follows is the bare-bones minimum. We are certain that you will want to add to this. We doubt you want to subtract.

Project Goals

Start at the top where you find the organization’s goal. In most cases, the goal of the organization is to make a profit. That much is obvious, but the interesting thing is what it does to make a profit. Even if yours is a not-for-profit organization, it does the same as a profit organization, it performs business activities. These can be supplying services, producing products, or almost anything else. These services are supplied to the organization’s customers. For the purposes of business analysis, it is expedient to divide these into customer segments depending on what they need.

The customers keep buying from the organization only if it provides some value to them. This means that we can derive a value proposition for each customer segment.

These three artifacts—the organization’s goals, the customer segments, and their value propositions—can be bundled together and called the project goals. In short, the goal of the project is to deliver the value proposition to each of the customer segments and thereby deliver value to the sponsor. You can see these artifacts in Figure 7.8.

Figure 7.8

Figure 7.8 The minimal, viable set of knowledge artifacts.

You must ensure that everybody on the team is well and truly aware of the project goals. Sometimes in the heat of battle they are forgotten, corrupted, or ignored. The project wanders off course, rudderless, and the final result is of little use to the customer segment. It fails to solve the right problem and does not deliver value.

Certainly, you will probably discover along the way that your goals are changing as the organization’s ecosystem changes, or that a new and better goal/segment/value emerges. It happens all the time. Reconvene with your sponsor and your team, discuss, argue, and re-establish the project goals collection. It is, after all, the supreme navigational artifact for your project.

To provide the value to the customers, the sponsoring organization usually requires some solutions—automated systems, machines, services, and so on. And that brings us to our next bundle of artifacts.

Solution Scope

The solution scope is a collective that links the information you gather about the business processes that makes up your chosen solution.

You might have discarded the notes, models, and sketches used in your safe-to-fail probes, or you might have kept them. They are probably interesting, but not all of them are necessary keepsakes. However, because you are making your decisions based on your safe-to-fail probes, we urge you to transfer the rationale for any decisions to the documentation arising from your probes.

For example, you should annotate your context model with the reasons that you chose that particular scope over another. That alone will save you hours of rediscovery and debate down the road. This applies to other models and sketches. Leaving behind your reasons for something is just as important as the something you’re leaving.

  • The solution scope collective should show the reason that scope was chosen.

There are business rules associated with any business scope. These are the rules that you would have discovered earlier in your investigation. These rules should be recorded so that anybody attached to the project has access to them. Your organization might have a central repository of business rules, so there is no need to repeat them. In the central repository, you might find it convenient to tag any rules that are applicable to your project to save the time of people who need to refer to them.

The solution scope collective also contains a list of business events. Business events are a natural way to partition the solution space and lead to natural solutions. We urge you to use them. The reason business events work so well is that they originate from the outside. In this way, they partition your solution in the same way that your customers see your solution. They are not arbitrary internal choices dictated by your politics or your internal management structures.

Story Maps

The story map shown earlier in Figure 7.5 is derived from the business events. We described in the previous chapter how the top row of the map is a set of cards—one for each business event. The cards shown in the columns below each of the business events illustrate the way you have chosen to implement them.

The advantage of a story map is that it gives you an overview of the solution and how you intend to develop it. The story map as we described it in the previous chapter is primarily a breakdown of the functionality; it shows the tasks needed for each of the business events. Along with the tasks, the story map should show the quality needs or nonfunctional requirements. These indicate how well the product carries out its functionality. You might also attach any wireframes or sketches that you have developed. Finally, make sure that, where necessary, you attach the rationale to your story map artifacts.

  • Leaving behind your reasons for doing something is as important as what you did.

One reason for using a story map, or any other form of backlog, is that stories are an outstanding way of tracking the progress of the project. A simple count of the number of stories is far better than guesswork. This count can be augmented by adding story points to the cards.

So if stories are useful, why don’t we start with stories and forget this other documentation stuff? The reason is that stories are almost always about a solution. If you start the project writing about the product you intend to build, you are thinking about a solution, not the problem. This means you have assumed the solution. Without correctly understanding the problem, any solution is possibly the wrong one. Stories are often spoken of as an invitation to a conversation about the problem, but they are still stories about an assumed solution. That is far too narrow a view to help you discover the real problem.


That brings us to the end of documentation, or to use more acceptable words, the artifacts from your analysis that the developers use to deliver, and what you are leaving behind for future generations of maintainers. Do this carefully; it is probably the most significant determinant of the future cost of maintaining the product that you are so lovingly building today.

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