The leader role in large-scale agile development
This presentation is the property of its rightful owner.
Sponsored Links
1 / 22

The leader role in large-scale agile development LARS-OLA DAMM Ericsson AB, Sweden PowerPoint PPT Presentation


  • 87 Views
  • Uploaded on
  • Presentation posted in: General

The leader role in large-scale agile development LARS-OLA DAMM Ericsson AB, Sweden. Agenda. Context Personal background Ericsson The leader role Challenges Are appointed leaders still needed in an agile environment?. SWEDEN. Roles at Ericsson. Coaching agile impl. Industrial

Download Presentation

The leader role in large-scale agile development LARS-OLA DAMM Ericsson AB, Sweden

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


The leader role in large scale agile development lars ola damm ericsson ab sweden

The leader role in large-scale agile development

LARS-OLA DAMM

Ericsson AB, Sweden


Agenda

Agenda

  • Context

    • Personal background

    • Ericsson

  • The leader role

    • Challenges

    • Are appointed leaders still needed in an agile environment?


The leader role in large scale agile development lars ola damm ericsson ab sweden

SWEDEN

Roles at Ericsson

Coaching

agile impl.

Industrial

Ph.D. student

Manager of

agile teams

Working in

agile teams

Sw. developer

2007

2011

2001

2014


Ericsson

Ericsson

>40 percent of the world's mobile traffic passes through Ericsson networks

>100000 employees

Fifth largest software company in the world ($ revenue from software)

Quick facts


Organization overview 1 3 system view

Organization overview (1/3)System view

System teams

Portfolio management

Total

~20 domains

~1000 developers

~10 locations on 3 continents

domain X

domain Y

= Cross-functional development team


Organization overview 2 3 domain view

Organization overview (2/3)Domain view

Domain architect team

Support teams, e.g.

environment automation,

deployment preparation

DOS (Domain Operative Steering)

Line manager

Chief architect

Feature development teams

Program manager

QA manager


Organization overview 1 3 team view

Organization overview (1/3)Team view

QA forum

PO forum

Architect forum


Development flow domain level

Functional/non-functional

regression testing

(continuous)

Release candidate*

Development flow (Domain level)

Feature GO

Unit/integration test failed OR

Manual review rejected

“Push review”

“Commit”

Check out

Release branch

Development/maintenance branch

Check in

Deployment prep.

*New market release done every 6 weeks


Overall maturity

Overall maturity


Agenda1

Agenda

  • Context

    • Personal background

    • Ericsson

  • The leader role

    • Challenges

    • Are appointed leaders still needed in an agile environment?


Leadership challenges

Leadership challenges

Ensure customer knowledge

Give teams purpose/vision

Handling

underperformers

Sustainable pace

Delivery commitments

Career paths/job titles

Process alignment

Performance appraisals

Salaries/rewards

Transparency

Benchmarking


Agenda2

Agenda

  • Context

    • Personal background

    • Ericsson

  • The leader role

    • Challenges

    • Are appointed leaders needed in an large-scale agile environment?


The leader role in large scale agile development lars ola damm ericsson ab sweden

Situational leadership


Commitments sustainable pace

Commitments &Sustainable pace


The leader role in large scale agile development lars ola damm ericsson ab sweden

Respect

Trust


Transparency

Transparency


Benchmarking

Benchmarking

  • Example:


Alignment

alignment

  • Reflections:

  • Align on outcomes, not how to achieve outcome

  • Have a delegated process for cont. improvement of aligned things


  • Login