Re: Self Organization in Scrum
- --- In scrumdevelopment@y..., "jsutherland" <jeff.sutherland@c...>
> Thanks to Grady for enlivening the discussion on Scrum. I'd liketo
> comment on the issue of self-organization which SCRUM was designedto
> create in software. Since software architectures reflect stronglythe
> implicit assumptions of the creators, getting people to self-organize
> is a way to affect innovation and dynamism of the software.success.
> The basic ideas around the first software Scrums came from:
> The New New Product Development Game
> Hirotaka Takeuchi; Ikujiro Nonaka
> Product Type: Harvard Business Review Article
> Product#: 86116 Pub. Date: January 01, 1986
> Length: 10p
> The key issues in successful Japanese teams are summarized below.
> They were always given a clear mission (impossible) by senior
> management and told the companies future depended on their
> Team members were carefully selected and then told to figure itout
> for themselves. Management was there primary to provide thingsthey
> needed and eliminate roadblocks, or when necessary, change teamJeff,
> 1. Drive to "zero information state"
> 2. Ambiguity and fluctuation breeds new dynamic order within team
> 3. Operate like startup company - initiative and risk, independent
> 4. Teams must demonstrate autonomy, self-transcendence, and cross-
I am not clear on what you mean by "Zero Information State". Is it
like zero-based budgeting, ie., start with a clean slate? Since
it's one of your key points, I really would like to understand it.