Publicação
Implementing an agile project management methodology on a Minimum Viable Product development
| Resumo: | In the past few years, the world has faced a rapid change in the digitalization of processes over several different economic sectors. But there are services where human contact is a part of their job, such as massagists, mindfulness guidance, yoga, therapy, etc. In those areas, digitalization and process automation are less important than human well-being. This thesis project was developed in a not-for-profit Swedish startup that creates solutions, including services and products, to help well-being providers increase efficiency in their service. The startup has identified a lack of automation in the well-being services providers’ administrative tasks, consequently wasting time they could use to help more people, with activities that do not add value to their business or society. This master thesis presents the project of developing a Minimum Viable Product of a solution to help well-being providers with their administrative tasks. This thesis project focus on selecting and implementing an agile methodology to support the software development of the MVP, with a restricted time and budget. The research aims to answer the question: "Which agile method or framework best suits the studied startup environment, considering the restricted time and budget to develop an MVP and why?". To achieve its objectives, the research method used to support the selection, implementation, improvement, and adaptation of the agile methodology was action research, considering the organization's needs, to support the delivery of a functional product that added value to the customer. The chosen methodology was Kanban, and through its improvement cycles it was possible, with the team's help, to define a structure that would help them achieve their goals. It was noted that the methodology promoted excellent communication between the teams and aligned the customer’s needs and the software development process. The project saved 14.5% of the budget and ended on time, considering the six months of planned development. |
|---|---|
| Autores principais: | Dias, Danna Beatriz Rodrigues |
| Assunto: | Agile Project management Software development Minimum Viable Product Ágil Gestão de projetos Desenvolvimento de software Produto Viável Mínimo |
| Ano: | 2022 |
| País: | Portugal |
| Tipo de documento: | dissertação de mestrado |
| Tipo de acesso: | acesso aberto |
| Instituição associada: | Universidade do Minho |
| Idioma: | inglês |
| Origem: | RepositóriUM - Universidade do Minho |
| Resumo: | In the past few years, the world has faced a rapid change in the digitalization of processes over several different economic sectors. But there are services where human contact is a part of their job, such as massagists, mindfulness guidance, yoga, therapy, etc. In those areas, digitalization and process automation are less important than human well-being. This thesis project was developed in a not-for-profit Swedish startup that creates solutions, including services and products, to help well-being providers increase efficiency in their service. The startup has identified a lack of automation in the well-being services providers’ administrative tasks, consequently wasting time they could use to help more people, with activities that do not add value to their business or society. This master thesis presents the project of developing a Minimum Viable Product of a solution to help well-being providers with their administrative tasks. This thesis project focus on selecting and implementing an agile methodology to support the software development of the MVP, with a restricted time and budget. The research aims to answer the question: "Which agile method or framework best suits the studied startup environment, considering the restricted time and budget to develop an MVP and why?". To achieve its objectives, the research method used to support the selection, implementation, improvement, and adaptation of the agile methodology was action research, considering the organization's needs, to support the delivery of a functional product that added value to the customer. The chosen methodology was Kanban, and through its improvement cycles it was possible, with the team's help, to define a structure that would help them achieve their goals. It was noted that the methodology promoted excellent communication between the teams and aligned the customer’s needs and the software development process. The project saved 14.5% of the budget and ended on time, considering the six months of planned development. |
|---|