Abstract: A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software.

Abstract: A method, system and computer-readable medium for creating software in a standardized manner are presented. The method includes the steps of: receiving, at a software factory, a description of software needs from a customer; creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs; inducting the project proposal into the software factory, wherein inducting the project proposal initially evaluates the project proposal's compatibility with a capacity of the software factory; parsing the project proposal into major functional areas; retrieving work packets that are appropriate for the project proposal, wherein the work packets are pre-stored, reusable, self-contained, discrete units of software code; assembling the work packets into a deliverable software; testing the deliverable software; and delivering the deliverable software to the customer.

Abstract: A method, system, and computer-readable medium for rapid on-boarding of a software factory are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: identifying choke-points in a first software project; creating a checklist of identifying factors that caused the choke-points that were identified in the first software project; receiving a new software project at a software factory, wherein the new software project is in a same software category as the first software project; presenting the checklist for the first software project; receiving new answers to the checklist; determining if the software factory is ready to handle the new software project based on the new answers to the checklist; and in response to determining that the software factory is ready to handle the new software project, configuring the software factory in a same configuration as that previously used by the first software project.

Abstract: A method, system, and computer-readable medium for maintaining a health of a software factory that creates custom software in a standardized manner is presented. In a preferred embodiment, the method includes the steps of: defining work packets to perform sub-functions of a custom software; tracking a transmission of the work packets to an assembly line in a software factory; monitoring any retrieval of software artifacts that are used to create the work packets; monitoring any on-going changes of work activities that are contained in the work packets; determining if execution of the work packets conforms to governance guidelines for the software factory; monitoring the software factory to ensure that the work packets comply with an architecture of the software factory; tracking quality metrics for an execution of the work packets in an assembly line in the software factory; and transmitting all tracked and monitored information described above to a dashboard.

Abstract: A method, system, and computer-readable medium for assembling work packets within a software factory are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: collecting a plurality of software artifacts that have been archived during an assembly of previous work packets; collecting a plurality of metrics that have been utilized during the assembly of previous work packets; defining a template for a new work packet, wherein the template for the new work packet is created by a packet definition process that defines attributes that are needed in the new work packet; selecting requisite software artifacts from the plurality of software artifacts; selecting requisite metrics from the plurality of metrics; and sending the template, requisite software artifacts and requisite metrics to a packet assembly process, wherein the packet assembly process assembles the requisite software artifacts to create the new work packet.

Abstract: A computer-implemented method, system, and computer-readable medium for inducting a software project into a software factory is presented, wherein an induction process identifies what processes and sub-processes are needed to create the software factory, and wherein the induction process identifies potential risks to the software factory.