Developers need to comprehend new code on a regular basis; a demanding task that gets complicated as projects grow in complexity and size. To help developers, documentation is typically added in the form of code comments, design documents, system documents, to name a few examples. Despite all these different kinds of documentation code base comprehension is still challenging and there is room for further exploration of assistance in this space.

In this paper, we explore storytelling as a strategy to assist developers in comprehending a code base, by exploring attachment of stories to developer tasks. We carry out an exploratory study using a design science based research structure with three iterations with feedback from four practitioners working at a consultancy company. We find that our participants typically miss information about rationale and alternatives explored in the documentation, and resort to getting this information from other developers. When asked to write their own stories for tasks our participants sought to add this missing information, but overall found story-writing challenging. We further saw that stories on task-level presents challenges connected to exposure of personal information and integration. We make recommendations for future designs in this space based on our results and list a couple of interesting directions for future work.