实战Scrum：敏捷软件项目管理和开发指南

Scrum
Agile
5星 · 超过95%的资源 | 下载需积分: 10 | PDF格式 | 3.05MB | 更新于2024-07-29 | 183 浏览量 | 31 下载量 举报
5 收藏
"Scrum® in Action: Agile Software Project Management and Development" 是一本由Andrew Pham和Phuong-Van Pham合著的书籍，由Course Technology PTR出版，于2013年2月发布，旨在为软件项目团队提供采用敏捷软件框架Scrum的成功实践指导。这本书是针对企业实践者的首部实战指南，包含了丰富的项目管理技巧，帮助团队充分利用资源，并通过财务术语与高管沟通，使用客观估算技术，以及阐述软件架构在Scrum中的角色。 Scrum是一种流行的敏捷开发框架，强调迭代和增量式开发，以应对需求变化和提高软件产品的适应性。在"Scrum in Action"中，作者深入浅出地讲解了如何实施Scrum方法，包括： 1. **敏捷原则**：书中涵盖了敏捷开发的核心原则，如快速响应变化、强调个体和交互、可工作的软件作为进度的主要衡量标准等，这些都是Scrum的基础。 2. **Scrum角色**：Scrum团队由产品负责人（Product Owner）、Scrum Master和开发团队组成。书中详细介绍了这些角色的职责和相互协作的方式。 3. **Scrum过程**：Scrum流程包括冲刺（Sprint）、每日Scrum会议、回顾会议和计划会议。书中会解释每个活动的目的和最佳实践。 4. **产品待办事项列表（Product Backlog）**：这是Scrum中的核心文档，用于记录所有待完成的工作。书中会介绍如何有效地管理和优先级排序。 5. **冲刺待办事项列表（Sprint Backlog）**：在每个冲刺开始时，团队从产品待办事项列表中选择一部分任务，形成冲刺待办事项列表。书中会讨论如何制定这些任务并确保它们在冲刺结束时完成。 6. **冲刺回顾**：这是一个重要的学习和改进机会，团队会审视过去的工作，识别问题并提出改进措施。 7. **估算与规划**：书中介绍了一种客观的估算技术，帮助团队更准确地预测工作量，以便更有效地规划冲刺。 8. **沟通与协作**：Scrum强调开放和透明的沟通。书中将探讨如何使用Scrum工具和技术来增强团队间的协作。 9. **适应性决策**：Scrum鼓励在开发过程中做出灵活的决策，以适应变化。书中会讲述如何在不确定的环境中做出明智的选择。 10. **与管理层的互动**：作者提供了使用财务术语与高层沟通的策略，帮助团队展示敏捷项目的投资回报和价值。 11. **软件架构**：Scrum中的架构是如何与迭代开发相结合的，以及在保持系统可维护性和扩展性的同时，如何在不断变化的需求中构建软件架构。 "Scrum in Action"不仅是一本理论性的指南，还包含了大量实践经验，对于想要采用或优化Scrum实践的项目经理、开发人员、产品负责人和其他团队成员来说，都是一本宝贵的参考资料。

相关推荐

filetype

Agile Project Management with Scrum

