Skip to main content

From Pair Programming to Mob Programming to Mob Architecting

  • Conference paper
  • First Online:
Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies (SWQD 2017)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 269))

Included in the following conference series:

Abstract

The real life of a developer is not about development – it is about maintenance. Today typical programmers do not develop applications from scratch but they spend their time fixing, extending, modifying and enhancing existing applications. The biggest problem in their daily work is that over time maintenance mutates from structured programming to defensive programming: The code becomes too complex to be maintained. We put in code which we know is stupid from an architectural point of view but it is the only solution that will hopefully work. Maintenance becomes more and more difficult and expensive.

In this paper, I will show you how pair programming, mob programming and mob architecting help your team to avoid this apparently inevitable dead end. These three levels of quality improvement start with programming in pairs evolve to programming with the whole team (mob) and finally arrive at improving the architecture with the whole team.

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

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Cunningham, W.: The WyCash portfolio management system. Experience report, OOPSLA 1992 (1992)

    Google Scholar 

  2. Lilienthal, C.: Langlebige Softwarearchitektur, Technische Schulden analysieren, begrenzen und abbauen, dpunkt.verlag (2015). English version in preparation

    Google Scholar 

  3. Martin, R.C.: Principle and Patterns (2000). http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf

  4. Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston (1999)

    Google Scholar 

  5. Succi, G., Marchesi, M.: Extreme Programming Examined (XP). Addison-Wesley, Boston (2001)

    Google Scholar 

  6. Jansson, P.: Get a good start with mob programming. https://thecuriousdeveloper.com/2013/09/15/get-a-good-start-with-mob-programming/. Accessed 25 Aug 2016

  7. Obermüller, K., Campbell, J.: Mob Programming - the Good, the Bad and the Great. http://underthehood.meltwater.com/blog/2016/06/01/mob-programming/. Accessed 29 Aug 2016

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Carola Lilienthal .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Springer International Publishing AG

About this paper

Cite this paper

Lilienthal, C. (2017). From Pair Programming to Mob Programming to Mob Architecting. In: Winkler, D., Biffl, S., Bergsmann, J. (eds) Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies. SWQD 2017. Lecture Notes in Business Information Processing, vol 269. Springer, Cham. https://doi.org/10.1007/978-3-319-49421-0_1

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-49421-0_1

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-49420-3

  • Online ISBN: 978-3-319-49421-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics