1

How to handle multiple stories with changes on the same big Cobol program/module in a Scrum Sprint without ending in a mini-waterfall at the end of the Sprint?

The risk is that the development sub-tasks of multiple stories are linked to each other, with 1 or 2 (pair programming) developers, and by this action all those stories are delivered at the same time. The result is a waterfall Sprint Burndown, and we want to avoid that.

gnat
  • 20,543
  • 29
  • 115
  • 306
Gunther De Cock
  • 11
  • 2

1 Answers1

2

Have you considered swarming? Everyone involved works together and there is little downtime from a development standpoint. Instead of various sub tasks in progress at once they are instead addressed sequentially within a sprint. This also breaks down knowledge and communication barriers.

Glad to see cobol and agile in the same sentence.

Machnik
  • 21
  • 2