tip ...

master the idea of fixed-length, variable scope efforts.

really, really, really internalize the idea.

seems simple enough, but here are some things ppl miss (1/n)
Right from the start you need to use language that conveys the nature of the effort. Say "well, since this is a variable scope effort..." *10

Repeat. Repeat. Repeat. It will not sink in unless you do.

Treat the end of the time-box as a hard stop.

(2/n)
Be very vocal about "benefits risk" and the need to reduce that uncertainty quickly at first. Use the words "risk" and "uncertainty" a ton...even if it makes people nervous. Otherwise ppl will not internalize it.

Treat the end of the time-box as a non-negotiable.

(3/n)
Be very clear that there will be no "crunch time" or last minute efforts to squeeze stuff in. That's not how you will roll.

Talk about "end to end" slices.

Be extremely clear that near the end, it will be low stress. You will not save it in the last week. (4/n)
If it helps people, share a "plan" about how scope will degrade gracefully to 100% guaranteed hit the end of the timebox.

Help people visualize it (user story mapping, assumption mapping etc.) (5/n)
Figuring out how to communicate fixed length / variable scope efforts in a way that 1) inspires the people doing the work... assuring this isn't a death march, and 2) explains how it works to the people not doing the work ... is an art. (6/end)
You can follow @johncutlefish.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.