EMERGING TRENDS IN SOFTWARE ENGINEERING
DEVOPS
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
3-4 weeks
|
|
|
2-4 weeks
|
|
|
1-4 weeks
|
|
|
4-8 weeks
|
Detailed explanation-1: -Sprints in scrum can be as long as you want; however, it’s most common for sprint length to be between 1 and 4 weeks. Teams running Scrum sprints need to decide what makes sense for them. We often see that team’s first instincts lean toward the extreme: Either 1-week sprints or 4-weeks sprints.
Detailed explanation-2: -Sprints are time-boxed periods of one week to one month, during which a product owner, scrum master, and scrum team work to complete a specific product addition. During a sprint, work is done to create new features based on the user stories and backlog. A new sprint starts immediately after the current sprint ends.
Detailed explanation-3: -Sprint planning is limited to a maximum of eight hours. The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.