Loading ...
Sorry, an error occurred while loading the content.

156293Re: [XP] High-fidelity Visualization – an Agile ac celerator?

Expand Messages
  • Jonathan Harley
    Feb 1, 2011
    • 0 Attachment
      IMO, high-fidelity mockups tend to imply completeness to users. One ends up
      having to justify why the estimates to complete the actual work are so
      'large', after all they saw it nearly complete..

      On Mon, Jan 31, 2011 at 4:45 PM, William Pietri <william@...> wrote:

      > On 01/30/2011 10:22 AM, MarvinToll.com wrote:
      > > Is anyone a practitioner with high-fidelity visualizations as a strategy
      > for `executable requirements' gathering and verification? How is that
      > working out?
      > You're talking pixel-perfect mockups?
      > I think it depends on the circumstance. They're necessary for user
      > testing or getting feedback from unsophisticated stakeholders. However,
      > they're expensive to create and hard to change, so they work against the
      > Agile grain.
      > The teams I saw doing best with this tended to do mostly low-fi mockups
      > (e.g., whiteboard sketches, Balsamiq), with a high-fidelity page or two
      > as a style guide when that was necessary. If they had to user-test
      > something, they might create more high-fidelity mockups, but those were
      > treated as disposable assets, rather than things that got updated over
      > time. I also see some teams who do mockups directly in HTML and CSS,
      > which can be less wasteful.
      > In XP-speak, I'd say that most uses of them violate DTSTTCPW. They add
      > inertia to the system, and I'd therefore generally call them an Agile
      > decelerator.
      > William
      > [Non-text portions of this message have been removed]

      [Non-text portions of this message have been removed]
    • Show all 20 messages in this topic