Agile/Scrum ≠ last minute!?

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.

No alt text provided for this image

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 reduces 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:

No alt text provided for this image

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


No alt text provided for this image

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 analysis upfront before sprinting.

No alt text provided for this image

? 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.

No alt text provided for this image

LEARN.PRACTICE.GROW

Marc, Executive PO

There can be a question to Rule 1- Unless you start sprinting you wouldn't know how to build it entirely as there can be surprises and unknowns that were either missed in the refinement, or you get to know as you proceed. While the team might have a fair idea on the how part but might not be the complete idea of how.

赞
回复

要查看或添加评论,请登录

Marc Vandyck的更多文章

  • Agile is all about Feedback

    Agile is all about Feedback

    This is an open letter to all people who are responsible in hiring and developing Agile people. Dear, Isn’t FEEDBACK…

    10 条评论
  • 3 Elements for Successful Scrum

    3 Elements for Successful Scrum

    Out of 100 companies practicing Scrum only 42 are successful. That means 58 are struggling with Scrum.

  • Respect the Method, Respect the Framework!

    Respect the Method, Respect the Framework!

    I got annoyed AND inspired by some conversations I had if we can do LEGO? SERIOUS PLAY? online. It compelled me to…

    2 条评论
  • I Scrum so I am Agile?

    I Scrum so I am Agile?

    Of course NOT! Isn’t Scrum Agile? Nyenk (= no and yes). Scrum can help you deliver software in a better way but doesn’t…

    6 条评论
  • Job interviews with Lego? (part 1) – the method

    Job interviews with Lego? (part 1) – the method

    How do you select the right people for YOUR team? That was the question I needed answered last year when I was asked by…

    17 条评论

社区洞察

其他会员也浏览了