DEVELOPMENT OF SPRINT PLANNING MODULE FOR SCRUM PROJECT MANAGEMENT TOOL
In this work, a sprint planning tool has been developed by integrating product backlog refinement tool and effort estimation technique with existing Agile Project Management tool. Effort estimation is the process to estimating how much work can be done in one sprint. Agile team have to measure th...
Saved in:
| Main Author: | |
|---|---|
| Format: | Final Project |
| Language: | Indonesia |
| Online Access: | https://digilib.itb.ac.id/gdl/view/54346 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | Institut Teknologi Bandung |
| Language: | Indonesia |
| Summary: | In this work, a sprint planning tool has been developed by integrating product
backlog refinement tool and effort estimation technique with existing Agile Project
Management tool. Effort estimation is the process to estimating how much work
can be done in one sprint. Agile team have to measure their capacity in order to
estimate the effort and time they need to run a sprint. Poor estimation can raise some
challenges in controlling sprints and the quality of software produced. On the other
hand, product backlog refinement tools and effort estimation techniques have been
proposed. Unfortunately, those tools and techniques have not been implemented in
existing Agile project management tools so that they can be used directly by users.
In order to integrate product backlog refinement tool and effort estimation
technique on existing Agile project management tool, the steps in sprint planning
process need to be examined. Those steps include product backlog refinement,
effort estimation, calculating team capacity, calculating sprint velocity, and
planning the iteration. Product backlog refinement is a step that needs to be done
before effort estimation, but it is also a challenge in Agile project management.
AQUSA is the one of the answers to these problems. SVM classifier used for
estimating story points from user story text. Taiga was chosen as Agile project
management tool that being developed. To integrate those tool and technique on
Taiga, new API endpoints created and some existing API endpoints and existing
user-interfaces are modified. The modified Taiga is tested with API functional
testing and software functional testing by running modified tool manually based on
scenarios. The test results show that the Agile tool that have been developed meet
the requirements specifications. |
|---|