Filter by

What do the Developers do in the last week of the Sprint?

June 27, 2022
But when you have scrum, for example, you need to deliver an increment every single sprint and that increment needs to be done. So the team needs to have a thing called a Definition of Done and done does not mean met the acceptance criteria. Doesn’t just mean that, there should be other considerations as well. So there’s the definition of done. I don’t want to really call it the checklist for how we do things around here, because that might be a bit too process-oriented and maybe a bit too detailed. There’s a nice balance between trust and being clear what we need to do, but as such the team would know what they need to do for something to be called on at the end of the sprint so they can show something at the end of the sprint. That’s all fine. But what do the developers do in the last week of the sprint? It feels like a loaded question because the assumption that I’m reading from the question is that the developers, in your case, write the code, and then they hand it off to some people who do some testing.

Meaning of Purpose

June 15, 2022
Scrum Guide 2020 mentions Sprint Goal and Product Goal because Scrum teams must have a Share Goal. The Share Goal is always essential, even though the Scrum Guide didn't say it before. Basically, the Common Goal helps the Scrum Team become consciously Autonomous. Because Autonomy will lead to chaos if the group doesn't have a Share Goal. (See picture below) In this article, I would like to share the problems the Scrum Team usually faces when setting their goals and making plans not to be unified or linked to achieving a Common Goal. Thereby, I share with everyone a compact tool that makes it easier for you to define the valuable Share Goals.
Webcast

Establishing a "Common Language" on a Scrum Team

January 6, 2022
Words matter, especially when working in any team setting. Words that are spoken or written by one person can have different meanings when read or heard by another. Scrum Teams have multiple members, which means the interpretation of words used in the team setting increases with each member. The chances of misinterpretation also increases. Shared understanding among members is needed to reduce complexity and provide greater clarity. So the need for a "common language" becomes critical to produce value every Sprint. Create your own playbook to help your teams and organization develop their "common language". In this Scrum Pulse webinar, Professional Scrum Trainer John Riley  demonstrates some theory and components behind a "common language". Words and phrases become less about jargon and more about shared understanding. You will also see some techniques to use in developing a team's common language, and how this language helps a team create artifacts. Some of these artifacts include Product Goals, team agreements, and Product Backlog Items.
Webcast

5 Ways to Improve Your Scrum Team's Process

November 3, 2021
There is a lot going on when it comes to delivering complex products in an uncertain and constantly changing world. In this webinar, Scrum.org Professional Scrum Trainer Stephanie Ockerman breaks it down to 5 ways Scrum Teams can discover their opportunities to improve the many different aspects of their process.
Webcast

Using Objectives and Key Results (OKRs) in Scrum

September 1, 2021
Objectives and Key Results (OKRs) act as goal-setting framework for defining and tracking objectives and their outcomes. OKRs are often misunderstood and are a powerful practice to create razor sharp organisational focus. Isn’t Scrum about goals and focus as well? There is the Vision, the Product Goal, the Sprint Goal as well as the Sprint Review. These elements of Scrum can be very well combined with OKRs. Actually, you might want to turn it around, start with OKRs and map your Scrum implementation to them. In this Scrum Pulse webinar Professional Scrum Trainer Ralph Jocham with Agile Actors #learning  gives a quick intro to OKRs, and you then you will learn how Scrum can benefit from using OKRs to create a network of responsibility from the vision down to individual Sprint Goals. This responsibility network offers a transparency most corporations long for.
Webcast

Goals, Measures, and other Mysteries - How Evidence-Based Management Helps Focus and Improve What Matters

April 8, 2021
In this discussion, Ralph Jocham, Don McGreal, and Patricia Kong discuss how to improve goals by adding specific measures to know when goals are achieved, how to seek toward goals using empiricism, and how to choose measures to help inform improvements. They will talk about Evidence-Based Management, a framework developed by Scrum.org to help organizations use empiricism to set goals and make progress toward those goals. 

A Home for Product Goal, Definition of Done, and Sprint Goal

November 19, 2020
In the 2020 Version of the Scrum Guide, the commitments were introduced for each artifact. These then became an element of Scrum; in that they need to be used to gain the maximum value that the Scrum Framework offers. They were always part of a Professional Scrum approach, now there is a clear connection of these commitments to the artifacts. They increase transparency, and the focussed delivery of Value. Each of the commitments now clearly support and sustain an artifact.
Document

The Scrum Guide

November 18, 2020
Scrum is defined completely in the Scrum Guide by Ken Schwaber and Jeff Sutherland, the originators of Scrum.  The Scrum Guide is maintained independently of any company or vendor and therefore lives on a brand neutral site.  The Scrum Guide is translated and available in over 30 languages.

Hiren's Secret Conversation With Covid.

May 3, 2020
*Covid is a fictional character based on my imagination that represents the strain of CoronaVirus that is causing the disease Covid-19. This is just a very simple and sincere attempt to put my knowledge and understanding about Covid-19 to test in this article and I tried making the connection with Scrum. I hope you enjoy it.