# US 2014/0195292 A1 · Techniques for instantiating and configuring projects > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195292 A1 - Document ID: US20140195292A1 - Status: Published application - Kind: A1 - Application number: 14/148,275 - Filed: 2014-01-06 - Published: 2014-07-10 - Earliest claimed: 2007-07-31 - Assignees: Novell, Inc. - Applicants: Novell, Inc. - Inventors: Michel Shane Simpson; Volker Gunnar Scheuber-Heinz; Lee Edward Lowry; Stephen R. Carter - Web page: https://patentgrep.com/patent/US20140195292A1 ## CPC - G06Q 10/06313: {Resource planning in a project environment} - G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling - G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations - G06Q 10/06311: {Scheduling, planning or task assignment for a person or group} - G06Q 10/1097: {using calendar-based scheduling for task assignment} - 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 Techniques for project management instantiation and configuration are provided. A master project includes policy directives that drive the dynamic instantiation and configuration of resources for a project. The resources are instantiated and configured on demand and when resources are actually requested, in response to the policy directives. ## Claims ### Claim 1 (canceled) ### Claim 2 A method, comprising: managing, by a device, a project that spans multiple project environments and devices; and dynamically delivering, by the device, resources, during appropriate stages of a lifecycle for the project, to each project environment on demand. ### Claim 3 (depends on 2) The method of claim 2, wherein managing further includes identifying components of the project from a project definition. ### Claim 4 (depends on 3) The method of claim 3, wherein identifying further includes parsing metadata that represents the project definition to identify the components. ### Claim 5 (depends on 3) The method of claim 3, wherein identifying further includes parsing a virtual project definition that logically represents the project definition to identify the components. ### Claim 6 (depends on 3) The method of claim 3, wherein identifying further includes representing selective groupings of the components as independent sub projects within the project. ### Claim 7 (depends on 6) The method of claim 6, wherein representing further includes recognizing at least one masked sub project that is to be hidden from view of project participants associated with the project. ### Claim 8 (depends on 2) The method of claim 2, wherein managing further includes assembling a series of definitions for multiple independent projects to form a project definition that defines the project and the resources. ### Claim 9 (depends on 2) The method of claim 2, wherein dynamically delivering further includes configuring the resources before delivery to ensure that each resource is configured for use within particular stages of the project. ### Claim 10 (depends on 2) The method of claim 2, wherein dynamically delivering further includes delivering each resource to a particular project environment when requested from a different resource within that particular project environment. ### Claim 11 (depends on 10) The method of claim 10, wherein delivering further includes preventing at least one delivery of a particular resource to the particular project environment based on evaluation of at least one condition in a project definition for the project. ### Claim 12 (depends on 2) The method of claim 2, wherein dynamically delivering further includes configuring each resource within a processing environment for a particular project environment receiving that resource. ### Claim 13 (depends on 12) The method of claim 12, wherein configuring further includes causing each resource to be instantiated within the processing environment. ### Claim 14 A method, comprising: managing, by a processor, a lifecycle for a project over disparate processing environments and devices; and dynamically causing, by the processor, each portion of the project to be instantiated within a particular processing environment when a determination is made that access to that portion is in a need. ### Claim 15 (depends on 14) The method of claim 14, wherein dynamically causing further includes, causing at least one portion to be instantiated within the particular processing environment as a hidden portion that is unavailable for access or view by a participant in that particular processing environment. ### Claim 16 (depends on 14) The method of claim 14, wherein dynamically causing further includes configuring resources associated with each portion before causing instantiation. ### Claim 17 (depends on 14) The method of claim 14, wherein dynamically causing further includes determining the need based on a detected completion of a task associated with the project. ### Claim 18 (depends on 14) The method of claim 14, wherein dynamically causing further includes determining the need based on a request issued from a resource operating within at least one of the particular processing environments. ### Claim 19 A system, comprising: a processor; and a project module, the project module operative to (i) execute on the processor; (ii) manage a lifecycle of a project over multiple disparate processing environments, and (iii) dynamically deliver portions associated with the lifecycle to each of the processing environments on demand. ### Claim 20 (depends on 19) The system of claim 19, wherein the project module is further operable to (iv) configure resources associated with each portion before dynamically delivery. ### Claim 21 The system of claim. 19, wherein the project module is further operable to (iv) enforce at least one policy restriction on at least one portion before delivery.