DUXU 2015: Design, User Experience, and Usability: Design Discourse pp 356-367 | Cite as
Software Project Management Combining Agile, Lean Startup and Design Thinking
Abstract
This paper describes a project management model named Converge, that combines Agile, Lean Startup and Design Thinking with the aim of producing user-centered software and sustainable innovation through empathy with users. The model is based on previous works combining the aforementioned methodologies and adjusted considering needs that arose from teams inside the lab, observed empirically. In order to test the method’s validity in a real project, an undergraduate team part of an experimentation lab followed the proposed model to guide the development of a homonymous data storage app.
The app was built in 8 weeks and, at the time of release, 80 % of testers considered it a better solution compared to ones they already used. Overall test results suggest that it is productive to combine the methodologies. The model met its aim since it guided the development of a novel software solution highly regarded by users.
Keywords
Project management Agile methodologies Lean Startup Design Thinking Model Software development Innovation Case studyReferences
- 1.Griffith, E.: Why startups fail, according to their founders (2014). http://fortune.com/2014/09/25/why-startups-fail-according-to-their-founders/
- 2.Tobak, S.: 9 Reasons why most startups fail (2014). http://www.entrepreneur.com/article/231129
- 3.Deeb, G.: The unlucky 13 reasons startups fail (2013). http://www.forbes.com/sites/georgedeeb/2013/09/18/the-unlucky-13-reasons-startups-fail/
- 4.Aulet, B.: Disciplined Entrepreneurship: 24 Steps to a Successful Startup. Wiley, New York (2013)Google Scholar
- 5.Ries, E.: The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business, New York (2011)Google Scholar
- 6.Brown, T.: Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation. Harper Business, New York (2009)Google Scholar
- 7.Brown, T.: Design thinking. Harv. Bus. Rev. 86(84–92), 141 (2008)Google Scholar
- 8.Nelson, E.: Extreme programming vs. interaction design (2002)Google Scholar
- 9.Bird, J.: Code ownership – who should own the code? (2011). http://swreflections.blogspot.com.br/2013/04/code-ownership-who-should-own-code.html
- 10.Poppendieck, M., Poppendieck, T.: Lean Software Development: An Agile Toolkit. Addison-Wesley Professional, Boston (2003)Google Scholar
- 11.Maurya, A.: Running Lean: Iterate from Plan A to a Plan That Works. O’Reilly Media, Sebastopol (2012)Google Scholar
- 12.Widman, J., Hua, S., Ross, S.: Applying lean principles in software development process–a case study. Issues Inf. Syst. 11(1), 635–639 (2010)Google Scholar
- 13.Nobel, C.: Teaching a lean startup strategy (2011). http://hbswk.hbs.edu/
- 14.Moe, N.B., Dingsøyr, T., Dybå, T.: A teamwork model for understanding an agile team: a case study of a scrum project. Inf. Softw. Technol. 52, 480–491 (2010)CrossRefGoogle Scholar
- 15.Virtual crash course in design thinking http://dschool.stanford.edu/dgift/
- 16.Lindberg, T., Meinel, C., Wagner, R.: Design thinking - a fruitful concept for IT development? In: Meinel, C., Leifer, L., Plattner, H. (eds.) Design Thinking: Understand - Improve - Apply, pp. 3–18. Springer, Heidelberg (2011)CrossRefGoogle Scholar
- 17.Lafreniere, D.: Extreme user research (2008). http://boxesandarrows.com/extreme-user-research/
- 18.Serrat, O.: The five whys technique (2009)Google Scholar
- 19.Mattimore, B.W.: Idea Stormers: How to Lead and Inspire Creative Breakthroughs. Jossey-Bass, San Francisco (2012)Google Scholar
- 20.Beaudouin-Lafon, M., Mackay, W.E.: Prototype development and tools. In: Sears, A., Jacko, J. (eds.) Human Computer Interaction—Development Process, pp. 122–142. Lawrence Erlbaum Associates, Hillsdale (2003)Google Scholar