Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Prototyping/Wire-framing and Agile/Lean
Last Post 24 Apr 2014 07:33 AM by Justin Todd. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Justin Todd
New Member
New Member
Posts:48
Justin Todd

--
17 Apr 2014 04:54 AM
    Morning,

    I wanted to get your opinions on the use of prototypes and wire-frames within the Agile and Lean contexts. I find them very useful in showing clients what they have asked for and the expected functionality but I suppose they can also be considered wasteful as they require quite a lot of upfront work and also prescriptive to the Development Team.

    Can they co-exist?

    Thanks,
    Justin
    Mandy Schoeman
    New Member
    New Member
    Posts:5
    Mandy Schoeman

    --
    17 Apr 2014 05:08 AM
    Hi Justin,

    Prototyping and wire-framing can be useful however balancing expectations associated to this will be difficult due to some clients wanting the "exact" screen. You also don't want to use software that makes the process of prototyping a long and arduous event.

    My advice:

    1. Use a piece of simple software like Balsamiq (quick, easy and has click through etc)
    2. Add your mockup step to your DoD (definition of done)
    3. Manage stakeholder expectations carefully (using the DoD will help)

    Go to their website http://balsamiq.com/products/mockups/ for more info

    Hope this helps
    Cheers
    Mandy
    Justin Todd
    New Member
    New Member
    Posts:48
    Justin Todd

    --
    17 Apr 2014 05:16 AM
    Hi Mandy,

    Thanks for the info. I will check it out. Have you heard of PowerStory? http://power-story.com.

    It is a PowerPoint plugin. I also saw storyboard which is another PowerPoint plugin but is part of Visual Studio 2013.

    They also look interesting.

    Thanks,
    Justin
    Mandy Schoeman
    New Member
    New Member
    Posts:5
    Mandy Schoeman

    --
    17 Apr 2014 04:48 PM
    Hi Justin,

    Thanks for the PowerPoint link, I'll definitely go try it out. Let me know how you like Balsamiq :-)

    Cheers
    Mandy
    Ludwig Harsch
    Basic Member
    Basic Member
    Posts:272
    Ludwig  Harsch

    --
    19 Apr 2014 03:31 AM
    Hi Justin,
    including Mockups in the DoD (and thus in the sprint backlog) is one option.
    Another option is to treat a mockup as part of a Product Backlog Item. The Scrum guide states, Product Backlog management includes [...] Ensuring the Development Team understands items in the Product Backlog to the level needed. To my experience, Mockups can help a lot in this purpose for stories that include a UI.
    The advantage of this approach is that the PO can manage stakeholder expectations before the item is in the Sprint Backlog. This can lead to less waste and less external dependencies within the sprint (impediments). On the other hand, it can happen that you create mockups for stories which will never be implemented, which is also waste.
    To your question, if this is too descriptive, ask the team how they prefer to work together, inspect and adapt.
    Oh and Mandy, Balsamiq is great :-)
    Justin Todd
    New Member
    New Member
    Posts:48
    Justin Todd

    --
    24 Apr 2014 07:33 AM
    Thanks for the feedback all.
    You are not authorized to post a reply.


    Feedback