Agile vs not agile

Get Started. It's Free
or sign up with your email address
Rocket clouds
Agile vs not agile by Mind Map: Agile vs not agile

1. Taxony of teams

1.1. Customer experience teams

1.1.1. Decisions

1.1.2. Behaviour

1.1.3. Satisfaction

1.2. Business process teams

1.2.1. Relationships

1.2.2. Collaboration

1.2.3. Divided responsibilities

1.3. Technology systems teams

1.3.1. IT development

1.3.2. Support customers teams

1.4. Charachteristics

1.4.1. Encourages exploration

1.4.2. Helps spot constraints

1.4.3. Reveals talent gaps

1.4.4. Visible to everyone

1.5. Examples

2. Customer experience teams

2.1. Decisions

2.2. Behaviour

2.3. Satisfaction

3. Decisions

4. Relationships

5. Agile vs not agile

5.1. gh

5.1.1. gh

5.1.1.1. gh

5.1.1.1.1. gh

5.1.1.2. ghgh

5.1.2. ghjghj

5.2. Agile vs not agile

6. Aim

6.1. teams

6.1.1. Small

6.1.2. Innovation

6.1.3. Enterpreneural

6.2. market

6.2.1. adapt cahging conditions

6.2.2. close to customers

6.3. result

6.3.1. team productivity

6.3.2. morale

6.3.3. faster time to market

6.3.4. better quality

6.3.5. lower risk

6.4. implementation

6.4.1. how many teams?

6.4.2. whole segment?

6.4.3. improve corporate performance as individual team performance?

6.5. companies

6.5.1. born agile

6.5.1.1. Spotify

6.5.1.2. Netflix

6.5.2. transform

6.5.2.1. Amazon

6.5.2.2. USAA

6.5.3. unsuccess

7. agile vs not agile

7.1. suit

7.1.1. innovation

7.1.1.1. products

7.1.1.2. services

7.1.1.3. processes

7.1.1.4. business models

7.1.2. departments

7.1.2.1. IT

7.1.2.2. HR

7.1.2.3. Product developement

7.1.2.4. Marketing

7.2. team

7.2.1. small

7.2.2. multidisciplinary

7.3. Work

7.3.1. dealing with problems

7.3.1.1. split task

7.3.1.2. prototyping

7.3.1.3. feedback

7.3.1.4. integrate

7.3.2. accountance

7.3.2.1. outcomes

7.3.2.1.1. growth

7.3.2.1.2. profitability

7.3.2.1.3. customer loyality

7.3.2.2. not outputs

7.3.2.2.1. lines of code

7.3.2.2.2. number of new products

7.3.3. leaders

7.3.3.1. chain-of-command bureaucracies

7.3.3.1.1. control

7.3.3.1.2. approval

7.3.3.1.3. top-down plans and directives

7.3.3.2. self-governing

7.3.3.2.1. where to innovate

7.3.3.2.2. how

7.3.3.3. leager coaches team members

7.4. Conditions

7.4.1. problems are complex

7.4.2. solutions are at first unclear

7.4.3. project requirements are likely to change

7.4.3.1. adapt to change

7.4.3.2. not stick a plan

7.4.4. close collaboration with end users is feasible

7.4.5. creative outperform command-and-control

7.4.6. Routine operations

7.5. Bosh example

7.5.1. 1. top-down management

7.5.2. 2. dual organization

7.5.2.1. hot new businesses run with agile teams

7.5.2.2. traditional functions left out of the action

7.5.3. 3.Felix Hieronymi

7.5.3.1. steering committee

7.5.3.2. software engineer - agile expert

7.5.4. 4. working committee

7.5.4.1. product owner

7.5.4.2. agile master

8. Building Agility

8.1. motivational system

8.1.1. training and coaching programm

8.1.2. revamp compensation system

8.2. special budget planning

8.2.1. avoiding annual planning

8.3. agile teams

8.3.1. face pressure from traditional departments

8.3.2. attack constraints during scaling

8.4. principles

8.4.1. integrating work streams

8.4.2. regular changes

8.4.3. modular approach

8.4.4. outsourcing is acceptable

8.4.5. consider feedback

8.4.6. close integration of agile teams

8.5. company

8.5.1. create

8.5.1.1. new principles

8.5.1.2. new values

8.5.2. change the culture

8.5.3. reduce control

9. Aim

9.1. teams

9.1.1. Small

9.1.2. Innovation

9.1.3. Enterpreneural

9.2. market

9.2.1. adapt cahging conditions

9.2.2. close to customers

9.3. result

9.3.1. team productivity

9.3.2. morale

9.3.3. faster time to market

9.3.4. better quality

9.3.5. lower risk

9.4. implementation

9.4.1. how many teams?

9.4.2. whole segment?

9.4.3. improve corporate performance as individual team performance?

9.5. companies

9.5.1. born agile

9.5.1.1. Spotify

9.5.1.2. Netflix

9.5.2. transform

9.5.2.1. Amazon

9.5.2.2. USAA

9.5.3. unsuccess

10. Divided responsibilities

11. Collaboration

12. Business process teams

12.1. Relationships

12.2. Collaboration

12.3. Divided responsibilities

13. Satisfaction

14. Behaviour