Project Management Training Courses Icon

Prototyping Workshop for Business Analysts

2 Days
Classroom Session   |  
3 Days
Live Online


ASPE is an IIBA Endorsed Education Provider of business analysis training. Select Project Delivery courses offer IIBA continuing development units (CDU) in accordance with IIBA standards.


NASBA continuing professional education credits (CPE) assist Certified Public Accountants in reaching their continuing education requirements.


Select courses offer Leadership (PDU-L), Strategic (PDU-S) and Technical PMI professional development units that vary according to certification. Technical PDUs are available in the following types: ACP, PBA, PfMP, PMP/PgMP, RMP, and SP.

14.00 CDUs

Expertise Level: Intermediate
Classroom Registration Fees
Group Rate:
(per registrant, 2 or more)
GSA Individual:
Live Online Registration
Live Online:
Private Onsite Package

This course can be tailored to your needs for private, onsite delivery at your location.

Learn More About Enterprise Team Training


Lively lectures combined with realistic practice exercises will provide you with the competence and confidence to improve project outcomes. You'll gain a thorough understanding of the challenges faced in defining correct user interface requirements, practical approaches for eliciting, presenting and gaining consensus on these requirements. If you play a role in defining the functionality of a system, you can't afford to miss this course!

Prototyping from the eyes of business analysis is not just about the final screen design, but rather the steps to attain the desirable user interface. In this workshop, the learning you will achieve is two-fold:

1. The steps in the prototyping process to yield a desirable interface. 
2. How the prototyping technique provides you as the business analyst an elicitation, analysis, and validation tool all in one as you iterate through the external interface requirements.

This learning will be obtained utilizing lecture, demonstrations and examples; then internalize the learning with hands-on small group exercises to iteratively develop a prototype and test it for usability. You and your peers will identify and discuss strategies and tactics that your organization should be using to better define interfaces.

Establish a greater awareness of the user centered design practices
Evaluate this essential prototyping elicitation and analysis technique
Mitigate risks in your project by having clear user interface requirements
Seek to understand the target audience needs
Evaluate the strategy of the user interface
Understand how parts of the business will be incorporated into requirements
Evaluate how the ideas and concepts of the business interrelate
Structure how the whole thing will fit together
Further elaborate the functional and data requirements
Document behavior in a sequential fashion to complete user goals
Upcoming Dates and Locations
Guaranteed To Run

There aren’t any public sessions currently scheduled for this course, but if you fill out the form below, we can tell you about how we can bring this course to you!

Course Outline

I. Overview of Prototyping

It is important to understand that User Experience Design and Usability Analysis are specialties in which experts receive degrees in the field. This two day class is aimed at equipping the business analysts to execute some forms of prototyping to drive out user-centric requirements. This section provides a background on the subject of Prototyping and how to use it. The power of prototyping is in visualization. Any visualization of a requirement will enable stakeholders to evaluate and clarify more details. The risk involved is that design is sometimes locked prematurely. The prototyping progression will increase effectiveness and reduce risk. There are elicitation considerations on what form of prototype is the most effective for the particular situation which is discussed in this section as well.

  • What is Prototyping
  • Why Create Prototypes?
  • Prototyping Progression
  • Prototyping Considerations

Practice Session for this chapter:

  • Identification of Types of Prototypes
  • Prototyping as a Risk Mitigation Technique

II. Inputs to Prototyping 

There are a couple of inputs needed before diving into the prototyping effort.

  • An understanding of the user
  • An understanding of the site strategy

The people who will be interacting with the user interface provide important context to the requirements elicitation, analysis and later design processes. By understanding their motivations, goals, habits, expectations, and assumptions, you will find yourself building user interface requirements that actually meet the needs of the user. The strategy of the site may not be a straight line to the final design of the solution; however there are three considerations that provide context for the design. You may look at how competitors have addressed like issues. You may want to build a conceptual model of the business to facilitate understanding of how the organization operates. You may need to construct an inventory of all the content the site must accommodate. In this section we will develop personas to understand the user and develop concept models to understand the site information.

  • Understanding the User
  • Understanding the Site Information

Practice Sessions for this chapter:

  • Develop a Persona
  • Present Personas in a Meet and Greet Party
  • Develop a Concept Model using Card Sort Technique
  • Validate Concept Model with Target Users

