Browse Prior Art Database

Method for automatically creating project management tasks when a "to do" entry is created in source code

IP.com Disclosure Number: IPCOM000234164D
Publication Date: 2014-Jan-15
Document File: 2 page(s) / 67K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a system for automatically making project management aware of "invisible" TO DO tasks - created by programmers in source code - without requiring onerous, manual, housekeeping.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 2

Method for automatically creating project management tasks when a "to do" entry is created in source code

During the software development process source code is often developed in a "piecemeal" fashion; source code may be checked-in (delivered) to a repository several times before the program code is complete - despite being still within the bounds of a single project task. During the development cycle a programmer may put "to do" items into the code as an "aide memoir" to perform an action in the future.

    This use of "to do" allows the programmer to note down and defer actions until later in the development cycle and can be considered a good thing. Generally only when a person actually views the code does the presence of these outstanding pieces of work become visible to anyone other than the original (or a subsequent) developer. Typically, the list of future actions is only known to the programmer who originally put the "to do" items into the source code and anyone who subsequently reads the source code - they are not easily visible to project management without

work being performed.

    The "to do" actions could be backed by a task management system, manually created in a project management system, which would allow for external visibility of

the outstanding work. However, that would require specific project management

work to be undertaken to achieve the desired effect and as such "to do" items are typically fairly informal, might a) result in such items not being created by programmers and/or b) some formality/rigour being required.

    The drawback of the option above is that specific work would need to be undertaken to make the items visible and, furthermore, there would also be the issue of following up on the tasks once the source code "to do" items were complete.

The core idea described here is to provide an automatic way of managing

project management task creation and maintenance from the insertion and editing of "to do" statements in source code.

    The advantages of the solution is the provision of visible project management task tracking directly from source code "to do" items with minimal manual effort. It

will allow for enhanced visibility of source code work items without the need for

explicit user actions from either programmers or project managers.

    The core idea is the maintenance of tasks in a project mana...