Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Business analyse 2.0

No description

Maurits Donga

on 26 November 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Business analyse 2.0

by: Maurits Jan Donga Business analyse 2.0 Or how does a BA project progress in time? BA 2.0 Project phases 1. Context related chaos
(exploration) Or what to do when? BA 2.0 Proces *. Exploration Or what is your focus? BA 2.0 contexts To be
(desired situation) Or what is it? Business analysis 2.0 Wikipedia: Business analysis is the discipline[1] of identifying business needs and determining solutions to business problems. Solutions often include a systems development component, but may also consist of process improvement, organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst. IIBA: Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. BA 2.0: Business Analysis 2.0 is the discipline of identifying and describing current business situations, future needs and/or describing possible solutions by means of intense stakeholder and context observation, analysis and involvement. BA 2.0 methods,
techniques & tools Or what to use when? Exploration methods, techniques & tools: As is:
Conversation (6 w's)
Delphi technique
Focus groups
User stories
Walk through Documentation methods, techniques & tools: BA 2.0 Situations Or when to use BA 2.0? 1. Requirements elicitation 2. Architectural analysis
& description 3. Business analysis & design 4. Process analysis
& design 5. Information
analysis & design 6. System
analysis & design 7. Infrastructure
analysis & design *. Analysis Different stakeholder views based on their context, needs and wishes 2. Abstracted truth (analysis & documentation) Abstracted conceptual truth based on general shared contexts, needs and wishes Consensus on shared understanding of reality. Context bounded needs and wishes are understood across context boundaries. 3. Contextualized reality (secure) To be:
Brainstorming & mindmapping
Conversation (6 w's)
Delphi technique
Focus groups
Role playing
Visioning *. Documentation *. Secure Analysis methods, techniques & tools: As is:
Delphi technique
Focus groups
Usability evaluation
Task analysis
Formal heuristic evaluation
Competitor analysis To be:
Affinity diagram
Card sorting
Delphi technique
Focus groups
User cost-benefit analysis
Wizard of oz prototyping As is:
Human centered design & documentation methods (Archimate, KISS, SMART)
Iterative design
Parallel design
Story boarding To be:
Human centered design & documentation methods (Archimate, KISS, SMART)
Iterative design
Parallel design
Story boarding Secure methods, techniques & tools: As is:
Focus groups/Subject matter experts feedback & review
Post-experience interview
Outsider evaluation To be:
Participatory design
Focus groups/Subject matter experts feedback & review
Role playing
Controlled user testing
Post-experience interview BA 2.0 Unique characteristics Or why is it different? Human centered No single solution Iterative evolution BA 2.0 Unique Selling Points Or why it works (better)? User focused, iterative evolution of multiple solutions towards a single solution means:
Increased productivity
Reduced errors
Reduced training and support
Improved acceptance
Enhanced reputation Use BA 2.0 if you want to be effective, efficient and satisfy your users and customers Why do we need Business Analysis 2.0? Or why do most projects fail? Poor user
input Stakeholder
conflicts Insufficient
communication Too many
requirements Scope changes Insufficient
stakeholder involvement Vague
requirements Which results in:
Cost overruns
Time overruns
Bad quality
A lot of training
And even more support Insufficient
familiarity As is
(current situation) Inside the business Outside the business
Full transcript