Agile/Scrum ≠ Last Minute

Many people in my Scrum training still struggle with “not ready” requirements in the Sprint (Planning).

Does this sound familiar?

❖ Still many questions about the requirements pop up during the Sprint;
❖ Only requirements for the next Sprint are prepared;
❖ Requirements are moved often from one Sprint to the next because they are not finished;

That’s because the Scrum pattern “Ready Backlog Items” was not respected!

Scrum is not about preparing just the next Sprint.

Scrum needs requirements (= Product Backlog) that are DEEP:
❖ Detailed JIT;
❖ Emerging;
❖ Estimated;
❖ Prioritized and Ordered;

Detailed JIT = 2 to 3 Sprints upfront

It means that analysis (= Backlog Refinement) just for the next Sprint leads to last minute analysis > last minute causes stress > Stress causes mistakes > mistakes lower quality.

So, Analysis for just the next Sprint jeopardises the success of your Sprint as still many questions can pop up during the active Sprint if the requirements are still unclear and you don’t have a Sprint Goal.

Metaphor:

JIT Backlog Refinement = 2 to 3 Sprints upfront = a high speed train

Backlog Refinement for the next Sprint = last minute = a local train

Once we start sprinting the high speed train has left the station. With JIT analysis it will arrive a lot earlier than the local train otherwise it becomes a local train that stops at every stop and we arrive much later.

True Scrum practice is preparing enough requirements JIT and then start doing. It means enough functional and technical analysis upfront before sprinting.

❖ Rule 1: don’t start sprinting as long as you don’t know how to build it
❖ Rule 2: don’t plan things if you don’t know yet how to build it
❖ Rule 3: read rule 1

Would you like to know how to learn and practice how to manage JIT requirements let’s get in touch via email training@agileatelier.com or let’s connect on LinkedIn or join our Meetup group.

LEARN.PRACTICE.GROW

Marc,
Executive PO