Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Loading in …3
×
1 of 4

Multi Team Agile Release Wall

1

Share

Download to read offline

In a larger environment it can be difficult to see what's happening with projects or products that span multiple teams. This presentation is a handout from my Lean 2011 talk on Visibility.

Related Books

Free with a 30 day trial from Scribd

See all

Multi Team Agile Release Wall

  1. 1. Nowhere to Run, Nothing to Hide Nothing to Hide Making Your Organization Progress and Agile Transition Visible Presented at Lean 2011 by Jason Little http://www.agilecoach.ca
  2. 2. multi-team release wall Jan Feb Mar Group 1 Group 2 Group 3 Version/ notes Major Release Minor Release Patch Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes 2.5 - notes 2.6 - notes 2.7 - notes Version/ notes Version/ notes 2.7 - notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes Version/ notes 2.5 - notes 2.5.1 - notes 2.7 - notes - hey, we do a lot of patches, what’s up with that? talk about what other data and challenges we discovered
  3. 4. The Release Wall <ul><li>snapshot of what’s being release by each team </li></ul><ul><li>do ‘scrum of scrums’ in front of release wall </li></ul><ul><li>colour coded to identify issues (IE: the example shows far too many patches, why is that?) </li></ul><ul><li>shows support and maintenance load on teams (IE: why don’t new features get done?) </li></ul><ul><li>answer questions like: “hey, when is 2.5 going out?” - check the wall! </li></ul>more visible charts and examples at http://www.agilecoach.ca/visibility

×