2/06/2014

Lean Feature Experimentation

End to end Quality and other challenges with Agile @ Scale

Mack Adams and Miten Mehta

Two sessions in one combined setting
. Broader topic - Agile @ Scale - Models and Patterns
. Drill down - End to end quality at scale

Notes in attached pictures...

Managing Requests without a Product Owner





John Felix

The Five Rules of Learning

Willem Larsen, host. 

experts showing off

The Agile Interview

Host: Graham Bremner

this process is used to hire developers for a XP team, parts are useful for hiring anyone involved in the software development process.
after an initial short candidate screen we decide to bring a candidate into our office for a full day interview.

our schedule is :
 1 hour fit question 
 1 hour technical screen
 lunch with team
 four 1 hour pairing sessions

What Happens When We Focus on Everyone's Needs?

Justin Redd



--
Justin
(503) 877-3335


Why Cycle Time Distribution Looks Like it Does and How We Can Use It

Troy Magennis

- Cycle time when plotted as a histogram follows certain patterns
- Understanding the odds of 4 people getting to a dinner reservation on-time (1 chance in 16) is the same issue as how delays cause a skewed distribution.
- Its unlikely that one story encounters EVERY type of possible delay, and its also unlikely that a story encounters NO delay
- By reducing a delay cause, you double the odds of delivery. E.g. for 3 people (possible delays) there is a 1 in 8 chance of on-time "delivery"
- Hypothesis: Cycle time follows a Weibull distribution
- Weibull distributions have a shape parameter. 1 = Exponential distribution this matches dev-ops teams , 1.5 matches Agile/Lean/Scrum teams, 2 = waterfall or thereabouts.
- Our goal is to find which delays move the curve to the left. 
- Possible way to compute: Use an algorithm used to join Frequency of delay, Recency of Delay and Length of delay. RFM analysis was comon in the 80's for direct marketing optimization. Can we use for waste reduction?

Seeding Agile in a Reluctant Team

Host: Jay Bazuzi

Avoid Agile terminology. Use "help" instead of "pair"

If you want people to change, need to focus on what they get out of it. Focus on very specific pain points.

Look at bug trends to motivate attention.

Celebration

Ask for their ideas. Make sure this turns in to action so they feel that speaking is worthwhile

Get some praise from users.

Cynefin model for cultural terrain https://en.wikipedia.org/wiki/Cynefin


Working remotely with an otherwise co-located team

Host: Jay Bazuzi

Useful technology:

Spycam: let's remote worker listen in to room chatter
Audio quality is important
For HVAC noise, blue mic snowball, or yeti mic

Video is important, but low quality is OK
Headsets for all, with good mics
VS Anywhere, for low-latency pair programming.
If screen sharing and you switch times a lot, split the screens to avoid full screen refresh
Wideteams.org


Presense:

Put a picture of me on the wall -avoid out of site out of mind
Designate a partner at the beginning of the day or task
Find a pair in the morning, but also check in during the day.

Maintenance - Lessons and Tips

Host: Scott Lonheim

ACI Coaching Model

Greg Myers
Agile Coaching Institute has a coaching model that identifies skills and practices useful for Agile Coaching.

The Website link: http://www.agilecoachinginstitute.com/agile-coaching-resources/
- This site has resources for each element of the model (click on links in the page)
Lyssa Adkins' (Of ACI) book: http://www.coachingagileteams.com
- Resources, excepts, link to purchase

Q&A with Diana Larsen on Agile Leadership

Willem Larsen, host. 

Prioritization between Agile Teams (W3-Blue)

Context:

In an environment where we have multiple teams, each with a product owner, how do we adjust the team priorities to ensure that overall business priorities are met? For example, team A may have a high priority story that is dependent on work by team B, but that work is a low priority for team B. What have people tried? What works?


Practices / Guidelines:

•             must get the product owners together to hash out the organization-wide priorities – individual teams can support this effort but can’t make the decisions

Agile Baseline Survey 4 of 4

Jean Richardson

Agile Baseline Survey 3 of 4

Jean Richardson

Agile Baseline Survey 2 of 4

Jean Richardson

Agile Transformation Stages, Obstacles, Approaches

Good conversation, thanks to all. The most recurring theme:  defining and communicating the "why" before and during any agile implementation is a key to success. See flip chart photos.

Agile Baseline Survey 1of 4

Jean Richardson

What Do You Want to Say to Your Boss and Can't?

Brent Barton

This was motivated by telling my boss I wanted to hit him.  Fortunately, I didn't get fired but it led to the desire to research transparency.

Statement Associate with this statement
My Boss wants to push decisions down but can't resist getting into the details. 9
"What got you where you are is now getting you nowhere." 7
Over-priviledging harmony: Consensus being more important than making good decisions. 7

Cumulative Flow Diagram 3 of 3

Cumulative Flow Diagram 2 of 3

Cumulative Flow Diagram 1 of 3

Open Office Space - How's that working for you?

Mary Panza - host

Summary: Open office space is still the preferred configuration for Agile/collaborative teams. However, this was clarified as an open space for teams, not necessarily the entire company/floor/department in one giant open area.

Considerations, Compromises and Recommendations


- Create an open space for each team, but not EVERYBODY in one giant space.

Agile Baseline Survey 3 of 3

Jean Richardson

Agile Baseline Survey 2 of 3

Jean Richardson

Agile Baseline Survey 1 of 3

Jean Richardson