FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention: PROJECT MANAGEMENT
2. Applicant(s)
NAME NATIONALITY ADDRESS
TATA CONSULTANCY Indian Nirmal Building, 9th Floor, Nariman Point, SERVICES LIMITED Mumbai-400021, Maharashtra, India
3. Preamble to the description
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.

TECHNICAL FIELD
[0001] The present subject matter relates, in general, to project management and,
particularly but not exclusively, to a computer-implementable project management system and method.
BACKGROUND
[0002] A project may be thought of as a collection of activities and tasks designed
to achieve a specific goal of an organization with specific performance or quality requirements while meeting any time and resource constraints. Project management refers to managing the activities that lead to the successful completion of a project. Project management may also be defined as the application of knowledge, skills, tools, and techniques to meet the project requirements. A lifecycle of project management is typically characterized by the following phases: initiating, planning, executing and controlling, and closing.
[0003] Several project management systems and methodologies are implemented
by organizations to ensure that the numerous projects undertaken by the organizations can be brought to completion. Efficiency of a project may depend on the timely completion of the project, completion within a stipulated budget, objectives met in an effective manner, etc. It is important to identify efficient methodologies for managing projects as they may be beneficial not only for a current project but also for future projects.
SUMMARY
[0004] This summary is provided to introduce concepts related to a system and
method of project management in an organization and these concepts are further described below in the detailed description. This summary is not intended to identify essential features of the present subject matter nor is it intended for use in determining or limiting the scope of the present subject matter.
[0005] System(s) and method(s) for management of a project are described. In one
implementation, the method comprises identifying at least two phases of the project. The at least two phases comprise one research level phase and one project level phase. The

method also comprises identifying tasks associated with each of the at least two phases, identifying a number of failure cycles in the research level phase, and evaluating an efficiency of the project based on the tasks and the number of failure cycles.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The detailed description is described with reference to the accompanying
figures. In the figures, the left-most digit(s) of a reference number identifies the figure in
which the reference number first appears. The same numbers are used throughout the
drawings to reference like features and components.
[0007] Figure 1 illustrates a network environment implementing a project
management system for management of a project, in accordance with an implementation
of the present subject matter.
[0008] Figure 2 illustrates a method for management of a project, in accordance
with an implementation of the present subject matter.
DETAILED DESCRIPTION
[0009] The present subject matter relates to systems and methods for management
of one or more projects. Project management implemented through the systems and the
methods of the present subject matter includes assessment of a project and project
management based on evaluation of efficiency of the project and project execution time.
[0010] A project may be defined as a temporary endeavor undertaken to create a
unique product or service. Each project may be characterized by various project dimensions, such as tasks required for creating the product or service, the human and infrastructural resources required for executing each of the tasks, the end result of the project, and technology using which the project is created. Each of the project dimensions is associated with project attributes, such as cost, scope, schedule and quality (CSSQ). For example, cost may be associated with the cost of recruiting human resources for a predefined task, and schedule may be associated with the time required for creating the product. Similarly, quality may be associated with technology used, and scope may be associated with desirable end result of the project.
[0011] A project typically follows a lifecycle which may include various project
phases. The project phases include an initiation phase, a planning phase, an execution and

control phase and a closing phase. Each of the project phases involves a variety of tasks and sub-tasks based on the project dimensions and project attributes. For example, the initiation phase may involve tasks, such as identifying project objectives, identifying stakeholders, and obtaining and confirming sponsorships. Efficient management of projects in an organization is an increasing problem as the number and complexity of projects handled by the organization may be high. Thus, an organization generally implements a method and system for project management. Role of project management is to identify the tasks and sub-tasks for each of the project phases and ensure that the project goes through all the identified tasks and sub-tasks of the each project phase in an efficient manner before the completion of the project. The overall objective may be to accelerate a product development schedule or maximize efficiency of resource utilization, minimize development cost, and resulting product cost.
[0012] Further, review or assessment to evaluate performance, efficiency and
execution time of a project, upon its completion, is an important task. Conventional methods and systems assess a project to evaluate its performance, efficiency and execution time on the basis of tasks and sub-tasks involved at the project phases. Conventional methods and systems do not consider tasks at a research phase of a project for the assessment. With this assessment, the evaluated efficiency and execution time of the project is not substantially accurate.
[0013] Systems and methods for project management are described herein. The
systems and the methods described herein also evaluate efficiency and execution time of projects to assess the projects and the project management.
[0014] A project for creation of one or more products or services may follow a
lifecycle which may include a research level phase and one or more project level phases. The research level phase may pertain to prototyping of the product or the service, and the project level phases may pertain to releasing the product or the service for users or in the market. The project level phase may include a project initiation phase, a project planning phase, a project execution and control phase, and a project closing phase. As mentioned earlier, each phase of the lifecycle may involve a plurality of tasks and sub-tasks that may be performed before the completion of that phase. The tasks and the sub-tasks associated with the research level phase hereinafter may be referred to as research level tasks, and

the tasks and the sub-tasks associated with each of project level phases hereinafter may
be referred to as project level tasks. The details of the research level tasks and the project
level tasks for each of the project level phases are described later in the description.
[0015] In an implementation, the research level phase may be carried out before
starting with the project level phases or may be carried out as a part of a project level phase, for example the project initiation phase. The research level phase involving the prototyping of the product or the service may be an important requirement. This may benefit the project level tasks, production and performance delivery before releasing and marketing the product or the service. A successful prototyping may assist in setting the project level objectives project level CSSQ and deliverables.
[0016] In the research level phase, for the creation of a product or a service, a
problem may be conceived and objectives may be obtained first, followed by identification of research team members, discussion with the research team members, and defining of research level CSSQ. Further, the prototyping-related tasks may involve research analysis, prototype development, prototype analysis, etc. It is possible that failures are observed during the prototyping stage. Failures in the product or service prototype could be due to poor prototype design, poor or inefficient functioning, poor performance, etc., which may influence in meeting the objectives. In such cases, reworking may be done till a successful prototype is obtained that meets the objectives and other similar aspects.
[0017] Further, it is possible that the research level phase may observe multiple
failures during the prototyping of product or service. Failures may influence the lifecycle
of the project in terms of overall cost, budget, scheduling and such, which may affect the
execution time and efficiency of the project. Thus, it is important to take note of the
research level phase and the failures observed therein for assessing the project and the
project management and evaluating efficiency and execution time of the project.
[0018] Failed tasks and sub-tasks in a phase or a failed phase of the project may
progress circularly. The circular progress of the failed phase, tasks or sub-tasks is indicative of repetitions, may be iterative, that are carried out till a success is achieved. Thus, for the purpose of the present subject matter, a failed phase and a set of failed tasks or sub-tasks may be understood as a failure cycle. On the other hand, successful tasks and

sub-tasks in a phase or successful phase of the project may progress linearly, as the successful phase, tasks or sub-tasks need not be repeated.
[0019] The methodology followed for the project management for a project,
according to the present subject matter, is based on identification of two or more phases of the project and identification of tasks associated with the identified phases. For the purpose of the description hereinafter the tasks may include the sub-tasks. The phases identified may be from a research level phase and one or more project level phases, and corresponding tasks may be from research level tasks and project level tasks. In an implementation, the research level tasks and the project level tasks may be based on one or more project-related attributes, such as objectives, CSSQ, deliverables and the like. The methodology, according to the present subject matter, also identifies a number of failure cycles in the research level phase, and subsequently assesses the project by evaluating efficiency of the project based on the identified research level tasks, project level tasks and number of failure cycles.
[0020] In an implementation, execution time for each of the research level tasks and
execution time for each of the project level tasks of each project level phase are obtained.
For the purpose of determining an execution time of the entire project, failed research
level tasks associated with each of the failure cycle is identified and an execution time for
the failure cycles based on execution times for the failed research level tasks is
determined. In an implementation, the execution time of the entire project is determined
based on the execution time for the failure cycles, execution times for the successful
research level tasks and the execution times for the project level tasks. The details of
determination of the execution time for the project are described later in the description.
[0021] Consideration of failure cycles and consideration of execution time for the
failure cycles facilitates in estimating the substantially true efficiency and the substantially true execution time for the project. The consideration of failure cycles in efficiency evaluation may also be suggestive to people involved in the project to find ways for reducing the failure cycles and thus reduce the execution time for the current project as well as for future projects. Thus, the methodology of the present subject matter for project management and evaluation of efficiency and execution time of the project is substantially more effective in comparison to the conventional methodologies.

