Revising Estimation

Many teams feel the need to go over finished stories and update their story points in order to reflect the amount of effort needed to complete them. They general notion is that it’s a good idea to fix the original estimates in order to reflect the “true” velocity of the team. Which later on will result in better estimates.

However, as  much as this sounds reasonable, actually doing this is counter productive.

Add a comment

Developing software is a game of decision making under conditions of uncertainty.

Read it again, please: 

Developing software is a game of decision making under conditions of uncertainty.

Once you get this fact into your head, embrace it, and act upon it, I believe that you and your organization will perform much better. You have my word. 
This is really the fundamental challenge we are presented with. This is where part of the complexity comes from.
As a part of an organization developing products, every day you find yourself forced to make decisions in situations with incomplete information and uncertainty.

Add a comment

The Israelite ManifestoAs Gojko Adzic once mentioned, “If there is a Scrum Master, there must be Scrum slaves, too”. And what a fine time in the year to reflect on this quote, with Passover eve coming up this Friday.

From Slavery to Freedom

The Passover Haggadah and the biblical story tells us of Moses, who approached Pharaoh and demanded: “Let My People Go!”, turned a wooden stick into a snake, summoned the ten plagues, yada yada yada (I am cutting out parts irrelevant stuff for my story), crossed the Red Sea, and Hey Presto! The People of Israel became free! At last! Hurray!!!

Only it wasn’t like that.

Add a comment

One of the common confusion around agile requirements is concerning the difference between Acceptance Criteria and Definition of Done. In this post I highlight the differences, and suggest a few practical ways of understanding and expanding your Definition of Done.
In a subsequent post I will address Acceptance Criteria.

The Dry Definition

Definition of Done are the terms which define what must and should (or must not and should not) be performed in order to declare a single requirement as complete. As such, the Definition of Done is a kind of a governing contract between the team and the product owner, reflecting the current standards of work that the team - developers and product owner.

Add a comment

ArrhythmiaWe have recently suffered from Arrhythmia. Irregularity of a normal pace. A disruption. Nothing to worry about, really, just a passing phase. This blog will soon return to it's normal cadence. It is, however, a great opportunity to discuss the phenomenon I nicknamed Agile Arrhythmia.

Huh?

As background reference I looked it up in Wikipedia. Here are some interesting quotes:

Add a comment

How can we help?

Email:
Subject:
Message:
multiply one and three and get

Register to get notified about new blog posts