I'm going with option C as well. Trying to define the entire Sprint Backlog during the planning meeting would be way too time-consuming and unrealistic.
I'm going with option C as well. Trying to define the entire Sprint Backlog during the planning meeting would be way too time-consuming and unrealistic.
I agree with Yuette. The Scrum Guide states that only enough of the Sprint Backlog needs to be defined to get the team started. Anything more would be overkill.
Option C seems to be the most reasonable approach. We don't need to define the entire Sprint Backlog, but enough to get us started and understand the work that needs to be done.
Aleshia
2 months agoCelestine
16 days agoHelene
17 days agoGabriele
25 days agoBarbra
2 months agoCristal
2 months agoCassie
Bettina
10 days agoBeatriz
11 days agoNaomi
19 days agoShonda
1 months agoHyun
1 months agoGlory
2 months agoDominque
2 months agoDierdre
2 months agoLashaun
2 months agoYuette
2 months agoKaitlyn
2 months agoTu
2 months agoFiliberto
3 months ago