The project team is currently facing a difficult situation originating from their difficulty in envisioning the future and the necessary steps to reach it together with a certain loss of motivation due to a strong feeling of stagnation. You try to unlock the situation by proposing a workshop. Which one would fit the best?

The scenario describes a team suffering from a lack of vision, unclear future steps, and a feeling of stagnation. The workshop described in option B, often known as the "Stairs to Heaven" or a similar timeline-based retrospective, is the most suitable solution. It is a holistic technique that addresses all the identified issues. By asking the team to reflect on the steps already taken ("steps down"), it acknowledges their past efforts and progress, which directly counteracts the feeling of stagnation and boosts motivation. Simultaneously, by focusing on the "steps up," it helps the team collaboratively envision the future, define clear milestones, and create an actionable plan, thus restoring a sense of direction and purpose.

A. This role-playing approach can create a confrontational atmosphere and focuses on debating arguments rather than collaboratively building a positive, shared vision for the future.
C. While team-building activities can improve morale, this option does not address the core project-related problems of unclear vision and lack of a concrete plan.
D. This approach is purely forward-looking. It fails to address the team's "strong feeling of stagnation" and "loss of motivation," which are best addressed by also reflecting on past accomplishments.

1. ISTQB® Certified Tester Foundation Level - Agile Tester Syllabus (Version 2014): Section 3.3.2, "The Activities of a Tester in an Agile Team," states that a tester contributes to retrospectives to "improve team processes." The technique in option B is a classic retrospective format designed for process and morale improvement. It aligns with the retrospective goal of reflecting on the project to identify improvements, which is a core agile practice emphasized in the syllabus.

2. Derby, E., & Larsen, D. (2006). Agile Retrospectives: Making Good Teams Great. The Pragmatic Bookshelf. This foundational text, often used in university software engineering courses, describes various retrospective activities. The "Timeline" activity (Chapter 6, pp. 67-70) is a similar concept to the "Stairs" metaphor. The authors explain that creating a timeline helps the team "see the 'arc' of the iteration or project" and "notice patterns," which is essential for overcoming stagnation and planning future steps.

3. Dingsøyr, T., Nerur, S., Balijepally, V., & Moe, N. B. (2012). A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software, 85(6), 1213-1221. https://doi.org/10.1016/j.jss.2012.02.033: This academic review discusses key agile practices, including retrospectives (p. 1216). It highlights their role in learning and adaptation. The workshop in option B is a structured method for team-based learning and adaptation, directly addressing the team's inability to envision and plan the necessary steps forward.