Our Approach -- iBusiness Solutions

Our Approach

iBusiness Solutions
7300 Metro Blvd, Suite 590
Edina, MN 55439
www.ibusiness-solutions.biz

Our Approach
Breaking Constraint Driven Project Life Cycle
Typical Model  Typical projects exist within the triple
constraint of scope, budget and time.
 The initiative’s fixed scope is
impacted by the realities of budgets.
 New information learned through the
project typically increases the scope,
but not the budget resulting in
potential failure.
iBusiness Solutions Model
 iBusiness Solutions turns this model
on its head to focus on what can be
accomplished with the given budget.
 Budget is still the #1 driver, and is
used with Time to identify what
Scope items produce the “Maximum
Value”.

iBusiness Solutions, Inc. www.ibusiness-solutions.biz. Copyright. All rights reserved. August 29, 2008 - 13

Our Approach
“Simply” 3 Steps
 Projects are complex enough on their
own, they don’t need to be burdened
Plan with overly complex delivery
approaches.
 At the heart of our delivery approach
is our 3 step process of planning,
visualizing, and building.

Visualize This approach combined with our
agile techniques, we are able to
quickly hone in on what’s important to
your business, and deliver the results
you need.

“Build”


Our Approach
Step 1: Planning

Step 1: Planning what needs be accomplished
 Identify on the people, processes, data, and technology
to support the project
 Resist jumping into the technology “too quickly”
 Cleaning, standardizing, and merging data
 Identify subject matter experts – business and IT
 Search for similar initiatives to leverage
 Evolution or release planning


Our Approach
Evolution/Release Plan

 Our custom approach to
identifying business
requirements, allows us
to fuse together critical
needs and release
schedules


Our Approach
iBusiness Agile Project Approach

 Our agile approach breaks down the large goals into releases and
executable iterations.
 Provides easy adjustments to ensure key features are delivered
 Creates continual feedback loop for deliverable improvements
 Increases benefits as features are useable as they are ready


Our Approach
Agile Differences

Process

By focusing on features, our agile approach reduces risks, improves alignment, and
accelerates project deliverables.

Our Approach
Step 2: Visualizing

Step 2: Visualizing what could be and should be
 This phase focuses on taking a visual look at where we are going
on the project.
 Focuses on visualizing business requirements around the following
areas:
 Business Process Requirements
 Data Hierarchy Requirements
 Visual Requirements
 Approach bridges IT and business teams together.


Our Approach
Business Process Model
 Highlighting the touch points
between people and data, possibly
identifying opportunities to
automate manual, inefficient, and/or
error-prone processes.
 Identifying all stakeholders that
might be impacted by either the
data they produce for this
application or the data they
consume from this application.
 Identifying the data sources that will
need to be analyzed as part of this
project.
 Identifying the database and other
technologies that are part of the
entire ecosystem within which this
application must work.

Our Approach
Hierarchy Diagram

 High-level representation of the major business
hierarchies, or dimensions, providing a clear look at the
data inside business processes.
 Provides a clear representation as to how data needs to
be assembled to realize the business needs.


Our Approach
Visual Requirements Model
 Quickly identify and model major
areas of requirements
 Leads to detailed requirements
definition
 Key: This is technology
independent
 Forces discussions that very often
identify:
 Shortcomings in the data
 Business rules that need to be
clarified
 A variety information that can
have significant impacts on the
design, development, and usage
of the dashboard application.


Our Approach
Step 3: “Building”

Step 3: “Building” the solution
 Building versus assembly
 Resist jumping to the technology “too quickly”
 IT’s role
 Business users’ role
 Focusing it all on the solution


Our Approach
Much to Consider

 Design best practices for dashboard applications
 Iterative design
 GUI usability guidelines and standards
Operational aspects – performance, security, usage tracking, etc.

Location intelligence – adding “where” to “when”

 Master data


Our Approach
Pains Addressed by BPM Applications

 Inconsistent view of operating performance
 Lack of relevant, timely insights delays diagnosis and response to
problems
 Dependence on multiple people and information sources to
understand the state of the business
 Wasted time spent gathering reports which contain duplicate and
incomplete information


Our Approach
Benefits of Our 3 Step Approach

 Accelerates the delivery of project benefits
 Avoids significant rework with JIT detailed design
 Raises the quality of deliverables through early testing
 Improves responsiveness to scope adjustments
 Minimizes alignment gaps to business goals
 Increases project visibility to leadership, stakeholders, and project
resources
 Increases estimating accuracy, by working in small chunks
 Improves project team throughput and satisfaction, by aligning
resources on what they do best!


Contact Us
For additional information, or to discuss your business needs in greater
detail please contact us at

Tim Brands
Office: 612-730-7404
E-Mail: tbrands@ibusiness-solutions.biz

Or visit our web site at: www.ibusiness-solutions.biz


Our Approach -- iBusiness Solutions

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Our Approach -- iBusiness Solutions

Similar to Our Approach -- iBusiness Solutions (20)

Recently uploaded

Recently uploaded (20)

Our Approach -- iBusiness Solutions