Home > Articles > Programming

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

Input Products

Once you've planned your workshop outputs, it's time to determine what input products you need. Using a set of well-thought-out input products speeds up your workshop and helps groups reach closure.

Input products include a variety of materials that prepare participants for the mental work they'll do, provide tools for jump-starting workshop activities, give guidance for creating higher-quality requirements models, and serve as doneness test resources. Input products can include the following:

  • The workshop agenda
  • Draft requirements models
  • Systems and user documentation
  • The results of pre-work
  • Templates
  • Workshop aids

The following subsections discuss each of these kinds of input products.

The Workshop Agenda

The workshop agenda is an ordered list of activities planned for the session. The agenda, which you send to all the participants before the workshop, should also include your other P's: purpose, participants, principles, products, and place. (See Chapter 9 for tips on designing your agenda; an agenda template is available on the book's Web site.)

Draft Models

Use predecessor requirements models or draft output models to jump-start your modeling work. For example, if you're creating use cases in the workshop, you can use an actor table or an actor map as a mechanism to help you create a list of use cases. By using focus questions about the predecessor model (for example, "What goals does this actor have for interacting with the system?"), you can elicit another related model. (See "Using Focus Questions" in Chapter 9 for more about focus questions.)

You can also use predecessor and draft requirements in performing doneness tests on models. For example, a list of scenarios created before the workshop can be used in testing use cases. To test for doneness during the workshop, you can use pre-work such as user-created scenarios and prototype screens created by the software team by walking through them in parallel with use case steps.

A draft version of a model provides the basis for an activity to fix or finish it. For example, you can use a draft event table or context diagram during an activity in which the group reaches closure on scope. A rough version of a statechart diagram gives you a starting point for generating more states, which in turn triggers events and business rules.

At a minimum, you should create a draft glossary before a requirements workshop. The terms in the glossary are the semantic basis for all your user requirements; the definitions are themselves fundamental business rules.

I like to ask one person to be the glossary guardian, the person in charge of keeping the glossary up-to-date during the workshop. The job of the glossary guardian is to listen for business terms that haven't been defined or that might need to be clarified. Allow everyone to tune in to terms; challenge each participant to also play the role of glossary guardian. (To make it fun, I sometimes announce a reward for anyone who stops the group when a term needs to be defined or clarified. Reverse rewards can work, too, if you make them humorous—for example, getting "banged" with a rubber hammer if you use a term without explaining it.)

The glossary guardian keeps the glossary up-to-date during the workshop.

Data modelers make excellent glossary guardians because they naturally think in terms of words and their connections, and they often seek precise definitions of business terms.

Universal Models An alternative or supplemental draft model you can use as input is a universal model. This generic business model is documented in books or available for purchase from consulting companies.

Universal models tend to be abstract. They use generic business terms (business party, transaction, event, agreement) that you can use as starting points for modeling activities. For example, if the universal model is represented as a data model, participants can list examples of each concept in the model or list subtypes to jump-start the modeling of their own domain model.

Systems and User Documentation

It's a good idea to have documentation available that might be useful during the workshop. This includes the project charter or vision statement, organization charts, operating procedures and guidelines, reference manuals, user documentation, help desk documentation, user job aids, training manuals and documentation, and systems manuals and documentation. Identify each document that might be useful, and be sure that someone is responsible for bringing it.

Pre-Work

Pre-work involves specific assignments for participants to complete before the workshop. Examples of pre-work include filling out a template that lists steps to complete a task, naming business rules in a specific format for a set of use cases, listing stakeholders and their functional areas, reviewing and commenting on a set of draft use cases, reading the project charter, listing key inputs needed by users, and drawing a poster that depicts an image of the future after the requirements have been met.

Asking participants to complete pre-work has one or more of these benefits:

  • It mentally prepares participants for the type of thinking they'll do in the workshop.

  • It provides research information and starting points to one or more workshop activities.

  • It forces participants to seek information from other experts who might fill gaps in their subject matter expertise.

Specifying some kind of pre-work signals that the requirements workshop isn't an ordinary meeting.

Workshop Orientation Meetings

Under certain circumstances I like to arrange orientation meetings before workshops.

