Best Practices for Adopting Visualization Into Your...

Mitch Bishop

Johann Mendoza

Best Practices for Adopting Visualization

Into Your Software Process

Dramatically cutting application development cost

#1 Issue Facing CIOs Today

How Do CIOs Get There? (part one)

Rationalization & consolidation of business software

How Do CIOs Get There? (part two)

Accelerating global sourcing programs

Business Software is Supposed to

Help Meet These Challenges

But...

The Way That Business Software is

Designed, Developed & Delivered is

Fundamentally Broken

“In the last year, 70% of projects failed to meet deadlines, &

50% of projects failed to meet the needs of the business;

80% of the issues stem from poor requirements.”

Standish Group Chaos Report, 2007

#

Business Users Don’t Know What They Want Until They See & Interact With It

#

Business Users Can’t Interpret Text Specs., Use Cases, Screen Shots, etc.

Long cycle times

Late stage rework

Poor adoption

Risky global sourcing

Blown business plans

Strained relationships

The Impact is Dramatic

The Solution: iRise Visualization

iRise Visualization Transforms Business & IT Communication

iRise Company Confidential Copyright © 2007 iRise, Inc. www.irise.com

Get to market twice as fast

Cut 30% of project cost

Virtually eliminate rework

Outsource more strategic development

Improve customer experience

Discover new innovations

270 Customers Tell Us: Visualization Delivers

• New custom applications

• Enhancements to existing systems

• SAP, IBM, Oracle extensions

• Mobile applications (e.g. iPhone)

• Web 2.0 & rich Internet applications

What Can You Visualize With iRise?

Our Vision

By 2020 ALL business software will be visualized prior to development, the

same way that visualization is a common practice in the design of every car, airplane

& semiconductor today

Mitch Bishop

Johann Mendoza

Best Practices for Adopting Visualization


Best Practices for Adopting

Visualization into your Software Process

• Agenda

» Goals

» iRise and Visualization

• iRise Roles

• iRise Visualization Methodology

• iRise Deliverables

» Integration into Waterfall

• Waterfall: At a Glance

• Impact to Waterfall Project Roles, Activities, and Deliverables

• Examples

» Integration into Agile

• Agile: At a Glance

• Impact to Agile Project Roles, Activities, and Deliverables

• Examples

» Closing Remarks

Goals



Goals

• Understand the Considerations & Best Practices for

Adopting and Integrating iRise and Visualization

• Understand iRise Visualization Roles, Activities, and

Deliverables

• Review Waterfall and Agile to:

» Identify areas where Visualization can be used

» Assess impacts to project roles, activities, and deliverables

» Understand iRise usage throughout both processes

» Discuss examples

• Experience a sample of iRise Adoption Services

iRise and Visualization



iRise Roles

• In Visualization, team members throughout your

software process may assume one or more of the

following iRise roles:

» iRise Modeler

» iRise Reviewer

» iRise Consumer

iRise Roles: Modeler

• Builds visualizations in iRise Studio

• Facilitates collaboration with Reviewers

• Iterates/refines visualizations until all parties agree

and understand what needs to be created

• Skill-set may include:» iRise Expertise: Proficiency in iRise

» Visualization Skills: Ability to understand customers’ needs and turn it

into something they can see

» Facilitation: Build shared understanding of what’s required, negotiate

priorities, and generate shared sense of what needs to be created

» User Experience: Understand how to build solutions that are usable,

practical, and attractive

» Process Modeling: Understand and build an efficient process flow into all

solutions

iRise Roles: Reviewer

• Conducts hands-on assessment of iRise visualizations

at many steps

• Provides input to Modelers to create and refine

visualizations

• Validates assumptions and requirements presented in

visualizations

• Helps drive the design process forward using

visualizations

• Confirms that visualized solution meets users’ needs,

solves their problems, and is usable… all before

coding begins

iRise Roles: Consumer

• Similar to Reviewers but not necessarily tasked with

providing visualization feedback

• Instead, leverages the visualization as input for their

downstream activities

• Receives the visualization and begins work on their

respective deliverables much earlier in the process –

w/o having to wait for coded application

• Accepts the visualization and uses it to write test

scripts, train users, deliver sales demos, etc.

iRise Visualization Methodology

• Visualization and the creation of iRise simulations are

iterative and collaborative activities

Scenario Ideation- Focus on Understanding the High-Level Scenario Flow

Iterate

Iterate

