Entries

To manage a lazy team with a Burndown Chart???

Burndown Chart is a very common useful artifacts in Agile Software Development teams. The main purpose of the Burndown chart is to keep track of the development progress and compare with what is planned at the beginning of the iteration. However, this is not a mean to check if the team has (intentionally) selected less work than they are capable to complete. Firstly, Burndown chart is not the arti...

Share with:

Use Cases or User Stories

This is the first article I translated for InfoQ. The topic is "Use Cases or User Stories"There is often misunderstanding about the different artifacts and techniques as if one were replacing the other. "Use Cases or User Stories" is one of such question.The other misunderstanding is even more fundamental, not understanding enough about the techniques in question.Mike Cohn did ...

Share with:

Introduction

Welcome to my blog! I always want to record down things I learned. But I am always lazy. Having spent some time thinking what to write and discussed with my friends, I decided to open a new blog for this.I have always been interested in software engineering, and realised that the current state of knowledge is far from enough for the problems we face in practice. I always like to read about differe...

Share with:

Hello World

Hi, This is a testing entry!...

Share with: