

#Scrum agile taskboard software
The aim of this research effort is to comprehensively evaluate the usability of four software project management tools based on experimental findings as well as heuristic assessment. Agile software project management methodologies have made their way into the mainstream culture of software development and have gotten the attention of software engineers and researchers due to their rapid growth. The successful management of software projects requires taking human and managerial factors into consideration. In case of customization, a task board's structure should be adjusted since this is the only beneficial kind of customization, that additionally complies more precisely with the concept of fast and easy project overview. They may be better served by focusing on the original task board design and by applying only carefully selected adjustments. According to our findings, agile teams should rethink their current task board design. The original task board design is more beneficial than individual colored codings and changed card sizes. Our findings yield that only the customized task board design with modified structures reduces the required time. In an eye tracking study with 30 participants, we compared an original task board design with three customized ones to investigate which design shortened the required time to identify a particular story card. Hence, task board customization is in conflict with the agile practice of fast and easy overview for everyone. The increased effort impedes the work of both the team and team externals. Although the customizations are intended to improve the task board's usability and effectiveness, they may also complicate its comprehension and use. They modify the structure of boards, define colored codings for different purposes, and introduce different card sizes. Teams often customize their task boards according to the team members' needs. It provides a good overview of the project status. The task board is an essential artifact in many agile development approaches.

We reflect on these findings through the lens of media synchronicity theory and conclude that this theory is useful for explaining the current use and future development of software tools to support agile globally distributed development teams. While distributed teams use a software only approach, a large portion of collocated teams we studied utilize a combination of a paper based task board and the archiving and integration properties of the software solution. Our findings indicate that the majority of the investigated companies that use the agile method Scrum also work with a software tool to support Scrum.

We interviewed a total of 15 developers and concluded that the paper-based task board currently still has many advantages when compared to its software-based solution. We investigate the deployment of these tools through a field research in 4 different companies that feature agile and globally distributed development teams. In this study we focus on the usage of such tools and task boards in particular. Software-based tooling has become an essential part of globally disitributed software development.
