你注意到的第一件事是所有程序员都同在一间屋里,经常是围坐在房屋中间的一张大桌子边。程序员们也许在旁边也有桌子和办公室,但你可通过所堆起来的成堆的书来确定大桌子才是真正的活动场所。 XPteamsworkinaseries
你注意到的第一件事是所有程序员都同在一间屋里,经常是围坐在房屋中间的一张大桌子边。程序员们也许在旁边也有桌子和办公室,但你可通过所堆起来的成堆的书来确定大桌子才是真正的活动场所。
XP teams work in a series of fixed iteration cycles. Iterations typically last 1, 2 or 3 weeks each depending on the team. (A given team will almost always use same the iteration size for every iteration.)
XP团队按一系列固定的迭代周期进行工作,根据团队的不同一个迭代周期通常持续1~3星期。(给定团队通常在每个开发周期都用相同的时间)
At the beginning of each iteration, the team gets together with the customer for a planning meeting. In that meeting, they go over the features the customer wants done in that iteration, breaking each feature down into individual engineering tasks. Individual developers then sign up for specific
tasks, and estimate those tasks. No developer is allowed to sign up for more work in the coming iteration than he completed in the previous iteration.
在每个开发周期的开始,团队和客户一起开一个计划会议。在会上他们要核实客户希望在本周期内要完成的特性,将每个特性分割为单独的工程任务。然后每个开发人员登记承担特定的任务并估计这些任务的工作量。不允许开发人员在下一个周期中承担比他上一个周期中所能完成的更多的工作。
During the rest of the iteration, the team will implement the features they signed up for, pair prog- ramming on all production code. All code is written test-first—that is, the developers don’t write any code until they have a failing test case. The developers write unit tests to test individual classes and subsystems. The customer provides functional or acceptance tests to validate the features that the programmers are developing.
在迭代周期的其他时间内,团队要实现他们所登记承担的任务,所有代码由编程对子一起完成。所有代码都是以测试第一(test-first)的原则来写的,也就是说开发者在程序没有出现测试失败之前不必修改代码。如果没有完成测试程序,开发人员就不能写功能代码。客户提供功能测试或验收测试来核实开发者所开发出来的特性。
At the end of the iteration (usually on a Friday), the programmers deliver a working system to the customer. The system may not be complete, but all functionality that is implemented works com- pletely, without bugs. The customer accepts delivery, and the team goes home early. The next Monday everyone meets again to plan the next iteration, and the cycle repeats itself.
liuxuepaper.com