I have always thought that this will be an iteration of another failure. After a short iteration 2 success, the team also needs more adaptation to maintain a stable speed. The medium term that iterations, it looks at the chaos, often being stuck, and there is a solution to someone a problem. The defects in the previous code did not have enough code now, making the project to the correct road more difficult.
But I am wrong.
After today I have worked hard, I found this iterative task seems to have been completed. Although it is still very imperfect, you can say a lot of places that must be improved. But after all, it is a part that has been completed. Perhaps, it is a good way to ensure that you can't do it.
For example, for me, my shortcomings are often lazy because I want too much. This week's state is equally, a machine is installed, and there will be a day in the road. Iterative task list, so that I eventually complete a half of the tasks of the entire iteration today, avoiding it, because my reason makes iteration failure.
It is found that the current iteration has become a variation of 2 weeks. The first one of the two iterations will always produce more legacy issues. The predicted task of the next iteration is often sufficient to resolve legacy issues while completing new features. And do not produce more legacy. This is actually equivalent to one iteration 2 weeks, and the end of the first iteration is equivalent to a review of the medium term iterative. It turned out that two weeks were tried, but at the time, I still think that everyone has a little effort to arrange for 2 weeks, so adjust to the present method, it seems that it is not bad.
The next iteration is completed, version 1 is released. This time you can get a customer (that is, our boss). If everything goes well, you will celebrate it after you are ready to complete, and then leave a day.
