Sid B. DaneSCRUM Ready TeamJune 21 and September 30, 2011

Prototyping in a SCRUM environment

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 2

Purposes and objectives of this document

Purpose• To help people understand:

– what prototyping can contribute to the project;

– understand the different forms of prototype and which one to use;

– who does the prototyping.

Objectives• Use prototyping:

– for the right purpose;– in the right way;– more often!

Target audience• Business stakeholders to

convince that the solution chosen is the right one;

• Business analysts to get requirements clear;

• Developers to have a unambiguous idea of the working of the product.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 3

What is prototyping?

A prototype is an early sample or model built to test a concept or

process or to act as a thing to be replicated or learned from.

πρῶτος τύπος = protos typos = first impression

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 4

Use of prototypes in our SCRUM process

• We use prototypes to identify requirements;– Requirements elicitation. Users can experiment with a prototype to

see how the system supports their work;– Requirements validation. The prototype can reveal errors and

omissions in the requirements.• We use prototypes for complex concepts in interaction and user

interface;• Prototyping can be considered as a risk reduction activity which

reduces requirements risks.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 5

Prototyping in the software process

Evolutionary prototypingAn approach to system development where

an initial prototype is produced and refined through a number of stages to the final system

Throw-away prototypingA prototype which is usually a practical

implementation of the system is produced to help discover requirements problems and then discarded. The system is then developed using some other development process

Customer Value prototypingAn innovative methodology used to

accelerate technology enabled projects and enable business confidence to prove that a solution can fulfil business requirements ahead of full implementation. Involves the creation of key business scenarios for complex business issues into a working prototype, brings a technology solution to life for key stakeholders and all within a time-boxed environment.

Rapid Design And VisualizationPrototyping to visualize ideas, discover

requirements and define scope. This is done in one or more sessions with the Stakeholders. The prototype is updated during these sessions to improve effectiveness of it.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 6

Different prototype variants depend on needs

Throw away

prototyping

Evolutionary prototyping

Rapid Design and Visualization

Customer Value Prototyping

little work, small scope

more work, broad scope

gather requirements

bringing concepts

to life

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 7

endgamesprintpregame

Prototyping in the SCRUM process

New Under analysis

Ready for poker Poker done Ready for

sprint In sprint Completed Released

throw away PT

evolutionary PT

RDV

CVP

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 8

Managing expectations

• You need to make sure that the stakeholders have the correct idea when they see or review the prototype. You don’t want them to think that the project is almost ready. It’s just a prototype.

– Lo-fi prototypes• Use when designs are not definite;• Use when you need to focus on scenarios and flow;• Helps your thinking process, without distractions;

– Hi-fi prototypes• When you need to convince stakeholders;• When designs are (almost) done;• If you’re adjusting existing functionality; Concept car

(movie clip)

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 9

The result

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 10

Prototyping in the pregame

• Prototypes generally are:– Identified during T-shirt estimation sessions;– Selected during start of requirements gathering process

• Prototyping for 4 specific reasons:– Get requirements clear (throw away prototyping)– Iteratively think and build (evolutionary prototyping)– Focus on and discover customer needs in multi disciplinary teams

(customer value prototyping)– Visualize concept with stakeholders (rapid design and visualization)

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 11

Prototype Tooling

• Adobe AIR• JustProto• Axure• Adobe Flash Catalyst• Plain HTML

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 12

Prototype Tooling: Adobe AIRQuick layout because of large library of components.

Easy to apply behaviors.

Easily distributable and has auto-update possibilities of the prototype.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 13

Prototype Tooling: JustProtoCreate clickable wireframes.

Limited behavioral functions.

Online, so working with team and distribution (collaboration) is easy.

Can export to HTML.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 14

Prototype Tooling: AxureCreate clickable wireframes.

Better behavioral functions.

Can export to HTML.

Can generate documentation in PDF.

Nice feature to add comments.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 15

Prototype Tooling: Adobe Flash CatalystCreate clickable wireframes.

Better behavioral functions.

Can export to HTML.

Can generate documentation in PDF.

Nice feature to add comments.

SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 16

Prototype Tooling: Plain HTML

Example: ReAura skin assessment