Foreword: Why Scrum Works<br>Suppose I’m traveling from Chicago to Boston by airplane. Before and during the flight, the pilot gets instructions from air traffic control. We take off on command and follow the prescribed route. Once we are in the air, computers predict almost to the minute when we will land in Boston. If things change—say the air is bumpy—the pilot must get permission to move to a different altitude. As we approach the airport, the pilot is told what runway to land on and what gate to go to.<br><br>If, however, I set out for Boston in a car, I can take whatever route I want, whenever I want. I don’t know exactly when I’ll get there, and I probably haven’t planned what route I’ll take or where I’ll stop for the night. En route, I follow traffic laws and conventions: I stop at red lights, merge into traffic according to the prevailing customs, and keep my speed consistent with the flow. In an automobile, I am an independent agent, making decisions in my own best interests framed by the rules of the game of driving.<br><br>It’s amazing to me that thousands upon thousands of people travel by car every day, accomplishing their goals in a framework of simple traffic rules, with no central control or dispatching service. It also amazes me that when I want to ship a package, I can enter a pickup request on the shipper’s Web site and a driver will arrive at my door before the time that I specify. The driver isn’t dispatched to each house; he or she receives a continually updated list of addresses and deadlines. It’s the driver’s job to plot a route to get all the packages picked up on time.<br><br>As complexity increases, central control and dispatching systems break down. Some might try valiantly to make the control system work by applying more rigor, and indeed that works for a while. But the people who prevail are those who figure out how to change to a system of independent agents operating under an appropriate set of rules. It might work to provide same-day delivery with a dispatch system that plans a driver’s route at the beginning of the day. However, it is far more difficult to preplan a pickup route when customers can enter pickup requests at any time. Taxi companies sort things out at a central control center. Some shipping companies send the request to the driver responsible for the area and let the driver determine the best route based on current conditions and other demands.<br><br>The more complex the system, the more likely it is that central control systems will break down. This is the reason companies decentralize and governments deregulate—relinquishing control to independent agents is a time- honored approach to dealing with complexity. Scrum travels this well-trodden path by moving control from a central scheduling and dispatching authority to the individual teams doing the work. The more complex the project, the more necessary it becomes to delegate decision making to independent agents who are close to the work.<br><br>Another reason that Scrum works is that it dramatically shortens the feedback loop between customer and developer, between wish list and implementation, and between investment and return on investment. Again, complexity plays a role here. When a system is simple, it’s not so hard to know in advance what to do. But when we are dealing with a market economy that changes all the time and with technology that won’t stand still, learning through short cycles of discovery is the tried-and-true problem-solving approach.<br><br>We already know this. We try out various marketing campaigns and discover which approach works. We simulate vehicle behavior during car design to discover the best slope of the hood and best distribution of weight. Virtually all process-improvement programs use some version of the Deming cycle to study a problem, experiment with a solution, measure the results, and adopt proven improvements. We call this fact-based decision making, and we know that it works a lot better than front-end-loaded predictive approaches.<br><br>Scrum is built on 30-day learning cycles that prove complete business concepts. If we already know everything and have nothing to discover, perhaps we don’t need to use Scrum. If we need to learn, however, Scrum’s insistence on delivering complete increments of business value helps us learn rapidly and completely. One of the reasons complete increments are important is that partial answers often fool us into thinking that an approach will work, when in reality, the approach doesn’t work upon closer examination. We know that until software is tested, integrated, and released to production, we can’t really be sure that it will deliver the intended business value. Scrum forces us to test and integrate our experiments and encourages us to release them to production, so that we have a complete learning cycle every 30 days.<br><br>Scrum doesn’t focus on delivering just any increment of business value; it focuses on delivering the highest priority business value as defined by the customer (Product Owner). The Product Owner and the Team confer about what that definition is, and then the Team decides what it can do in 30 days to deliver high-priority business value. Thus the short feedback loop becomes a business feedback loop—Scrum tests early and often whether the system being developed will deliver value and exactly what that value will look like. This allows the system to be molded over time to deliver value as it is currently understood, even as it helps to develop a better understanding of that value.<br><br>Another reason Scrum works is that it unleashes the brainpower of many minds on a problem. We know that when things go wrong, there are people around who knew there was a problem, but somehow their ideas were overlooked. For example, when the space shuttle disintegrated on reentry, a widely reported interpretation of the causes of the disaster suggests that there were engineers who were well aware that there could be a problem, but they were unable to get their concerns taken seriously. What management system can we use to leverage the experience, ideas, and concerns of the people closest to the work to be done?<br><br>According to Gary Convis, president of Toyota Motor Manufacturing Kentucky, the role of managers in a healthy, thriving, work environment is “to shape the organization not through the power of will or dictate, but rather through example, through coaching and through understanding and helping others to achieve their goals.[1] <br><br>Scrum turns small teams into managers of their own fate. We know that when we are responsible for choosing our own driving route to Boston, we will find a way to get there. We will detour around construction and avoid rush hour traffic jams, making decisions on the fly, adapting to the independent decisions of all of the other drivers out there. Similarly, Scrum Teams accept a challenge and then figure out how to meet that challenge, detouring around roadblocks in creative ways that could not be planned by a central control and dispatching center.<br><br>If teams are of a size that encourages every member to participate, and team members feel like they are in control of their own destiny, the experience, ideas, and concerns of individual members will be leveraged, not squelched. When team members share a common purpose that everyone believes in, they will figure out how to achieve it. When teams understand and commit to delivering business value for their customers, when they are free to figure out how to perform tasks, and when they are given the resources they need, they will succeed.<br><br>Gary Convis notes that Toyota’s sustainable success comes from an “interlocking set of three underlying elements: the philosophical underpinnings, the managerial culture and the technical tools. The philosophical underpinnings include a joint [worker], customer-first focus, an emphasis on people first, a commitment to continuous improvement…. The managerial culture…is rooted in several factors, including developing and sustaining a sense of trust, a commitment to involving those affected by first, teamwork, equal and fair treatment for all, and finally, fact-based decision making and long-term thinking.[2] <br><br>Scrum works for all the same reasons. Its philosophical underpinnings focus on empowering the development team and satisfying customers. Its managerial culture is rooted in helping others achieve their goals. Its technical tools are focused on making fact-based decisions through a learning process. When all of these factors are in place, it’s hard for Scrum not to succeed.<br><br>—Mary Poppendieck<br>Poppendieck.LLC
141 浏览量
filetype

