Integrated advance scheduling of indeterminate projects in an integrated development process

• US 7,559,049 B1
• Filed: 12/08/2003
• Issued: 07/07/2009
• Est. Priority Date: 12/08/2003
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Hemmat, Merzad, Branch, Bill G. Jr.
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): DAO, THUY CHAN
• Application Number:
  US10/730,601
• Time in Patent Office: 2,038 Days
• Field of Search: 717/101, 717/100
• US Class Current: 717/102
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change

Abstract

A method for scheduling software releases for a computer system. The method can consist of planning a series of releases for a given time period, each release having an initial allocation of capacity. Information regarding proposed software projects is reviewed and initial estimates of cost and duration for such projects are provided to customers for approval to move into detailed analysis. On receiving approval for each project, the planned series of releases and the initial estimate of cost and duration are reviewed and capacity is reserved in a release having available capacity. As detailed analyses and customer feedback change the scope of the projects approved for further analysis, the reserved capacity is adjusted and, where available capacity is not present, the reserved capacity is moved to a later release. As detailed analyses are completed and projects finally approved, the scheduled reservations are booked in the releases.

Claims

1. A computer implemented method for scheduling resources to be used in a software development project comprising:

a planning department receiving information from a customer regarding a software development project to be completed through define, discover, design, develop, and deploy phases, the software development project is one of a plurality of software development projects bundled in a release, wherein the release has a predefined resource capacity;

the planning department initially reviewing the received information and providing initial feedback in the define phase prior to completing a detailed requirements analysis in the discover phase, wherein the discover phase is in support of business requirements which are documented in a centralized repository and enable traceability and reuse in subsequent projects, and wherein the detailed requirements analysis includes a plurality of steps including one or more of functional requirements modeling, system requirements modeling, and application integration modeling;

the planning department reserving resources for the software development project from the predefined resource capacity for the release via a software tool that uses past experience and the information received from the customer as input and produces an estimate of resources required for the software development project as output prior to completing the detailed requirements analysis, wherein reserving resources reduces availability of the predefined resource capacity in the release for subsequent software development projects;

the planning department confirming the reserved resources at each of the plurality of steps in the detailed requirements analysis;

the planning department offering the customer a final contract upon completion of the plurality of steps of the detailed requirement analysis, wherein the final contract describes the resources to be used for completion of the project; and

the planning department storing a list of the reserved resources on a computer readable medium.

2. The method of claim 1, further comprising after reserving resources:

scheduling the reserved resources as agreed upon in the contract upon approval of the contract by the customer through the planning department.

3. The method of claim 2, wherein one of the plurality of steps of the detailed requirements analysis comprises:

a functional requirements modeling step.

4. The method of claim 2, wherein one of the plurality of steps of the detailed requirements analysis comprises:

a system requirements modeling step.

5. The method of claim 2, wherein one of the plurality of steps of the detailed requirements analysis comprises:

an application integration modeling step.

6. The method of claim 2, wherein one of the plurality of steps of the detailed requirements analysis comprises:

a contract development step.

7. The method of claim 1, further comprising:

reserving resources for a second software development project subsequent to reserving resources for the software development project and prior to completing the detailed requirements analysis for the second software development project, wherein the resources for the second software development project are reserved from a predefined resource capacity for a second release subsequent to the release based on the release not having sufficient available resource capacity for the second software development project.

8. The method of claim 1, further comprising:

a customer providing second information regarding a second software development project to be completed through define, discover, design, develop, and deploy phases;

a planning department initially reviewing the provided second information and providing initial feedback in the define phase prior to completing the detailed requirements analysis in the discover phase;

the planning department reserving resources for the second software development project from a predefined resource capacity for a second release based on the second information prior to completing the detailed requirements analysis for the second software development project and based on the release not having sufficient available resource capacity for the second software development project due to the reservation of the resources for the software development project in the release.

10. The method of claim 8 wherein the managing of the customer'"'"'s expectations comprises the planning department giving the customer an estimate of the likely duration of the project based on past experience and on the preliminary information provided by the customer.

11. The method of claim 10 wherein the customer'"'"'s approval of the project for further analysis is based on the estimate of the likely duration of the project.

9. A computer implemented method for scheduling resources needed for a project to be completed through define, discover, design, develop, and deploy phases, comprising:

a planning department managing a customer'"'"'s expectations about the project based on preliminary information the customer provides to the planning department, wherein the project is one of a plurality of projects bundled in a release, wherein the release has a predefined resource capacity;

the planning department receiving approval of the project from the customer, in the define phase, for further analysis in the discover phase, wherein the discover phase is in support of business requirements which are documented in a centralized repository and enable traceability and reuse in subsequent projects, and wherein the further analysis includes a plurality of steps including one or more of functional requirements modeling, system requirements, and application integration modeling;

the planning department reserving resources for the project from the predefined resource capacity for the release, wherein the reserving of resources is aided by a software tool that uses past experience and the preliminary information as input and produces an estimate of the resources required as output, wherein reserving resources reduces availability of the predefined resource capacity in the release for subsequent projects;