IterateHigh-Fidelity Simulation- Incorporate Layout, Look-and-Feel, and Usability

Analysis-Level Simulation- Identify and Validate the Functionality of each Scenario

1

2

3

Scenario Ideation: Sample Output

Analysis Level Simulation: Sample Output

High Fidelity Simulation: Sample Output

iRise Visualization Deliverables: What to Build

• At each stage of the iRise Visualization Methodology,

deliverables will have varying degrees of Visual

Fidelity and Functional Complexity

• Visual Fidelity

» Includes all aspects of a system’s design including elements such

as colors, shapes, layout, typefaces, graphical assets, and copy

• Functional Complexity

» The behavior of the system in response to the user (a.k.a.

interaction, business and data logic)

iRise Visualization Deliverable: What to Build

• Enough detail so customer figures out what’s

going on, but no more

• Not meant to be polished

• “Quick-and-dirty”

• Enough detail so customer figures out what’s

going on, but no more

• Generally static pages lacking dynamic behavior

• Textual descriptions or placeholders used to

describe behavior

• Relevant design elements applied allowing

customer to visualize layout and presentation

of page

• Wireframes

• Relevant dynamic elements applied allowing

customer to interact with behavior and operation

of page

• Usability and user experience elements

introduced and tested

• Textual descriptions converted to functional and

dynamic behavior

• Polished design or high quality screens

• Looks exactly or almost like the application to

be delivered

• “To-the-pixel” design

• Outcome of numerous iterations

• Behaves exactly or almost like the application to

be delivered

• Findings from usability and user experience

testing applied in behavior

• Outcome of numerous iterations

Visual Fidelity Functional Complexity

Med

Low

High

Integration into Waterfall



Waterfall – At a Glance

SUBMIT

PROJECT

REQUEST

DETERMINE

BUSINESS

NEED

ASSESS RISK

DEVELOP

BUDGET

PRIORITIZE

ADD TO

PORTFOLIO

DEFINE HI

LEVEL

RQMTS

RESEARCH

PACKAGE

SOLUTIONS

PROPOSE

SOLUTION

DESIGN

SET UP

PROJECT &

RESOURCES

REFINE

SCOPE &

PROJ. PLAN

DEVELOP HI-

LEVEL

ARCH.

QUALITY

TOLLGATE 1

DEFINE

CHANGE

MGMT PLAN

DEFINE

BUSINESS

PROCESSES

CONDUCT

VENDOR

EVALS

DEFINE

SOLUTION

RQMTS

DEVELOP

SOLUTION

ARCH.

QUALITY

TOLLGATE 2

FINALIZE

SCHEDULE/B

UDGET

DEVELOP

PROJ MGMT

PLAN

DEFINE USE

CASES/

SCENARIOS

DEFINE

FUNC

RQMTS

DEFINE

DESIGN SPEC

DEFINE

DETAILED

DESIGN

DEVELOP

TRNG/MKTG

MATERIAL

DEVELOP

TEST

SCRIPTS

DRAFT OPS

SUPPORT

APPROACH

DEVELOP

UAT PLAN

DEVELOP

TECHNICAL

SOLUTION

DEVELOP

TEST

CASES

CONDUCT

UAT

TESTING

CONDUCT

UNIT/SYS

TESTING

CONDUCT

PERF

TESTING

TRAIN

USERS &

SUPPORT

PERFORM

MKTING

COMM.

IMPLEMENT

OPS

SUPPORT

CLOSE

PROJECT

TRANSITION

TO SUSTAIN

QUALITY

TOLLGATE 3

QUALITY

TOLLGATE 4

FU

NC

TIO

NA

LPR

OJEC

T M

GM

TT

EC

H.

QA

CHANGE

MGMT

ASSESSMENT

FINALIZE

PROJ MGMT

PLAN

FINALIZE

CHANGE

MGMT PLAN

PROPOSE PLAN DEFINE BUILD/TEST DEPLOY

Waterfall: Propose Phase

Process Activity Define High Level Requirements (HLR)

iRise Phase(s) Used Scenario Ideation

Modeler(s) BA

Reviewer(s) Project Sponsor, Project Manager, Business SME

Consumer(s) by Phase Plan/Define: BA, PM, Architect

II. iRise Role to Project Role Mappings

Visual Fidelity Low

Functional Complexity Low

Input(s) Project Charter

Output(s) High Level Requirements and Scenario Flows in iRise, Textual Requirements in

iRise

