Successfully reported this slideshow.
Your SlideShare is downloading. ×

Prototyping in a Scrum environment

Ad

Prototyping in a SCRUM environment


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

Ad

Purposes and objectives of this document

Purpose                                                        Target audience
•...

Ad

What is prototyping?


  A prototype is an early sample or
    model built to test a concept or
   process or to act as a ...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Loading in …3
×

Check these out next

1 of 16 Ad
1 of 16 Ad
Advertisement

More Related Content

Slideshows for you (19)

Advertisement

Similar to Prototyping in a Scrum environment (20)

Advertisement

Prototyping in a Scrum environment

  1. 1. Prototyping in a SCRUM environment Sid B. Dane SCRUM Ready Team June 21 and September 30, 2011
  2. 2. Purposes and objectives of this document Purpose Target audience • To help people understand: • Business stakeholders to – what prototyping can contribute to the convince that the solution chosen project; is the right one; – understand the different forms of prototype and which one to use; • Business analysts to get – who does the prototyping. requirements clear; • Developers to have a unambiguous idea of the working Objectives of the product. • Use prototyping: – for the right purpose; – in the right way; – more often! SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 2
  3. 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 3
  4. 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 4
  5. 5. Prototyping in the software process Evolutionary prototyping Throw-away prototyping An approach to system development where A prototype which is usually a practical an initial prototype is produced and refined implementation of the system is produced through a number of stages to the final to help discover requirements problems system and then discarded. The system is then developed using some other development process Customer Value prototyping An innovative methodology used to accelerate technology enabled projects and enable business confidence to prove Rapid Design And Visualization that a solution can fulfil business requirements ahead of full implementation. Prototyping to visualize ideas, discover Involves the creation of key business requirements and define scope. This is scenarios for complex business issues done in one or more sessions with the into a working prototype, brings a Stakeholders. The prototype is updated technology solution to life for key during these sessions to improve stakeholders and all within a time-boxed effectiveness of it. environment. SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 5
  6. 6. Different prototype variants depend on needs gather Throw little work, requirements away small scope prototyping Evolutionary prototyping Rapid Design and Visualization bringing more work, concepts Customer Value Prototyping broad scope to life SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 6
  7. 7. Prototyping in the SCRUM process pregame sprint endgame RDV Under Ready for Ready for New Poker done In sprint Completed Released analysis poker sprint throw away PT evolutionary PT SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 7
  8. 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 8
  9. 9. The result SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 9
  10. 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 10
  11. 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 11
  12. 12. Prototype Tooling: Adobe AIR Quick 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 12
  13. 13. Prototype Tooling: JustProto Create 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 13
  14. 14. Prototype Tooling: Axure Create 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 14
  15. 15. Prototype Tooling: Adobe Flash Catalyst Create 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
  16. 16. Prototype Tooling: Plain HTML Example: ReAura skin assessment SCRUM Ready Team, Sid B. Dane, June 21 and September 30, 2011, Prototyping 16

×