WEEK 2Wednesday

Professionalism

COSC 40943 · Senior Design · Week 2

WEEK 2Wednesday

You have a team now

Monday: the repository is your team's memory.

Today: what happens when the problem is not in the repository.

WEEK 2Wednesday

How senior design teams fail

  • Week 4. Somebody notices a teammate has stopped showing up
  • Week 4. Nobody says anything
  • Week 7. The team routes around them. It works
  • Week 12. An integration nobody owns is late
  • Week 15. "X did nothing all semester" appears on four peer evaluations
WEEK 2Wednesday

Eleven weeks too late

In week 15, every option I have is a bad one.

In week 4 the options were good, and cheap:

one uncomfortable ten-minute conversation.

WEEK 2Wednesday

Attack the problem, not the person

Not

"You're lazy."

This

"The endpoint wasn't done by Friday, as we agreed on the 12th."

WEEK 2Wednesday

A team problem is a defect

flowchart LR
    O["<b>Observe</b><br/>Describe the behavior"] --> A["<b>Analyze</b><br/>Explain the impact"]
    A --> I["<b>Investigate</b><br/>Ask for their perspective"]
    I --> F["<b>Fix</b><br/>Agree on a path forward"]
    F -.->|"it recurs"| O
WEEK 2Wednesday

Observe

"You never do anything."

Ask the room

What's wrong with this?

WEEK 2Wednesday

"#41 was assigned to you on Sep 14. It's Oct 2, the branch has no commits, and the demo is on the 9th."

Key point

Three facts and a date. None of it is arguable.

WEEK 2Wednesday

You already have the evidence

  • The board
  • git log
  • The pull request
  • The channel
WEEK 2Wednesday

But not this

Pitfall

Volume is not contribution.

Commit counts measure typing.

Typing is the part the agent does now.

Any productivity metric you can game will be gamed. Your agent can now game them at two hundred lines a minute.

WEEK 2Wednesday

Analyze

Not

"I'm the only one doing anything."

This

"The front end had nothing to integrate against, so Checkpoint 2 missed the demo."

WEEK 2Wednesday

Investigate

  • What's going on with #41?
  • Is something blocking you?
  • Did I misunderstand what you'd taken on?
  • What would help?

Then stop talking.

WEEK 2Wednesday

What you will usually find

Key point

They're stuck, and embarrassed.

WEEK 2Wednesday

Fix

Not

"Communicate more."

This

"Reply in the channel within 24 hours on weekdays."

An owner, an action, and a date. Written down.

WEEK 2Wednesday

Six you will meet this term

  • The Ghost. Three unanswered messages, nine days, an empty branch
  • The Nine-Minute Tax. Always late. Five people wait. That's forty-five minutes of your team, every week
  • "Yeah, I'll take that." Volunteers for everything in the meeting. Delivers none of it
  • Merged, Unread. The agent wrote it, they pasted it, nobody read it, their name is on it
  • The Rubber Stamp. "LGTM" on nine hundred lines, forty seconds after it opened
  • The Hero. Silent for three weeks, then two thousand lines at 11pm before the demo
WEEK 2Wednesday

Now notice what I just did

I labeled six people.

Pitfall

Don't do that.

WEEK 2Wednesday

Same six, said out loud

  • Ghost → "You've missed two meetings and #41 hasn't started. What's going on?"
  • Nine-Minute Tax → "The last four meetings started late waiting for you. Can you make 4:00, or should we move it?"
  • Merged, Unread → "Walk me through why this swallows the exception."
WEEK 2Wednesday

Five rules

  • Talk early. Within 48 hours
  • Use evidence
  • Connect it to project goals
  • Ask before assuming
  • End with an agreement
Key point

Waiting doesn't make the conversation easier. It makes it bigger.

WEEK 2Wednesday

Unread agent output

The agent

The behavior is not "you used AI."

It's submitting code you can't explain.

"Walk me through why this swallows the exception."

WEEK 2Wednesday

"The agent wrote it"

Pitfall

Not available as a defense.

Your name on the pull request is the claim.

"The agent wrote it" has the same standing in code review that "the compiler wrote it" has in court.

WEEK 2Wednesday

When it's aimed at you

  • Ask what they observed
  • Say what happened, undecorated
  • Agree the action
WEEK 2Wednesday

If it doesn't work

  • Your team. Almost everything ends here
  • Your TA. Bring the evidence and the agreement that wasn't kept
  • Me. Improvement plan, then professionalism review
WEEK 2Wednesday

Except these

Pitfall

Academic integrity · harassment · discrimination · threats · anything unsafe

Come to me immediately.

No protocol. No 48 hours. Don't raise it with the person first.

WEEK 2Wednesday

Pair up. Neither of you is you

Sam took a use case three weeks ago. Two missed meetings. Nine days, no answer in the channel.

Ask the room

Decide now: who opens, and who is Sam.

WEEK 2Wednesday

Round one: open with the label

Pitfall

"You're being a ghost."

Say it exactly like that.

The only conversation in this course that is supposed to fail.

WEEK 2Wednesday

Round two: Sam has a reason

Sam, pick one. Do not say which.

  • Two jobs since August
  • Stuck, and too embarrassed to say so
  • Something at home
  • Thought somebody else had picked it up
Ask the room

Open again, properly. Find out which one.

WEEK 2Wednesday

How many of you guessed right?

Key point

You do not get to skip Investigate. You will guess wrong, in front of somebody who knows you guessed.

WEEK 2Wednesday

Friday

  • Your team's first hour together
  • Fix the weekly meeting time you'll defend all term
  • Sign the contract. Clause 7 is this lecture, in your words
  • Your TA verifies Checkpoint 0 at your table
Key point

Write clause 7 while nobody is angry. It's the only time anybody writes a fair one.

WEEK 2Wednesday
Key point

Observe. Analyze. Investigate. Fix.

Attack the problem, not the person.

Talk within 48 hours.

Professionalism

space PgDn
Next step or slide
PgUp
Back
S
Skip to the next slide
O
Overview of all slides
N
Speaker notes
B
Black the screen
Ctrl+P
Print / PDF handout, one slide per page