Retrospective Process Tracing. A Waste Identification Technique in Lean and Agile Software Development

Abstract

This master’s thesis describes a new waste identification technique, adapted from the Process Tracing sub-method Explaining Outcome described in Beach et al. (2013). The aim of the technique is to enable development teams, that adhere to the principles of Agile and Lean development, to identify waste that is the result of the teams’ uniqueness in team and organizational structure, which also cannot be directly identified by looking at the literature of waste categories or Agile success factors. The thesis cites the findings of a three-month long exploratory Action Research study, involving six team members developing a travel expense reimbursement system. The technique was found to enable a cost-efficient waste identification process within the team, and could serve as a substitute for the traditional Retrospective Meetings as described in the Scrum Guide. The findings are believed to be of importance to teams of similar parameters, but verification studies should be held to better understand the technique’s scalability and generalizability. The thesis should be of interest to practitioners and academics alike, and especially so for project managers of small-scale development teams.