layout: true name: titleslide class: center, middle
.footnote[ ###
@JeffHoover
@schmonz
####
#aab17
[schmonz.com/talk
/2017-aab](https://schmonz.com/talk/2017-aab/) ] --- layout: true name: footnotelinks .left-column[
] .footnote[ ###
@JeffHoover
@schmonz
####
#aab17
[schmonz.com/talk
/2017-aab](https://schmonz.com/talk/2017-aab/) ] --- template: titleslide ## The Best Team Anywhere:
Distributed Agile Tradeoffs and Techniques
## Amitai Schleier & Jeff Hoover ### 2017/05/05 ??? 1. Press 'C' to clone and move it to projector 2. Press 'P' to show these here presenter notes ### 100 minutes Colocated Agile is the easiest way to do a hard thing. Distributed Agile is harder. But it's 2017! It's strategically valuable to be able to work effectively with people no matter where they are. Bring your laptops and prepare to experience the basic mechanics, pitfalls, and techniques of distributed teamwork, including "remote" pairing. --- layout: false template: footnotelinks .right-column[ # Our Goals For This Session _[Assumption: you value pairing, or are open to it]_ 1. **Try** a remote pairing tool (maybe one you've never used) 2. **Share** knowledge in the room about remote-pairing traps and tricks 3. **Connect** each other to more sources of knowledge ] --- .right-column[ # Required (1/3): Lotsa Laptops! - We have some headsets (you can keep them!) - Otherwise, built-in audio ] --- .right-column[ # Get These Slides ##
schmonz.com/talk
/2017-aab
] --- .right-column[ # Required (2/3): Code of Conduct ## [agileandbeyond.com/2017
/codeofconduct.html](http://agileandbeyond.com/2017/codeofconduct.html) ] --- .right-column[ # Why have a CoC? ## [agileandbeyond.com/2017
/codeofconduct.html](http://agileandbeyond.com/2017/codeofconduct.html) **Not** to prevent behavior we don't like -- nothing can -- but To remind ourselves, when we see some, how _we'll_ want to behave. ] -- .right-column[ ### Why do we test-drive code? It's a cognitive aid: Declaring our intentions helps us live up to them. ] --- .right-column[ # Specification By Example ## [agileandbeyond.com/2017
/codeofconduct.html](http://agileandbeyond.com/2017/codeofconduct.html) ### Key features 1. "Harassment includes..." 2. "We expect participants to..." 3. "If you are being harassed, notice that..." ### Homework Build shared understanding: Pair in the [Open Space](http://sched.co/AUTj) (Conf Room C) on a few Given/When/Then examples. (Extra credit: Automate them.) ] --- .right-column[ # "Individuals and interactions..." - When we're not next to each other, how can we have interactions? - We need help from tools - Tools have
affordances
- Affordances influence behavior > "That which does _for_ you, also does _to_ you." > --Gene Hughson, [The Iron Law of Tools](https://genehughson.wordpress.com/2012/11/19/the-iron-law-of-tools/) ] --- .right-column[ # What's different when pairing is remote? We have to work harder to... - _Start_ talking (think of all the ways this costs!) - Feel warm feelings for each other - Spread team information - Verbalize even more (e.g., our emotions) - Work smaller (get things done, be seen, merge less painfully) - Regularly tune ourselves and our tools - Learn a new toolset ] --- .right-column[ # What can get in the way? - WiFi is bad - Time zones don't match - Everyone else is in a place together - Hard to hear - Relying on built-in audio instead of headset - Sharing app might accidentally be muted. System audio might accidentally be muted. Or both. - Hard to be heard - Hard to take a little turn - Hard to stay focused - Hard to take a break - Cultural differences (language, idiom, slang) - Understand meaning but not be in alignment ] --- .right-column[ # Required (3/3): Your Questions About Remote Pairing ] --- .right-column[ # Required (4/3): Move Your Feet ## Two options: ### 1. Not your thing? Cool, find something else or ### 2. Sound good? Cool, find your new pair partner. Then sit at a different table. ] --- .right-column[ # Activity: Try one of these - [Screenhero](https://screenhero.com) - [AtomPair](https://atom.io/packages/atom-pair) - [Zoom](https://zoom.us) - [join.me](https://www.join.me/) - Google Hangouts - TeamViewer - tmate.io - WebEx - Skype See also (and edit!) the list of tools at [Shape My Work](http://shapemywork.com/pair). ] --- .right-column[ # Retro: How'd it go? - Zoom required account signup, was very easy, then worked well - couldn't share IDE in full-screen; shrink mode, share, then re-maximize - see screen _and_ person simultaneously - group chat with video works really well - [Google Hangouts Meet](https://meet.google.com/) for audio and video - has presentation mode - Started with Google Hangouts, tried to invite, weren't buddies, couldn't - Then got Screenhero, but one participant had a tablet and couldn't do that - Screenhero required invite, was easy, had to invite each other - one partner can IM the other, the other can't reply - Audio for Google Meet was good; for Zoom, both good and not good - got feedback from everyone being in the same room - Network issues to be expected, but realistic-ish ] --- .right-column[ # Activity: "Devious Remote Partner" 1. First person writes a falsifiable statement _in a document_ - Ex: "gophers gestate for 23 months" - be devious - If stuck for ideas, some examples: - George Patton lived to be 101 years old - Birds use magnetism to navigate - Beer was invented in a monastery 2. Both discuss whether the statement is true - Voice/IM/Text - Whatever you can get to work 3. 2nd person uses search engine to find a source of evidence - Enter quote into document - Enter URL into shared document 4. Regroup and discuss ] --- .right-column[ # Retro: How'd it go? - Audio latency high enough to bother; pair without headphones couldn't tell; communicated via shared text editor - Hangouts Meet + shared Google Doc worked well - A new pair with Screenhero had a very smooth time - An existing pair with Zoom also had a smooth time - Company laptop had unprompted software upgrade; couldn't do exercise - Three people was hard, technical issues - Microphone problem, tried to change settings and couldn't fix - Tablet couldn't initiate - Important to have a reliable backchannel when main channel falls down - A permanent "room" is helpful ] --- .right-column[ # Q1: Is text-only bandwidth helpful? ] --- .right-column[ # Q2: How do you treat everyone equally when not all are colocated? ] --- .right-column[ # Q3: What are some good screensharing apps? ] --- .right-column[ # Q4: How do I identify which of several people are talking? ] --- .right-column[ # Q5: What are some ways for business and tech to pair remotely? ] --- .right-column[ # Q6: How do you get team cohesion in multiple locations? ] --- .right-column[ # Q7: How do we resolve differences of opinion? ] --- .right-column[ # Q8: How do we grok depth of understanding and agreement? ] --- .right-column[ # Retro (1/2): What You'll Try - Discover what works, standardize, and document how to get started - "Norming" conversation with a new distributed team - Communicating silently in a shared text editor - Evaluate Zoom ] --- .right-column[ # Retro (2/2): What We Can Try - More free stuff that people actually want - Schedule a second conference room across the hall - Go longer, try multiple tools; maybe a full-day exercise - More prior info about bringing headsets, installing software, prep up front - Describe it differently so more non-devs will stick around - Offer more value directly to managers so they stick around - Have a presenter be remote! ] --- .right-column[ # More Resources - [Shape My Work](http://shapemywork.com), a new wiki about distributed Agile - [Remote Pairing page](http://shapemywork.com/pair) - [ScatterSpoke](https://www.scatterspoke.com/) for distributed agreement - Web: [Mark Kilby's Remotely Agile](http://remotelyagile.info) - Podcast: [Collaboration Superpowers](http://www.collaborationsuperpowers.com) - Free e-Book: [The Ultimate Guide to Remote Work](http://amzn.to/2q7hG28) - e-Book: [Remote Office Required](http://amzn.to/2phqxKF) - e-Book: [The Year Without Pants](http://amzn.to/2qIzgGT) - Amitai's experience: [Working From Everywhere](https://schmonz.com/2013/10/17/working-from-everywhere/) ] --- .right-column[ # Agile in 3 Minutes ##
agilein3minut.es
> "Before Agile in 3 Minutes, I couldn't get my team to have a > conversation about important topics. Now I have to timebox it."
-
8: Care
-
9: Pair
-
32: Mob
] --- .right-column[ # Agile in 3 Minutes: The Book ## [leanpub.com/agilein3minutes
/c/aab17](https://leanpub.com/agilein3minutes/c/aab17) The simplest _essays_ that could possibly work. $4 today! ] --- .right-column[ # Let's Keep Going ##
schmonz.com/coach
Does your company deliver valuable software? Maybe Amitai can help. Consulting, coaching, training. ] --- template: titleslide ## The Best Team Anywhere:
Distributed Agile Tradeoffs and Techniques
## Amitai Schleier & Jeff Hoover ### [schmonz.com](https://schmonz.com) & [blog.jhoover.com](http://blog.jhoover.com)