UPA 2011 - Better Usability Through Visualization

  • 432 views
Uploaded on

 

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
432
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. UPA – Better Usability Through Visualization
    Chuck Konfrst, Senior Visualization Designer / Director of Branding & Communications
  • 2. Welcome!
    Agenda
    • Introductions
    • 3. What Is Visualization?
    • 4. Visualization Demonstration
    • 5. Group Breakout
    • 6. Mock Project Requirement Sessions
    • 7. Questions & Answers
    © 2011 OneSpring® All Rights Reserved.
  • 8. Introductions
    • Name
    • 9. Company
    • 10. Role
    • 11. What you’d like to get out of the workshop
    • 12. Favorite Cartoon Character & Why
    © 2011 OneSpring® All Rights Reserved.
  • 13. Visualization
    What Is Visualization?
    © 2011 OneSpring® All Rights Reserved.
  • 14. “68% of projects fail, run late, or are OVER budget.”- The Standish Group, 2009 Chaos Summary Report
    “70% of REWORK is attributed to correcting requirements errors.” - Meta Group
    “30% of project costs are REWORK .”- Forrester Research
    © 2011 OneSpring® All Rights Reserved.
  • 15. Visualization for Software Definition
    Today, the ability to pre-visualize a software application has become a reality.
    Using scenarios as the initial “sketches” of a storyboard, visualization tools allow software definition teams to model entire applications before writing a single line of code.
    © 2011 OneSpring® All Rights Reserved.
  • 16. Visualization for Software Definition
    AutoCAD/CAM technologies that revolutionized the automotive, aeronautical, and construction industries.
    Now, software visualization tools can simulate applications and help stakeholders truly understand process flow, behaviors, look and feel, and other aspects of the application before it is built.
    © 2011 OneSpring® All Rights Reserved.
  • 17. The key benefit to visualization is the ability to validate your requirements from the start with stakeholders
    This, in turn, leads to the realization of the following benefits:
    • Reduction of Requirements Cycles by at least 30%
    • 18. Reduction ofRequirements Defects by at least 80%
    • 19. Reduction ofProject Delivery Times by at least 35%
    • 20. Improved User Experience
    • 21. Increased Innovation
    © 2010 OneSpring, LLC. All Rights Reserved.
    © 2011 OneSpring® All Rights Reserved.
  • 22. © 2011 OneSpring® All Rights Reserved.
  • 23. Most SDLC methods define requirements late in the lifecycle. These requirements typically lack any experiential aspect. They represent only functionality, not experience.
    Traditional
    © 2011 OneSpring® All Rights Reserved.
  • 24. Visualization occurs at the beginning of the lifecycle and provides stakeholders the ability to experience and validate requirements from the start.
    The New Approach
    © 2011 OneSpring® All Rights Reserved.
  • 25. Visualization is a framework for how to better innovate and collaborate
    The New Approach
    © 2011 OneSpring® All Rights Reserved.
  • 26. Accelerating the time to understanding and consensus provides a far greater return on investment.
    Visualization
    100%
    50%
    Traditional
    0%
    The Benefit
    © 2011 OneSpring® All Rights Reserved.
  • 27. Visualization
    Visualization Tools
    © 2011 OneSpring® All Rights Reserved.
  • 28. Caveats
    • The Tools aren’t as important as
    • 29. The People
    • 30. The Process
    • 31. The Culture
    © 2011 OneSpring® All Rights Reserved.
  • 32. Tools
    © 2011 OneSpring® All Rights Reserved.
  • 43. Visualization
    Demonstration
    © 2011 OneSpring® All Rights Reserved.
  • 44. Visualization
    Previsualization
    © 2011 OneSpring® All Rights Reserved.
  • 45. The Paradox
    While the software definition process and its artifacts have multiplied over the years, with the rise of methods such as Waterfall, Rational Unified Process, Agile, and more – the surprising fact is that projects are failing at a higher rate than ever before.
    © 2011 OneSpring® All Rights Reserved.
  • 46. Increased Complexity and Costs
    This failure occurred because software applications were rapidly increasing in both size and complexity, outstripping methodologies for development.
    While traditional processes and artifacts were helping, more efficient, effective communication and elicitation was needed to ensure project success. The shortfall left by established methods was significant.
    © 2011 OneSpring® All Rights Reserved.
  • 47. Consumer Demand
    The motion picture industry was experiencing the same dilemma.
    Audiences were more savvy and demanding more from entertainment. With the bar raised, filmmakers also needed to improve their process and tools to more effectively create their art.
    © 2011 OneSpring® All Rights Reserved.
  • 48. Previsualization
    • is a collaborative process that generates preliminary versions of application features, functionality and process flows in a low-resolution format
    • 49. enables the project stakeholders to more effectively communicate a shared vision and understanding of a project through visual exploration
    © 2011 OneSpring® All Rights Reserved.
  • 50. Previsualization
    Enables true cross-functional collaboration
    Provides a preliminary project experience, from concept to use
    Includes application features, functionality, and process flows in a low-resolution format
    Provides stakeholders with a source for a single, shared vision
    Enables rapid visual exploration of project goals and alternate solutions
    © 2011 OneSpring® All Rights Reserved.
  • 51. Previsualization
    For the first time, a director, cast, and crew could envision every shot, sequence, and f/x in a movie before actual production was underway.
    Every aspect of a movie could be planned and analyzed before shooting began—and nuances, special effects, and point of view could be thoroughly explored.
    Director, cast, and crew could completemany takes on a sceneor sequence, all beforefilming started.
    © 2011 OneSpring® All Rights Reserved.
  • 52. © 2011 OneSpring® All Rights Reserved.
  • 53. Previsualization
    Live Website
    Header
    Hotel Name
    Progress Bar
    Reservation Process
    Check-In Date
    Check-Out Date
    Rate Preferences
    Group/Corporate Numbers
    Number of Rooms
    Number of Adults
    Number of Children
    Smoking Preference
    IATA Number
    Hotel Photo
    Personalization Content Slots
    © 2011 OneSpring® All Rights Reserved.
  • 54. Low Resolution
    Live Website
    © 2011 OneSpring® All Rights Reserved.
  • 55. Medium Resolution
    Live Website
    © 2011 OneSpring® All Rights Reserved.
  • 56. High Resolution
    Live Website
    © 2011 OneSpring® All Rights Reserved.
  • 57. Levels of Fidelity
    © 2011 OneSpring® All Rights Reserved.
  • 58. Visualization
    Joint Application Modeling®
    © 2011 OneSpring® All Rights Reserved.
  • 59. JAM Session®
    The session is comprised of these essential “ingredients”…
    +
    +
    +
    Rapid Iterative
    Design
    Small Group Collaboration
    Flow
    Visualization
    © 2011 OneSpring® All Rights Reserved.
  • 60. Collaboration in small groups provides an effective means of problem solving within a structured environment
    Small Group Collaboration
    Complex problems that go beyond the routine require the communication of shared knowledge to create viable solutions/approaches
    © 2011 OneSpring® All Rights Reserved.
  • 61. The roles “match” the work environment and support the task flow…
    Visualization Screen
    Documentation Screen
    Producer
    Facilitates Flow
    Analyst“Left Brain”
    Designer“Right Brain”
    Business
    SME on “What?”
    IT
    SME on “How?”
    © 2011 OneSpring® All Rights Reserved.
  • 62. Insight – observation to gain valuable knowledge and context on the business, customer and technologies
    Clarity - design activities that crystallize the gathered insights to form a model of the experience
    Focus – socialization and measurement of the experience model to provide continuous improvement and validation
    © 2011 OneSpring® All Rights Reserved.
  • 63. Pairing documentation with visualization means that the requirements written by the Visualization Analyst:
    • Reflects the wishes, wants, and needs of the stakeholders
    • 64. Aligns (traces) directly to visualized pages of the future system
    • 65. Coincides with a rich, interactive vision of the future system
    • 66. Eliminates ambiguity of verbally elicited requirements
    Documentation
    © 2010 OneSpring, LLC. All Rights Reserved.
    © 2011 OneSpring® All Rights Reserved.
  • 67. ”Flow also happens when a person’s skills are fully involved in overcoming a challenge that is just about manageable, so it acts as a magnet for learning new skills and increasing challenges. If challenges are too low, one gets back to flow by increasing them. If challenges are too great, one can return to the flow state by learning new skills.”
    Flow
    - MihalyCsikszentmihalvi (July. 1997) Psychology Today
    © 2011 OneSpring® All Rights Reserved.
  • 68. A key aspect to generating the Flow includes both the environment in which the JAM Session takes place and the mental investment by the stakeholders
    Goals are clear
    Feedback is immediate
    Balance between opportunity & capacity
    Concentration deepens
    The present is what matters
    Control is no problem
    Sense of time is altered
    Loss of ego
    Flow
    © 2011 OneSpring® All Rights Reserved.
  • 69. Visualization
    Mock Session
    © 2011 OneSpring® All Rights Reserved.
  • 70. © 2010 OneSpring, LLC. All Rights Reserved.
    © 2011 OneSpring® All Rights Reserved.
  • 71. Session
    • Description of the Project
    • 72. Introduction of Stakeholders
    • 73. Introduction of the Requirements Team
    • 74. Visualization of Project Requirements
    © 2011 OneSpring® All Rights Reserved.
  • 75. What Can You Do?
    • Use visualization as a tool during requirements elicitation
    • 76. Partner with a Business Analyst
    • 77. Don’t worry about the tool, focus on the people & process
    © 2010 OneSpring, LLC. All Rights Reserved.
    © 2011 OneSpring® All Rights Reserved.
  • 78. Visualization
    Now It’s Your Turn!
    © 2011 OneSpring® All Rights Reserved.