There is a line of research within Project Management that looks at “runaway” IT projects. This research seeks to understand why project teams continue to commit resources to failing projects. It’s referred to as “escalating commitment”” Read More …
This is a research-in-progress paper accepted to the 2019 Americas Conference on Information Systems (AMCIS 2019). Schmalz-Carter-Lee-2019-The-I-in-Team Abstract Software project failure continues to be a concern and managing risk our best hope of project success. While IS literature has investigated Read More …
Citation Barki, H., Rivard, S., & Talbot, J. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203–225. Other Sources Beath, CM. (1983). Strategies for managing MIS: A transaction cost approach. Proceedings of the Fourth Read More …
A place for me to keep notes from across multiple sources regarding the definition of “feature creep.” Read More …
The authors take a risk classification framework from Keil et al. (1998) and analyze which categories of risk are most important for product and process outcomes. The big conclusion is that managing risks tied to “scope and requirements” and “execution” are most important overall, affecting both classes of outcomes. This happens to be where I think identity research will have the biggest implications for project teams. Read More …
Citation Schmidt, R., Lyytinen, K., Keil, M., & Cule, P. (2001). Identifying Software Project Risks: An International Delphi Study. Journal of Management Information Systems, 17(4), 5–36. Notes Keil et al. (1998) and Schmidt et al. (2001) involve the same group Read More …
In the course of their work, the authors describe six dimensions of risk in IT projects. Three of these have factors that pertain to my work on identity in the development process. Read More …
The authors break down several categories of IT risk, including a set of factors that relate to my current studies: Human behavior, technology and technical issues, management activities and controls, and individual activities all have sub-categories that pertain in some way. Read More …
This is older, but I’ve seen Jones referenced for software risk. The book tries to be a comprehensive look at risk in MIS software development (for the period). Specific to feature creep, Chapter 9 is a description of Creeping User Requirements. Read More …
This is project management from the Organization Theory perspective. The material feels dated and a bit alien, challenging concepts from that domain which I’ve never considered or encountered in the wild. It may help me understand older PM literature, though. Read More …