Team Dynamics for phun and pr0fit

by Kacper Wysocki

kwy@redpill-linpro.com k@delta9.pl

img/engine.jpg

short-engagement consultant

  • am a systems person

  • linux

  • security

  • performance

  • trouble shooter

Varnish Security Firewall

https://github.com/comotion/VSF

PRADS

Passive Realtime Asset Detection System https://github.com/gamelinux/prads

100+ engagements

people are teh hardest problem

img/notbutter.jpg

'_'

img/bike.jpg

teamwork?

purpose

of team is to strengthen each other thru dynamics of work/play!

talk and act each other

  • into

  • outof

  • and thru

  • things

smarter and faster

than an awesome lone cowboy

img/advertising.gif

a note on focus

focus is important. preserve at all costs!

img/energy.jpg

most effective team?

touches base

  • whatrudoin

  • wherugoin

  • whachaneed

  • opportunities

  • comms

whatrudoin

if you can't explain it in 1 minute,
I don't wanna know

write me a letter

wherugoin

light at the end of the tunnel

whachaneed

need som hlep?

opportunities

any info that cant be acted on by info src

chat

to avoid interruption don't ping

source

peerless communication

img/truck.jpg

Team Structure

Roles

lead, secondary, manager, sales

lead

  • responsible for solution

  • tech client contact

  • design

  • strategy

sekundær

  • sounding wall

  • implementation

  • research

  • tactics

manager

  • protect

  • focus

  • motivate

  • bless teams

  • assign mission

sales

  • drive client relations

  • client followup

  • negotiations

  • contract

  • renewals

how to take blame without shame

the post-mortem

root cause analysis w all stakeholders

  • essential!

root cause analysis

should document fails

img/destruction.jpg

processing fault

team accepts failure when individual accepts failure and blame without shame

routines for badness

team must have routine for fuckups without shame game.

tabbekake

  • I fucked up, so I got cake for everyone

symbolic act of accepting blame

tabbekake.

img/sunspots.gif

book of five rings

you must do sufficient research

img/pat.jpg

failure modes

nearly infinite

how can a project fail? Let's enumerate.

poor prep

didn't have the right info

mismatch

people and competence not matched to task at hand

bad terms

terms of contract force asymmetry

doomed to failure: locked into bad

bad spec

overly complex specification

or

inflexible design

followup

rythm of engagement broken, communication is loosing momentum

handover

dropped ball?

overbooked

critical team members have too much on their plate

lone gunman

taking all the heat; not what he signed up for

fuckup

people make mistakes,

but it's team fail when team member has not enough support

clusterfuck

wrong on so many levels don't know where to begin (read: management fail)

the old goats mission

you know what they do with the goat, don't you?

we just asked you here so you could take the blame

weak kungfu

pm skillz req'd

timewaster

2nd party is leading us on, on our dime!

vengance meeting

round 2 of some

historical hurt

means they want payback

Thanks for all the phish!

https://github.com/comotion

6BD0 3F9C 5F77 AD24 F60A 86EC FD82 7E34 674A 506F Kacper Wysocki <kwy@redpill-linpro.com>

img/invaders.gif