Agile estimation
First Claim
1. A method for size estimation of a plurality of user stories used in one or more agile software development projects assigned to multiple teams, the method comprising:
- obtaining, by a processor, the plurality of user stories associated with a software for size estimation analysis;
computing, by the processor, a base size for each of the plurality of user stories based on a basic parameter from a plurality of basic parameters assigned to each of the multiple teams, wherein the basic parameter comprises a pre-defined threshold value representing a characteristic contributing to complexity of each of the user stories, wherein computing the base size for each of the plurality of user stories comprises;
providing a plurality of options for the at least one basic parameter for each of the plurality of user stories, wherein the plurality of options are choices selected for a user story, in response to a basic parameter, and wherein the plurality of options provided as both values and text vary for each basic parameter from the plurality of basic parameters;
allocating a predefined score, based on selection of one of the plurality of options for the at least one basic parameter;
determining an intermediate base size of each user story, by consolidating predefined scores for each of the user stories for the at least one basic parameter;
determining a stringent base size and a comfortable base size for each user story, wherein the stringent base size is an integer identified in Fibonacci series that is closest to and smaller than the intermediate base size of a respective user story, and wherein the comfortable base size is an integer of Fibonacci series closest to and larger than the intermediate base size of the respective user story; and
computing the base size of each user story as one of the stringent base size and the comfortable base size closer to the intermediate base size of the respective user story, wherein a notification is provided to a user, if the computed base size is larger than the predefined threshold value as an indication to break each of the user story into multiple user stories;
ascertaining, by the processor, an additional size for the plurality of user stories based on at least one additional parameter, wherein the at least one additional parameter comprises an environmental factor affecting delivery of the software, wherein the additional size is indicative of a quantitative measure of complexity associated with delivery of the software impacting the execution of the plurality of user stories and wherein the ascertaining comprises;
determining, by the processor, against each additional parameter, whether impact of the each additional parameter is story-specific or sprint-specific;
determining, by the processor, received score as an intermediate additional size for the plurality of user stories against each additional parameter based on the user input score and depending on whether the impact of the respective additional parameter is story-specific or sprint-specific; and
computing, by the processor, the additional size for the plurality of user stories based on the intermediate additional size determined against each additional parameter;
determining, by the processor, an overall size of the plurality of user stories by consolidating the base size for and the additional size for each of the plurality of user stories corresponding to a predefined sprint for estimating a sprint velocity, wherein the sprint velocity is an estimation of number of story points delivered for each of the plurality of user stories in the predefined sprint, and wherein the overall size estimation is determined using a parametric analysis of the plurality of user stories by comparing the overall size of the plurality of user stories across sprints and one or more agile software development projects; and
ascertaining, by the processor, a consolidated effort for execution of the plurality of user stories based on the estimated sprint velocity along with a pre-baselined delivery rate, wherein the pre-baselined delivery rate is a quantitative measure of capability of the team in terms of time required for execution of the user story, the pre-baselined delivery rate is measured in person hours per story point (PH/ISP), and varied according to a technology of a user story.
1 Assignment
0 Petitions
Accused Products
Abstract
The present subject matter relates to size estimation of a plurality of user stories for agile software development. The plurality of user stories associated with a software may be obtained, and a base size for each of the plurality of user stories may be computed based on at least one basic parameter. The at least one basic parameter is indicative of a parameter affecting complexity associated with execution of a user story. Subsequently, an additional size for the plurality of user stories may be ascertained, based on at least one additional parameter. The at least one additional parameter is indicative of an environmental factor affecting delivery of the software. The overall size of the plurality of user stories is determined by consolidating the base size for each user story with the additional size for the plurality of user stories.
7 Citations
15 Claims
-
1. A method for size estimation of a plurality of user stories used in one or more agile software development projects assigned to multiple teams, the method comprising:
-
obtaining, by a processor, the plurality of user stories associated with a software for size estimation analysis; computing, by the processor, a base size for each of the plurality of user stories based on a basic parameter from a plurality of basic parameters assigned to each of the multiple teams, wherein the basic parameter comprises a pre-defined threshold value representing a characteristic contributing to complexity of each of the user stories, wherein computing the base size for each of the plurality of user stories comprises; providing a plurality of options for the at least one basic parameter for each of the plurality of user stories, wherein the plurality of options are choices selected for a user story, in response to a basic parameter, and wherein the plurality of options provided as both values and text vary for each basic parameter from the plurality of basic parameters; allocating a predefined score, based on selection of one of the plurality of options for the at least one basic parameter; determining an intermediate base size of each user story, by consolidating predefined scores for each of the user stories for the at least one basic parameter; determining a stringent base size and a comfortable base size for each user story, wherein the stringent base size is an integer identified in Fibonacci series that is closest to and smaller than the intermediate base size of a respective user story, and wherein the comfortable base size is an integer of Fibonacci series closest to and larger than the intermediate base size of the respective user story; and computing the base size of each user story as one of the stringent base size and the comfortable base size closer to the intermediate base size of the respective user story, wherein a notification is provided to a user, if the computed base size is larger than the predefined threshold value as an indication to break each of the user story into multiple user stories; ascertaining, by the processor, an additional size for the plurality of user stories based on at least one additional parameter, wherein the at least one additional parameter comprises an environmental factor affecting delivery of the software, wherein the additional size is indicative of a quantitative measure of complexity associated with delivery of the software impacting the execution of the plurality of user stories and wherein the ascertaining comprises; determining, by the processor, against each additional parameter, whether impact of the each additional parameter is story-specific or sprint-specific; determining, by the processor, received score as an intermediate additional size for the plurality of user stories against each additional parameter based on the user input score and depending on whether the impact of the respective additional parameter is story-specific or sprint-specific; and computing, by the processor, the additional size for the plurality of user stories based on the intermediate additional size determined against each additional parameter; determining, by the processor, an overall size of the plurality of user stories by consolidating the base size for and the additional size for each of the plurality of user stories corresponding to a predefined sprint for estimating a sprint velocity, wherein the sprint velocity is an estimation of number of story points delivered for each of the plurality of user stories in the predefined sprint, and wherein the overall size estimation is determined using a parametric analysis of the plurality of user stories by comparing the overall size of the plurality of user stories across sprints and one or more agile software development projects; and ascertaining, by the processor, a consolidated effort for execution of the plurality of user stories based on the estimated sprint velocity along with a pre-baselined delivery rate, wherein the pre-baselined delivery rate is a quantitative measure of capability of the team in terms of time required for execution of the user story, the pre-baselined delivery rate is measured in person hours per story point (PH/ISP), and varied according to a technology of a user story. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. An agile estimation system used in one or more agile software development projects assigned to multiple teams, the agile estimation system comprising:
-
a processor; a base size estimation module, coupled to the processor to; obtain the plurality of user stories associated with a software for size estimation analysis; and compute a base size for each of the plurality of user stories based on a basic parameter from a plurality of basic parameters assigned to each of the multiple teams, wherein the basic parameter comprises a pre-defined threshold value representing a characteristic contributing to complexity of each of the user stories, wherein computing the base size for each of the plurality of user stories comprises; providing a plurality of options for the at least one basic parameter for each of the plurality of user stories, wherein the plurality of options are choices selected for a user story, in response to a basic parameter, and wherein the plurality of options provided as both values and text vary for each basic parameter from the plurality of basic parameters; allocating a predefined score, based on selection of one of the plurality of options for the at least one basic parameter; determining an intermediate base size of each user story, by consolidating predefined scores for each of the user stories for the at least one basic parameter; determining a stringent base size and a comfortable base size for each user story, wherein the stringent base size is an integer identified in Fibonacci series that is closest to and smaller than the intermediate base size of a respective user story, and wherein the comfortable base size is an integer of Fibonacci series closest to and larger than the intermediate base size of the respective user story; and computing the base size of each user story as one of the stringent base size and the comfortable base size closer to the intermediate base size of the respective user story, wherein a notification is provided to a user, if the computed base size is larger than the predefined threshold value as an indication to break each of the user story into multiple user stories; an additional size estimation module, coupled to the processor, to ascertain an additional size for the plurality of user stories based on at least one additional parameter, wherein the at least one additional parameter comprises an environmental factor affecting delivery of the software, wherein the additional size is indicative of a quantitative measure of complexity associated with delivery of the software impacting the execution of the plurality of user stories and wherein to ascertain the additional size, the additional size estimation module; determines against each additional parameter, whether impact of the each additional parameter is story-specific or sprint-specific; determines received score as an intermediate additional size for the plurality of user stories against each additional parameter based on the user input score and depending on whether the impact of the respective additional parameter is story-specific or sprint-specific; and computing the additional size for the plurality of user stories based on the intermediate additional size determined against each additional parameter; a work allocation module, coupled to the processor, to determine an overall size of the plurality of user stories by consolidating the base size for and the additional size for each of the plurality of user stories corresponding to a predefined sprint for estimating a sprint velocity, and wherein the sprint velocity is an estimation of number of story points delivered for each of the plurality of user stories in the predefined sprint, wherein the overall size estimation is determined using a parametric analysis of the plurality of user stories by comparing the overall size of the plurality of user stories across sprints and one or more agile software development projects; and ascertain, by the processor, a consolidated effort for execution of the plurality of user stories based on the estimated sprint velocity along with a pre-baselined delivery rate, wherein the pre-baselined delivery rate is a quantitative measure of capability of the team in terms of time required for execution of the user story, the pre-baselined delivery rate is measured in person hours per story point (PH/ISP), and varied according to a technology of a user story. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method comprising:
-
obtaining, by a processor, the plurality of user stories associated with a software for size estimation analysis; computing, by the processor, a base size for each of the plurality of user stories based on a basic parameter from a plurality of basic parameters assigned to each of the multiple teams, wherein the basic parameter comprises a pre-defined threshold value representing a characteristic contributing to complexity of each of the user stories, wherein computing the base size for each of the plurality of user stories comprises; providing a plurality of options for the at least one basic parameter for each of the plurality of user stories, wherein the plurality of options are choices selected for a user story, in response to a basic parameter, and wherein the plurality of options provided as both values and text vary for each basic parameter from the plurality of basic parameters; allocating a predefined score, based on selection of one of the plurality of options for the at least one basic parameter; determining an intermediate base size of each user story, by consolidating predefined scores for each of the user stories for the at least one basic parameter; determining a stringent base size and a comfortable base size for each user story, wherein the stringent base size is an integer identified in Fibonacci series that is closest to and smaller than the intermediate base size of a respective user story, and wherein the comfortable base size is an integer of Fibonacci series closest to and larger than the intermediate base size of the respective user story; and computing the base size of each user story as one of the stringent base size and the comfortable base size closer to the intermediate base size of the respective user story, wherein a notification is provided to a user, if the computed base size is larger than the predefined threshold value as an indication to break of the each of the user story into multiple user stories; ascertaining, by the processor, an additional size for the plurality of user stories based on at least one additional parameter, wherein the at least one additional parameter comprises environmental factor affecting delivery of the software, wherein the additional size is indicative of a quantitative measure of complexity associated with delivery of the software impacting the execution of the plurality of user stories and wherein the ascertaining comprises; determining, by the processor, against each additional parameter, whether the impact of the each additional parameter is story-specific or sprint-specific; determining, by the processor, received score as an intermediate additional size for the plurality of user stories against each additional parameter based on the user input score and depending on whether the impact of the respective additional parameter is story-specific or sprint-specific; and computing, by the processor, the additional size for the plurality of user stories based on the intermediate additional size determined against each additional parameter; determining, by the processor, an overall size of the plurality of user stories by consolidating the base size for and the additional size for each of the plurality of user stories corresponding to a predefined sprint for estimating a sprint velocity, and wherein the sprint velocity is an estimation of number of story points delivered for each of the plurality of user stories in the predefined sprint, and wherein the overall size estimation is determined using a parametric analysis of the plurality of user stories by comparing the overall size of the plurality of user stories across sprints and one or more agile software development projects; and ascertaining, by the processor, a consolidated effort for execution of the plurality of user stories based on the estimated sprint velocity along with a pre-baselined delivery rate, wherein the pre-baselined delivery rate is a quantitative measure of capability of the team in terms of time required for execution of the user story, the pre-baselined delivery rate is measured in person hours per story point (PH/ISP), and varied according to a technology of a user story.
-
Specification