Abstract

Just about everybody is for innovation, everybody talks about it and finds it vitally important, but somehow we have a shortage of methodological advice on how to make innovation more likely in software development – at least at the level of the software team or project. The Agile Manifesto offered promise for innovation by changing focus back to software itself more than elaborate requirements and processes. This change opened up for experimentation, learning, and flexibility in software projects, but the values of the Agile Manifesto sought to develop better software more effectively, not to innovate. How can we focus specifically on software innovation? A methodology for software innovation must stand on a set of values to guide work on the methodology as well as work inspired by it. These values have both theoretical and practical implications. This talk proposes one such set of values, illustrates their potential, and outlines a methodology to facilitate team-based software innovation.