In one workshop I facilitated, participants came from around the globe. They had pre-work assignments and would be gathering in a central location for the session. Many of them had never participated in a requirements workshop, and few of them knew one another. We arranged a videoconference orientation meeting kicked off by the project sponsor. In this meeting, we reviewed the workshop agenda and clarified how to complete the pre-work. We also discussed important issues such as what to wear and how they would access their voice mail on breaks during the workshop. This 45-minute meeting helped to break the ice before the live workshop.

Here are some circumstances under which you should consider holding an orientation meeting:

  • Participants have pre-work assignments that may involve completing templates or doing complex research.

  • Participants don't know one another.

  • Participants would benefit from hearing suggestions for what materials to bring to the workshop.

  • You are meeting over a period of days or weeks.

Keep the meeting short, and be sure you have the project or workshop sponsor kick it off to set the stage.

Pre-work is essential when you're operating under a tight time frame, when users are surrogates and not real subject matter experts, when participants hail from different business areas, or when you'll be working with detailed requirements. Your workshop schedule must take into account the time for preparing pre-work. For example, you may need to create a template with instructions (see "Templates" next).

Designing pre-work is one thing, but how do you get participants to complete it? Your sponsor and your planning team can help. For example:

  • Have the pre-work assignments made by the sponsor or an influential planning team member.

  • Provide information at least one week before the workshop.

  • Conduct an orientation meeting to brief participants on how to complete the pre-work, particularly if their assignments are complex.

  • Ask the workshop sponsor or project sponsor to send e-mail or voice mail to the participants requesting that they complete their pre-work.

  • Have the pre-work responses sent to the workshop sponsor or a planning team member rather than to the facilitator.

Business Rules Templates

Business rules come in many forms and categories, including terms, facts, constraints, factor clauses, and action clauses. There's no agreement on a standard set of categories for business rules—nor should there be, because the rules should fit the business problem. Some business problems are more business rule-based (for example, insurance underwriting), whereas others are more business rule-constrained (such as payroll). Business rules are vital for high-quality requirements, and they also provide useful links to other requirements models.

You can capture your business rules as free-form statements generated by business people, but these statements tend to be ambiguous and not rigorous. Each free-form business rule may decompose into numerous rules. You must untangle each statement and resolve its internal inconsistencies. Also, it's hard to trace such unstructured statements to other requirements models, and they create change control headaches. If the rules are smaller and more discrete, you can more easily manage change. To capture business rules atomically, it helps to have a business rule template designed for the purpose.

A business rule template presents standard, precise syntax for writing business rules. The template should be designed so that the resulting business rules are declarative, atomic, distinct, independent statements. The very process of tailoring a template to a particular business problem is beneficial because it requires you to understand the problem in great depth. This means working directly with business customers to design and tailor the template.

Examples of useful business rule templates include the following:

  • Each <business term> may <verb phrase> <business term>.

  • When <event|condition is true>, then <action>.

  • If <condition true>, then <condition true/conclusion>.

You can use your templates during the workshop to guide participants in writing business rules.

Templates

Templates are standardized formats that you use during workshop activities to structure the contents of an output product. Templates can be used for building the requirements models, prioritizing requirements, creating related deliverables (such as an action plan or a communication plan), debriefing the workshop, and assessing the team climate (if you incorporate team-building activities into the workshop).

Creating templates forces your workshop planning team to think deeply about project-specific deliverables. It also helps participants to make the best use of their workshop time, and it helps you to provide precise, clear instructions about workshop tasks.

For one workshop, I worked with the planning team to settle on a template for the use cases. For another, I created a business requirements matrix template for use during the workshop. For yet another, I designed a simple form for capturing scenarios. In another case, I devised a template for scenario testing our use cases and data model. In several workshops in which the subsequent software product had cross-functional impact, I used a communication plan template. For most workshops delivering precise business rules, a business rule template is also critical.

Your template should include instructions (or it should be supplemented by a document work aid that has instructions) and perhaps examples of how to properly complete the template. Templates can be created as word processing documents or can be drawn on posters. If your recorder acts as a technographer (see Chapter 5), she can input the group's work into a word processor. You can then display or print the contents of all completed templates for participants to refer to or review during the session.

