Skip to main content
Springer Nature Link
Log in

Roles and Responsibilities in Feature Teams

  • Chapter
  • First Online:
Agility Across Time and Space

Abstract

Agile development requires self-organizing teams. The set-up of a (feature) team has to enable self-organization. Special care has to be taken if the project is not only distributed, but also large and more than one feature team is involved. Every feature team needs in such a setting a product owner who ensures the continuous focus on business delivery. The product owners collaborate by working together in a virtual team. Each feature team is supported by a coach who ensures not only the agile process of the individual feature team but also across all feature teams. An architect (or if necessary a team of architects) takes care that the system is technically sound. Contrariwise to small co-located projects, large global projects require a project manager who deals with—among other things—internal and especially external politics.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. Brooks, F. P. Jr. (1995). The mythical man-nonth: Essays on software engineering (20th anniv. ed.). Reading: Addison-Wesley (Quoted from p. 42 and p. 44).

    Google Scholar 

  2. Cockburn, A. (2006). Agile software development: the cooperative game (2nd ed.). Reading: Addison-Wesley.

    Google Scholar 

  3. Liker, J. K. (2004). The Toyota way. 14 management principles from the world’s greatest manufacturer. New York: McGraw-Hill (Quoted from p. 241).

    Google Scholar 

Further Reading

  1. http://www.agilemanifesto.org.

  2. Eckstein, J. (2004). Agile software development in the large. Cambridge: Dorset House.

    Google Scholar 

  3. Eckstein, J. (2010). Agile software development with distributed teams. Cambridge: Dorset House.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Gaussstr. 29, 38106, Braunschweig, Germany

    Jutta Eckstein

Authors
  1. Jutta Eckstein
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Jutta Eckstein .

Editor information

Editors and Affiliations

  1. School of Engineering, Blekinge Institute of Technology, Ronneby, 372 25, Sweden

    Darja Šmite

  2. Dept. Information & Communication, Technology (ICT), SINTEF, Trondheim, 7465, Norway

    Nils Brede Moe

  3. Dept. Information Sciences, Uppsala University, Uppsala, 751 20, Sweden

    Pär J. Ågerfalk

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Eckstein, J. (2010). Roles and Responsibilities in Feature Teams. In: Šmite, D., Moe, N., Ågerfalk, P. (eds) Agility Across Time and Space. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-12442-6_19

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-12442-6_19

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-12441-9

  • Online ISBN: 978-3-642-12442-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics