Previous Lecture Lecture 10 Next Lecture

Lecture 10, Wed 01/27

Wed Lecture: Teamwork, part 1, jpa05 continuation, Exploration of legacy app

Overview

Last Night recap

Last night in discussion section was oriented around this assignment: https://ucsb-cs156.github.io/w21/lab/jpa05/

Teams worked in breakout rooms on getting started on it, and getting as far as possible on it.

A few cleanup items:

Announcements by project:

Questions about jpa04/jpa05?

Teamwork is Challenging

If your team experience so far has been “less than ideal”:

We are going to be talking a lot about teamwork in this course.

And having already had some “less than ideal” experiences may actually be a good thing.

Most real world software development is a team effort

Most software is too large and too complex to be produced or maintained by a single individual.

Teamwork is essential to success.

We’ll talk about about in this course.

What is a Team?

From an article by Jim Sisson, emphasis and formatting added:

“What is the difference between a group of employees and a team?”

“Members of the team are mutually committed to the goals and to each other.”

“This mutual commitment also creates joint accountability which creates a strong bond and a strong motivation to perform.”

Teams don’t just happen: The Tuckman Stages

A Psychologist named Bruce Tuckman studied what happens with both successful and unsuccessful teams. His data revealed a set of common stages that teams go through, which are now known as the “Tuckman Stages”:

  1. Forming
  2. Norming
  3. Storming
  4. Performing

Later, a fifth stage was added: (5) Adjourning, to describe what happens after a team is finished with its work and no longer working together (i.e. what will happen to these ten teams in Mid-March when this course is over.)

More information is available here: https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_development

Let’s take 7 minutes to read the first four stages, and then 8 minutes to complete the exercise linked to below (two multiple choice questions, one short answer.)

What stage is your team at?

Let’s take a moment to read about these, and then do some writing about that.

This exercise counts towards your course participation grade.

In your breakout rooms

In your team repo

Recall that each of you has a team repo for notes:

5pm 6pm 7pm
team-5pm-1-NOTES team-6pm-1-NOTES team-7pm-1-NOTES
team-5pm-2-NOTES team-6pm-2-NOTES team-7pm-2-NOTES
team-5pm-3-NOTES team-6pm-3-NOTES team-7pm-3-NOTES
team-5pm-4-NOTES team-6pm-4-NOTES team-7pm-4-NOTES

In this repo, please create a new directory 01.27 and a README.md in that directory, as shown in this image:

create 01.27/README.md

In the README.md file, put a link to your jpa05 deployment. No special syntax is needed in GitHub Flavored Markdown to get a URL to be a link:

Our jpa05 deployment is here: https://cs156-w21-team-5pm-1-courses.herokuapp.com/

Under the 01.27 directory, each of the team members should create a file with their first name followed by .md, e.g. Amy.md, Brian.md, Chris.md, etc.

Now:

Here is a guide to GitHub Flavored Markdown syntax: https://guides.github.com/features/mastering-markdown/

Do this individually first. Then have a group discussion about what you found, and assemble your suggestions together in one document, in the 01.27/README.md file.