III. Site Maps 

This section addresses the overall structure of the site utilizing the Site Map. The site map represents how the user will experience the site in a somewhat hierarchical fashion. The site map will also advise navigation. A site map is a particularly important deliverable in the progression to understand how all the site functionality is intended to fit together without getting down in the minutia of the details.

  • Site Map Overview
  • Elaborating the Site Map
  • Site Map Presentations

Practice Sessions for this chapter:

  • Develop Site Map

IV. Flow Chart 

Before we dive into developing the screen design from the site map in the previous section, we need to focus on the steps in the processes. The flow chart is a good medium for defining the sequential steps of a completing a specific task from beginning to end. This will bridge the gap between the site map, which provides a clear start point, but does not provide a sequential pathway after that, AND what the user interface may look like, we will call those wireframes.

  • Flow Chart Overview
  • Elaborating the Flow Chart
  • Flow Chart Presentations

Practice Sessions for this chapter:

  • Develop Flow Chart

V. Wire Frames

Humans will always gravitate toward pictures and toward simple representation of complex ideas, which are the whole point of a wire frame. In this section you will learn about this controversial document beginning to blur the line between structure and visual design. The wireframe starts to represent information on the user interface.

  • Wire Frame Overview
  • Elaborating Wire Frames
  • Wire Frame Presentations

Practice Sessions for this chapter:

  • Develop Wire Frames

VI. Usability Study

The goal of any user-centered activity is to make the interface better for the target audience and their goals. With wire frames in hand from the previous section, you are ready to test their usability. The beauty of this technique is that we will garner useful feedback in time to do something about it. Usability experts have honed skills in the interpretation of usability studies, but anyone who cares about making better interfaces can benefit from learning the basics of usability testing. That said there is always more to learn.

  • Usability Study Overview
  • Usability Study Process

Practice Sessions for this chapter:

  • Develop a Usability Study
  • Conduct a Usability Study
  • Conduct a Consolidated Usability Study

VII. Digital Prototyping Tool

In the early stages of user interface definition, paper prototyping may be the most viable option to garner the most open and honest feedback. Your decision as to when and if to use a digital prototyping tool depends on a number of things such as people/logistics, development context, tasks/date/test scenarios, timing and scope to name a few. In this section, we will explore aspects of using a digital prototyping tool.

  • Overview of a Digital Tool
  • Demonstration of a Prototyping Tool

Practice Sessions for this chapter:

  • Observe a demonstration of a prototyping tool

VIII. Screen Design

This is the point in which we cross the line from requirement definition to the design of the solution but before the actual development. Even Agile methodology requires some understanding of the requirements prior to the actual design of the screens. These screen designs do not magically appear, they work in cooperation with the elements of the prototyping progression in the previous sections. The screen design can be successful when the following are understood:

  • The user needs
  • Underlying strategy and content of the site
  • The overall structure from the site map
  • User flows for completing tasks
  • Relative priorities of content as defined in the wireframes

This section provides business analysts with the distinction between requirements and design as well as an appreciation of the challenges faced by the technical design/development team members

  • Overview of Screen Design Functionality
  • Topics of Design and Content

IX. Websites and Application Prototyping Considerations

Today, we deal with screens of all shapes and sizes – low-resolution cell phones, full-color PDAs, multi-touch screens of all sizes, wall projectors, - but there's no telling how we will access and receive information in the future. Analysts and designers have to deal with this fast changing world. The Business Analyst should be aware of the opportunities and obstacles faced by the design.

  • Device Platforms
  • Design Strategies
  • Design Elements and Templates
Who should attend

This course is valuable for all those involved in managing and defining projects. 

  • Business Customer or Partner who wants to work more effectively with IT colleagues to identify project requirements for solving business problems
  • Business Analyst who needs to define or gather users' business requirements
  • Business Systems Analyst who wants to understand user's business requirements, translate them into clear statements of functional and system requirements and add value to IT projects
  • Systems Analyst who must develop correct technical specifications from functional and system requirements
  • Designer or Developer who desires to produce a high-quality system from the functional and systems requirements
  • Project Manager or Team Leader who must ensure that IT project team members correctly understand customer needs and deliver high quality solutions within project constraints

Yes, this course looks perfect for my needs!