Clearly, the answer is D. Scrum is all about shipping working software at the end of each Sprint. Anyone who thinks otherwise must be living in a different galaxy.
A) After the acceptance testing phase. Nope, that's not it. Scrum is about getting working software into the hands of users as quickly as possible, not waiting for lengthy testing cycles.
E) When the Product Owner asks to create one. Wait, what? That's not how Scrum works at all. The Product Owner doesn't just randomly demand an increment when they feel like it.
D) At the end of every Sprint. That's the whole point of the Scrum framework - to deliver a potentially shippable increment of working software at the end of each Sprint.
D) At the end of every Sprint. That's the whole point of the Scrum framework - to deliver a potentially shippable increment of working software at the end of each Sprint.
C) Every 3 Sprints. I think having a new increment of working software every 3 Sprints allows for more time to work on larger features and improvements.
Valene
27 days agoBrendan
9 days agoJoaquin
11 days agoNickolas
29 days agoLauran
30 days agoRickie
4 days agoWilda
15 days agoAlishia
1 months agoDanica
3 days agoLinette
9 days agoGertude
14 days agoJerilyn
1 months agoKate
7 days agoFausto
10 days agoMalcom
15 days agoNiesha
2 months agoNickolas
2 months agoJettie
3 months ago