[0022] While aspects of described systems and methods for the project
management can be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system(s).
[0023] Figure 1 illustrates a networking system 100 implementing a project
management system 102 configured to manage projects, according to an implementation of the present subject matter. The networking system 100 may be understood as a public or a private networking system. In an implementation, the project management system 102 is configured to monitor, regulate, control and coordinate the project in an organization or an enterprise by creating an effective project management framework. The project management system 102 is also configured to assess the projects for their efficiency and execution time. The project management system 102 may be implemented in a computing device that includes, but is not limited to, a desktop PC, a notebook, a portable computer, a smart phone, a PDA, a tablet, and the like.
[0024] During the project management, the project management system 102 may
communicate with a server 104 hosting data and various applications required for the purpose of project management. The server 104 may be implemented as any of a variety of computing devices, including, for example, a server, a workstation, and a mainframe computer. The server 104 may be one, or combination of one or more, storage server or network server.
[0025] The project management system 102 of the present subject matter is
communicatively coupled to the server 104 over a network 106 through one or more communication links. The communication links between the project management system 102 and the server 104 are enabled through a desired form of communication, for example, via dial-up modem connections, cable links, and digital subscriber lines (DSL), wireless or satellite links, or any other suitable form of communication. The network 106 may be understood as a network, including personal computers, laptops, various servers and other computing devices.
[0026] Further, the network 106 may be a wireless network, a wired network, or a
combination thereof. The network 106 can also be an individual network or a collection of many such individual networks, interconnected with each other and functioning as a

single large network, e.g., the Internet or an intranet. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and such. The network 106 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), etc., to communicate with each other. Further, the network may include network devices, such as network switches, hubs, routers, and Host Bus Adapters (HBAs), for providing a link between the project management system 102 and the server 104. The network devices within the network 106 may interact with the project management system 102 and the server 104 through the communication links.
[0027] In an implementation, the server 104 is implemented with a knowledge base
108. The knowledge base 108 may store and provide information or data that may be
utilized for the purposes of project management as described in the description
hereinafter. The knowledge base 108 may include rules, procedural representations, use
case scenarios, etc. These rules are implemented as conditional statements providing a
result in response to various scenarios. In one implementation, the knowledge base 108 is
periodically updated and modified to reflect new rules and best practices followed in
industries, corporate organizations and/or academic organizations.
[0028] Further, the project management system 102 may be a software-based
implementation or a hardware-based implementation or a combination thereof. In one implementation, the project management system 102 may be implemented on the server 104 or may be implemented external to the server 104 and accessed for the purposes of assessing maturity of business processes.
[0029] The project management system 102 includes one or more processor(s) 110,
interface(s) 112, and a memory 114 coupled to the processor(s) 110. The processor 110 can be a single processor unit or a number of units, all of which could include multiple computing units. The processor 110 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 110 is

