PROJECT MANAGEMENT SYSTEM

• US 20080052146A1
• Filed: 05/31/2007
• Published: 02/28/2008
• Est. Priority Date: 05/01/2006
• Status: Abandoned Application

• Current Assignee: TopCoder, Inc. (Wipro Limited)
• Original Assignee: TopCoder, Inc. (Wipro Limited)
• Inventors: Fernandez-Ivern, Javier, Norman, Lorie, Hughes, John, Hughes, Robert, Messinger, David, Jefts, Anthony
• Application Number:
  US11/755,909
• Publication Number:
  US 20080052146A1
• Time in Patent Office: Days
• US Class Current: 705/9
• 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/06313 Resource planning in a project environment
• CPC Class Codes: G06Q 10/06393 Score-carding, benchmarking or key performance indicator [KPI] analysis

Abstract

A production contest management system enables management of workflow and scoring of projects, for example in a production contest environment. A project is divided into “phases.” Project managers can specify project phases, and for each phase, required timing and deliverables. For phases that involve a review (e.g., screening, review board, peer review), scorecards used to perform the review may be specified. The scorecards are made accessible electronically to one or more reviewers. The scorecards may be available on-line, or may be downloaded, completed, and then uploaded. Once received, scorecards are tallied. In this way, the management system helps coordinate production of a product that is produced using production competitions. The system allows for simultaneous management of multiple projects and production teams.

Claims

1. A method for managing a project, comprising:

facilitating selection of a template for a project, the template comprising a number of project phases, the project phases comprising a submission phase and a review phase;

receiving configuration for the phases of the project, the configuration comprising designating a start time for a first phase of the project and adding a second review phase to the project;

automatically starting the project at the start time of the first phase of the project;

providing the status of the project upon request; and

automatically starting the added phase when previous phases have completed.

2. The method of claim 1, wherein the project is a production contest.

3. The method of claim 2, wherein the project is a production contest for the production of a software component.

4. The method of claim 2, wherein the project is a production contest for the production of a software application.

5. The method of claim 1, further comprising receiving submissions.

6. The method of claim 4, wherein the step of providing status comprises providing information about deliverables due.

7. The method of claim 1, further comprising, during the review phase, facilitating the completion of scorecards.

8. The method of claim 6, wherein the scorecards are transmitted to a users'"'"' computer, completed on the users'"'"' computer, and received from the users'"'"' computer.

9. The method of claim 6, wherein the scorecards are completed on-line.

10. The method of claim 1, further comprising, during the added phase, facilitating completion of scorecards.

11. A method for conducting a production competition, comprising:

facilitating creation of a scorecard comprising questions and question types;

storing the created scorecard;

facilitating specification of a review phase, the review phase configured to require completion of the created scorecard;

facilitating specification of a project, the project configured to include the specified review phase;

receiving submissions from submitters;

upon receipt of the submissions, making the scorecards available electronically to reviewers for completion during the review phase.

12. The method of claim 11, wherein the scorecard comprises groups of questions.

13. The method of claim 11, wherein the method comprises facilitating creation of two or more scorecards, and the two or more scorecards are each completed by reviewers during the review phase.

14. The method of claim 11, wherein the submissions are assigned an identifier such that the identity of the submitter is not revealed to reviewers.

15. The method of claim 11, wherein the submissions are manually screened to assure formal compliance with submission rules.

16. The method of claim 11, wherein the submissions are automatically screened for formal compliance with submission rules.

17. The method of claim 16, wherein the review phase begins upon successful automatic screening of a submission.

18. The method of claim 11, wherein an aggregation phase is configured following the review phase.

19. The method of claim 11, wherein the production competition is for the development of a software component.

20. The method of claim 11, wherein the production competition is for the development of a graphic design.

21. A contest-based development management system, comprising:

a project phase specification subsystem;

a submission receiving subsystem;

a scorecard development subsystem;

a scoring subsystem for facilitating scoring of received submissions during a specified project phase using developed scorecards; and

an award management subsystem for managing awards granted to submitters based on the results specified by the scoring subsystem.

22. The system of claim 21 wherein the project phase specification subsystem facilitates specification of criteria for ending phases prior to a specified end date/time.

23. The system of claim 22, wherein the criteria comprise submission of specified deliverables.

24. The system of claim 22, wherein the criteria comprise successful passing of automatic screening.

25. The system of claim 22, wherein the project phase specification subsystem facilitates specification of a scorecard for use in a project phase.

26. The system of claim 21, wherein the submission receiving subsystem facilitates uploading of submissions.

27. The system of claim 21, wherein the submission receiving subsystem comprises a screening subsystem.

28. The system of claim 21, wherein the submission receiving subsystem facilitates the submission of submissions such that the identity of the submitter is not known to a reviewer.

29. The system of claim 21, wherein the scorecard development subsystem facilitates development and storage of scorecards.

30. The system of claim 21, wherein the award management subsystem provides information about awards that are due and awards that have been sent.

31. A contest-based development management method, comprising:

facilitating development and storage of scorecards;

facilitating specification of project phases;

receiving submissions during one or more of the project phases;

facilitating scoring of received submissions during a specified project phase using developed scorecards; and

managing awards granted to submitters based on the results specified by the scoring subsystem.

32. The method of claim 31 wherein facilitating specification of project phases comprises facilitating specification of criteria for ending phases prior to a specified end date/time.

33. The method of claim 32, wherein the criteria comprise submission of specified deliverables.

34. The method of claim 31, wherein the criteria comprise successful passing of automatic screening.

35. The method of claim 31, wherein the project phase specification comprises facilitating specification of a scorecard for use in a project phase.

36. The method of claim 31, wherein the step of receiving submissions further comprises facilitating uploading of submissions.

37. The method of claim 31, wherein the method further comprises screening the submissions.

38. The method of claim 31, wherein receiving submissions comprises facilitating the submission of submissions such that the identity of the submitter is not known to a reviewer.

39. The method of claim 31, wherein managing awards comprises providing information about awards that are due and awards that have been sent.