×

Work packet enabled active project schedule maintenance

  • US 8,452,629 B2
  • Filed: 07/15/2008
  • Issued: 05/28/2013
  • Est. Priority Date: 07/15/2008
  • Status: Expired due to Fees
First Claim
Patent Images

1. A system comprising:

  • a processor;

    a data bus coupled to the processor;

    a memory coupled to the data bus; and

    a computer-usable medium embodying computer program code, the computer program code comprising instructions executable by the processor and configured for maintaining a project schedule within at least one software factory by performing the steps of;

    launching a project management tool, wherein the project management tool comprises an end-to-end project plan for at least one project, and wherein said at least one project creates at least one software product using said at least one software factory in a global delivery network;

    appending a status block to a work packet that is utilized when executing said at least one project within said at least one software factory, wherein the work packet is a self-contained work unit that is assembled within said at least one software factory, wherein each work packet constitutes a contractual agreement that governs a relationship among a design center, a software factory governance board, a software factory operations unit, and an assembly line in the software factory, wherein the design center breaks a software project into major functional areas, wherein the software factory governance board determines whether or not to allow the software factory to accept the software project, wherein the software factory operations unit dispatches the software project to the assembly line, wherein the assembly line receives and executes work packets that are specified by the design center to create a customized deliverable unit of software, and wherein the work packet comprises a header, wherein the header comprises a unique identification number, a description of the work packet, a type description of the work packet, and an identifier of a parent object from which the work packet has inheritance, and wherein the work packet includes governance procedures, standards, reused assets, work packet instructions, an integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines, wherein the exit criteria is a checklist for returning the work packet and the customized deliverable unit of software to the software factory, and wherein the status block defines an execution status of the work packet;

    initiating execution of said at least one project;

    automatically triggering an alert from said at least one software factory whenever the execution status of the work packet changes; and

    transmitting the alert to the project management tool to update a project schedule for the project, wherein the completion status of the end-to-end project plan reflects a status of a project schedule for a project described by the end-to-end project plan.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×