因为想在团队里能高效实现版本迭代,故学习敏捷开发。以下是学习摘抄。
我们遵循以下原则:
- 我们最优先做的是通过尽早地、持续地交付有价值的软件来满足客户需要。
- 我们欢迎需求的变化,即使到了开发后期。敏捷过程能够驾驭变化,为客户创造优势。
- 经常交付可以工作的软件,从几个星期到几个月,时间间隔越短越好。
- 在整个项目开发期间,业务人员和开发人员必须朝夕工作在一起。
- 围绕斗志高昂的人构建项目。给他们提供所需的环境和支持,并且信任他们能够完成任务。
- 在团队内部,最有效率也最有效果的信息传达方式,就是面对面的交谈。
- 可以工作的软件是进度主要的度量标准。
- 敏捷过程提倡可持续开发。出资人、开发者和用户应该总是保持稳定的开发速度。
- 对卓越技术和良好设计的不断追求有助于提高敏捷性。
- 简单——尽量减少工作量的艺术是至关重要的。
- 最好的架构、需求和设计都源自自我组织的团队。
- 每隔一定时间,团队都要总结如何更有效率,然后相应地调整自己的行为。
ps:图书馆借的书,是图灵的书,书名没记,,忘了 orz
附录:英文原版(来源网络)
Principles behind the Agile Manifesto
We follow these principles:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity–the art of maximizing the amount of work not done–is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.