Required Meetings
| What | Who | What | When/where |
|---|---|---|---|
| Class | Everyone | See next section | See informaton on the right |
| Coaching | Team and me | weekly 30-minute retrospective reviews | video conference, schedule TBD |
| Client | Team and clients | weekly hour-long iteration planning |
winter, face-to-face in Ford ITW, see Canvas spring, determined by clent and team |
| Client | Team and clients | weekly 20-minute mid-week check-in | video conference, determined by clent and teams |
| Team | Team members | 6 to 8 hours of coding swarms per week | two to four swarming sessions, scheduled to enable all team members to attend |
Class Format
Lectures are limited and rare. Most classes have a topic that begins with some short reading, followed by discussion. Many classes will have an in-class team activity, such as practicing writing user stories, assigning story points, configuring a project for automated testing, and so on.
Projects
This course has two 5-week projects:
- The Team Project
- You design it, implement it, test it on real users, repeatedly, then demo it to the class, and show it when you first meet your clients. You learn to become an effective efficient gelled development team.
- The Client Project
- You are contractors, working to help the client turn their product idea into reality. They are responsible for the vision, priorities, testing, and final demos. You are responsible for coding, keeping them accurately informed of progress and problems, and helping them create the best possible product in the time available.