Course Introduction and Teamwork

1
Course Introduction and Teamwork

• CS 3911 Spring 2004
• Bob Waters
• Santosh Pande

2
Agenda

• Course Overview
• Syllabus
• Project Ideas
• Deliverables
• Friday, January 9 _at_ 5 PM - Status Report 1
• Project Selection
• Team Formation
• Lecture Teamwork

3
Course Overview

• Class Webpage
• Purpose of Course
• Class Schedule
• Specialization Recommendation
• Important Questions
• Can I come to different section?
• Can I work with person in different section?
• Can I find my own project?
• How many people are in my team?

4
Grading Percent

• Status Reports 15 _at_ .67 10
• Documentation 35
• Project Plan (5)
• Requirements (10)
• Design (15)
• Delivery (5)
• Presentations 15
• Midterm (5)
• Final (10)
• Software (Advisor) 40

5
Available Projects

• Course Web Page
• First Come/First Served on Selection
• Need full team (3-5) to lock-in project
• Amount of work is computed based on number of
  team members
• Each credit hour 50-60 Hours of effort
• 3 hour course 150-180 Hours
• Times number of people

6
What is a Team?

• A small number of people
• with complementary skills
• who are committed to a common purpose,
• performance goals, and
• approach
• for which they hold themselves mutually
  accountable
• Katzenbach Smith
• When two heads together are better than two
  heads individually McConnell

7
Highly Effective Teams

• Shared vision
• Common big picture
• Builds trust
• Commitment to the Team
• Team supercedes individual
• Desire to contribute

• Interdependence among Team
• Rely on strengths
• Everybody contributes
• Effective communication
• Constant clear
• Mutual understanding
• Bad news too

8
Software Project Roles

• Programmer
• Project Manager
• Technical Lead
• Tester
• Technical Writer/ Documentation Coordinator

• Analyst
• Designer
• Marketing
• Customer Delivery
• Installation
• Configuration
• Training

9
Possible Organization

• Team Leader/Project Manager
• Motivate team members
• Plan/Run Meetings
• Prepare weekly status reports
• Allocate tasks/workload
• Maintain project files
• Act as development engineer

10
Possible Organization (2)

• Development Manager
• Lead team in producing development strategy
• Prepare time and size estimates for product
• Lead in development of SRS
• Lead in producing design
• Lead in development of SDS
• Lead in developing test plan for development,
  integration and system testing
• Lead in developing test materials and running
  tests
• Lead in producing user-level documentation
• Act as development engineer

11
Possible Organization (3)

• Planning Manager
• Lead the team in producing project plan
• Lead team in developing schedule for next
  iteration
• Lead team in producing the balanced task plan
• Track teams progress against plan
• Act as development engineer

12
Possible Organization (4)

• Quality/Process Manager
• Lead team in producing and tracking the quality
  plan
• Alert team leader to quality problems
• Lead team in defining and documenting the
  processes and process improvement plan.
• Establish team development standards
• Review proposed changes to baseline
• Act as moderator for reviews
• Act as recorder at team meetings
• Act as development engineer

13
Possible Organization (5)

• Support Manager
• Lead team in defining support needs and obtaining
  tools and facilities
• Chair Configuration Control Board and
  Configuration Control
• Maintain the Configuration Control System
• Maintain system glossary
• Maintain issue and risk tracking system
• Act as reuse advocate
• Act as a development engineer

14
Why Teams Can Fail

• Personnel Problems
• Team leaders unwilling to confront and resolve
  problems
• Cover up ignorance
• I dont know how to explain it just works
• Excessive desire for privacy
• I dont need anyone to review my

• Territorial
• No one else can fix the bugs in my code.
• Grumble about team decisions revisit past
  discussions
• Communication
• What we have here is a failure to communicate

15
Dysfunctional Team Members

• Hitchhikers
• Couch Potatoes

16
Some Advice...

• Class is a lot of work but its worth it
• Faculty Interaction
• Letters of recommendation
• Interview fodder
• Get on a project you have some interest in!!!

• Everyone on your team should not be exactly like
  you
• Remember diversity of project team roles
• Be careful of mixing projects and close friends