When plans do not work out: how plans are used in software development projects

Kari Rönkkö, Yvonne Dittrich, Dave Randall

Research output: Contribution to journalArticlepeer-review

33 Citations (Scopus)


Based on empirical material from the area of software engineering, this articlediscusses the issue of plans and planning as an integral part of and prerequisite for software development work. It relates observed practices to literature produced by the Computer Supported Cooperative Work community. Empirical studies of software development practice seldom address re-planning. By analyzing the empirical material from one project we are able to show how certain kinds of co-ordination problems arise and how they may be dealt with. The empirical research does not focus primarily on the character of plans; instead, it raises the question ‘what means are necessary and should be provided in order to cope with situations when plans do not work out? In relation to plans, especial emphasis is on ‘‘due process’’, i.e. how the project plan and the company wide project model are maintained to enable the identification and articulation of deviations from it. On the basis of our empirical analysis we propose to support the articulation and coordination work necessary in situations where plans do not adequately work out.

Original languageEnglish
Pages (from-to)433-468
Number of pages35
JournalComputer Supported Cooperative Work
Issue number5
Publication statusPublished - 2005
Externally publishedYes

Swedish Standard Keywords

  • Social Sciences (5)
  • Computer Sciences (10201)


  • Articulation work
  • due process
  • plans
  • project management
  • software engineering


Dive into the research topics of 'When plans do not work out: how plans are used in software development projects'. Together they form a unique fingerprint.

Cite this