December 5: Final project deliverable due
December 1: Client Demos, Team Advice in Ford ITW. Demo Times
November 30: In-class demos, client advice writing task.
November 18: Iteration planning with clients! Saturday 11:00am Ford ITW
November 10: Iteration planning with clients! Friday 10:30am Chambers Hall (Foster St), lower level
November 9: Ionic testing activity
November 4: Iteration planning with clients! Saturday 11:00am Ford ITW
November 2: Purple / Yellow team demos. Client project demos.
October 27: Meet your clients! 10:30am Ford ITW
October 26: New Team Meet and Prep
October 26: Final Team Project Demo: In-class app demos and wrap up discussion.
October 17: Google visit
October 9: Start of weekly coaching meetings and Retrospective reports
September 26: First demo!
September 21: Hybrid setup report and four-panel storyboard.
September 19 Day One -- What each team needs to prepare for the first day of class!


TTh 11am - 12:20am


Tech M164


Chris Riesbeck


Demo #1 Task

You've built your first app slice. You've tested it on users. Time to show it off with a demo!

You have at most 3 minutes to demo. To make the most of it,

A good demo is not a feature tour. Features are the worst possible way to demo an app. They're a terrible way to design an app. Microsoft Word has thousands of features. Most of them are never used.

The right way to demo is with a story. A story has realistic people in a realistic situation. There's a problem. Your app comes to the rescue and the problem is solved. That's what a demo needs to tell, and all it needs to tell. Less is more.

For more on stories and apps, see Storytelling by Design by Kim Goodwin.


Update your Product Box in the shared Google Team Projects Demo #1 slide set, as necessary.

Have at least one designated note taker to write down notes on things that didn't work, and comments from the class.

Questions? Ask your team mates. Still unclear? Post questions to Piazza.