III. iRise Visualization Deliverable

I. Integration into Activity

IV. Comments» Begin collaboration in iRise Definition Center in this activity

Waterfall: Plan Phase

Process Activity Define Use Cases and Scenarios

iRise Phase(s) Used Scenario Ideation > Analysis Level Simulation

Modeler(s) BA, Interaction Designer

Reviewer(s) Project Manager, Business SME, Architect, Developer

Consumer(s) by Phase Define: BA, PM, Architect, UX, IA, ID, VD, Developer

Build/Test: Developer, Architect, QA, Tester, Data Modeler


Visual Fidelity Low > Med

Functional Complexity Low > High

Input(s) iRise Visualization of High Level Requirements

Output(s) Visualized Use Cases and Scenarios in iRise, Textual Requirements in iRise



IV. Comments» Leverage iRise Asset Libraries when building higher visual fidelity and functional complexity

» Continued collaboration in iRise Definition Center

Waterfall: Define Phase

Process Activity Define Functional Requirements

iRise Phase(s) Used Analysis Level Simulation > High Fidelity Simulation


Reviewer(s) Business SME, PM, BA, Developer, UX, IA, ID

Consumer(s) by Phase Define: PM, VD, UX, IA, Architect

Build/Test: Developer, QA, Tester

Deploy: Trainer, Sales, Marketing, Change Management, Support, Sustain


Visual Fidelity Med

Functional Complexity Low > High

Input(s) Use Cases/Scenarios in iRise, Interaction Guidelines, Style Guide

Output(s) Func Rqmts Doc in iRise, Interactive Wireframes in iRise (Prototype)



IV. Comments» Capture Textual Requirements in iRise

» Leverage iRise Asset Libraries when building higher visual fidelity and functional complexity


Waterfall: Define Phase

Process Activity Define Design Specifications

iRise Phase(s) Used Analysis Level Simulation > High Fidelity Simulation

Modeler(s) Interaction Designer, Visual Designer

Reviewer(s) Business SME, PM, BA, Developer, UX, IA, ID

Consumer(s) by Phase Define: PM, VD, UX, IA, Architect

Build/Test: Developer, QA, Tester

Deploy: Trainer, Sales, Marketing, Change Management, Support, Sustain


Visual Fidelity High

Functional Complexity Med > High

Input(s) Func Rqmts Doc in iRise, Use Cases in iRise, Interaction Guidelines, Style Guide

Output(s) Design Specifications in iRise, Updates to Style Guide & Interaction Guidelines



IV. Comments» Capture Textual Requirements in iRise

» Leverage iRise Asset Libraries when building higher visual fidelity and functional complexity


Waterfall: Build/Test Phase

Process Activity Develop Test Scripts

iRise Phase(s) Used N/A (iRise Consumers Only)

Modeler(s) N/A

Reviewer(s) N/A

Consumer(s) by Phase Build/Test: Developer, QA, Tester

Deploy: Change Management, Support, Sustain


Visual Fidelity Med > High


Input(s) iRise Visualization

Output(s) Test Scripts, Test Cases, Test Plan



IV. Comments» Some UAT moved upstream and completed in Define Phase

» Use iRise scenarios as starting point for Test Scripts

Waterfall: Deploy Phase

Process Activity Train Users and Support

iRise Phase(s) Used N/A (iRise Consumers Only)

Modeler(s) N/A

Reviewer(s) N/A

Consumer(s) by Phase Deploy: Trainer, Support, Sustain




Input(s) iRise Visualization

Output(s) Trained Users, Trained Support Team



IV. Comments» Centralized training via iRise Definition Center

» Distributed training via iRise iDocs

» No need for training environment setup

» Consider moving this activity upstream to Test Phase to accelerate Training

Integration into Agile



Agile – At a Glance

SPRINT 0 SPRINT 1 SPRINT 2…

Sprint BacklogSprint Backlog

Sprint BacklogSprint Backlog

Sprint BacklogSprint Backlog Sprint 1 Backlog Sprint 2 Backlog

20

Days

24

Hrs

20

Days

24

Hrs

Product Backlog

Sprint 1 Incremental Release Sprint 2 Incremental Release

1

2

3

4

1

2

3

4

Agile: Sprint 0 - Plan and Prioritize Sprints

iRise Phase(s) Used Scenario Ideation > Analysis-Level Simulation

Modeler(s) Product Owner, BA

Reviewer(s) Scrum Master, BA, Architect, Application SME

