top of page

Patterns of Time-Oriented Software Development: New BetaCodex Network research paper published


BetaCodex research paper No. 27 reveals why time orientation is the way to go in software development. And provides surprising detail around how to adopt a TOSD system


A new BetaCodex Network research paper – our 27th since 2008 – has been published today. Patterns of Time-Oriented Software Development (TOSD) features 18 characteristics of TOSD that we learned about since we went public with the approach in October last year.


The patterns collected in this paper will help practitioners (and their advisors) with establishing and running TOSD systems, in practice. The previous research paper, Introducing Time-Oriented Software Development, written by Sebastian Kubsch and myself, presented the key TOSD concepts like the OK Point, the distinction between Conceptualization and Realization, List curation and the TTEO principle. Upon reading that paper, you may have noticed that TOSD is very minimalistic.


The new paper, by contrast, explores the fine print of time orientation in product development. It doesn’t add new features to TOSD, but examines the spaces in-between, so to speak. We discovered the 18 patterns of the paper by working with pioneering companies such as Pradtke, through extensive research into software development literature, and by studying concepts of time orientation further like those outlined in the newly published book What would Ernst Weichselbaum do?


Comments


bottom of page