Abstract
The paper is basically dedicated to the problem of effort estimation for the Product Backlog items of IT projects led accordingly to the Scrum framework. The effort estimation issue is important, because low quality estimation decreases the efficiency of project implementation. The paper proposes an estimation method for the Product Backlog items of Scrum-based IT projects (which can be adapted also to other projects), which has two original elements with respect to the state of art in Scrum estimation: the usage of fuzzy numbers and strict rules for consensus forming, combined with a space for human interaction. The assumptions of the method should be complied with and were formulated on the basis of literature and authors experience. Two case studies were used for an initial method validation. The case studies confirmed a high potential of the method to increase estimation quality in Scrum-based projects, as well as in other project types. The case studies were conducted using research methods fulfilling the symmetry principle. The paper is thus an example of symmetry in management research.
Highlights
After a dozen years, both small organizations [1] and large multinationals ones [2] have been usingScrum in their daily operations [3]
The paper is basically dedicated to the problem of effort estimation for the Product Backlog items of IT projects led to the Scrum framework
We propose to begin with an easier method, where the experts are instructed about the meaning of the membership function from Figure 1 and subsequently are asked three questions: What is the most optimistic value of effort estimation of Product Backlog item Fj, j = 1, . . . , J, where J is the number of elements in the Product Backlog
Summary
Both small organizations [1] and large multinationals ones [2] have been using. Scrum in their daily operations [3]. Scrum is already assessed fairly positively in the business context, it still requires further development and refinement [4]. This encompasses the project estimation issue, with a special emphasis on the estimation of the effort needed to accomplish the elements of the Product Backlog, performed before each Sprint. Demands in the industry set to estimating software development effort are nowadays considerably elevated [5,6,7] and it is general management knowledge that accurate ( acceptably close to actual values) estimates increase the efficiency of project implementation.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
