21/11/2019

Business Intelligence
Building the BI Project Plan Program Studi Sistem Informasi Agus Cahyo Nugroho, S.Kom., M.T.

Project resources
Roles vs resources
Roles and resources chart
Team members & other players
Documenting business requirements
Requirements-Gathering Techniques
Overview The data difference
Data needed to support your desired functionality
Successful BI

With a technology architecture in mind and a list of

major applications to build, the project manager works with his project team to begin working out the major tasks of the project. A list of required skills must accompany each step so the project
role will become a specific resource.
Early on you should assemble a general list of roles
Project Project required for the project. A role is a standard combination of abilities and sets of skills
resources resources

Think of a role as a job associated with a single verb —

say, “tester” or “documenter” or “network analyzer.” It describes someone who has all the skills necessary to perform that one more general function in a project environment. Of course, some o
Engineer”.
Once the project-management team determines all the roles, it’s time to match them up with your available resourc
that matches roles with resources; in this case, the role-

Project Roles vs
to-resource relationship is (in database terms) many-to-
resources resources
many. That’s because you may find that some team
members can play more than one role — and in some cases, you must have multiple people playing a single role.

1
 21/11/2019

Roles and resources chart

Most business intelligence projects include the following

professionals who are each experts in one or another key area of the project. You should get familiar with the titles and responsibilities of these roles:

Project manager: This person coordinates and manages all

Team project activities.
Business analysts: This person is tasked with working closely with all stakeholders to codify the requirements for the project. BA’s also manage the requirements documentation and oversee the change cont
members

ETL developers: Various people can fill this role

(unique to BI projects):
extracting, transforming, and loading data. This domain of responsibility includes all
BI developers: Often these are experts in particular domains of technology. They manage the end-user environment — whether in terms of reporting, analysis, visualization,
TheorBI
some other
data tool. This group might include application developers, data-mining experts, or
repository
report developers.
Team The end-user environment
TeamDatabase administrator: This person designs and maintains the members
memberstarget data repository that is the destination for operational data
feeds.
Data administrator: The person in this role plays an important part in any BI project: identifying and analyzing operational data sources throughout an organization, and developing a process to bring the data together.

Testers: With so many diverse elements in a BI

application environment, there could be a considerable variety of quality-assurance roles. When you’re developing the project plan you’ll need to
For example, some projects may require all of these specialty testers: account for people who serve as quasi-resources — folks outside the project team wh
Front-end testers for the user-facing software Some examples of these roles are :
A data-quality analyst who can monitor the data itself to ensure that it’s performing as advertised End-users: These people will ultimately be relying on the BI environment to perform
Integration testers who will make sure that the tools at various points in the development cycle.
applications are working together properly, and that all the pieces have come together as designed
Team
Other players
members

2
 21/11/20

Network infrastructure: Because all that BI data will

flow over the corporate network, and the data repository and applications will probably reside in the company data center, you’ll need the cooperation of the infrastructure team to get the e
Risk-management and security experts: These people help your team comply with corporate standards for handling data and recording your organization’s
processes.

Other players

Subject-matter experts: Interpreting the data (and the

kinds of insights the users are seeking) may require an outside expert who understands the nature of the business. For example, a large retailer might invite a store manager or the point-of-sa
are storing.

Other players

Specifically, a requirements document should contain some or all of

Different companies — even different teams in the same company the following general features:
— have different names for this process. But whether you call it a Business Requirements Document (BRD), a System RequirementsProject
Specification (SRS), Needs
assumptions: Analysis
Elements (NA),
either fullyororany one ofoutside
partially what seems like a million
your control otherbestuffy
that must names
in place for t
functional information about your system. And your BI team has to Project features: A quick overview of the main deliverables. Requirements: The meat of the docume
Documenting build it.
Documenting Process flows: How the main components of the project will
interact, and how the users will work with the system.
business requirements business requirements

Requirement priority: The subjective level of importance assigned

