Advertisement

Application of Agile Development Methodology and User-Centered Design for the Interdisciplinary Project Zuku

  • Max Vilcapoma
  • Freddy Paz
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10918)

Abstract

The user-centered design allows the creative teams to focus on the real needs avoiding investing effort in features that will not add value to the product to be elaborated, this also reduces the rework that may result from not being clear about the requirements and assuming the that our experience dictates as a truth as to what may be useful to the end user. Within a multidisciplinary development project in which different specialties are part of the creative process and its implementation, the team members’ skills and experience in each of the involved areas are exploited, for the project to be developed will be a result of the sum of all the parts and not individual work. In consequence, the application of a user-centered methodology with agile development is presented in which the point of view of the different team members can contribute to the development of the software product. This paper describes what the Zuku project consists of, the context in which it was developed, methodologies involved, phases of the project and final results of the implementation.

Keywords

User-centered design Agile development Multidisciplinary development project Design sprint Design thinking 

References

  1. 1.
    Munari, B.: Cómo nacen los objetos?, 3rd edn. Gustavo Gilli, Barcelona (1983)Google Scholar
  2. 2.
    Choudhary, B., Rakesh, S.: An approach using agile method for software development. In: International Conference on Innovation and Challenges in Cyber Security (2016)Google Scholar
  3. 3.
    de Souza Carvalho, W., Rosa, P., dos Santos Soares, M., Teixeira da Cunha Jr., M., Buiatte, L.: A comparative analysis of the agile and traditional software development processes productivity. In: 30th International Conference of the Chilean Computer Science Society (2011)Google Scholar
  4. 4.
    2015 Chaos Report on Software Development. https://www.linkedin.com/pulse/2015-chaos-report-software-development-steve-dean. Accessed 06 July 2017
  5. 5.
    Simon, H.: The Sciences of the Artificial, 3rd edn. MIT Press, Cambridge (1996)Google Scholar
  6. 6.
    Villegas, M., Giraldo, W., Collazos, C., Granollers, T.: Software process implementation method with eclipse process framework composer: MPiu+a case. In: 8th Computing Colombian Conference (2013)Google Scholar
  7. 7.
    Knapp, J., Zeratsky, J., Kowitz, B.: Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster, New York (2016)Google Scholar
  8. 8.
    Become more effective with the 3-day design sprint. https://www.osudio.com/en/blog/postings/how-to-the-3-day-design-sprint. Accessed 06 July 2017
  9. 9.
    Trender, M.: Ux Design for Startups, United States (2013)Google Scholar
  10. 10.
    Nielsen, J.: Iterative user-interface design. Computer 26, 32–41 (1993)CrossRefGoogle Scholar
  11. 11.
    Smith, R.: Scrum Guide: Agile Project Management Guide for Scrum Master and Software Development Team. Createspace Independent Publishing (2016)Google Scholar
  12. 12.
    McInerney, P., Maurer, F.: UCD in agile projects: dream team or odd couple? Interactions 12, 19–23 (2005)CrossRefGoogle Scholar
  13. 13.
    Mental Health Commission: Multidisciplinary Team Working, Ireland (2016)Google Scholar
  14. 14.
    Afonso, A., Reis, J., Pérez, M.: Usability assessment of web interfaces – user testing. Int. J. Inf. Sci. 3(3), 57–62 (2013)Google Scholar
  15. 15.
    Galli, F., Suteu, I.: Design thinking as a disruptive discourse embracing conflict as a creative factor, Milano, Italy (2013)Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  1. 1.Pontificia Universidad Católica Del PerúLima 32Peru

Personalised recommendations