Improving UX through Application Lifecycle Management


Published on

Learn how you can leverage Microsoft Expression and Microsoft Visual Studio Team System to improve your overall application lifecycle, decrease your time to market, and ultimately raise the quality of your applications.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Improving UX through Application Lifecycle Management

  1. 1.
  2. 2. “The future is already here—it’s just unevenly distributed.” William Gibson
  3. 3. Making hard things easier
  4. 4. Picking the right approaches
  5. 5. Understanding how we’re different
  6. 6. Learn how to not ignore dysfunction
  7. 7. Push our teams in the right direction
  8. 8. What to do when we get stuck
  9. 9. Design is more than this Poor design can shortchange outcomes
  10. 10. Design workflow has a history Source: Charles and Ray Eames
  11. 11. And many processes we're familiar with Source: Gregg Berryman
  12. 12. But are based on different mediums Source: Gregg Berryman
  13. 13. We've adapted these processes Source: Gregg Berryman
  14. 14. To serve us better Source: Gregg Berryman
  15. 15. And tried to make them agile and simple Source: Gregg Berryman
  16. 16. Source: Chris Bernard
  17. 17. Source: Chris Bernard
  18. 18. Source: Institute of Design
  19. 19. But design planning starts even sooner Source: Hasso Plattner Institute of Design
  20. 20. And the way we're working is changing Source: International Design Magazine
  21. 21. Old processes are well understood Source: Chris Bernard
  22. 22. Perhaps universally understood
  23. 23. Source: Jesse James Garrett
  24. 24. Trouble is here
  25. 25. We can do better
  26. 26. “We don’t have good visibility into project status” “Our (distributed) teams are not communicating effectively” “Requirements are not sufficiently defined or tracked” “We need lightweight, agile design processes” “Prototyping is not rapid nor integrated”
  27. 27. Design Team Development Team One to Four Weeks
  28. 28. Choose process during team project creation
  29. 29. Quality Work • Bug • Task • Exit criteria • Backlog Item • Usability Issue • Wireframe Task • Release Note • IA Task Planning Project management • • Scenario Issue • • Use Case Change request • • Design Requirement Risk • • Content Requirement Design Risk • Business Requirement • Interaction Design Idea Black = MSF work item type White = new work item type
  30. 30. Yes No
  31. 31. Remaining Work Schedule Project Velocity Item Reactivation Scope Creep Requirements Tracking Item Burndown Quality Indicator
  32. 32. “Rosario” • Instant Messenger • Improved Agile Process • Additional Roles • “Dashboarding” • What if analysis 2005 2008 • Simple Report Creation • Nested Work Items 2008 SP1 2010 2008 2007 2006 2005
  33. 33. Your feedback is important!
  34. 34. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.