Consumer(s) Scrum Master, BA, Interaction Designer, UX, Developer, Architect


Visual Fidelity Low > Med

Functional Complexity Low > Med

Input(s) Product Backlog

Output(s) Sprint Backlog, Scenario Flows/Low Fidelity Visualization and Rqmts Text in iRise


I. Integration into Sprint

IV. Comments» Visualize with goal of identifying LOE, scope/estimates, priority, quick-wins, low hanging fruit, and

dependencies

» After Sprint Backlogs are prioritized, Modeler preps for upcoming Sprint (i.e. Sprint 1) by refining

visualization to Med Fidelity/Med Functionality

Agile: Sprint 0 – Prepare the iRise Asset Library

iRise Phase(s) Used Analysis-Level Simulation > High Fidelity Simulation

Modeler(s) Interaction Designer, Visual Designer, UX

Reviewer(s) Interaction Designer, Visual Designer, UX, Developer, Architect

Consumer(s) Scrum Master, BA, Interaction Designer, UX, Developer, Architect




Input(s) Existing iRise Asset Library, Interaction Guidelines, Style Guide

Output(s) Updated iRise Asset Library with Design Patterns



IV. Comments» iRise Asset Library should contain Templates, Masters, Predefined Styles, Design Patterns, etc.

» Preparing this ahead of time allows teams to quickly achieve High Fidelity visualizations within the fast-

paced Agile environment

Agile: Sprint 1 and Beyond…

iRise Phase(s) Used Analysis-Level Simulation > High Fidelity Simulation


Reviewer(s) Product Owner, Scrum Master, ID, VD, UX, Developer, Architect

Consumer(s) Scrum Master, BA, ID, Developer, Architect, QA, Tester, Trainer


Visual Fidelity Med > High (if necessary)

Functional Complexity Med > High (if necessary)

Input(s) Sprint Backlog, Low/Med Fidelity Visualization in iRise, iRise Asset Library

Output(s) Med – High Fidelity Visualization, Textual Requirements in iRise Doc Text



IV. Comments» Uncovered requirements in Sprint are either factored back into visualization or reprioritized and moved

to a later Sprint

» Towards end of current Sprint, begin Med – High Fidelity visualization for next Sprint

Agile: Sprint 1 Example

• Weeks 1 - 2 » Team confirms understanding of, and validates, requirements by reviewing the Visualization

» Coding begins as early as middle of week 1

• Week 3» Validate code with Visualization - uncovered requirements are visualized or moved to future Sprint

• Week 4» Training and marketing communications commence and backlog updates performed

» Modeler begins visualization for next Sprint

Week 1 Week 2 Week 3 Week 4

Modeler refines Visualization: Med to High Fidelity (Leverage iRise Asset Library)

Consumers validate coded application with Visualization

Team iterates and documents requirements in iRise

Consumers develop, test, QA

iRise Visualization Leveraged: Green

Reviewers validate & provide feedback on Visualization

Consumers train users & communicate marketing

Modelers update Visualization w/ uncovered requirements (if necessary)

Consumers update Product/Sprint Backlogs

Begin Visualization for next Sprint: Med Fidelity

Closing Remarks



Recap of Best Practices

• Integrating iRise and Visualization

» Identify all activities that can benefit from Visualization

» Map iRise Visualization Methodology to activities/phases/Sprints

» Map iRise Roles to Project Roles

» Determine level of Visual Fidelity and Functional Complexity

» Replace or augment existing process deliverables with iRise Visualization

» Revisit and refine your methodology after a few projects

• Visualization using iRise

» Iterate early and often

» Build for Reviewers in current phase AND Consumers downstream

» Move activities upstream, if possible

» Capture textual requirements in iRise Document Text

» Leverage iRise Definition Center: Visualization is an iterative AND

collaborative process

» Prepare an iRise Asset Library: Achieve High Fidelity/Functionality quicker!

• If you need further assistance with integration, engage iRise PS for

Adoption Services

69

Contact Information:www.irise.com

[email protected]

[email protected]

iRise: (800) 556-0399

Thank you for attending

Best Practices for

Adopting Visualization


Please submit questions now...

http://www.irise.com/

mailto:[email protected]

mailto:[email protected]?subject=Web%20Seminar%20-%20Adopting%20Visualization

Best Practices for Adopting Visualization Into Your...

Documents

Transcript of Best Practices for Adopting Visualization Into Your...