esciencecenter-digital-skills/teamwork-for-research-software-development

Some comments on lesson 6 "Challenges for Agile way of working in research"

Closed this issue · 0 comments

Style
Can we format the Solutions part using a solution syntax?

Text
Cultural challenge: Many scientists are traditionally used to working individually in an isolated silo, without proper version control. I dont think the link between working individually and using version control is clear here.

Large-scale projects challenge: Because scientific research is often not an optimization problem but an explorative journey, emergent design in iterative sprints does not always lead to the best large-scale functionality and/or desired research outcomes. I found it hard to understand this sentence, can we break it into smaller parts and elaborate it.

Distributed expertise challenge: In Agile methodologies it is often assumed that a task can be picked up by any team member. In Agile resources, it is explained that a Scrum team is a cross-fucntional team (group of people with different functional expertise). Therefore, the assumption that a task can be picked up by any team member is not valid.

What is “value” challenge: The goal of the Agile way of working is to maximize value for the customer. I understand what is meant by this section, we want to explain that it is not easy to define the "value" and "user" in research projects. However, this section needs revision. The goal of agile is minimizing technical risks and increasing agility while considering user feedback. (Just for more info: to measure agility (Agile progress), the flow between "Market value" and "Organizational capability" is inspected.)

keypoints: Agile methodologies can be adapted so that they work well in a research setting. Perhaps we can add some more specific points about challenges and solutions.