Project Archetypes: A Blessing and a Curse for AI Development
Mateusz Dolata, Kevin Crowston, Gerhard Schwabe

TL;DR
This paper examines how traditional project archetypes influence AI development projects, highlighting their potential to become outdated and proposing a new archetype for cognitive computing projects based on interviews.
Contribution
It identifies existing archetypes in AI projects and introduces a new cognitive computing archetype to better guide AI development efforts.
Findings
Identified four existing project archetypes in AI projects.
Developed a new archetype: cognitive computing project.
Provided insights for managing archetypes in AI development.
Abstract
Software projects rely on what we call project archetypes, i.e., pre-existing mental images of how projects work. They guide distribution of responsibilities, planning, or expectations. However, with the technological progress, project archetypes may become outdated, ineffective, or counterproductive by impeding more adequate approaches. Understanding archetypes of software development projects is core to leverage their potential. The development of applications using machine learning and artificial intelligence provides a context in which existing archetypes might outdate and need to be questioned, adapted, or replaced. We analyzed 36 interviews from 21 projects between IBM Watson and client companies and identified four project archetypes members initially used to understand the projects. We then derive a new project archetype, cognitive computing project, from the interviews. It can…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