Agile.Project.Management.with.Scrum

Foreword: Why Scrum Works<br/>Suppose I’m traveling from Chicago to Boston by airplane. Before and during the flight, the pilot gets instructions from air traffic control. We take off on command and follow the prescribed route. Once we are in the air, computers predict almost to the minute when we will land in Boston. If things change—say the air is bumpy—the pilot must get permission to move to a different altitude. As we approach the airport, the pilot is told what runway to land on and what gate to go to.<br/><br/>If, however, I set out for Boston in a car, I can take whatever route I want, whenever I want. I don’t know exactly when I’ll get there, and I probably haven’t planned what route I’ll take or where I’ll stop for the night. En route, I follow traffic laws and conventions: I stop at red lights, merge into traffic according to the prevailing customs, and keep my speed consistent with the flow. In an automobile, I am an independent agent, making decisions in my own best interests framed by the rules of the game of driving.<br/><br/>It’s amazing to me that thousands upon thousands of people travel by car every day, accomplishing their goals in a framework of simple traffic rules, with no central control or dispatching service. It also amazes me that when I want to ship a package, I can enter a pickup request on the shipper’s Web site and a driver will arrive at my door before the time that I specify. The driver isn’t dispatched to each house; he or she receives a continually updated list of addresses and deadlines. It’s the driver’s job to plot a route to get all the packages picked up on time.<br/><br/>As complexity increases, central control and dispatching systems break down. Some might try valiantly to make the control system work by applying more rigor, and indeed that works for a while. But the people who prevail are those who figure out how to change to a system of independent agents operating under an appropriate set of rules. It might work to provide same-day delivery with a dispatch system that plans a driver’s route at the beginning of the day. However, it is far more difficult to preplan a pickup route when customers can enter pickup requests at any time. Taxi companies sort things out at a central control center. Some shipping companies send the request to the driver responsible for the area and let the driver determine the best route based on current conditions and other demands.<br/><br/>The more complex the system, the more likely it is that central control systems will break down. This is the reason companies decentralize and governments deregulate—relinquishing control to independent agents is a time- honored approach to dealing with complexity. Scrum travels this well-trodden path by moving control from a central scheduling and dispatching authority to the individual teams doing the work. The more complex the project, the more necessary it becomes to delegate decision making to independent agents who are close to the work.<br/><br/>Another reason that Scrum works is that it dramatically shortens the feedback loop between customer and developer, between wish list and implementation, and between investment and return on investment. Again, complexity plays a role here. When a system is simple, it’s not so hard to know in advance what to do. But when we are dealing with a market economy that changes all the time and with technology that won’t stand still, learning through short cycles of discovery is the tried-and-true problem-solving approach.<br/><br/>We already know this. We try out various marketing campaigns and discover which approach works. We simulate vehicle behavior during car design to discover the best slope of the hood and best distribution of weight. Virtually all process-improvement programs use some version of the Deming cycle to study a problem, experiment with a solution, measure the results, and adopt proven improvements. We call this fact-based decision making, and we know that it works a lot better than front-end-loaded predictive approaches.<br/><br/>Scrum is built on 30-day learning cycles that prove complete business concepts. If we already know everything and have nothing to discover, perhaps we don’t need to use Scrum. If we need to learn, however, Scrum’s insistence on delivering complete increments of business value helps us learn rapidly and completely. One of the reasons complete increments are important is that partial answers often fool us into thinking that an approach will work, when in reality, the approach doesn’t work upon closer examination. We know that until software is tested, integrated, and released to production, we can’t really be sure that it will deliver the intended business value. Scrum forces us to test and integrate our experiments and encourages us to release them to production, so that we have a complete learning cycle every 30 days.<br/><br/>Scrum doesn’t focus on delivering just any increment of business value; it focuses on delivering the highest priority business value as defined by the customer (Product Owner). The Product Owner and the Team confer about what that definition is, and then the Team decides what it can do in 30 days to deliver high-priority business value. Thus the short feedback loop becomes a business feedback loop—Scrum tests early and often whether the system being developed will deliver value and exactly what that value will look like. This allows the system to be molded over time to deliver value as it is currently understood, even as it helps to develop a better understanding of that value.<br/><br/>Another reason Scrum works is that it unleashes the brainpower of many minds on a problem. We know that when things go wrong, there are people around who knew there was a problem, but somehow their ideas were overlooked. For example, when the space shuttle disintegrated on reentry, a widely reported interpretation of the causes of the disaster suggests that there were engineers who were well aware that there could be a problem, but they were unable to get their concerns taken seriously. What management system can we use to leverage the experience, ideas, and concerns of the people closest to the work to be done?<br/><br/>According to Gary Convis, president of Toyota Motor Manufacturing Kentucky, the role of managers in a healthy, thriving, work environment is “to shape the organization not through the power of will or dictate, but rather through example, through coaching and through understanding and helping others to achieve their goals.[1] <br/><br/>Scrum turns small teams into managers of their own fate. We know that when we are responsible for choosing our own driving route to Boston, we will find a way to get there. We will detour around construction and avoid rush hour traffic jams, making decisions on the fly, adapting to the independent decisions of all of the other drivers out there. Similarly, Scrum Teams accept a challenge and then figure out how to meet that challenge, detouring around roadblocks in creative ways that could not be planned by a central control and dispatching center.<br/><br/>If teams are of a size that encourages every member to participate, and team members feel like they are in control of their own destiny, the experience, ideas, and concerns of individual members will be leveraged, not squelched. When team members share a common purpose that everyone believes in, they will figure out how to achieve it. When teams understand and commit to delivering business value for their customers, when they are free to figure out how to perform tasks, and when they are given the resources they need, they will succeed.<br/><br/>Gary Convis notes that Toyota’s sustainable success comes from an “interlocking set of three underlying elements: the philosophical underpinnings, the managerial culture and the technical tools. The philosophical underpinnings include a joint [worker], customer-first focus, an emphasis on people first, a commitment to continuous improvement…. The managerial culture…is rooted in several factors, including developing and sustaining a sense of trust, a commitment to involving those affected by first, teamwork, equal and fair treatment for all, and finally, fact-based decision making and long-term thinking.[2] <br/><br/>Scrum works for all the same reasons. Its philosophical underpinnings focus on empowering the development team and satisfying customers. Its managerial culture is rooted in helping others achieve their goals. Its technical tools are focused on making fact-based decisions through a learning process. When all of these factors are in place, it’s hard for Scrum not to succeed.<br/><br/>—Mary Poppendieck<br/>Poppendieck.LLC<br/><br/>
240 浏览量
filetype

