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.

2. www.designthinkingdigest.com

3. “The future is already here—it’s just
unevenly distributed.”
William Gibson

4. Making hard things easier

5. Picking the right approaches

6. Understanding how we’re different

7. Learn how to not ignore dysfunction

8. Push our teams in the right direction

9. What to do when
we get stuck

11. Design is more than this
Poor design can shortchange outcomes

13. Design workflow has a history
Source: Charles and Ray Eames

14. And many processes we're familiar with
Source: Gregg Berryman

15. But are based on different mediums
Source: Gregg Berryman

16. We've adapted these processes
Source: Gregg Berryman

17. To serve us better
Source: Gregg Berryman

18. And tried to make them agile and simple
Source: Gregg Berryman

21. Source: Chris Bernard

22. Source: Chris Bernard

23. Source: Institute of Design

24. But design planning starts even sooner
Source: Hasso Plattner Institute of Design

25. And the way we're working is changing
Source: International Design Magazine

26. Old processes are well understood
Source: Chris Bernard

27. Perhaps universally understood

28. Source: Jesse James Garrett

29. Trouble is here

31. We can do better

33. “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”

34. Design Team
Development Team
One to Four Weeks

40. Choose process during
team project creation

42. 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

45. Yes No

46. Remaining Work Schedule
Project Velocity Item Reactivation
Scope Creep Requirements Tracking
Item Burndown
Quality Indicator

47. “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

48. Your feedback is important!

49. © 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.