How frequently should Agile Release Trains release?
Choose the correct option from below list
14 comments · newest first
SA
Sage
11 months ago
Totally agree with A, it keeps things organized.
JA
Jaime
11 months ago
Once per iteration? That seems too frequent!
AL
Alisha
11 months ago
C sounds great, but is it really practical?
AL
Alesia
11 months ago
I think B makes more sense for flexibility.
VI
Vincent
12 months ago
A is correct! One release per PI is the standard.
VE
Verdell
12 months ago
I’m confused! I thought releases were supposed to happen continuously, but I also remember something about the PI timeframe.
AD
Adell
12 months ago
I’m leaning towards "once per iteration," but I vaguely recall something about continuous delivery being important in Agile.
PE
Pearly
1 year ago
I remember practicing a question about release frequency, and I feel like "on demand" could be a valid choice too.
LE
Leonora
1 year ago
I think Agile Release Trains should release once per PI, but I'm not entirely sure if that's the only option.
GI
Giuseppe
1 year ago
I'm pretty confident the answer is A - one release per PI. That aligns with the Agile principle of frequent, incremental delivery. But I'll double-check the details to be sure.
CA
Carman
1 year ago
Continuous releases (option C) seem like the most Agile approach, but I'm not sure if that's the right answer for Agile Release Trains specifically. I'll have to review my notes on that.
LE
Leota
1 year ago
Hmm, I'm a bit unsure about this one. I know Agile Release Trains are related to Agile development, but I'm not totally clear on the release frequency. I'll have to think this through carefully.
CL
Claudia
1 year ago
I think the key here is understanding the concept of Agile Release Trains. Based on that, I'd say the correct answer is A - one release per PI.
VE
Velda
1 year ago
Okay, let's see. The "Mark Duplicate" button implies that the problem will be marked as a duplicate, so I'm going to go with option B, "Duplicated".