Nexus Open assessment - question regarding Sprint length
In the Nexus Open assessment, the question about "two factors should be most considered when establishing the length of a Sprint", has the following "correct" answers:
i) The risk of being disconnected from the stakeholders
ii) The level of uncertainty over the technology to be used
Bullet (i) is definitely correct but how does (ii) count for a correct answer? I don't get this.
It also contradicts with the book Nexus Framework for Scaling (https://www.amazon.com/Nexus-Framework-Scaling-Scrum-Continuously/dp/01…) which states the exact opposite regarding the technology used.
Anyone that can shed some light on this?
There are two essential considerations to balance, both of which relate to risk and uncertainty.
- Disconnection from stakeholders will increase uncertainty about the work being performed, due to attenuated feedback. Shorter sprints provide more formal opportunities for inspection and adaptation, and by making Sprint Goals more modest, the risk presented by any failure would decrease. If there is little stakeholder disconnection then longer sprints might be countenanced.
- The more uncertain a Development Team is about the technology needed to build "Done" product increments, the less predictive they can be about any forecast of work. Shorter sprint cycles, by reducing the quantity of work to be estimated and the scope of any associated Sprint Goal, can reduce the risk presented by any failure. If the team are confident regarding technical matters, then the reliability of any forecast they make is likely to increase. More work can be taken on, more ambitious goals can be attempted, and sprint cycles can potentially be longer.
Ok, so when should 'length of a Sprint' be established? If there is nothing like Sprint 0, there could be some kick-off meeting where we discuss about expectations, technology and other stuff before Sprint 1 right? Within that kick-off meeting, will both the matters be taken up?
1. Technology to be used
2. Length of sprint
What else will be discussed?
Sorry for digressing. I have just started to learn here.
thanks,
V.
Ok, so when should 'length of a Sprint' be established? If there is nothing like Sprint 0, there could be some kick-off meeting where we discuss about expectations, technology and other stuff before Sprint 1 right? Within that kick-off meeting, will both the matters be taken up?
What if you would add these kind of things as PBI's, so you enable the team to create the product in the way they are most comfortable with and give them a great learning opportunity?