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.
敏捷宣言遵循的原则
我们遵循以下原则:
我们最重要的目标,是通过持续不断地
及早交付有价值的软件使客户满意。
欣然面对需求变化,即使在开发后期也一样。
为了客户的竞争优势,敏捷过程掌控变化。
经常地交付可工作的软件,
相隔几星期或一两个月,倾向于采取较短的周期。
业务人员和开发人员必须相互合作,
项目中的每一天都不例外。
激发个体的斗志,以他们为核心搭建项目。
提供所需的环境和支援,辅以信任,从而达成目标。
不论团队内外,传递信息效果最好效率也最高的方式是
面对面的交谈。
可工作的软件是进度的首要度量标准。
敏捷过程倡导可持续开发。
责任人、开发人员和用户要能够共同维持其步调稳定延续。
坚持不懈地追求技术卓越和良好设计,敏捷能力由此增强。
以简洁为本,它是极力减少不必要工作量的艺术。
最好的架构、需求和设计出自自组织团队。
团队定期地反思如何能提高成效,
并依此调整自身的举止表现。
相关推荐
Twelve Principles of Agile Software 敏捷软件的十二条原则
The Principles and Strategies of The Principles and Strategies of Design Patterns Design Patterns Alan Shalloway, Net Objectives, alshall@netobjectives.com <br/>James R.Trott, ...
看起来混乱无比的代码,却打印出英文歌曲the twelve days of christmas的歌词
Twelve
In the early days of computer science, the interactions of hardware, software, compilers, and operating system were simple enough to allow students to see an overall picture of how computers worked....
Twelve-month cash flow.xls
of techniques and explain their application in a reasonably complex environment, such as a multi-team development project including twenty to sixty participants. Consequently, this book also reflects ...
Eric Brewer:CAP Twelve Years Later——How the 'Rules' Have Changed@2012
Refactoring to Patterns reflects three years of refinement and the insights of more than sixty software engineering thought leaders in the global patterns, refactoring, and agile development ...
Twelve Ton Goldfish
The CAP theorem asserts that any ... How- ever, by explicitly handling partitions, designers can optimize consistency and availability, thereby achieving some trade- off of all three.
CAP Twelve Years Later: How the“Rules” Have Changed英文原版pdf
外研一起小学英语五下《Module2Unit 2 Lunch is usually at half past twelve.》word教案 (2).docx
At the Symposium on Principles of Distributed Computing in the year 2000, Eric Brewer held a keynote talk about his experience with the recent changes in the development of distributed databases....
Twelve(1).java
Twelve Month Sales Forecast.xls
twelve.ino
SCI写作方法-Twelve Steps to Developing an Effective First Draft of your Manuscript
Twelve-Lead Electrocardiography.pdf 书籍
Twelve Ton Fishstick