agile-software-development

This book is written for the more experienced audience. The book does not contain procedures to follow to develop software; in fact, core to the book is the concept that every technique has limitations. Therefore, it is impossible to name one best and correct way to develop software. Ideally, the book helps you reach that understanding and then leads you to constructive ideas about how to deal with this realworld situation.
71 浏览量
filetype

Scrum in Action - Agile Software Project Management and Development

### Scrum in Action: 敏捷软件项目管理和开发 #### Scrum简介 Scrum是一种敏捷开发框架，主要用于软件开发项目，但也可应用于其他复杂产品或服务的开发过程。Scrum的核心理念是通过迭代（通常称为Sprints）的方式...
60 浏览量
filetype

《Scrum in Action: Agile Software Project Management全球教程》

《Course.Technology.PTR.Scrum.in.Action》是一本关于敏捷软件项目管理和开发的专业课程，由Andrew Pham 和 Phuong-Van Pham 携手创作，隶属于Cengage Learning旗下的Course Technology PTR系列。该课程专为IT行业...
93 浏览量
filetype

Best Practices In Scrum Project Management And Xp Agile Software Development.pdf

本文将基于《Best Practices in Scrum Project Management and XP Agile Software Development》的内容，详细介绍这两种方法的核心理念、实施步骤以及它们如何帮助Primavera Systems这家拥有21年历史的项目组合管理...
199 浏览量
filetype

THE SCRUM PRIMER: An Introduction to Agile Project Management with Scrum

### 敏捷项目管理Scrum入门指南 #### Scrum简介 Scrum是一种敏捷开发方法，旨在提高团队的工作效率和灵活性。它强调通过迭代的方式完成项目，每次迭代都会产生可用的产品增量。Scrum的核心理念是适应变化而非严格...
184 浏览量
filetype

Scrum Agile Software development

- **Scrum角色**：主要包括三种角色——产品负责人(Product Owner)、Scrum Master和开发团队(Development Team)。 - **产品负责人**：负责定义产品的愿景并确保团队专注于高价值的工作项。 - **Scrum Master**：...
122 浏览量
filetype

User Stories Applied: For Agile Software Development

User Stories Applied: For Agile Software Development &lt;br&gt;by Mike Cohn &lt;br&gt;Publisher: Addison-Wesley Professional (March 11, 2004) &lt;br&gt; Agile requirements: discovering what your users...
193 浏览量
filetype

Agile Project Management with Scrum.pdf

**Agile Project Management with Scrum** 这个标题明确地指出了本书的主题：如何将敏捷开发中的Scrum方法应用于项目管理。Scrum是一种流行的敏捷开发框架，它强调团队合作、迭代式进展以及适应性计划。 #### 描述...
501 浏览量
敖日格勒
  • 粉丝: 21
  • 资源: 21
上传资源 快速赚钱

最新资源