CSE/ISE 308Software Engineering

Team

Organization

READY?

FIRST!

ALL

PAST

PROGRAMMING

SINS

ARE

FORGIVEN

What is the point of this class?

TO MAKE

SOMETHING GREAT

Teams

• Let's start by making teams of 4

• Rules to start:– teams must always sit together

– teammates must always be respectful to one another

– teammates must always answer each others' emails

– teammate should learn and know each others' schedules• to time teamwork, not to time robberies

Here are your Teams

Team Rules• 4 Roles– Lead Programmer– Project Manager– Lead Designer– Data Designer

• Other stuff– Mutiny Clause

– The Apprentice Clause

– Software Engineer to be named later Clause

Attendance• Taken each meeting (lecture)

• There are 28 meetings (lectures) this semester

• Students are allowed 3 excused absences

• Each absence after 3 will lower that student’s grade by ½ letter grade (i.e. B+ to B)

What’s the project?

What’s the deal?

Project Managers run the meeting• With help of lead programmer

• What does “run the meeting” mean?– take attendance

– set the agenda – list of topics to discuss

– lead the discussion

– bring up topics one at a time

– assign action items (tasks)

– write meeting minutes

– follow up on action items enter and update all meeting info via project management tool

• This includes today

What’s an action item?• An assigned task

• First task, assign team roles

• All tasks should have an owner and completion date

• Tasks with distant horizons should be periodically reviewed– Is it on track?– Does the owner need help?– Is the owner overloaded?– Is the owner alive?

Meeting #1 (today)• Agenda– take attendance– everyone introduce themselves one at a time• name, email address, place of residence, 300-level

course experience, favorite musical artist

– team programming– the meeting/presentation laptop issue– Project Management Software– Source Control– Work schedule

Upcoming Topics

• Front-End Technologies

• The Google App Engine

• The Google Datastore

• The Google Web Toolkit