敏捷软件开发管理-IBM孙昕摘要.ppt

* Scrum teams need to have a “we’re all in this together attitude.” This can sometimes be undermined if a team has specialized job descriptions or roles. For example, if a team includes a dedicated “tester” then this may give the rest of the team an opportunity to shirk the responsibility to test. With the highly complex technologies of the world today it is too simplistic to think that everyone can be a DBA and everyone can write server-side J2EE or .Net code. A successful Scrum team does not need to be comprised entirely of generalists. However, for a team of specialists to be successful each specialist must accept general responsibility for the system as a whole. I may not know how to solve our project’s most intricate Oracle problems but I’m going to do whatever I can to help, which may simply include taking on some of our database specialist’s other responsibilities to free her to solve the complex problems. * Consequences Quality levels will be reduced. Morale will be reduced - with team members saying that nothing has changed since the waterfall days. * Consequences The team is less efficient than it could be and there will waste as people are blocked. In addition the team will improve more slowly without mentoring. * Consequences The team will not believe in the decisions made. A real team (see Katzenbach and Smith: The Wisdom of Teams: Creating the High-Performance Organization) will never form. Suboptimal decisions will be made since they will come from a single source. * Jazz 将敏捷开发与 IDE 结合起来，以进行流畅的规划、工作和管理 Practices and tools support each other – each practice requires multiple tools = integration. A better tool has widespread impact Incremental design: SCM – private versions, SCM can track refactorings, feedback from continous build Continuous integration: team build, personal build, build health status in dashboard, work items track build status Test driven development: build, frequent test failures report Iteration sprints: iteration planning u