TY - JOUR
T1 - Industry Application of Software Development Task Measurement System
T2 - TaskPit
AU - Suthipornopas, Pawin
AU - Leelaprute, Pattara
AU - Monden, Akito
AU - Uwano, Hidetake
AU - Kamei, Yasutaka
AU - Ubayashi, Naoyasu
AU - Araki, Kenji
AU - Yamada, Kingo
AU - Matsumoto, Ken Ichi
N1 - Publisher Copyright:
© 2017 The Institute of Electronics, Information and Communication Engineers.
PY - 2017/3
Y1 - 2017/3
N2 - 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.
AB - 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.
UR - http://www.scopus.com/inward/record.url?scp=85016098335&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85016098335&partnerID=8YFLogxK
U2 - 10.1587/transinf.2016EDP7222
DO - 10.1587/transinf.2016EDP7222
M3 - Article
AN - SCOPUS:85016098335
SN - 0916-8532
VL - E100D
SP - 462
EP - 472
JO - IEICE Transactions on Information and Systems
JF - IEICE Transactions on Information and Systems
IS - 3
ER -