configured to fetch and execute computer-readable instructions and data stored in the
memory 114.
[0030] The interface(s) 112 may include a variety of software and hardware
interfaces, for example, interfaces for peripheral device(s), such as a keyboard, a mouse,
an external memory, and a printer. The interface(s) 112 may enable the project
management system 102 to communicate with other devices, such as external computing
devices and external databases.
[0031] The memory 114 may include any computer-readable medium known in the
art including, for example, volatile memory such as static random access memory
(SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory,
such as read only memory (ROM), erasable programmable ROM, flash memories, hard
disks, optical disks, and magnetic tapes.
[0032] The memory 114 includes module(s) 116 and data 118. The modules 116
include routines, programs, objects, components, data structures, and the like, which
perform particular tasks or implement particular abstract data types. The modules 116
further include modules that supplement applications on the project management system
102, for example, modules of an operating system. The data 118, amongst other things,
serves as a repository for storing data that may be processed, received, or generated by
one or more of the modules 116.
[0033] In an implementation, the modules 116 of the project management system
102 include a phase and task identification (PTI) module 120, a failure identification
module 122, an evaluation module 124 and other module(s) 126. The other module(s)
126 may include programs or coded instructions that supplement applications and
function, for example, programs in the operating system of the project management
system 102.
[0034] In an implementation, data 118 include phase and tasks data 128, time and
efficiency data 130 and other data 132. The other data 132 includes data generated as a
result of the execution of one or more modules in the other module(s) 126.
[0035] In an implementation, a user may access the project management system
102 for managing and assessing one or more projects. For the purposes of the description
herein, the user may be understood as a professional who has skills and capability of

managing projects. The user may include one or more of a research head, a project head, a project manager, project consultant or any other member involved in the project. In an implementation, the user may be an authentic user who is allowed to access the project management system 102. In an implementation, the user is provided with a user interface, such as a graphic user interface (GUI), which may be used for the purposes of project management.
[0036] In an implementation, the user identifies a project to be managed, and the
project management system 102 may accordingly receive a request from the user for the project management. The project may be for creation of one or more products, for example a machine, an apparatus, a component and like, or one or more services, for example a banking service, a telecommunication service and like. The PTI module 120 identifies at least two phases of the project. The PTI module 120 further identifies tasks associated with the identified phases.
[0037] In an implementation, the PTI module 120 may automatically fetch the tasks
on a predefined basis from an external database or allow the user to manually feed or fetch the tasks associated with the project. In an implementation, the knowledge base 108 may have the information or data related to phases and associated tasks, and the project management system 102 may communicate with the knowledge base 108 for the identification of the phases and the tasks.
[0038] The phases of the project may include a research level phase and at least one
of a project level phase, such as a project initiation phase, project planning phase, a project execution and control phase and a project closing phase. The tasks may be from the research level tasks and the project level tasks. In an implementation, the research level tasks and the project level tasks may include conventional tasks and sub-task. The project is understood to follow the research level tasks and the project level tasks before its completion. Tables 1 to 5 provide details for the phases of the project, and tasks/sub-tasks associated with each of the phases. Tables 1 to 5 are only for the purpose of explanation, and other tasks or sub-tasks may also be considered.

TABLE 1
Phase Task Sub-task
Research Level Conceiving of a → discussions between project head,

Phase problem associated with one of a product and a service research head, project manager

Obtaining of Objectives → discussions between project head, research head, project manager

Team members identification for the research level phase → discussions between project head, research head, project manager
→ identify roles and responsibilities of team members
→ obtain approval

Defining research level cost, scope, schedule and quality standards → discussions between project head, research head, project manager, team members, sponsors, stakeholders
→ obtain approval

Research analysis and Designing → literature survey
→ understanding of the state of the art
→ modeling, simulations → setting up of infrastructure

Prototype development → setting up of required resources
→ execution of activities for development of protoype

Prototype analysis → design and quality analysis
→ functional and performance analysis
→ efficiency analysis
TABLE 2
Phase Task Sub-task
Project Initiation Phase Project database development —* maintain name, code and type of project; required-by-date, etc.

Project charter creation —> identify project level objectives
—> define project level cost, scope, schedule, quality standards
—► identify initial project team members —+ identify stakeholders —► identify roles and responsibilities of team members and stakeholders
—> establish work breakdown structure of
team members, project manager, project
head
—> identify risks, related to resource

availability, cost overrun, schedule overrun, scope creep and technology, involved in the project

Obtaining sponsorship → discussion between project manager, stakeholders, sponsors

Review of the project level tasks associated with the project initiation phase → discussion between project manager, stakeholders, sponsors

Obtaining an approval to move a next project level phase → discussion between project manager, stakeholders, sponsors
TABLE 3
Phase Task Sub-task
Project Planning Phase Estimation of deliverables, activities and efforts for the project → prior knowledge of past enterprise, industrial or academic projects
→ knowledge of organizational standards

Refinement of project cost, scope, schedule, quality standards → discussion between project manger, stakeholders, sponsors, team members

Defining strategies for mitigating risks associated with the project, wherein the risks comprises risks related to technology, resource availability, cost overrun, scope creep and schedule overrun → discussion between project manger, stakeholders, sponsors, team members, experts

Establishing a communication plan → establish reporting hierarchy, frequency of reporting, method and medium of reporting

Change management required for the
project → discussion between project manger and team members

Establishing a project execution plan → establish various activities based on deliverables
→ resource assignment

Review of the project level tasks associated with the project planning phase → discussion between project manager, stakeholders, sponsors

Obtaining an approval to move to a next project level phase → discussion between project manager, stakeholders, sponsors
TABLE 4
Phase Task Sub-task
Project Execution and Control Phase Project execution management → execution of project execution plan
→ ensuring all functions and activities are performed correctly and on time
→ updation of progress on daily basis
→ monitoring, analysis and controlling of any deviations in functions and activities

Management of project cost, scope, schedule and quality standard → management of change to scope
→ management of changes to schedule
→ implementation of quality assurance and quality control proedures
→ control and manage costs based on a defined budget

Monitoring and controlling of risks associated with the project → utilization of defined strategies for avoiding or mitigating risks
→ application of new strategies for avoiding or mitigating new risks

Review of the project level tasks associated with the project execution and control phase → discussion between project manager, stakeholders, sponsors

Obtaining an approval to move to a next project level phase → discussion between project manager, stakeholders, sponsors
→ obtain acknowledgement from project manager, customer decision-maker, stakeholders, sponsors
TAB LE5
Phase Task Sub-task

Project Closing Phase Conducting a post-implementation review for the project → assessment of cost, schedule, resources and quality
→ obtain survey feedback on the project from team members, customer, users, stakeholders, sponsors
→ derive and store lessons learned form the project
→ derive and store best practices for future projects

Performing an administrative closeout for the project → provide feedback to team members
→ acknowledgment of efforts
→ report improvements in the process to question-answer team for changing procedures accordingly
→ update skills inventory
→ storing all project related data, information and material in a database
[0039] In an implementation, with the identified research level tasks and project
level tasks for each of the phases, the user may be able to track tasks to be performed during the course of the project. In an implementation, the user may maintain a check-list comprising the identified research level tasks and the project level tasks. Further, in an implementation, the user may feed data comprising information associated with each task. Such data may comprise start and end date of a task, time spent for completing a task and comments comprising relevant details for a task. The user may feed in the data in real-time or in a periodic manner. The data associated with the identified phases and tasks for the project may be stored in the phase and tasks data 128 of the project management system 102.
[0040] As mentioned earlier, the research level phase may observe failures during
the research, designing and prototyping. The failures may results in repetition of some of the research level tasks. For example, research analysis and designing, prototype development and prototype analysis may have to be repeated in a cyclic or iterative manner till a successful prototype is obtained. Each set of repeating research level tasks may constitute a failure cycle. The failure may be identified based on the prototype analysis, and the research level phase may observe multiple failure cycles.

[0041] In an implementation, the failure identification module 122 is configured to
identify number of failure cycles (NFC) in the research level phase. The failure identification module 122 may allow the user to feed data related to failure cycles or may identify the failure cycles based on the data fed by the user against the research level tasks.
[0042] In an implementation, the evaluation module 124 is configured to obtain a
number of research level tasks (NRLT) and a number of project level tasks (NPLT) that are
carried out during the project. The evaluation module 124 may automatically determine
the number of research level tasks (NRLT) and the number of project level tasks (NPLT)
from the data fed by the user against the tasks or may allow the user to feed the numbers.
[0043] Further, in an implementation, the evaluation module 124 is configured to
evaluate an efficiency (E) of the project based on the following equation:
E = (NRLT + NPLT) / (NRLT + NPLT + NFC) equation 1
Equation 1, for evaluation of the efficiency (E), indicates that the higher the number of failure cycles (NFC) the lower will be the efficiency (E). Also, in case, if there are no failures or no failure cycles, i.e., the value of NFC is 0, then the value of E is 1, i.e., the efficiency of the project is 100%. The data associated with the efficiency (E) for the project may be stored in the time and efficiency data 130 of the project management system 102.
[0044] The failures cycles may not only be observed during the research level
phase, particularly during the prototyping, but also may be observed in one or more of the project level tasks of one or more of the project level phases. In an implementation, the failure identification module 122 may be configured to identify the number of failure cycles in the one or more project level phases and the evaluation module 124 may consider the number of failure cycles in the project level phases for the evaluation of efficiency of the project.
[0045] Further, in an implementation, the PTI module 120 is configured to obtain
an execution time (tRLT) for each of the research level tasks and obtain an execution time (tPLT) for each of the project level tasks for each of the project level phases. It is possible that the execution time for some of the research level tasks and/or project level tasks is

substantially insignificant. In an implementation, the PTI module 120 may allow the user to feed the tRLT and tPLT, or may automatically determine the tRLT and tPLT from the data fed in by the user for each tasks as mentioned earlier. The data associated with the execution times (tRLT, tPLT) for the project may be stored in the time and efficiency data 130 of the project management system 102.
[0046] In an implementation, the failure identification module 122 may be
configured to identify, in addition to the number of failure cycles, failed research level tasks associated with each of the failure cycles. The failed research level tasks may include one or more research level tasks or sub-tasks that are repeated or re-executed as the research results were undesirable or not successful. In an example, the failure could be in prototype design, in functioning and performance of the prototype, and the like. In such cases, the research level tasks such as designing, prototype development are considered as failed tasks and thus, the same tasks along with the prototype analysis may have to be repeated. In an implementation, each failure cycle may involve different number of failed research level tasks. In an implementation, the failure identification module 122 may identify the failed research level tasks for each failure cycle based on the data fed by the user for each task, as mentioned earlier, or may allow the user to feed the data in real-time for the identification.
[0047] Based on the identified failed research level tasks for the each failure cycle,
in an implementation, the evaluation module 124 determines execution time (TFC) for all the failure cycles. The execution time (TFC) for the failure cycles is determined using the execution times (tRLT) for the identified failed research level tasks, as mentioned earlier. In an implementation, the execution time (TFC) for the failure cycles is determined by first calculating the execution time (TFCi) for each (ith)failure cycle and then adding the execution times (TFCi) for all the failure cycles. As described earlier, the failure cycle may proceed or progress in a circular manner. Thus, the execution time (TFCi) for the failure cycle may be calculated as (π/2) times the square of the summation of the execution times (tRLT) for all the failed research level tasks for that failure cycle. The data associated with the execution times (TFC) for the failure cycles may be stored in the time and efficiency data 130 of the project management system 102.

[0048] The following description describes the determination of TFC in detail. In an
example, a project may involve q number for failure cycles (NFC), and q number of
failure cycles may have p1, p2, , pq number of failed research level tasks, respectively.
At first, the execution time (TFCI) for the each (ith) failure cycle may be calculated based on the following equation:
TFCi = (Π /2)*(∑ tRLTj)2, equation 2
wherein
j = 1 to pi; and
Pi = number of the failed research level tasks for the ith failure cycle.
Upon calculating the execution time (TFCi) for each of the failure cycles based on equation 2, the execution time (TFCi) for all the failure cycles may be determined based on the following equation:
TFCI -∑ TFCi equation 3
wherein
i = 1 to q; and
q is the number of failure cycles (NFC).
[0049] Further, in an implementation, the evaluation module 124 is configured to
determine a project execution time (Tp). The project execution time (Tp) is determined using an execution time (TPLT) for all the project level tasks, the execution time (TFC) for the failure cycles and an execution time (TSRLT) for successful research level tasks. The execution time (TPLT) for all the project level tasks is calculated by adding the execution times (tPLT) for the project level tasks. For calculating the execution time (TSRLT) for the successful research level tasks, the evaluation module 124 may first identify the successful research level tasks and then add the execution times (tRLT) for those research level tasks. The successful research level tasks may be a difference of the total research level tasks and the failed research level tasks. The TSRLT and TPLT are calculated by taking summations of execution times (tRLT, tPLT) are indicative for linear progress of those research level tasks and project level tasks that are not repeated, and hence successful.

Thus, if a project involves no failures or no failure cycles, the project progresses in a
linear manner. The data associated with the execution times (TPLT, TSRLT, TP) for the
project level tasks, successful research level tasks and the project may be stored in the
time and efficiency data 130 of the project management system 102.
[0050] The following description describes the determination of Tp in detail. In an
example, the project may involve m number of project level tasks and s number of successful research level tasks. The execution time (TPLT) for the project level tasks is calculated based on the following equation:
TPLT = ∑ tPLTi equation 4
wherein
r = 1 to m; and
m = number of project level tasks.
The execution time (TPLT) for the successful research level tasks is calculated based on the following equation:
TSRLT =∑ tRLTk equation 5
wherein
k = 1 to s;
s = number of the successful research level tasks.
Upon calculating the values of TPLT and TSRLT based on equations 4 and 5, respectively,
the project execution time (Tp) is determined based on the following equation:
TP = TFC + TSRLT + TPLT equation 6
[0051] In an implementation, the knowledge base 108 is updated with the
efficiency (E) and the project execution time (TP), as determined by the project management system 102, for the project. This may assist in assessing the current project and may assist in management of future projects.
[0052] In an implementation, for the purpose of determination of project execution
time (TP), the data related to execution times may be entered by the user in real-time or

periodically while the project is being undertaken or may be entered by the user after the
completion of the project.
[0053] Figure 2 illustrates a method 200 for management of a project, in
accordance with an implementation of the present subject matter. The method 200 may
be described in the general context of computer executable instructions. Generally,
computer executable instructions can include routines, programs, objects, components,
data structures, procedures, modules, and functions that perform particular functions or
implement particular abstract data types. The method 200 may also be practiced in a
distributed computing environment where functions are performed by remote processing
devices that are linked through a communications network. In a distributed computing
environment, computer executable instructions may be located in both local and remote
computer storage media, including memory storage devices.
[0054] The order in which the method 200 is described is not intended to be
construed as a limitation, and any number of the described method blocks can be
combined in any order to implement the method 200, or an alternative method.
Additionally, individual blocks may be deleted from the method 200 without departing
from the spirit and scope of the subject matter described herein. Furthermore, the method
200 can be implemented in any suitable hardware, software, firmware, or combination
thereof.
[0055] Referring to Figure 2, although the method 200 for project management may
be implemented in a variety of project management systems, in the embodiments
described in Figure 2, the method 200 is explained in context of the aforementioned
project management system 102 for the ease of explanation.
[0056] At block 202, a request is received for management of a project. In an
implementation, the request may be received from a user, such as a professional having
skills to carry out project management. The user may identify a project for management
and assessment to determine the efficiency and the project execution time for the project
and accordingly make a request at the project management system 102.
[0057] At block 204, at least two phases of the project are identified. The phases
are identified from a research level phase and a project level phase. The project level
phase may include a project initiation phase, a project planning phase, a project execution

and control phase and a project closing phase. In an implementation, the project management system 102 identifies the phases based on the data fed by the user, or from the knowledge base 108 or an external database having relevant data associated with project management.
[0058] At block 206, tasks associated with each of the phases of the project are
identified. The tasks are from research level tasks and project level tasks. Tables 1 to 5
list the research level tasks associated with the research level phase and the project level
tasks associated with each of the project level phases, according to an implementation. In
an implementation, tasks are identified from the knowledge base 108 or an external
database having relevant data associated with project management by the user depending
upon his intellect or automatically by the project management system 102.
[0059] At block 208, number of failure cycles in the research level phase is
identified. As described earlier, the failure cycles may include the research level tasks
that are repeated due to observation of failures. Such research level tasks are understood
as failed research level tasks. In an implementation, the project management system 102
identifies the number of failure cycles based on the data fed by the user.
[0060] After identifying the number of failure cycles, efficiency (E) of the project is
evaluated at block 210. The efficiency (E) is evaluated based on the identified research level tasks and project level tasks and the number of failure cycles. In an implementation, the project management system 102 evaluates the efficiency (E) based on equation ] as described earlier.
[0061] In an implementation, at block 212, execution time (tRLT) for the research
level tasks and execution time (tPLT) for the project level tasks are obtained. In an implementation, the project management system 102 obtains the execution times (TRLT, tPLT) based on the data fed by the user.
[0062] At block 214, the failed research level tasks associated with each of the
failure cycles are identified. As mentioned earlier, each failure cycle may involve different number of failed research level tasks. In an implementation, the project management system 102 identifies the failed research level tasks and its number based on the data fed by the user.

[0063] Upon the identification of failed research level tasks for each failure cycle,
an execution time (TFC) for all the failure cycles is determined at block 216. The value of TFC is determined based on the execution times (tRLT) for the failed research level tasks, In an implementation, the project management system 102 determines the value of TFC based on equations 2 and 3 as described earlier.
[0064] At block 218, a project execution time (TP) for the project is determined.
The value of TP is determined using the value of TFC, an execution time (TPLT) for all the project level tasks and an execution time (TSRLT) for all successful research level tasks. For calculating the value of TSRLT, the successful research level tasks are identified. In an implementation, the values ofTSRLT, TpPLT, and Tp are calculated or determined based on equations 4, 5 and 6 as described earlier.
[0065] Although embodiments for management of projects have been described in
language specific to structural features and/or methods, it is to be understood that the invention is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary embodiments for management of projects.

I/We claim:
1. A computer implemented method for management of a project, the method
comprising:
identifying at least two phases of the project, wherein the at least two phases comprise one research level phase and one project level phase;
identifying tasks associated with each of the at least two phases;
identifying a number of failure cycles in the research level phase; and
evaluating an efficiency of the project based on the tasks and the number of failure cycles.
2. The method as claimed in claim 1, wherein the tasks comprises research level tasks
for the research level phase and project level tasks for the at least two project level
phases, and wherein the method further comprises:
obtaining execution time for the research level tasks; and
obtaining execution time for the project level tasks; and
determining a project execution time based on the execution time for the research level tasks and the execution time for the project level tasks, wherein the evaluating is based in part on the project execution time.
3. The method as claimed in claim 2 further comprising identifying failed research level tasks associated with each of the failure cycles, and wherein the determining the project execution time comprises determining execution time for the failure cycles based on execution time for the failed research level tasks.
4. The method as claimed in claim 1, wherein the research level tasks are selected from a group consisting of:
conceiving of a problem associated with one of a product and a service;
obtaining of objectives associated with one of the product and the service;
identifying team members for the research level phase;
defining research level cost, scope, schedule and quality standards;
research analysis and designing;
developing a prototype; and
analyzing the prototype.

5. The method as claimed in claim 1, wherein the project level phase comprises a
project initiation phase, and wherein the project level tasks associated with the project
initiation phase are selected from a group consisting of;
developing a project database;
creating project charter;
obtaining sponsorship;
reviewing the project level tasks associated with the project initiation phase; and
obtaining an approval to move a next project level phase.
6. The method as claimed in claim I, wherein the project level phase comprises a
project planning phase, and wherein the project level tasks associated with the project
planning phase are selected from a group consisting of:
estimating deliverables, activities and efforts for the project;
refining project cost, scope, schedule, quality standards;
defining strategies for mitigating risks associated with the project, wherein the risks comprises risks related to technology, resource availability, cost overrun, scope creep and schedule overrun;
establishing a communication plan;
managing changes required for the project;
establishing a project execution plan;
reviewing the project level tasks associated with the project planning phase; and
obtaining an approval to move to a next project level phase.
7. The method as claimed in claim 1, wherein the project level phase comprises a
project execution and control phase, and wherein the project level tasks associated with
the project execution and control phase are selected from a group consisting of:
managing project execution;
manageing project cost, scope, schedule and quality standard; monitoring and controlling of risks associated with the project; reviewing the project level tasks associated with the project execution and control phase; and
obtaining an approval to move to a next project level phase.

8. The method as claimed in claim 1, wherein the project level phase comprises a
project closing phase, and wherein the project level tasks associated with the project
closing phase are selected from a group consisting of:
conducting a post-implementation review for the project; and performing an administrative closeout for the project.
9. A project management system (102) comprising:
a processor(110); and
a memory (114) coupled to the processor (110), wherein the memory (114) comprises:
a phase and task identification module (120) configured to
identify at least two phases of a project, wherein the at least two phases comprise one research level phase and one project level phase; and
identify tasks associated with the at least two phases; a failure identification module (122) configured to identify a number for failure cycles in the research level phase; and
an evaluation module (124) configured to evaluate an efficiency of the project based on a number of the identified tasks and the number of failure cycles.
10. The project management system (102) as claimed in claim 9, wherein the tasks comprises research analysis and designing, prototype development and prototype analysis associated with the research level phase, and wherein the failure identification module (122) is configured to identify the number of failure cycles based the prototype analysis.
11. The project management system (102) as claimed in claim 9, wherein the project level phase comprises a project initiation phase, a project planning phase, a project execution and control phase and a project closing phase.
12. The project management system (102) as claimed in claim 9, wherein the tasks comprises research level tasks associated with the research level phase and project level tasks associated with the project level phase, and wherein the phase and task identification module (120) is configured to obtain an execution time (tRLT) for each of the research level tasks and obtain an execution time (tPLT) for each of the project level tasks.

13. The project management system (102) as claimed in claim 12, wherein the failure
identification module (122) is configured to identify failed research level tasks associated
with each of the failure cycles, and wherein the evaluation module (124) is configured to
determine execution time (TFC) for the failure cycles based on an equation:
TFC - ∑ TFGI, wherein
i = 1 to q;
q = the number of failure cycles;
TFCi = (π/2)*(∑tRLTj)2;
j = I to pi; and
Pi = number of the failed research level tasks for the ith failure cycle.
14. The project management system (102) as claimed in claim 13, wherein the evaluation
module (124) is configured to
identify successful research level tasks associated with the research level phase; and
determine a project execution time (TP) based on an equation:
Tp = TFC + TSRLT + TPLT; wherein
TSRLT = ∑ tRLTk; k = 1 to s; s = number of the successful research level tasks; and
TpLT = ∑ tPLTr;
r = 1 to m; and
m = number of project level tasks.
15. A computer-readable medium having computer-executable instructions that when executed perform acts comprising:
identifying at least two phases of the project, wherein the at least two phases comprise one research level phase and one project level phase; identifying tasks associated with the at least two phases; identifying a number of failure cycles in the research level phase; and

evaluating an efficiency of the project based on the tasks and the number of failure cycles.