© Jeff Dalton 2019
Jeff DaltonGreat Big Agilehttps://doi.org/10.1007/978-1-4842-4206-3_48

48. Prototyping/Spike

Jeff Dalton1 
(1)
Waterford, MI, USA
 

Description

A prototype, or sometimes called a “spike” if it’s limited in scope or functionality, is a technique used by agile teams to create a product or service proof-of-concept in order to quickly solicit feedback about the design from customers and end users, or to help the team understand the user stories (see “Spike (Design Spike) for more information). Prototypes or spikes can be developed in various ways depending on the type of feedback desired. For example, they can be created using basic materials (e.g., pen and paper) or sophisticated technologies (e.g., markup languages). Prototypes or spikes allow customers to interact with a product giving product teams insight into which features are most important to the end user. The ability to experiment with multiple prototype iterations, and test various concepts in the field, provides critical input into refining the product vision.

../images/470826_1_En_48_Chapter/470826_1_En_48_Figa_HTML.jpg

Typical Roles

  • Product Owner

  • Product Management Team

  • Agile Team

  • End Users

Desired Behaviors

  1. 1.

    Design prototypes/spikes to generate feedback on features, characteristics, and usability.

     
  2. 2.

    Observe end users as they explore each prototype/spike.

     
  3. 3.

    Gather end-user information to help refine the overall product direction.

     
  4. 4.

    Experiment with multiple iterations of prototypes/spikes.

     
  5. 5.

    Groom the product backlog after each prototype/spike to ensure that specific functionality is added, removed, or updated.

     
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.14.252.193