- Three pitches: 30 minutes
- About this course: 15 minutes
- Team work: 30 minutes
- Only 3 minutes per team!
- 30 seconds: Three ideas
- 2 minutes: Market feedback
- "Have you seen [existing app that does idea]?"
- "What about [big problem for idea]?"
- 30 seconds: Poll
- "Yes" -- you would be interested in trying out the product
- You can vote yes for more than one idea
About this course
There are three deliverables for this course.
- Your team project
- Your client project
- You and your team
The third is most important in the long run.
How This Course Works
- Build / Reflect / Improve / Repeat
- Learn by doing, not listening to lectures
- Class is for discussion, setting goals, doing work
- Your key resources:
- I need to know if you can
- avoid common project and team pitfalls
- apply agile ideas to each project appropriately
- improve constantly through retrospection
- I look for clues everywhere
- Tasks not finished, or done incorrectly
- Team issues missed or minimized
- Client "surprises"
- Odd data points, like very few or very many github commits
- 80 points for two team project × your CATME contribution factor
- up to 20 points for individual retrospectives
- See the course page for details
Teams: Some Assembly Required
- "How well you work with your team will make or
break your experience in this course. If you have a good team,
this will be one of the most awesome EECS courses you'll take.
If not, it'll be just another big project
that you need to get done."
- Myths about teams:
- Set up a
swarming schedule for this week
- Pick a communication pipeline: Email? FB Messenger,
- Decide what your app is
- Start working on