Templates help to ensure that you get high-quality, consistent information from participants. This is especially critical when you use multiple subgroups working on different requirements for the same model at the same time during the session, a technique discussed in Chapter 9. Templates also force you to clarify doneness tests because you must describe what each deliverable should look like. If you can visualize what the group members must deliver, it's easier to design the collaborative processes to get them there. Templates also help you to give precise instructions to the group during the workshop.

You can supplement the template with a completed example (see "Examples" later in this chapter), which helps participants understand the models they need to create.

Tips for Working on Posters

  • Print in thick, CAPITAL letters.

  • Write straight up and down.

  • Use plain block letters (not script).

  • Avoid black, except for numbering charts.

  • Use these colors for text: blue, brown, purple, green.

  • Use these colors for highlighting: orange, red, yellow, pink.

  • Be faithful to people's own words.

  • Use white space liberally.

  • Consider using the symbols shown in Table 7-4.

Table 7-4 Poster Symbols

Bullets (centered dot) to help items stand apart

Stars for noteworthy items

Circles to connect ideas and draw attention to items

Borders to frame a page or blocks of text

Arrows for sequences, cycles, and merging


Workshop Aids

Workshop aids are tools for conducting activities in the session. These aids include static posters for participants to reference, sample models, instructions or tips to use while working on the models, worksheets for documenting changes to models, and materials and supplies.

Posters Posters are charts that are visible in the room. Create your posters before the workshop, and place them on the workshop room walls using tape, pins, or tacks or by using sticky poster paper (posters on a pad with the top back prepared with repositionable glue). You should prepare posters with the following titles:

  • Workshop Purpose
  • Workshop Products
  • Workshop Agenda (the flow of activities)
  • Issues or Parking Lot (titled and left blank)
  • Input Products
  • Actions (titled and left blank)
  • Decisions (titled and left blank)

Examples Sample models use a "begin with the end in mind" philosophy: They show participants what the end product should look like by providing simple but correct examples. I've found these examples useful for almost every requirements model that employs a template, including use cases, business rules, and scenarios. To create examples that are relevant to the problem, consult with your planning team or other subject matter experts. Even an example that's wrong, but is correctly written or drawn, is useful for participants.

Instructions and Tips Prefabricated instructions or guidelines can help you save time during the workshop. Tell participants what they need to do for each workshop activity, and also give them written instructions (paper handouts or on posters). This method gives everyone a reference point for completing activities.

Provide instructions, especially early in a workshop, for subgroup activities (see Chapter 9). For example, instructions might stipulate that there should be a timekeeper, a recorder, and someone to make sure that the content of the work follows a template format.

It's a good idea to include tips for creating high-quality models. In one workshop, I gave participants a list of good verbs to use in their use case names. In another, I provided a list of verbs for them to use for data model relationships. These kinds of tips help save workshop time.

Worksheets Your recorder can use worksheets for tracking the disposition of and changes to requirements models. When your recorder uses a laptop with a word processor or spreadsheet program, you can project the changes on a screen or print them for reference. In several workshops that delivered use cases, I found a use case completion worksheet helpful (see the Web site for an example).

A note of caution: Don't assume that your readers will be able to understand your workshop aids. Test any input products you create—instructions, examples, tips, worksheets— before you give them to participants. Ask planning team members and a few of the participants to review the instructions and see whether they understand them. Then, during the workshop, review the instructions and ask for clarifying questions.

Materials and Supplies Materials and supplies include all the physical things you'll need to run the workshop: items such as name cards, posters, cards or sticky notes, color markers, paper cutters, side-hole punches, a printer, and binders. (A generic list is available on the Web site.)

Set up binders with dividers in which participants can store all the paper documents they'll work with during the session. I like to supply tab dividers already labeled for things such as purpose, principles, and agenda. The binders can also hold copies of modeling tips, activity instructions, templates, and examples.

After the workshop, participants can use the binders for reference and for storing hard copies of requirements and workshop and project information. Binders save people time by helping them to avoid searching through large sets of documents. They also help participants stay organized during the workshop, and using them sends a message that their work warrants a special storage place.

  • + 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