the planning department confirming the reserved resources at the end of at least one of the plurality of steps in the further analysis;

upon completion of the plurality of steps in the further analysis, the planning department offering the customer a final contract describing resources to be used for completion of the project;

upon approval of the contract by the customer, the planning department scheduling the reserved resources as agreed upon in the final contract; and

the planning department storing a list of the reserved resources on a computer readable medium.

12. The method of claim 9 wherein the confirming of the reserved resources comprises determining whether the results of the further analysis indicate whether modifications are needed in the reserved resources.

13. The method of claim 12 wherein, if it is determined that modifications are needed in the reserved resources, alerts are sent to projects dependent on a project for which modifications are needed in the reserved resources, the alerts informing the dependent projects that further analysis may be needed.

14. The method of claim 9 wherein the further analysis comprises a functional requirements modeling step, a system requirements modeling step, an application integration modeling step, and a contract development step.

15. A computer implemented method for scheduling resources to be used in a software development project comprising:

a customer submitting information about the software development project to an Information Technology department, wherein the software development project is completed through define, discover, design, develop and deploy phases, and wherein the software development project one of a plurality of software development projects bundled in a release, wherein the release has a predefined resource capacity;

the Information Technology department analyzing the feasibility of the project and estimating its cost in the define phase;

the customer deciding whether to proceed to the discover phase with the project based on the analysis of feasibility and estimate of cost, wherein the discover phase is in support of business requirements which are documented in a centralized repository and enable traceability and reuse in subsequent projects;

upon deciding to proceed to the discover phase, the customer prioritizing and funding the project and the Information Technology department reserving resources for the software development project from the redefined resource capacity for the release, wherein the reserving of resources is aided by a software tool that uses past experience and the information submitted by the customer as input and produces an estimate of the resources required as output, wherein reserving resources reduces availability of the predefined resource capacity in the release for subsequent projects;

the Information Technology department modeling in the discover phase at least one requirement for the project after deciding to proceed to the discover phase, wherein modeling the at least one requirement includes one or more of function requirements modeling, system requirements modeling, and application integration modeling;

upon completion of the at least one requirement modeling, the Information Technology department giving the customer a final contract with an estimate of resources needed for completion of the project; and

booking the reserved resources as agreed on in the final contract upon approval of the final contract with the estimate by the customer; and

the planning department storing a list of the reserved resources on a computer readable medium.

16. The method of claim 15 further comprising, during the requirement modeling, the Information Technology department determining whether the results of the modeling of a requirement indicate that modifications to the requirement are needed.

17. The method of claim 16 wherein, when modifications are needed, alerts are sent to projects dependent on a project for which modifications are needed in the reserved resources, the alerts informing the dependent projects that further analysis may be needed.

18. A computer implemented method for scheduling software releases for a computer system comprising:

planning a series of releases for a given time period through define, discover, design, develop, and deploy phases, wherein each release has an initial allocation of resource capacity;

reviewing information regarding proposed software projects and providing initial estimates of cost and duration for such projects to customers in the define phase for approval to move into a detailed analysis in the discover phase, wherein the discover phase is in support of business requirements which are documented in a centralized repository and enable traceability and reuse in subsequent projects;

on receiving approval for the detailed analysis for each project, reviewing the planned series of releases and the initial estimate of cost and duration for the approved project and reserving capacity for the approved project in a release having sufficient available resource capacity in the initial allocation of capacity of the release, wherein the reserving of capacity for the approved project is aided by a software tool that uses past experience and the information regarding the approved project as input and produces an estimate of the resources required as output; and

, wherein reserving capacity reduces availability of the initial allocation of resource capacity of the release for subsequent projects, and wherein the detailed analysis includes one or more of functional requirements modeling, system requirements modeling, and application integration modeling;

adjusting the reserved capacity as the detailed analysis and as customer feedback change the scope of the projects approved for the detailed analysis and, where available capacity is not present, moving the reserved capacity to a later release;

as the detailed analysis of the approved projects are completed and the approved projects are finally approved for development through a contract, booking the reserved capacity in the releases; and

the planning department storing a list of the reserved capacity on a computer readable medium.

19. The method of claim 18, wherein reviewing the planned series of releases and the initial estimate of cost and duration for the approved project further comprises:

reviewing the preliminary test approach as determined in the initial review, the type of lab required, and the available capacity in the required lab.

20. The method of claim 18, wherein reviewing the planned series of releases and the initial estimate of cost and duration for the approved project further comprises:

reviewing dependencies with other projects.

21. The method of claim 18, wherein reviewing the planned series of releases and the initial estimate of cost and duration for the approved project further comprises:

reviewing the available workforce in the required areas.

22. The method of claim 18, further comprising prior to planning a series of releases for a given time period:

receiving from customers estimates of total time required for proposed projects in the given time period; and

,

adding the received estimates to get a total amount of time for the given time period and dividing the time into releases throughout the time period.

23. The method of claim 22, wherein the number and capacity of the planned releases is determined by the total amount of time received.

24. The method of claim 22, wherein an extra percentage of time is added to the capacity allocated to each release.