显然在中小型MIS开发过程管理中照搬CMM或敏捷软件过程都是行不通的。
Obviously, neither CMM nor Agile Software process can't be used to the development process of the medium or small MIS with the dogmatism.
敏捷软件开发的首要价值是“过程和工具之上的个人和交互”1，我们在该框架中已经采用的价值。
The first value of Agile software development is "individuals and interactions over processes and tools" 1, a value that we've adopted in this framework.
敏捷开发团队试图用恰好够用的过程，在合适的时机，按照预期交付高质量的软件。
Agile development teams attempt to use just enough process in just enough places to enable the predictable delivery of quality software.
RUP和其他敏捷软件工程过程能够很好地迎接这些挑战。
The RUP and other agile software engineering processes are capable of addressing these challenges.
本文讲述了一个我们如何在一家公司的特定项目中指导敏捷软件开发过程的故事。
This paper tells the story of how we coached the adaption process of agile software development in a company, with a focus on one specific project.
尽管经常与敏捷过程连接在一起，例如极限编程，但是概念和实践都不是什么新的——只是众所周知的软件开发最佳实践上的一种变体。
Although often linked with Agile processes, such as eXtreme programming, the concept and practices are nothing new — just a variation on well-known software development best practices.
这篇文章的目的是通过采取持续集成方式，让开发过程更敏捷并提高软件的质量。
This article aims to make your development process more agile and improve the quality of your software by adopting a continuous-integration approach.
这种变化，特别是在逐步实施敏捷过程中，在软件开发过程中产生了新的改进需要，这种需要最终会成为将来某次回顾会议的主题。
This change, especially in gradual agile implementations, creates a new need-for-improvement in the development process that eventually becomes the topic of one of the future retrospectives.
这种方式已经取得了关于软件过程成熟度的比较正式的成果，如能力成熟度模型(CMM)，和敏捷方法，如极限编程和Scrum。
This approach has led to more formal efforts to achieve software process maturity, such as the Capability maturity Model (CMM), and agile methods such as Extreme Programming and Scrum.
OpenUP产品家族中的过程是作为扩展被写入核心的OpenUP过程的，它信奉实用和敏捷的哲学，关注软件开发所具有的协作的本性。
Processes in the OpenUP family are written as extensions to the core OpenUP process, which embraces a pragmatic, agile philosophy focusing on the collaborative nature of software development.
避免软件小组在到敏捷开发转变的过程中出现常见的错误。
Avoiding the common mistakes software teams make in transitioning to agile.
在进行非软件项目时(固件类、电子类、机械类等)，敏捷实践的思想和过程是否仍旧有效？
Are Agile practices and processes effective when conducting non-software projects (firmware, electronic, mechanical, etc.)?
这则讯息说明了在采用敏捷软件开发的过程中，应该强调什么样的人性面及方法、实践及工具。
This message implies what human aspects and methods, practices and tools should be emphasized in adoption processes of agile software development.
第二篇文章“在大型机构中将敏捷性引入RUP 的策略”是由JoshuaBarnes 撰写的，它从一个相反的方向对待软件处理过程中的挑战。
The second article, Strategies for Bringing Agility to RUP by Joshua Barnes, approaches the software process challenge from the opposite direction.
根据课程表自动编排系统运行过程中的需求变化，应用敏捷软件开发思想重构系统，对系统再分析。
Based on the change of the system of Auto-programme of Curriculum Timetable, discussed and presents some thoughts about the re-developing on the agile development.
通过对敏捷软件开发方法在软件维护性开发中的应用，给出敏捷软件开发方法在软件维护性开发中的可参考性流程和实现过程。
This paper gives some information and method of agility in the maintaining development by the application of agile method in the maintainenance development.
也许在这过去几年最引人注目对软件过程的思考的改变-“敏捷agile”一词的出现。
Probably the most noticeable change to software process thinking in the last few years has been the appearance of the word 'agile'.
也许在这过去几年最引人注目对软件过程的思考的改变-“敏捷agile”一词的出现。
Probably the most noticeable change to software process thinking in the last few years has been the appearance of the word 'agile'.
应用推荐