Study about software project management with Design Thinking

This article presents an ongoing work on how it may be possible to work on software development using not only agile methodologies for the processes, but also the use of Design Thinking for the requirements analysis and software quality measurement. Given that there is the difficulty in the software process of understanding what the user really needs through Requirements Engineering, much of the fact that the software product is intangible and difficult to measure, it is necessary to listen to the end user about what he really needs. This process brings the Thinking Design mental model to improve the process of understanding what the user really needs, using their pillars: empathy, collaboration and prototyping. From this process, we can arrive at an extremely assertive Requirements Analysis model as to what the end user actually needs from that software product. On the other hand, we have to measure the quality of software, where we have measures that are more linked to the process and less linked to fit with qualitative metrics such as usability or productivity results that the user has reached. Based on this, a study was made on the possibility of using Design Thinking to help the Software Engineering process, listening to the user more and delivering software that he, the end user, unconsciously modelled, working only the interpretation of problems and needs according to the actual needs of that user.