Industry Application of Software Development Task Measurement System: TaskPit

Pawin SUTHIPORNOPAS  Pattara LEELAPRUTE  Akito MONDEN  Hidetake UWANO  Yasutaka KAMEI  Naoyasu UBAYASHI  Kenji ARAKI  Kingo YAMADA  Ken-ichi MATSUMOTO  

Publication
IEICE TRANSACTIONS on Information and Systems   Vol.E100-D   No.3   pp.462-472
Publication Date: 2017/03/01
Online ISSN: 1745-1361
Type of Manuscript: PAPER
Category: Software Engineering
Keyword: 
processs measurement,  system development,  case study,  

Full Text: PDF(2MB)
>>Buy this Article


Summary: 
To identify problems in a software development process, we have been developing an automated measurement tool called TaskPit, which monitors software development tasks such as programming, testing and documentation based on the execution history of software applications. This paper introduces the system requirements, design and implementation of TaskPit; then, presents two real-world case studies applying TaskPit to actual software development. In the first case study, we applied TaskPit to 12 software developers in a certain software development division. As a result, several concerns (to be improved) have been revealed such as (a) a project leader spent too much time on development tasks while he was supposed to be a manager rather than a developer, (b) several developers rarely used e-mails despite the company's instruction to use e-mail as much as possible to leave communication records during development, and (c) several developers wrote too long e-mails to their customers. In the second case study, we have recorded the planned, actual, and self reported time of development tasks. As a result, we found that (d) there were unplanned tasks in more than half of days, and (e) the declared time became closer day by day to the actual time measured by TaskPit. These findings suggest that TaskPit is useful not only for a project manager who is responsible for process monitoring and improvement but also for a developer who wants to improve by him/herself.