Back to List

How to Use Prototyping to Model and Analyze BI Requirements

Rachael Wilterdink Rachael Wilterdink  |  
Aug 15, 2019
 
If you’re involved in eliciting, modeling, analyzing, or consuming requirements for Business Intelligence projects, this post is for you. This is the tenth and final technique in our blog series on 10 Techniques for Business Analysts (BAs) to model and analyze Business Intelligence (BI) requirements.
 

What is Prototyping?

It’s creating a mocked-up version of whatever it is you want to build (before you build it). The official definition of prototyping, according to the IIBA®, is: “Prototyping is used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements. It is also used to optimize user experience, to evaluate design options, and as a basis for development of the final business solution.” - BABOK® v3.0
 
Prototyping is a method to provide early modeling in order to identify:
  • Missing requirements
  • Improperly specified requirements
  • Unsubstantiated assumptions
  • Early stages of design
 

What Are the Types of Prototyping?

  • Throw-away
    • Very “rough” version (low-fidelity)
    • Could by drawn on a napkin or a whiteboard
    • Not polished
  • Evolutionary (or Functional)
    • Closely resembles the finished product
    • Higher degree of fidelity
    • Could be developed into working software
 
types of prototyping
 

Pros

Prototyping can be quick, easy, and cheap. It lets you explore a design without much effort so you can quickly get feedback from a user before doing any actual development. Prototyping enables innovation and iterative development. This is an excellent way to prove out a concept without wasting time and money.
 

Cons

If you build a throw-away prototype, you won’t be able to build on it – it just goes in the garbage. But if you build an evolutionary prototype, you’ll be able to save the work you did to create the initial prototype – while building on it based on user feedback.
 

Conclusions

They say a picture is worth a thousand words. In this case, it’s absolutely true. People are visual by nature, and they would much rather have something to look at that “describes” their desired solution without having to read a bunch of words. It’s a fantastic tool that should be in everyone’s toolbox. For Business Intelligence specifically, mocking up dashboards or reports before coding them is an excellent way to validate that you are building what your users want.
 
And that’s a wrap! I hope you enjoyed this blog series and that you’ll be able to add a few of the techniques to your toolbox! Let me know what you think and if you know of any other business analysis techniques that are useful when working on BI projects. I would love to know about them!
 

Free Agile Resources


References:
“IIBA Home.” IIBA | International Institute of Business Analysis, www.iiba.org/.
“PMI.” PMI | Project Management Institute, www.pmi.org/.
 
Business AnalysisBusiness Intelligence

 

Love our Blogs?

Sign up to get notified of new Skyline posts.

 


Related Content


Blog Article
How to Drive User Adoption Before, During and After Project Launch
Cory SchmittCory Schmitt  |  
Sep 26, 2019
In Part 1, we talked about some of the factors that can impact adoption before the project even kicks off. In Part 2, we talked about the things that you can do to improve adoption during the project’s Execution. In this last installment, we’ll talk about actions you can take just...
Blog Article
How to Improve User Adoption During Your Project's Execution
Cory SchmittCory Schmitt  |  
Sep 19, 2019
In Part 1, we talked about some of the factors that can impact adoption before the project even kicks off. In Part 2 here, we’ll talk about the things that you can do to improve adoption during the project’s Execution.   Know Your Users “Know Your Users” is a broad...
Blog Article
Pre-Project Components That Can Impact User Adoption
Cory SchmittCory Schmitt  |  
Sep 12, 2019
Does the following situation sound familiar?   You were on a project that rolled out a new application to the organization. You and the team spent many long days (and some nights) building the new application. The team worked hard, and you came in on-time and on-budget. As part of the...
Blog Article
Using Human Hard-Wiring to Create a Strong Agile Experience
Rachel RieckRachel Rieck  |  
Aug 22, 2019
If you have experience on agile teams and are looking to tweak a few things or try something different, then this Trifecta of Greatness blog series is right for you. For more background on the strategies and tactics our Solutions Consulting Director learned from a pivotal agile journey, be sure...
Blog Article
Decision Rights, Team Lead Communication, and Smackdowns (Habits of a Successful Agile Team)
Rachel RieckRachel Rieck  |  
Aug 08, 2019
If you have experience on agile teams and are looking to tweak a few things or try something different, then this blog series is right for you. This is the fifth blog in the Trifecta of Greatness series and highlights a few last habits and techniques. For more background on the strategies and...