New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

GAQM CSM-001 Exam - Topic 4 Question 99 Discussion

Actual exam question for GAQM's CSM-001 exam
Question #: 99
Topic #: 4
[All CSM-001 Questions]

You are the new Scrum Master at a company currently doing RUP in three month iterations. Your current task in switching from RUP to Scrum is to define how long the Sprint cycle should be. In what units of time should you define the sprint cycle?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Delisa
2 months ago
A fixed amount of hours? Really? That seems impractical.
upvoted 0 times
...
Elenora
2 months ago
Definitely agree with weeks, it keeps momentum!
upvoted 0 times
...
Cherelle
2 months ago
Sprints are usually 1-4 weeks long.
upvoted 0 times
...
Sarah
3 months ago
Days could work too, but I prefer weeks for better planning.
upvoted 0 times
...
France
3 months ago
Months? That feels too long for Agile.
upvoted 0 times
...
Filiberto
3 months ago
I feel like defining Sprints in hours might be too granular. I recall that most resources suggest weeks or days for better planning.
upvoted 0 times
...
Luke
3 months ago
I practiced a question similar to this, and I think a fixed amount of weeks makes sense, but I wonder if we should consider the team's capacity too.
upvoted 0 times
...
Ellsworth
4 months ago
I think Sprints should be a fixed amount of days, like 14 or 21, but I’m a bit confused about how that fits with the three-month iterations we’re currently using.
upvoted 0 times
...
Rebbecca
4 months ago
I remember that Sprints are usually defined in weeks, but I'm not sure if excluding holidays is the best approach.
upvoted 0 times
...
Tennie
4 months ago
I think the best approach here is to define the sprint cycle in a fixed amount of weeks, excluding holidays. That aligns with the Scrum framework and gives the team a consistent rhythm to work within.
upvoted 0 times
...
Glenn
4 months ago
I'm a bit confused on this one. Should the sprint cycle be defined in months, weeks, days, or hours? I want to make sure I choose the right option to properly transition the team from RUP to Scrum.
upvoted 0 times
...
Vicki
4 months ago
I've got this! The sprint cycle should be defined in a fixed amount of days. That way, the team can plan their work in a predictable way and it's easy to track progress.
upvoted 0 times
...
Lewis
4 months ago
Hmm, I'm a little unsure about this one. I know Scrum typically uses a fixed time period for sprints, but I'm not sure if it's weeks, days, or something else. I'll have to think this through carefully.
upvoted 0 times
...
Ben
5 months ago
This is a pretty straightforward question. I think the best approach is to define the sprint cycle in a fixed amount of weeks, excluding holidays. That way, the team can plan their work consistently and account for any time off.
upvoted 0 times
...
Justa
6 months ago
Haha, a fixed amount of hours? What is this, the Matrix? C. Days is clearly the way to go, people.
upvoted 0 times
Jina
5 months ago
A) A fixed amount of months
upvoted 0 times
...
...
Leontine
7 months ago
I'm going with A. A fixed amount of months is the traditional way to do it, and why mess with a good thing?
upvoted 0 times
Trinidad
5 months ago
B) A fixed amount of weeks, excluding holidays
upvoted 0 times
...
Verda
5 months ago
A) A fixed amount of months
upvoted 0 times
...
...
Elise
7 months ago
B. A fixed amount of weeks, excluding holidays, makes the most sense to me. That way we can plan around team members' schedules.
upvoted 0 times
Odette
5 months ago
B) A fixed amount of weeks, excluding holidays
upvoted 0 times
...
Rolland
6 months ago
C) A fixed amount of days
upvoted 0 times
...
Rolande
6 months ago
A) A fixed amount of months
upvoted 0 times
...
Luther
7 months ago
B) A fixed amount of weeks, excluding holidays
upvoted 0 times
...
Reyes
7 months ago
A) A fixed amount of months
upvoted 0 times
...
...
Leana
7 months ago
I believe hours would be too granular for defining sprint cycles.
upvoted 0 times
...
Kirk
7 months ago
D. A fixed amount of hours is the way to go. That way we can really maximize productivity during the sprint!
upvoted 0 times
Serita
5 months ago
D. A fixed amount of hours is the way to go. That way we can really maximize productivity during the sprint!
upvoted 0 times
...
Dottie
5 months ago
D) A fixed amount of hours
upvoted 0 times
...
Coral
5 months ago
C) A fixed amount of days
upvoted 0 times
...
Kenneth
6 months ago
B) A fixed amount of weeks, excluding holidays
upvoted 0 times
...
Billi
7 months ago
A) A fixed amount of months
upvoted 0 times
...
...
Lura
8 months ago
I disagree, I think days would be a better unit of time for sprint cycles.
upvoted 0 times
...
Flo
8 months ago
I think the answer is C. A fixed amount of days seems like the most logical unit of time for a Scrum sprint cycle.
upvoted 0 times
An
7 months ago
I prefer A) A fixed amount of months for the sprint cycle, it gives a longer planning horizon.
upvoted 0 times
...
Coral
7 months ago
I think B) A fixed amount of weeks, excluding holidays, could also work well for defining the sprint cycle.
upvoted 0 times
...
Merilyn
8 months ago
I agree, C) A fixed amount of days makes the most sense for a Scrum sprint cycle.
upvoted 0 times
...
...
Kara
8 months ago
I agree with Harley, weeks make more sense for sprint cycles.
upvoted 0 times
...
Harley
8 months ago
I think we should define the sprint cycle in weeks.
upvoted 0 times
...

Save Cancel