Author: jcdejong

Posted on

The difference between the ‘forecast’ and the ‘Sprint Backlog’ in Scrum

There is a difference between the forecast and the Sprint Backlog in Scrum. Exactly what this difference is, has eluded me for some time, and it may very well be unclear to you too. The difference may seem subtle but can have real practical benefits as you will learn below.

Continue reading here: https://www.scrum.org/resources/blog/difference-between-forecast-and-sprint-backlog-scrum

Posted on

How to Lead Change Management – A Systemic Approach

Any time leaders try to introduce change into an organization they will be faced with the fear and conflicts of the people involved in the changes. Dealing with these reactions is one of the most delicate, intangible and crucial aspects of leading change management. How can we do that in a systematic and constructive way? Dr. Goldratt was able to identify six levels (or layers) of resistance to change.

  • Level 1: Disagreement about the problem
  • Level 2: Disagreement about the direction of the solution
  • Level 3: Lack of agreement that the solution will bring the expected benefits
  • Level 4: Fear of negative consequences generated by the solution
  • Level 5: Too many obstacles along the road that leads to change
  • Level 6: Not knowing what to do

Read the complete article here: https://www.intelligentmanagement.ws/how-to-lead-change-management-systemic-approach/

Posted on

Getting Results from Sprint Reviews

Some insights of this video include:

  • What could the agenda of a sprint review look like?
    • Show the (big picture) vision of the product
    • What was the sprint goal (vision of the previous sprint)
    • Discussing the sprint itself
      • what went wrong
      • what problems did we run into?
      • how did we solve these problems?
      • what still needs to be solved?
    • Review the increment (not really a demonstration, but an actual review)
    • Now that you’ve seen it, do we need to change anything?
    • Project likely completion dates
    • Collaborate/discuss what should be built next?
      • What is the marketplace we are operating in?
      • What are our competitors doing?
    • Final question: should we change the Product Backlog, should we change?

Posted on

Slaying Technical Debt

In this Scrum Tapas video, Professional Scrum Trainer Todd Miller discusses the concept of Technical Debt and ideas on how to work to remove it. He looks at different concepts and why removal over time is important to the long-term viability of a product.

  1. create a “Wall of Tech Debt” visible area
  2. every time you encounter tech debt, add a sticky note
  3. at each sprint planning, add a sticky to the sprint backlog and fix it.