1. 01/29 Introduction to Course: Boot Up
2. 01/31 Goal-oriented Design, Production/Processes
3. 02/05 Presentations, Team Identity Project Overview [Due: Individual Identity Presentations]
4. 02/07 Squirrel Eiserloh Lecture: Meet in 405 (Wabash)
5. 02/12 Project Planning & Team Dynamics
6. 02/14 Team Identity Project Presentation, Client Communications [Due: Completed Team Identity Project]
7. 02/19 Introduction to the Big Project
8. 02/21 Target Audience Assessment [Due: Draft game plan]
9. 02/26 Prototyping and User Testing [Due: Final game plan]
10. 02/28 Review Prototypes [Due: client sign-off on game plan]
11. 03/04 User Testing [Due: Paper prototype]
12. 03/06 Production Review [Due: Progress update on user testing]
13. 03/11 Production Review [Due: Functional prototype]
14. 03/13 Production Review [Due: User testing report]
15. 03/18 Version 1 Presentation [Due: Project, client sign-off, and documentation]
16. 03/20 Version 1 Postmortem [Due: Agendas for 9 meetings (9-10,12-14)]
17. 04/01 Reboot for version 2
18. 04/03 Team Agenda
19. 04/08 Team Agenda
20. 04/10 Team Agenda
21. 04/15 Version 2 Presentation [Due: Project, client sign-off, and documentation]
22. 04/17 Version 2 Postmortem
23. 04/22 Team Agenda
24. 04/24 Team Agenda
25. 04/29 Team Agenda
26. 05/01 Team Agenda
27. 05/06 Team Agenda
28. 05/08 Team Agenda
29. 05/13 Version 3 Presentation [Due: Project, client sign-off, and documentation]
30. 05/15 Version 3 Postmortem [Due: Assessment papers]

Topics

• Introductions (instructor and students)
• Overview of course
• Syllabus walkthrough

In-class Assignments

Make something great (with limited resources and a limited timeframe).

Elevator Pitch (Due next class)

Pretend you just walked onto an elevator and you see the person that you would most like to work with (or for). You have two minutes to introduce yourself and convince them that you are the right person for the job.

1. You know a specific job is open. What is that job? Make sure you are clear on what exactly you want to do. Pretend they have several jobs open – make sure they realize the one you want.
2. You have never met this person before. You need to introduce yourself and communicate in a very short time frame how you are perfect for the position.
3. Tips: remember to say your name, hand over a card when done (this can be a pretend card you don’t need to make one)

A few benefits of this exercise:

1. Consider this a warm-up to the larger identity presentation you will be giving on 02/05.
2. Gives your team a quick introduction to what you are passionate about and what you want to be doing when you leave Columbia.
3. A fun way to connect to your classmates. Some of the past pitches have been really creative.

Homework

These assignments are due before the next class begins.

1. Prepare your "elevator pitch" for next class.
2. Purchase the required text (Dynamics of Software Development (Best Practices) by Jim McCarthy and Michele McCarthy, Microsoft Press, 2006; ISBN: 0735623198)
3. Watch the video on the CD that came with your text (DoSD): "23 1/2 Rules of Thumb" (If you have a used text without a cd you can watch these on the McCarthy site, but the resolution is much better on the cd.)
4. Start working on your Individual Identity Presentation (due 02/05)

Two Major Areas of Learning and Practice

Teamwork & Professional Product for External Client

Core Protocols

If your team would like to get to a state of shared vision in the shortest amount of time possible, and with the greatest possible effect, adoption of The Core Protocols is likely the best bet available. Of course, your adoption of the Protocols will be greatly simplified - and both your adoption and ongoing operating costs reduced - by an understanding of the Patterns and Antipatterns surrounding them. But you will never experience the true beauty of The Core unless you personally adopt Core protocols. Imagine that you have an architect’s design in hand for a new building. You can imagine the final building more fully than you could without such a document; but you will not enjoy the protection and features of the building until you inhabit it. Then, you will know the architect’s skill, or suffer its absence. The Core’s design intent is revealed in its adoption rather than its postulation or analysis. mccarthyshow.com

There are four steps the McCarthys recommend taking to get your team booted up and functioning as quickly and effectively as possible.

1. Checking In - management of personal presence
2. Deciding - practicing unanimous decision-making
3. Aligning - disclosing motive and setting goals
4. Envisioning - creating shared vision

Check In

The CheckIn protocol provides two major components for establishing and developing high-performance collaboration: an enlistment procedure and an interpersonal connectivity process. The former (re)affirms each individual’s commitment to a body of proven efficiency-enhancing behaviors. The latter provides individuals with an opportunity to efficiently reveal their personal states.

Perfection Game

(See page 183 of DoSD)

Elevator Pitches

Each person will pitch and, using the Perfection Game, the rest of the class will help them improve it.

Goal-oriented Design

Production/Processes

Teamwork Games

1. Anyone who...
2. Bunny Bunny

Homework

These assignments are due before the next class begins.

1. Read in DoSD The Core Protocols V3.0 pages 175-186, and pages 3-82 (The Introduction and "Opening Moves" sections)
2. Complete your Individual Identity Presentation (due 02/05)

[Due: Individual Identity Presentations]

Check In

Remaining Elevator Pitch

Presentations

Overview: Team Identity Project

Homework

These assignments are due before the next class begins.

1. Read in DoSD pages 83-104
2. Begin work on Team Identity Presentation (due 02/14)

Note: 02/12 will be approximately half of class devoted to client communications, and approximately half available to your team to meet about the project. DO NOT expect to be able to complete the project within class time. This assignment requires you to connect with your classmates outside of scheduled class time.

Guest Lecture: 5:30 pm

Squirrel Eiserloh, Technical Director, Ritual Entertainment
623 South Wabash Avenue, Room 405

Squirrel is currently at Ritual Entertainment where he serves as department chair, programming lead, and advocate for agile development methodologies and rapid iteration. Squirrel subscribes to the "Zen" philosophy of programming and game development, putting emphasis not only on quality of code but on craftsmanship, flow, engineering, teamwork, and communication. Read more...

Homework

These assignments are due before the next class begins.

1. 02/07 Read in DoSD pages 105-136

Check In

Dynamics of Software Development

Protocol: Ask for Help

Protocol: Decider

Protocol: Investigate

Protocol: Click

1-1 Meetings

Starting next week each team member should meet individually with your instructor at least once a week. These meetings will be short - less than 15 minutes each.

Homework

These assignments are due before the next class begins.

1. 02/12 Read in DoSD pages 136-174 (you should have the entire text finished at this point)
2. Complete the Team Identity Project (Documentation for this project is not required but will add points to the grade)

Check In

Presentation

Post Mortem

Client Communications

Homework

These assignments are due before the next class begins.

1. Prepare for Tuesday's meeting
2. Research documentation