# US 10,503,499 B2 · Methods and systems for managing agile development > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,503,499 B2 - Document ID: US10503499B2 - Status: Granted - Kind: B2 - Application number: 15/369,786 - Filed: 2016-12-05 - Published: 2017-06-08 - Granted: 2019-12-10 - Earliest claimed: 2015-12-04 - Assignees: David Anthony Bishop - Applicants: David Anthony Bishop - Inventors: David Anthony Bishop - Web page: https://patentgrep.com/patent/US10503499B2 ## CPC - G06F 8/77: Software metrics - G06Q 10/101: Collaborative creation, e.g. joint development of products or services - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Aspects of the present disclosure provide a method for managing product development that includes receiving development data. The method also includes recording an amount of time spent developing one or more project features; calculating, based at least in part on development data and the amount of time spent developing the feature, business momentum; and calculating, based on certain development data, project agility and market agility. ## Claims ### Claim 1 A method for managing product development comprising: receiving development data comprising: project requirements data comprising a time value indicating a time required for development for a feature of a project; and project timeline data comprising a feature deadline and a development deadline; recording an amount of time spent developing the feature; and calculating, based at least in part on comparing the time value against the difference between the time required for development for the feature and the amount of time spent developing the feature, business momentum. ### Claim 2 (depends on 1) The method claim 1 further comprising identifying whether a ratio of time value compared to the difference between the time required for development for the feature and the amount of time spent developing the feature fails to meet a predetermined threshold. ### Claim 3 (depends on 1) The method of claim 1, wherein the time value is expressed in units of ideal engineering days, each ideal engineering day equaling approximately six hours of work. ### Claim 4 (depends on 1) The method of claim 1 further comprising, responsive to receiving an indication to apply a hybrid-Agile approach, implementing stage gates, each stage gate being defined as a short-term deadline that occurs prior to the development deadline. ### Claim 5 (depends on 1) The method of claim 1 further comprising: receiving an indication of a request to manage development of a combination of software, firmware, and hardware; tracking development of the combination; and calculating business momentum for the combination. ### Claim 6 A method for managing product development comprising: receiving development data comprising: customer data including a first feature of a project; project timeline data including a feature deadline and a development deadline; budget data; and project requirements data comprising: requirements of the first feature; a first priority value indicating a level of priority of the first feature; a first penalty value indicating a penalty for failing to deliver the first feature by at least one of (i) the feature deadline and (ii) the development deadline; a first cost value indicating a financial cost of developing the first feature; and a first time value indicating a time required for development of the first feature; calculating, project agility by calculating the ratio of the time value compared to an amount of time remaining until the feature deadline; and calculating market agility by, at least in part, calculating the ratio of the cost value compared to the budget data. ### Claim 7 (depends on 6) The method of claim 6 further comprising calculating an average of the project agility and the market agility. ### Claim 8 (depends on 7) The method of claim 7, wherein the average is referred to as agile vorticity. ### Claim 9 (depends on 6) The method of claim 6 further comprising calculating a sum of the project agility and the market agility. ### Claim 10 (depends on 9) The method of claim 9, wherein the sum is referred to as agile vorticity. ### Claim 11 (depends on 6) The method of claim 6 further comprising calculating a product of the project agility and the market agility. ### Claim 12 (depends on 11) The method of claim 11, wherein the product is referred to as agile vorticity. ### Claim 13 (depends on 6) The method of claim 6 further comprising, upon receiving an indication to apply a hybrid-Agile approach, implementing stage gates, the stage gates being defined as short-term deadlines that all occur prior to the development deadline. ### Claim 14 (depends on 6) The method of claim 6 further comprising: receiving an indication of a request to manage development of a combination of software, firmware, and hardware; and tracking development of the combination; and calculating business momentum for the combination. ### Claim 15 (depends on 6) The method of claim 6 further comprising: receiving a feature change request that includes a second feature, wherein the second feature supplements or replaces the first feature; receiving second project requirement data corresponding to the feature change request, the second project requirement data comprising: requirements of the second feature; a second priority value indicating a level of priority of the second feature; a second penalty value indicating a penalty for failing to deliver the second feature by the feature deadline and/or development deadline; a second cost value indicating a financial cost of developing the second feature; and a second time value indicating a time required for development of the second feature; and calculating an updated project agility, which relies at least in part on the second time value and the feature deadline. ### Claim 16 A method for managing product development comprising: receiving development data comprising: project timeline data comprising a first feature deadline and a development deadline; customer data comprising a first feature of a project; budget data; and project requirements data comprising: a time value indicating a time required for development of the first feature; requirements of the first feature; a first priority value indicating a level of priority of the first feature; a first penalty value indicating a penalty for failing to deliver the first feature by the feature deadline and/or development deadline; a first cost value indicating a financial cost of developing the first feature; and a first time value indicating a time required for development of the first feature; recording an amount of time spent developing the project feature; calculating, based at least in part on comparing the time value against the difference between the time required for development for the feature and the amount of time spent developing the feature, business momentum; calculating, based at least in part on the time value and the feature deadline, project agility; and calculating, based at least in part on the cost value and the budget data, market agility. ### Claim 17 (depends on 16) The method of claim 16 further comprising: receiving a feature change request comprising a second feature, wherein the second feature supplements or replaces the first feature; receiving second project requirement data corresponding to the feature change request, the second project requirement data comprising: requirements of the second feature; a second priority value indicating a level of priority of the second feature; a second penalty value indicating a penalty for failing to deliver the second feature by the feature deadline and/or development deadline; a second cost value indicating a financial cost of developing the second feature; and a second time value indicating a time required for development of the second feature; and calculating, based at least in part on the second time value and the feature deadline, an updated project agility.