#agile-dev

這是過去一個月來主要遇到的兩個問題，目前的理解如下： 1. 當project從0開始，如何做出第一個user story?   → 切出所有involve的元件，必要的話再逐項拆細 2. 至於architecture的部分，不用一口氣全部到位，而是依照當時需求逐步增加 > The thing about agile architecture is that it is always evolving, not planned up-front or completed in the first few sprints. In the case of going from zero to value, I'd suggest that you look at the user story, the acceptance criteria (constraints, UATs, etc.) and derive what the minimum architecture required is. Make a small architecture sketch, outlining the components needed for this story, and then you can break down the tasks accordingly. Your components will move, change, and evolve over time, but that is a good thing. The important thing is to focus on the value, not the system. 參考來源： http://stackoverflow.com/a/7994970/3758703