Part 1
July 17, 2013
David Hussman
Agility Coach, Instructor, Owner, DevJam
Andy Powell
Product Evangelist, VersionOne
Collaboration that Scales
Connecting Teams and Programs via
Essential Conversations
The CDS (Chief Discussion Starter)
https://sites.google.com/site/twincitiespracticalagility/
Scaled Collaboration Varies
Collaboration Starts with Conversation
Within
(a team)
Across
(teams)
Outside
(teams)
Project
Program
Portfolio
Product Conversations
Daily Conversations
Learning Conversations
Reflective Conversations
Cross Product
Cross Team Conversations
Dependency Conversations
Ideation Conversations
Investment Conversations
Leadership Conversations
1
2
3
Within
( a team or a project )
Growing Collaboration in Context
Developing Products
Iterative Learning
Dealing w/ Adversity
Maintaining Health
Designing Agility
Discovering / Delivering
Continuous Delivery
Reflective Correction
Evolving the Process
Getting Productive
Staying Productive
Getting Ready
Product Thinking
Developing Products
Iterative Learning
Dealing w/ Adversity
Maintaining Health
Designing Agility
Discovering / Delivering
Continuous Delivery
Reflective Correction
Evolving the Process
Getting Productive
Staying Productive
Getting Ready
Essential Product Discussions
- Story Telling -
- Product Context -
- Distributed Ideation -
What are your story telling tools?
personas - story maps - sketches
How does context matter?
System Context
Product Context
How do you do distributed discovery?
“If Google Docs and Post It Notes had a child, it would be CardBoard”
www.cardboardit.com
Pragmatic Planning and Standing
Developing Products
Iterative Learning
Dealing w/ Adversity
Maintaining Health
Designing Agility
Discovering / Delivering
Continuous Delivery
Reflective Correction
Evolving the Process
Getting Productive
Staying Productive
Getting Ready
How much planning is enough?
Where is the value?
What is the cost?
Are standups feeding the team?
Are you collaborating or just reporting?
Are you discovering or solving?
Dude’s Law: Value = Why / How
V=
W
HI =
V
R
How much process is enough?
How much planning is enough?
What is the least amount of process that adds the most
real value? – Consider throwing out “The Book”
Why are they standing there?
Talk to the wall
Discover but don’t solve
Ask 5 Silent Why’s
Starting distributed connections
Rotate who goes first
Press ‘3’ Key to speak
Use name to humanize people
Pair people across locations
Raj
Maria
Ivan
Susan
Use humor to focus on outcomes
How do you talk about value delivered?
Measuring, Learning and Adapting
Developing Products
Iterative Learning
Dealing w/ Adversity
Maintaining Health
Designing Agility
Discovering / Delivering
Continuous Delivery
Reflective Correction
Evolving the Process
Getting Productive
Staying Productive
Getting Ready
How often are we watching real users?
What is the best product direction?
What is the next best investment?
What can we learn from the past?
How can we apply it to the future?
How are you learning about users?
What’s your next best investment?
Are people reflecting and learning?
How do can you spark reflective dialog?
Across
( many teams or a program )
Don’t mistake crowds for collaboration
Cross cutting conversations require effort
Checklist Thinking (and leaning)
Cross cutting collaboration at scale
Cross Cutting Collaboration
People
Products
Technology
Cross Cutting ( teams and people )
Cross Cutting ( products )
Cross Cutting ( complexity )
How adaptive is your eco-system?
Outside
( teams and across portfolios )
Who’s on the outside and why?
Connecting to the Outsiders
Ideators
Investors
Leaders
Ideators
What is the next best investment?
Investors
Leaders
Are your skeptics on the outside?
Avoid Epistemic Arrogance
“The difference between what you know
and what you think you know”
So what now?
( putting these questions to work )
Reframing Our Learning
Building for the future Building to adapt
Talking about code Talking about tests
Late integration Continuous Deployment
What’s required? What’s needed?
How many hours? How much product?
How much cost? How much opportunity?
(from) Last Millennia (to) This Millennia
How big? Too big?
Learning to estimate Learning from estimates
Completing work Validating value delivered
If you are looking for more …
http://devjam.com/2013/07/12/cutting-an-agile-groove-overview/
http://www.versionone.com/product/agile-
project-management-tool-overview/
Questions?
© 2013 DevJam - All rights reserved.
www.devjam.com
david.hussman@devjam.com

AgileLIVE - Collaboration that Scales - Part 1

  • 1.
    Part 1 July 17,2013 David Hussman Agility Coach, Instructor, Owner, DevJam Andy Powell Product Evangelist, VersionOne
  • 2.
    Collaboration that Scales ConnectingTeams and Programs via Essential Conversations
  • 3.
    The CDS (ChiefDiscussion Starter) https://sites.google.com/site/twincitiespracticalagility/
  • 4.
  • 5.
    Collaboration Starts withConversation Within (a team) Across (teams) Outside (teams) Project Program Portfolio Product Conversations Daily Conversations Learning Conversations Reflective Conversations Cross Product Cross Team Conversations Dependency Conversations Ideation Conversations Investment Conversations Leadership Conversations 1 2 3
  • 6.
    Within ( a teamor a project )
  • 7.
    Growing Collaboration inContext Developing Products Iterative Learning Dealing w/ Adversity Maintaining Health Designing Agility Discovering / Delivering Continuous Delivery Reflective Correction Evolving the Process Getting Productive Staying Productive Getting Ready
  • 8.
    Product Thinking Developing Products IterativeLearning Dealing w/ Adversity Maintaining Health Designing Agility Discovering / Delivering Continuous Delivery Reflective Correction Evolving the Process Getting Productive Staying Productive Getting Ready Essential Product Discussions - Story Telling - - Product Context - - Distributed Ideation -
  • 9.
    What are yourstory telling tools? personas - story maps - sketches
  • 10.
    How does contextmatter? System Context Product Context
  • 11.
    How do youdo distributed discovery? “If Google Docs and Post It Notes had a child, it would be CardBoard” www.cardboardit.com
  • 12.
    Pragmatic Planning andStanding Developing Products Iterative Learning Dealing w/ Adversity Maintaining Health Designing Agility Discovering / Delivering Continuous Delivery Reflective Correction Evolving the Process Getting Productive Staying Productive Getting Ready How much planning is enough? Where is the value? What is the cost? Are standups feeding the team? Are you collaborating or just reporting? Are you discovering or solving?
  • 13.
    Dude’s Law: Value= Why / How V= W HI = V R How much process is enough?
  • 14.
    How much planningis enough? What is the least amount of process that adds the most real value? – Consider throwing out “The Book”
  • 15.
    Why are theystanding there? Talk to the wall Discover but don’t solve Ask 5 Silent Why’s
  • 16.
    Starting distributed connections Rotatewho goes first Press ‘3’ Key to speak
  • 17.
    Use name tohumanize people Pair people across locations Raj Maria Ivan Susan
  • 18.
    Use humor tofocus on outcomes
  • 19.
    How do youtalk about value delivered?
  • 20.
    Measuring, Learning andAdapting Developing Products Iterative Learning Dealing w/ Adversity Maintaining Health Designing Agility Discovering / Delivering Continuous Delivery Reflective Correction Evolving the Process Getting Productive Staying Productive Getting Ready How often are we watching real users? What is the best product direction? What is the next best investment? What can we learn from the past? How can we apply it to the future?
  • 21.
    How are youlearning about users? What’s your next best investment?
  • 22.
    Are people reflectingand learning? How do can you spark reflective dialog?
  • 23.
    Across ( many teamsor a program )
  • 24.
    Don’t mistake crowdsfor collaboration Cross cutting conversations require effort
  • 25.
    Checklist Thinking (andleaning) Cross cutting collaboration at scale
  • 26.
  • 27.
    Cross Cutting (teams and people )
  • 28.
    Cross Cutting (products )
  • 29.
    Cross Cutting (complexity )
  • 30.
    How adaptive isyour eco-system?
  • 31.
    Outside ( teams andacross portfolios )
  • 32.
    Who’s on theoutside and why?
  • 33.
    Connecting to theOutsiders Ideators Investors Leaders
  • 34.
  • 35.
    What is thenext best investment? Investors
  • 36.
  • 37.
    Are your skepticson the outside?
  • 38.
    Avoid Epistemic Arrogance “Thedifference between what you know and what you think you know”
  • 39.
    So what now? (putting these questions to work )
  • 40.
    Reframing Our Learning Buildingfor the future Building to adapt Talking about code Talking about tests Late integration Continuous Deployment What’s required? What’s needed? How many hours? How much product? How much cost? How much opportunity? (from) Last Millennia (to) This Millennia How big? Too big? Learning to estimate Learning from estimates Completing work Validating value delivered
  • 41.
    If you arelooking for more … http://devjam.com/2013/07/12/cutting-an-agile-groove-overview/ http://www.versionone.com/product/agile- project-management-tool-overview/
  • 42.
    Questions? © 2013 DevJam- All rights reserved. www.devjam.com david.hussman@devjam.com