Monthly Archive

For August, 2018

User Stories

A good way of composing Product Backlog items is using “user stories”. This is an example:

As an end user, I want to get a report on my account activity, to check if everything is OK.

Yes, it’s small. That’s the point! We prefer to have small items, because it makes it easier to control the project. We can also produce enough 100% done small items in each iteration, while if the items are large, it’s hard to say when they are really done.

Continue reading

Product Backlog Items

No, it’s not OK to have an item like “create the solution architecture” in the Product Backlog, because it’s predictive. We need to design the product iteratively.

We only have functions there; things that the customer can understand, and when produced, can try out and give us feedback. That’s why Product Backlog Items should have two characteristics:

Continue reading

Starting the Project

The first thing we should do is to create the “Product Backlog”. It’s the list of features we have thought about for the project. It’s the definition of the scope.

However, Scrum is not predictive, so we do not plan upfront. Instead of creating a complete Product Backlog, we just add enough items for the next few cycles (aka iterations or Sprints). Then we will start the first cycle and keep updating the Product Backlog “adaptively”.

Continue reading

Is Agile New?

Can you imagine no one thought about or tried adaptation 2000 or 3000 years ago? I can’t. I just can’t believe it was invented in the last 20 or 30 years. Just imagine ancient wars; were they predictive, or adaptive?

Of course we didn’t have modern labels such as Agile, or new frameworks such as Scrum, but the concepts had been there. At least, that’s how I believe.

Continue reading