METHOD AND APPARATUS FOR PLANNING AND MONITORING MULTIPLE TASKS BASED ON USER DEFINED CRITERIA AND PREDICTIVE ABILITY

Abstract: Individual employees are permitted to be individuals and plan their work as individuals. Individuals are only asked to plan their work within a limited tasking horizon (26). Employees track their progress using verbs (28) that are designed to capture the reasons behind positive and negative predictive ability (30). Verbs are analyzed and expected predictive error, also known as risk, is calculated. Once verbs are captured, they can be analyzed for ways to improve predictive ability. In addition, the risk can be factored into the initial planning stage so as to include an expected predictive error in the initial planning.

Description: nr-LE Method and Apparatus for Planning and Monitoring Multiple Tasks Based on User Defined Criteria and Predictive Ability. I. FIELD OF THE INVENTION The present invention relates to an improved method and apparatus for planning and monitoring the assignment and completion of a project that is comprised of an aggregate of tasks. II. TECHNICAL BACKGROUND A project typically requires a large amount of time and involves many individuals from different disciplines and professions. Project oriented tasks typically have more uncertainty and fluidity than other types of work, such as repetitive tasks performed with functionally oriented work. As a result, specialized methodology and tools for managing projects have been needed. Large companies typically utilize programmable computers and associated databases to manage available personnel and track expended labor hours. Various internal and external funding accounts may exist to which personnel may charge their labor time. Because large companies are unable to track and predict the work habits of individual employees, they track macro indicators such as total cost and total time. Planning on a macro level is never accurate and never identifies the reasons for the inaccuracies so as to permit the planning model to be refined. Common examples of macro models include tracking work performed in completing a capital project so that it can be depreciated for tax purposes. Accordingly, a specific Capital Project Appropriation Request (CPAR) is created to which personnel may charge expended time in performing work thereunder. One convenuonal system is known as the Automated Issue Management System (AIMS) and is used in conjunction with another conventional system called Time Entry System (TES) which are used for capitalizing internal and external labor The systems are contained in convenuonal programmable computers for more accurately managing the large number of personnel involved and the substantial number of individual tasks associated with various capital projects A project manager typically initiates a project bv opening a specific work request in die AIMS system The system automatically provides a respecuve AIMS number, which tvpically has a correlation to a single CPAR number. The manager assigns personnel to complete tasks based on an AIMS number The TES system allows personnel to record through a personal computer expended ume per AIMS number as the work is completed. The TES system allows the manager to examine cumulative time expended for specific AIMS numbers, with the manager manually correlating the AIMS number to a specific CPAR. Although the AIMS and TES systems facilitate managing projects in a large company, project planning and managmg is nevertheless relatively complex in most circumstances. To further facilitate project management in large companies, commercially available software has been developed One available management tool or product is convenuonally known as Microsoft Project from Microsoft Corp., and another product is ABT Project Workbench from the Applied Business Technology Corporation. These software tools allow companies to define project plans in accordance with tasks and time schedules for available personnel resources, and are typically operated in stand-alone fashion or in conjunction with other commercially available software products for facilitating the overall management of projects However, these commercially available products are designed for specific applications and are therefore limited in capability, as well as having no built in capability for managing pro j ect funding such as the CPAR example introduced above. An example of previously disclosed systems include United States Patent No. 5,111 ,391 , which describes a staff scheduling data processing system and method schedules staff and management personnel at locations remote from a central locauon by applying central locauon policy to unique remote locauon data to insure the optimum staff schedule for each remote site. United States Patent No. 5,818,715 describes a method and system for modifying a project model in response to an update. United States Patent No. 5,767,848 descπbes a development support system for supporting new product development activiues, which includes a target storage for storing target values of schedules of product development, and the cost and the performance of d e product; an esumating unit for estimating schedules of product development and the cost and the performance of the product on die basis of the models stored in the model storage. The '848 patent includes a unit for monitoring electronic mail necessary for carrying out tasks essential to the development of the product, extracting information relating to the progress of tasks essential to carrying out the development of the product, and providing the members of the development project team with informauon about the progress of the tasks. Umted States Patent No. 5,765,140 describes a dynamic project management system includes a server network and a master database. Umted States Patent No. 5,692,125 describes a scheduling system, events and/or groups of events arc checked at a scheduling time to insure that certain fixed conditions associated with the event(s) are satisfied. Umted States Patent No. 4,942,527 descπbes a computing apparatus for an improved information system that manages All of these proposed systems, however, fail to adequately include factors necessarv for adequate task planning and are incapable of efficienriy and accurately planning and managing project tasks. All of these svstems are based on the premise that planning is dependent upon macro attributes, such as time and cost. In tying planning to these macro attributes that are used regardless of the employee base and regardless of the planning model, these svstems are inherently limited and fail to account for the way people actually work III. SUMMARY OF THE INVENTION The present invention is designed to evaluate the entire workflow process for human factors on both macro and micro levels The present invention breaks down projects into micro events and tracks the group's predicuve ability (the ability to plan and carry out tasks as planned) The present system recognizes that certain factors that effect planning and management are incapable of being quanufied on a macro level and must be incorporated into the planning process on a micro level The present system recogmzes that the best knowledge of how productive or efficient an individual employee will be over a given ume period is likely to rest with that individual employee. Not even' individual is able to predict or schedule work with the same degree of accuracy The accuracy of an enure group to plan and execute on that plan is only as good as the weakest link The present invenuon recognizes this and provides a system and method that uses tasks and user defined goals to measure predicuve ability. As individual predicuve ability is opumized, the group's predicuve ability is also opumized This permits projects to be planned and executed with die greatest degree of planning accuracy Thus, the present system has several stages Individual employees are permitted to be individuals and plan their work as individuals Individuals are onlv asked to plan their work \\ ithin a limited tasking horizon Employees track their progress using verbs that are designed to capture the reasons behind positive and negative predicm e ability Verbs are analyzed and expected predictive error, also know as risk, is calculated Once verbs are captured they can be analyzed for ways to improve predictive abilm In addition, the risk can be factored into the initial planning stage so as to include an expected predictive error in the initial planning Tasks may also be analyzed and linked to od er tasks to account for inherent related task risk In general, the present invenuon breaks projects down into individual assignable tasks Tasks are assigned for a predetermined time, up to the tasking horizon, bv an employer or project manager The tasking horizon is designed to be a realistic plannmg window that corresponds to die length of time most employees can plan their work In one example, die tasking horizon is a two-week period It may also be a week, davs or mond s Depending on die tasks, workers and work environment, the tasking horizon mav vary Next, verbs are selected d at capture die types of dialogues that an employee faced with die task mav use to describe their progress Verbs are meant to capture generalized categories of dialogue diat workers would routinely engage in if thev were each interviewed on a routine basis throughout a project For example, verbs may be selected to provide s series of potential answers to a standard question, such as "why do you think vou performed this task faster or slower than estimated*" In one embodiment, verbs can be broken down into employee dependent verbs (health, mental well being, etc ), task related verbs (new computers not working, etc ), environmental verbs (snow, etc ) or in any number of ways Verbs are used to categorize and classify employee responses to assist in maximizing predictive ability Each employee is provided with access to a task assignment station or a PC The task assignment stauon proudes d e emplovee with know ledge about dieir tasks that need to be scheduled, started or completed during the next tasking horizon The database does not set a time period in which each task is to be completed but allows the employee to instruct the system when, and in what order, die employee thinks that a task will be started and finished As the system w orks bv maximizing the employee's predictive ability, it is preferable that the employee has some control over the scheduling of tasks As employees perform tasks they access the database to record when a task is started and when it is completed. In addition, die task assignment stauon is provided wid d e list of verbs to select from that best describe die reason the task was completed before or after die employee predicted An employee's ability to accurately predict when a task is completed, or not, is referred to as churn Thus, churn is a measure of the employee's predicuve abilitv An employee d at starts w ork when expected and finishes when expected will have a low churn One goal of the present invention is to have each employee accurately predict when tasks will be completed This information is invaluable in accurately predicting and plannmg projects When individual predictive ability is optimized, the group benefits and is able to accurately predict and plan projects Because d e present invenuon is based on employee input, it has the advantage of gathering unique data on the way employees work Because die system has access to employee verbs, it can also be used to identify management issues, such as d e need for framing that will assist the employer in minimizing future churn The present system also assists in identifying natural work patterns ol employees and accounts for the way employees actuallv ork when plannmg projects Because die present invenuon is a dynamic system, radier d an a static (cost and ume) system, the traditional \ ocabularv that has been used in management svstems is insufficient Thus, in die present invenuon the follow ing terms have definitions odier dian dieir tradition definition Thev are as follows IV. BRIEF DESCRIPTION OF THE DRAWINGS The foregoing and other advantages and features of the invention will become more apparent from die detailed description of d e preferred embodiments of the invenuon given below with reference to die accompanying drawings in which: Figure 1 is a diagram of an on-site implementation of die current system; Figure 2 is a diagram of an off site implementation of the current system, Figure 3 is a schematic of an alternative database configuration, Figure 4 is a flow chart of the employer task assignment stage, Figure 5 is a flow chart of die task scheduling stage, Figure 6 is a flow chart of a churn management stage, Figure 7 is a flow chart of a predictive management stage, Figure 8 is a logic diagram of a task assignment stage interface, Figure 9 is a logic diagram of churn monitoring stage, and Figure 10 is a flow diagram of a predicuve management svstem V. DETAILED DESCRIPTION OF THE DRAWINGS AND OF THE PREFERRED EMBODIMENT The present svstem is designed to be dynamic and thus the hardware needed to implement it from embodiment to embodiment varies considerably The present invenuon can be run on an internal network as shown in figure 1 or o\ er an external network (including die Internet) as shown in figure 2 Employees are connected to a network database 5 through the use of a PC A manager is also connected to d e network database 5 through a PC Those of ordinary skill in the art will understand that a PC with a Pentium processor, 16 megs of RAM, a 5 meg hard- dπve, an operating system (such as Windows '95 or higher) and a 56k modem or network connection are adequate to implement d e present invention In its most basic embodiment the entire svstem can be provided on a single PC widi a Pentium processor, 64 megs of RAM, a 5 GB hard-drive, an operating system (such as Windows NT or similar operating system) that multiple user's have access to Likewise, in a hardwired embodiment, similar components may be provided in a hardwired form Another implementation involves web server software running on a server d at is used to produce an external network configuration As shown in figure 2, an external network, such as the Internet 6, is provided A server 7, such as a Netscape ES server is provided that is operationally connected to a workstation 8, such as a Sun Microsystems Workstation The database 5 mav be ιded externally or internally to one or more of the PCs or workstations The types of databases used may varv considerably As shown in figure 3, the database 5 mav have multiple sub-databases, which mav be partitioned portions of database 5 or mav be additional databases The sub-databases mav include a section to hold data associated with the present svstem 5a, employee human resource data 5b and/or time and billing data 5c The multiple databases may be located at different locations and data mav be shared on a periodic basis or though other conventional means As the present invention is designed to operate dynamically, d ose of ordinary skill in die art will recognize that it may be installed over a variety of computing systems For example, in addition to the single network svstem shown in figure 1 , it is expressly contemplated diat multiple networks and/or sub-networks mav be incorporated and that the present invenuon may be implemented in whole or in part over all or over selected poruons of the network. For example, the management funcuons, such as assigning risk, may be implemented in an upper management system, d e task assignment mav be implemented in an on-site direct management system and the employee plannmg system may be implemented over an employee network. Although die present invenuon is a dynamic system diat is ulumatelv designed to be recursive, the operation of the present invention is best understood if one begins with the employer task assignment stage 10 When the multiple aspects of the present invenuon are described, those of ordinary skill in the art will recognize how the system works on itself to constandv refine and upgrade is predictive abilities The present invention works by recognizing diat projects mav be interpreted as discrete tasks diat must be completed during the project Each task has a start and stop date and each task has an action item associated widi it In other words, P = ∑T„ (X, Y) where P is the project, T is each task, X is a start date and Y is a completion date or time until completion In a more complicated embodiment, individual tasks may be linked Thus, a task whose start date is linked to the stop date of another task may be linked Tasks may be linked direcdy, diat is a task that cannot be started until another task is completed, or they mav be linked indirecdv An lndirecdv linked task mav be related indirecdy, such as a task in a different phase of die project, such diat its start date is likely to be influenced by d e stop date of tasks that in the preceding phase of die pro j ect Linked tasks will be described more in detail in d e discussion below concerning risk As shown in figure 4, d e project is input 12 and die tasks separated out 14 The process of task separation mav be automated or may be carried out bv an operator As d e recursive nature of the present invenuon is appreciated, the tasks or types of tasks likely to be in a project mav be automatically determined in the task breakdown step 14 The present system can record projects and tasks and provide diat information as a default when a new project is initiated. Once d e tasks in a project have been determined, d e next aspect of the present invention is die planning of the tasks The project as a whole will have an ultimate start and stop date The project start and stop dates are die ultimate time window in which the individual tasks must be completed The present invention recognizes that the most effective planning is generally limited to a predetermined period of time, which is likely to be much smaller dian the project time period Thus, for task planning purposes the project is broken down into a tasking horizon 16 The tasking horizon is designed to be a realistic window of time o\ er winch tasks can be scheduled In a preferred embodiment, the task horizon is one or two weeks, but it mav be a number of davs, weeks or even mondis depending on the tasks being assigned and die group being assigned die tasks If the project window is represented by X t , where t= 1 to Z, the tasking window (W) mav be represented as a function of X. to X^ K ,, assuming that t is measured in days and there are 5 davs in a work week The tasks can thus be sorted as a function of time (t) and scheduled accordingly P(X, ) = ∑lV(X„ λ l )T n (X, , Y) -•- = 1 It is important to note that in a multi-tiered implementation of the present invention the tasks mav be assigned to groups, which mav then assign the tasks to individual employees or groups Thus, it is expressly contemplated diat in some implementations diere will be multiple tiers of task assignments In such multi-tiered implementations it is expressly contemplated diat different groups or sub-groups may have different tasking horizons It is also expressly contemplated that die start date of a task may depend in whole or in part on die stop date of anodier task Thus, d e present invention permits tasks to be linked or to be assigned with a risk factor, which will be described in more detail below The next step is to assign verbs (V) 18 to each task P(X l ) = ^ W(X l , X l ^ )T ι , (X, . V, V ^l ) Verbs are designed to capture the types of dialogue that a worker would use to explain whv a task was or was not started and/or completed as planned Verbs may be assigned for all tasks on a project or mav change from task to task By requiring the employee to select a verb, the emplovee/emplover dialogue is standardized so that it is capable of analysis In a preferred embodiment it is contemplated d at there w ill be multiple verb sets that die task assignor can simply select In one embodiment, a \ erb set is provided that is task independent and includes verbs that are assigned to a task regardless of what that task mav be Other verb sets may be task dependent A third set of verbs may be provided that are employee specific Employee specific verbs mav be based on an employee's HR data and mclude verbs that relate to children, medical conditions, etc Any or all of diese verb sets mav be used and die present invention is not limited to any one verb set Some examples of verbs mav include the following groups The final step is to assign the tasks 20 that occur during the tasking horizon The assignment of tasks can be implemented on a periodic basis or may be assigned at the beginning of the project for automauc assignments during the appropriate tasking horizon Each day, or at set intervals, the svstem mav check the unassigned tasks and assigns tasks d at fall within the next tasking horizon It is also expresslv contemplated d at tasks may be self- assigned At which point verb sets mav be selected from a predetermined verb set or mav be subsequendv assigned by an employer As shown in figure 5 after a task has been assigned, die task needs to be scheduled 22 Scheduling is accomplished bv having the employee, or in some embodiments die employer, assign start and stop dates 26 Although the present invention is described with respect to start and stop dates, those of ordinarv skill in the art will recognize diat the invention mav be implemented using a start date and a number of working hours or in anv odier time and work measurement svstem, such as a start date and cost The start and stop dates set the standard against which the scheduler's planning abilities are measured It is also expresslv contemplated that a default start and stop date may be provided with die task that die employee may modify The next step is for the employee to record the task performance 28 It is preferable that task performance is recorded on a daily basis In addition to indicating a task is started or completed, the employee is asked to select a verb 30 associated with the action (starting and/or stopping) that best describes whv die task was or was not started and/or completed as predicted The differences between the planned start and stop dates and the actual start and/or stop dates is classified as churn (C) C — 1 Λ prc( ] lclL j , 1 p rι jι C ι L j ) ~ * ( A. a ua ι , I a d uai ) The verb is used to classify the reasons for churn, or in other words die reason for why the task was performed as planned or not performed as planned Churn mav be broken down into start churn, completion churn, time churn, cost churn or any other variety Churn is simply a measure of die relative predictive ability of the employee in relationship to one or more tasks Churn mav be a composite figure or an index of one particular type of ability In a preferred embodiment, the churn capturing process is triggered when task dates appear, \ anish, and/or move into or out of a current tasking horizon (sometimes) The task edit interfaces (employee side interface) contain data entry fields for estimated start and completion, as well as actual start and compleuon dates for a particular task Depending on die case, anv and/or all of the aforementioned date \ alues mav change during a single transaction Therefore, a set of rules is necessary to govern date entn. , as well as rules to ern w Inch date change or changes should generate churn An example of date rules is as follows: • An estimated date cannot be changed if an accompanying actual date exists. • If an actual date is created and die accompanying estimated date does not exist, it is automatically populated with the value of die actual date. • Complete dates mav not precede start dates of the same type. • If changes to date fields are valid, then a determination is made whether churn should be generated using churn rules Due to the nature of churn and data entry variables involved, churn generation does not have to be limited to a single formula. Rather, churn may be generated based on a series of decisions using information provided by the application user. Churn is captured for all events witiiin a single transaction diat meet churn generation requirements. One example of the general preprocessing of churn is as follows: • If a date changes but does not enter or exit the current tasking horizon, t en churn is not generated for the date. • If no start and/or completion date values exist for a task, then new estimated dates are always processed before new actual dates. This is based on the date rule that estimated dates cannot change while accompanying actual dates exists. In other words, if the actual date is processed first, then processing die change to the estimated date afterwards would violate the date rule. • If an actual date vanishes and its accompanying estimated date appears or is moved into or out of the current tasking horizon, then again, the estimated date is processed after the actual date Based on these churn preprocessing rules, an example of churn generation rules is as follows: • If an estimated date is created in or moved into the current tasking hoπzon, dien negative churn is generated • If an estimated date is deleted or moved out of the current tasking horizon, positive churn is generated • If an estimated date exists in die current tasking horizon, and an actual date is moved out of, or is created outside of the current tasking horizon, d en positive churn is generated. • If an actual date is deleted or is moved out of the current tasking horizon and die accompanying estimated date is not in the current tasking horizon, dien positive churn is generated. • If an actual date is created in or is moved into the current tasking hoπzon and die accompanying estimated date is not in die current tasking horizon, d en negative churn is generated Churn percentages can thus be calculated as follows • Project Churn Rate = 100 * DCT / TT • Negative Churn Rate = 100 * DCN / TT • Posiuve Churn Rate = 100 * DCP / TT where DCT is equal to die distinct churning tasks in project, DCN is equal to die distinct tasks in project that churned negatively, DCP is equal to the distinct tasks in pro j ect that churned positively and TT is equal to die number of tasks in project An example of a churn calculation can be understood from the following example If 100 tasks exist in the current tasking horizon, 5 unplanned tasks are introduced into the current tasking hoπzon and 10 tasks slip to d e next tasking horizon, the positive churn is 10%, die negative churn is 5% and d e total churn is 7 5% Those of ordinary skill in die art w ill appreciate diat there are many different churn scenarios and that die above example is one of many alternatives It is expressly contemplated that an optional employee scheduling monitoring module may be used that keeps track of the time between task scheduling updates. If an employee does not update task performance within peπodic periods of time, for example weekly, a remmder to the employee to update his/her tasks can be sent by the module. One example of a logic diagram for an employee side interface 52 is shown in figure 8. This embodiment is designed for use over a network system that is preferably implemented over die Internet and uses a distributed object architecture system, such as CORBA, JAVA or JAVA BEANS. Those of ordinary skill of d e art will recognize that die interface may be modified and implemented over a wide variety of systems. The employee first logs in dirough a convenuonal login 54 and authentication 56 routine. After log , die employee may select the views or items to be displayed 58. If the churn rate is requested 60, d e most currendy available churn data is retrieved 62 and displayed 64. Depending on die type of churn being calculated (task based, employee based and/or environmentally based), multiple churn rates may be displayed. It is expressly contemplated that churn may be displayed numerically, graphically or in any other convenuonal means If the employee chooses to view tasks 80, the system retrieves the tasks assigned to that employee 66 and displays diem 68. If the task is new 70, the employee is provided with die ability to set the anticipated start and stop date 78. If the tasks is an existing tasks 74, die employee may update their progress on anv of the tasks 74. In addition, for each task that receives a data input, the employee is requested to enter a verb and/or to select a verb from a predetermined list The logic diagram is ended at 82. Determining why tasks are not performed as planned is one of the goals of the present invention When tasks are not performed as planned tiicx' are classified as churn. The verbs that are associated with the reason for the churn can then be analyzed to determine what if anything the employer can do to either minimize the churn or anticipate its occurrence. In one embodiment as shown in figure 6, a churn management program 32 is actively connected to die employee task data. Task progress is monitored against the employee's scheduled progress 34. Discrepancies in progress are classified as churn. Churn is calculated 36 and may be either positive or negative. Both positive and negative churn represent a failure of the planning period to accurately predict what actions would occur. Churn can be analyzed on many different levels. Churn may be calculated by task, by task type, by employee, by groups of employees, etc. Churn is monitored on multiple levels to help identify why the churn occurred. Churn helps identify what an employer can do to reduce churn and also helps d e employer recognize what churn it will never be able to reduce. By quantifying churn, the employer may optimize the working environment while at the same time quantifying the intangible variable d at force tasks and projects to be completed in a manner other than what was predicted. When churn is encountered, it is important to know if the reason for the churn and whether it has anything to do with die task itself or the individual who performed the task. The verb associated with the positive churn rate is analyzed to determine what if any effect it should have on an assigned risk factor 40. Risk factors may be churn dependent or they may be task dependent. Risk factors can be assigned as a function of die predicted length of a project or can be factored as percentage of error or both. For example, an "installing" task may take, on average, 5 working days to complete. An employee that predicts the task can be completed in 4 days will have a risk of 1 day assigned to the task. Alternately, die employee or task can be calculated to take 25% longer than planned. Thus, an employee that schedules the "install" for 4 davs mav be assigned a 1 day (25% x 4 days) πsk factor In addition, a task such as "programming" may not be able to be started until d e "installing" task is completed A risk factor mav be assigned to the "programming" start date that is a function of the on-time completion risk associated with the "installing" task The risk associated with multiple tasks mav be quantified and assigned a weight that reflects the influence of the related task Thus, for example if there is a 25% chance that the "installing" step mav not be completed as planned and the "installing" task has a direct effect on the "programming task, a 100% weight, die risk associated with the "installing" task will be attributed to the "programming task." The verbs associated widi die churn are important is assigning task risk values and in deciding whedier diere is anything diat an employer can do to minimize the churn For example, if die same worker takes 6 days to do an "install" but identifies a family emergency (personal reason) for the delay, the πsk factor assigned to die task may not be modified at all The reason for the churn is employee based and not task based. The employee's risk factor may also only be effected if the mcident rate of family emergencies experienced bv d e worker exceeds some predetermined norm Thus, if die employee experiences a 10% greater likelihood of having personal emergencies and on average workers schedules are effected by personal emergencies in 10% of the tasks that are performed, the worker mav have a 1% increased risk factor ( 10% additional πsk of a 10% norm) of incurring churn If die worker's churn is 1 day and d e risk factor is 1%, die worker may have a 01 dav increased risk On die odier hand, if die same employee identifies training as die reason for the churn, the employer mav weigh the cost benefit of training and the possible increase in productivity Thus, die present svstem permits tangible and intangible risk to be calculated and norms determined by using verbs that are not attributable to any given personal reason. Because die present invention mirrors how people actually work, it may use Human Resource (HR) data to assist in predicting likely work patterns. In an alternate embodiment, die churn and risk assessment is made in combination with the employee's human resource data and/or anv other data that the employee is willing to share. Events, hobbies, children, family obligations as well as other significant events that can be quantified can be worked into die churn/risk calculation. An employee's risk may fluctuate in relation to trackable events and assigned accordingly. For example, a risk factor mav increase or decrease for an employee with children during known vacation periods. When children are home during vacations, depending on the family situation, the employee's risk value may increase or decrease Thus, if an employee's personal profile indicates that diey have children, the children's vacation can automatically be factored into the churn/risk calculations. Likewise, odier commitments, whether d e employee is on a sport's team or predictable event, such as vacation, can be used to identify churn patterns and optimize risk calculations The net effect of diis type of risk analysis is that die employer can capture the intangible reasons for churn and make realistic decisions about how long tasks will take. Another important advantage of die system is in identifying employees with below average intangible churn. Employee's who work equally hard regardless of odier commitments or events. The employer may use risk management to ensure that employee's do not overwork diemselves and take appropriate time off. One example of a churn monitoring program 84 is shown in figure 9 This embodiment is designed for use over a network system diat is preferably implemented over the Internet and uses a distributed object architecture svstem, such as CORBA, JAVA or JAVA BEANS Those of ordinary skill of the art will recognize that the interface mav be modified and implemented over a wide variety of systems Tasks are first extracted 86 and the associated churn and verbs are determined 88 The churn is classified as positive or negative 90 The verb, reason for the churn, is then analyzed 92 If verb categoπes are used, die verb can first be compared to the known employee dependent verbs 94 If the verb is employee based, in other words unique to that employee, the verb is compared to an expected norm value and a risk factor is assigned 96 The risk factor is recorded in a database 98 and, if necessary, an ov erall risk factor is modified 100 for die employee If the churn is not employee dependent 94, die churn is next analyzed to determine if it is task related 102 If the churn is task related die churn is compared to a norm and assigned a weight and the information is recorded 112 Likewise, die overall risk factor associated widi that task may be modified 114 If the churn is not related to die employee or a particular task, it is classified as environmentally related 104 The churn is recorded and the overall environmental risk factor associated with environmental related churn is modified 108 If another task/churn requires analyzing 1 15, it is sent through die same process until the program ends 1 16 One of the main goals of the present system is to assist in the planning stage, before tasks are assigned Therefor, a predictive management svstem 42, as shown in figure 7, is designed to assist in identifying how long a project, composed of multiple tasks, will take and predict the risk ( unexpected time variations) involved with the project The predictive management svstem 42 works bv attempting to find as many data points diat can be correlated with known data The first step is to input tasks 44 and anv information concerning the employee base 46 that is available The verbs that correspond with expected tasks may also be designated 48 The predictive management system then looks for direct and indirect matches amongst the data and compiles the πsk 50 For example, if one or more employees have performed a task that is part of the project, die ume period that the task will likely take to perform can be estimated If direct task matches are not possible, the system can nevertheless use employee based risk and/or environmental risk to estimate the non-task dependent risk diat the project is likely to encounter The system can also compare employee bases and extrapolate predictive information Graphing of risk factors can also be used to extrapolate risk factor trends diat are odierwise not captured by the current svstem. Risk mav be calculated for a project as a whole, for given Ume periods or for given tasks This permits die employer with general predictive information and die ability to identify die most likely place in a project where it will have the greatest likelihood of encountering problems. Staffing decisions and realistic goals can thus be set by management before tasks are assigned to groups or individual employees. Another example of a predictive management system, which may also be referred to as a profiler, involves die creation of a template for a new project, team, person, etc. based on statistical information that has been gathered in the past One example of a predictive management center 1 18 is shown in figure 10 Tasks are identified 120 along with available employees 122. Each employee's πsk profile is extracted 126 from a database Next, the tasks diat will need to be completed are compared against the tasks that the employee's e performed in the past 128 Environmental and employee personal risk is added and an average time for each task is computed togedier widi a composite risk factor 132 Tasks diat do not have a direct match 1 34 are identified and either an estimation is made bv the operator how long each task should take to complete 1 36 Employee and environmental risk factors are added, together with the operator's new task predictive πsk factor 138. A total completion time and project πsk factor is then generated 140 The present system mav estimate die hkelv employee plannmg values using a Fibonacci sequence. For a system size environment the formula is- S = CK i T* For development efforts d e formula is where S is die svstem size, C is the technology constant, K is die total effort and T is die development time. Those of ordinary skill in die art will recogmze diat other well known med ods of data analysis and pattern recognition, such as Least-Square Estimation, Best Linear Unbiased Estimation, Maximum-Likelihood Estimation, Mean- Square estimation, Maximum A Posteriori Estimation, Wiener Filtering, Kalman Filtering, Iterated Squares, Extended Kalman Filtering, etc , mav be used widi die present invention Those of ordinary skill in the art will appreciate that this is where die system begins to turn on itself and becomes recursive As predictive ability is captured it can be anticipated and improved While die invenuon has been descπbed in detail in connection widi the preferred embodiments known at the ume, it should be readily understood that die invention is not limited to such disclosed embodiments Rather, die invenuon can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with die spirit and scope of the invenuon Accordingly, the invenuon is not to be seen as limited by the foregoing descπption, but is only limited by the scope of the appended claims. We claim:

Claims: 1 . A method for planning tasks comprising the steps of: breaking a project into tasks; selecting a tasking horizon; selecting at least two verbs for at least one of said tasks; receiving a predicted start date for said at least one task; receiving an actual start date for said at least one task; receiving one of said at least two verbs that corresponds to said actual start date; comparing said predicted start date said actual start date; and computing churn of said at least one task. 2. The method as claimed in claim 1 furdier comprising the step of: classifying said received verb as employee dependent. 3. The method as claimed in claim 1 further comprising the step of: classifying said received verb as task dependent. 4. The method as claimed in claim 1 further comprising die step of: classifying said received verb as environment dependent. 5. The mediod as claimed in claim 1 further comprising die step of: computing a risk factor based at least in part on said computed churn. 6. The method as claimed in claim 1 furdier comprising die step of: computing a risk factor based at least in part on said received verb. 7. The method as claimed in claim 1 further comprising the steps of: comparing said tasks of said project to previously performed tasks; extracting previously performed task completion data; and computing an expected task completion time based at least in part on said previously performed task completion data. 8. The med od as claimed in claim 1 further comprising the steps of: comparing said tasks of said project to previously performed tasks; extracting a risk factor associated with said previously performed tasks; and computing an risk factor based at least in pan on said extracted risk factor. 9. A method for planning tasks comprising the steps of: breaking a project into muluple tasks, wherein there is at least a first task and a second task; selecting a tasking horizon; selecting at least two verbs for said first task; selecting at least two verbs for said second task; assigning said first task to a first task assignment stauon; assigning said second task to a second task assignment station; receiving a predicted start date and a predicted completion data for said first task from said first task assignment station; receiving a predicted start date and a predicted completion data for said second task from said second task assignment stauon, receiving an actual start date and a verb for said first task, receiving an actual start date and a verb for said second task, compuung churn of said first task; compuung churn of said second task, compuung a risk factor for said first task; and computing a risk factor for said second factor 10 An apparatus for planning task comprising. a management module for breaking a project into tasks, selecting a tasking horizon and for assigning at least two verbs for at least one of said tasks, a task assignment station for receiving said at least one task and for entering a predicted start date for said at least one task and for entermg an actual start date; wherein said management module and said task assignment stauon are operationally connected and wherem said management module receives predicted start date and said actual start date and computes a churn

Inventors: BENNETT MATTHEW, CLARK DOUGLAS, FINWICK JAMES, RICHARDSON SANDRA, BENNETT, MATTHEW, CLARK, DOUGLAS, FINWICK, JAMES, RICHARDSON, SANDRA
Applicants: BENNETT MATTHEW, CLARK DOUGLAS, FINWICK JAMES, METIER LTD, RICHARDSON SANDRA, BENNETT, MATTHEW, CLARK, DOUGLAS, FINWICK, JAMES, METIER, LTD., RICHARDSON, SANDRA
Application year: 2000
Main classification: G06F17
IPC codes: G06Q10