to a requirement or group of requirements. Traceability and change information: Links that show requirements’ origins and interdependencies.
As long as the resulting document addresses these two main
Prototypes and screen shots: Mock-ups of key user interfaces.
Documenting Documenting
Use cases: Step-by-step narratives outlining how actors (users or external systems) interact with the system in question.
concerns, you’re in good shape:
Specifies the functional requirements of the application being designed
business requirements business requirements
Describes the business processes that the application will address

3
 21/11/20

The usual methods include the following:

Group meetings: Get a bunch of stakeholders in a room and hash out the requirements.
Individual interviews: Talk one-on-one with representatives from the user community.
Questionnaires: Ask stakeholders what their needs are via e- mail.
Requirements- Prototypes and pilot storyboarding: Show folks the possible
scenarios of how the application might look — and ask for feedback.
Gathering Techniques

Requirements-gathering activities for a BI implementation is

different from that of other technology implementations in one key respect: the data. With business intelligence projects, you’re not

conducting any transactions that create new data; you’re simply

The data using data that already exists in the system.
That means you have to work with the user groups to determine what data they need to do their jobs well, what data they’d like to have to do their jobs better, and how best BI tools can deliver that
difference data to them.

On the flip side of that, you’ll be working with data providers — At the heart of the business intelligence process is the information
teams who control historical data in various databases throughout Data needed stored by your system (or systems) that will ultimately feed the applications and lead to insights. Whe
What data do we need to work with?

The data
the organization — to determine what information your BI tools can to support your desired Where is it currently stored?
access and make available for the users. Your team will need to carefully research and specify both data supply and data demand inHow
the project requirements;
important how you
is it to the users (thatmatch theoften
is, how two is
will
it determine
used)?
difference the success or failure of your project. functionality

Unlike transactional applications, business intelligence systems

The best BI
never actually create data. Your system will read information from existing systems, manipulate it, and perhaps even derive some temporary deployments
data are but
to work with, compact, well-conceived,
it’s a one-way and BI
street; your work as won’t create data that will be pe
system
deciding whether to pull the data into a data warehouse, or access it expected. That gives your team an early success and a platform to build upon.
Data needed
to support your desired If the system meets its business objectives — whatever those may
functionality Successful BI be in your company’s situation — that’s all that matters.
And there are certain things you can do to increase your chances of success. In fact, most successful B

where it

4
 21/11/20

That means shoot for reachable goals, such as a finite domain of

reports, or a single analysis tool. Realism means grounded in reality, but it also implies well-defined. The business headaches you’re
addressing may not be sexy, but you know exactly what they are

and what their negative impact is on the organization.

Be realistic Think in terms of six-month timelines. The first six months may include the task of assembling a data-collection point — say, a data warehouse with some simple reporting tools on top of it. But after the six-month iterations that f
bite-sized chunks.

There’s nothing worse than an IT team forcing a solution on a team

that’s satisfied with the applications they’re already using. Wherever
Follow possible, your BI solution should aim to solve a problem that’s dying
to be solved — one that’s been neglected for years, really important to the company, or both.
Demand

Your implementation strategy is built to solve an existing problem,

Sometimes the sorest tooth has the hardest cavity to fill. Rule #1 — but the steps should be additive; each piece of the solution contributing to the success of the next.
set realistic goals — has priority. Don’t get yourself in over your head; you’ll find that the hot potato isn’t so easy to pass along once it’s in your hands.
On the other hand, you’ll often get a lot of help if you’re trying to
crack a tough nut. And you’ll need that cooperation from the business groups you’re working with.
A perfect example is building related data marts that cover related
Follow Act now, but subject matter while keeping an eye on creating a grand solution down the road; that’s a holistic, data
or defining characteristics about your customers.
Demand think ahead

Terima Kasih
Those short-term, small-scale successes fuel the team to do bigger
a aguscahyonugroho.blogspot.com WA : 082220700282
Act now, but and better things. And the tools they build — along with the experience they gain — from those data-mart implementations will
make later success that much more likely.
think ahead