A magic place for coding




  1. 在敏捷宣言遵循的12条原则中挑选1条你感兴趣的原则进行风险评估。(“原则”参见Lec.5, slide 8-10;“风险”参见Lec.3, slide 17)


12 priciples

  1. Our highest priority is to satisfy the customer through early and
    continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile
    processes harness change for the customer’s competitive
  3. Deliver working software frequently, from a couple of weeks to a
    couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily
    throughout the project.
  5. Build projects around motivated individuals. Give them the
    environment and support they need, and trust them to get the job
  6. The most efficient and effective method of conveying information
    to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors,
    developers, and users should be able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
    enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is
  11. The best architectures, requirements, and designs emerge from
    self-organizing teams.
  12. At regular intervals, the team reflects on how to become more
    effective, then tunes and adjusts its behavior accordingly.


  1. 需求变更风险
  2. 进度风险、预算风险、管理能力风险、信息安全风险
  3. 应用技术风险、质量控制风险、软件设计与开发工具风险、员工技能风险
  4. 人力资源风险、政策风险、市场风险、营销风险


Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.


  1. 需求变更风险:敏捷开发要求客户与开发者全程参与,因此开发者能够及时地响应客户的需求变更。
  2. 进度风险:不断地适应客户的需求有可能导致进度变慢。但后面的其他原则保证了开发进度的正常进行。
  3. 预算风险:及早地交付有利于减少开发的预算,但不断地需求调整有可能导致预算的增加。
  4. 管理能力风险:由于客户与开发者直接参与讨论,因此整个开发过程中的管理文档可能需要多次修改,该风险大大增加。
  5. 信息安全风险:由于开发者的目标是让客户满意,对于信息安全部分有可能忽略,因此这个风险也是值得注意的。
  6. 应用技术风险:开发者需要满足客户的不断变更的需求,因此有可能开发者本身的技术不成熟,导致最后开发的产品无法满足客户需求。
  7. 质量控制风险:由于开发者只需要做出让客户满意的产品,因此在质量控制这一方面可能比较少关注。
  8. 软件设计与开发工具风险:由于软件的设计与开发的全过程都是客户与开发者共同参与讨论的,因此这一部分是有所欠缺的。
  9. 员工技能风险:这个取决于技术人员的技术水平,在其他原则中有提到。
  10. 人力资源风险:这个取决于团队的构成,在其他原则中有提及。
  11. 政策风险:政策变更有可能导致客户的需求变更,进而导致开发者的工作变更。
  12. 市场风险:开发者能够尽早地交付用户满意的产品,可以认为是适合市场需求的。
  13. 营销风险:因为产品能够让客户满意,所以营销方面不存在过多问题。


  1. Niwot Ridge Resources
  2. Agile Development: Advantages vs. Disadvantages


Welcome to my other publishing channels