Iteration can be extended

[jdudley1123]

Suggestion from Charné

[suninthesky]

There's something really interesting about how iterations build on each other - I found the need to duplicate an iteration when extending our own testing of outcomes a few weeks ago.

FYI @trompodrone

[jdudley1123]

I was thinking we could do something like on Ochre where we keep a record of building on or pivoting an iteration.

[trompodrone]

@jdudley1123 Like that idea, sort of like a timeline?

[jdudley1123]

Talking to @trompodrone about this, and it seems like we might just want to be able to change the debrief date of an iteration to extend it rather than create a new copy.

[suninthesky]

@trompodrone @jdudley1123 Does this mean the originally planned debrief doesn't happen? Debriefs seem to be important moments of reflection independent of work completed - important to consider how the execution of this feature might affect the behaviour we're looking to support.

[jdudley1123]

Hmm, good point. We could go for two debriefs, though that might end up being just as complicated as creating a copy. Semantically, creating a new iteration when you're really just extending an iteration doesn't seem right.

[trompodrone]

In practice, it would mean that the debrief would be delayed but a mid-point check-in would usually happen in place of the original debrief to check-in on a team's progress.