Sprint Planning with a Digital Aid Tool: Lessons Learnt

Abstract

Managing the product's backlog is a major task in agile projects. This case study reports on one organization's experiences from the transition to a backlog management tool and its contribution to improving sprint planning.. Our key lessons learnt are that a tool is particularly appropriate to organize and specify backlog items in a transparent manner and to handle dependencies. However, we also observed an overhead in backlog management and in reporting during meetings. The concrete project settings play the paramount role in whether such a tool helps or harms the process.

Design of a Web System for the administrative control of the medical records in a Health Center

“…Likewise, it has an iterative model together with the incremental model for successive constructions of the application [5][6]. This methodology is developed in 5 phases, it begins with the first sprint or called Product Backlog in which user stories will be made, gathering all the requirements together with the user to obtain good results in the application to be developed [7]. The second phase is about the Sprint Backlog, where the one who leads the Scrum team, delegates the tasks to the developers and to have a better performance, through an organization tool the leader delegates an increase per developer giving an acceptable time to make the increase [8].…”