Low Ceremony Processes for Short Lifecycle Projects

  • Anthony I. WassermanEmail author


Modern software applications, particularly those for mobile devices and web applications, are fundamentally different from traditional applications. Many of those applications are developed by startup businesses, which are under time and financial pressure to release their applications as quickly as possible. They have chosen to use agile methods for their development activities, largely because the administrative overhead for the process is low and the release cycle for the product is short. In this chapter, we contrast software processes based on the amount of management overhead (“ceremony”), describing the characteristics of startup businesses and their use of low-ceremony processes.


Software Development Process Modern Application User Story Agile Method Capability Maturity Model 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Agile Alliance: Manifesto for Agile software development. (2001)
  2. 2.
    Blank, S., Dorf, B.: The Startup Owner’s Manual: The Step-By-Step Guide for Building a Great Company. K & S Ranch, Pescadero (2012)Google Scholar
  3. 3.
    Boehm, B.: A spiral model of software development and enhancement. Computer 21(5), 61–72 (1988)CrossRefGoogle Scholar
  4. 4.
    Burns, E., Prakash, W.H.: Continuous Integration in Practice. McGraw Hill Osborne Media, New York (2013)Google Scholar
  5. 5.
    Chrissis, M.B., Konrad, M., Shrum, S.: CMMI for Development: Guidelines for Process Integration and Product Improvement, 3rd edn. Addison-Wesley Professional, Reading (2011)Google Scholar
  6. 6.
    Humphrey, W.S.: Characterizing the software process: a maturity framework. IEEE Softw. 5(2), 73–79 (1988)CrossRefGoogle Scholar
  7. 7.
    Humphrey, W.S.: Managing the Software Process. Addison-Wesley Professional, Reading (1989)Google Scholar
  8. 8.
    Naur, P., Randell, B.: Software engineering. Technical report, NATO Science Committee (1969)Google Scholar
  9. 9.
    Ries, E.: The Lean Startup. Crown Business, New York (2011)Google Scholar
  10. 10.
    Sutherland, J.: Scrum: The Art of Doing Twice the Work in Half the Time. Crown Business, New York (2014)Google Scholar
  11. 11.
    Wasserman, A.I.: Toward a discipline of software engineering. IEEE Softw. 13(6), 23–31 (1996)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  1. 1.Integrated Innovation InstituteCarnegie Mellon University – Silicon ValleyMoffett FieldUSA

Personalised recommendations