INTELLIGENT TIMESHEET ASSISTANCE

• US 20120174057A1
• Filed: 03/09/2012
• Published: 07/05/2012
• Est. Priority Date: 07/14/2010
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: NARENDRA, NANJANGUD C., RAJAN, RENUKA S., RYMAN, ARTHUR G., SENGUPTA, BIKRAM, THAKKAR, RAJESH P.
• Application Number:
  US13/417,070
• Publication Number:
  US 20120174057A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management

Abstract

A timesheet assistant mines development items in a repository of a computer to form identified development items. Development context information and effort indicators, associated with the identified development items, are extracted. Statistical analysis is applied to tasks of the identified development items using the effort indicators. Efforts expended on the tasks are predicted using historical data to create effort estimates. Developer reported efforts for the identified items are received, and a timesheet is generated using the development context information, the effort estimates and the developer reported effort. The timesheet is presented for review, verification, and approval.

Claims

1. A method for preparing a timesheet in a software development environment, comprising:

mining, using a processor, development items in a repository of a computer to form identified development items;

extracting, using said processor, development context information, and effort indicators associated with said identified development items;

applying, using said processor, statistical analysis to tasks of said identified development items using said effort indicators;

predicting effort expended on said tasks using historical data to create effort estimates;

receiving developer reported effort for the identified items;

generating a timesheet using said development context information, said effort estimates and said developer reported effort; and

presenting said timesheet for review, verification, and approval.

2. The method of claim 1 wherein mining development items in said repository to form said identified development items further comprises:

mining work items, change sets, estimated effort and status information from a repository of information for a development environment, wherein said work items, change sets, estimated effort and status information describe a volume and complexity of work done and expertise of a developer associated with the work.

3. The method of claim 1 wherein extracting development context information and effort indicators associated with said identified development items further comprises:

extracting changed files from a source code repository; and

extracting effort predictors for use in effort prediction.

4. The method of claim 1 wherein applying statistical analysis to tasks of said identified development items using said effort indicators further comprises:

generating metrics using a work item data extractor and a code parser to determine a time curve and predict effort for subsequent tasks.

5. The method of claim 1 wherein predicting effort expended on said tasks to create effort estimates further comprises:

calculating effort for all said identified development items to form predicted effort thereof; and

performing statistical analysis on said formed predicted effort.

6. The method of claim 1 wherein generating said timesheet using said development context information, said effort estimates and said developer reported effort further comprises:

generating a report in the form of a timesheet, wherein information in the report is in a hierarchical construct with increasing levels of detailed information and including as input additional indications of effort for tasks not represented by artifacts in the repository and assigning tasks to categories based on comparability of effort requirements.

7. The method of claim 1, further comprising:

determining whether said timesheet has been verified and approved;

responsive to a determination that said timesheet has been verified and approved, applying timesheet information to a repository;

using linear regression to fit an effort curve and determine regression coefficients; and

performing periodic re-calibration of said coefficients as more data on said tasks of said identified development items is captured for effort prediction using information from said repository.