{"id":22514677,"url":"https://github.com/worktile/wt-wiki-agile","last_synced_at":"2026-01-28T12:02:36.181Z","repository":{"id":85245503,"uuid":"209238345","full_name":"worktile/wt-wiki-agile","owner":"worktile","description":null,"archived":false,"fork":false,"pushed_at":"2019-11-19T03:47:26.000Z","size":147,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":6,"default_branch":"develop","last_synced_at":"2025-06-03T06:57:39.421Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Dockerfile","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/worktile.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-09-18T06:49:41.000Z","updated_at":"2019-11-19T03:36:38.000Z","dependencies_parsed_at":"2023-07-26T05:39:24.085Z","dependency_job_id":null,"html_url":"https://github.com/worktile/wt-wiki-agile","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/worktile/wt-wiki-agile","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/worktile%2Fwt-wiki-agile","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/worktile%2Fwt-wiki-agile/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/worktile%2Fwt-wiki-agile/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/worktile%2Fwt-wiki-agile/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/worktile","download_url":"https://codeload.github.com/worktile/wt-wiki-agile/tar.gz/refs/heads/develop","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/worktile%2Fwt-wiki-agile/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28845103,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-28T10:53:21.605Z","status":"ssl_error","status_checked_at":"2026-01-28T10:53:20.789Z","response_time":57,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-12-07T03:20:15.990Z","updated_at":"2026-01-28T12:02:36.142Z","avatar_url":"https://github.com/worktile.png","language":"Dockerfile","funding_links":[],"categories":[],"sub_categories":[],"readme":"“**敏捷（Agile）**，即创造和响应变化的能力。”\n\n国际敏捷联盟（The Agile Alliance）是如此定义“敏捷”的。的确，在这个所谓的“VUCA”时代，几乎任何组织不再仅仅谋求当前的生存力和竞争力，它们意识到唯有变化才是永恒的主题，因此更希望自己能够不断适应难以预测的变化。在面对不确定性时，我们通常会尝试很多可能有效的方法，通过收集反馈、分析和学习，做出相应的调整，如此反复。如何能在更短的周期内完成更高的投入产出比，则是敏捷所要讨论的。\n\n从上世纪90年代开始，人们试图以敏捷的方式开展工作。在软件开发领域，传统的构建软件的方式逐渐被摒弃，取而代之的是在实践中先后诞生了一些颇受关注的轻量级的软件开发方法。2001年，17位软件开发人员聚集在犹他州的Snowbird，讨论他们对于工作的想法与各种软件开发方法，寻找其中的共性，最终一同发布了著名的**“敏捷宣言”**以及12项原则，正式宣告了敏捷开发运动的开始。\n\n如今我们所说的**敏捷软件开发**是基于敏捷宣言定义的价值观和原则的一系列框架、方法和实践的总称。这些方法的共性标志是强调开发团队与产品所有者之间的密切配合，不断评估开发需求、计划和结果，频繁交付小的、可用的价值“增量”，以及组建跨职能协作的自组织团队。团队成员之间的信任和开放式的沟通、协作、适应是敏捷的核心， 而在团队中形成产品质量、可用性和完整性等方面的统一标准，持续优化工作规则和流程则是自组织的体现。敏捷倡导者和实践者坚信，自组织是敏捷开发团队发挥最佳的灵活性、创造力和生产力以应对变化的能力源泉。\n\n这个知识库将从整体上介绍敏捷软件开发，也会具体分享一些流行的敏捷框架，包括：\n\n* **Scrum**，由 Scrum 团队以及与之相关的角色、仪式、工件和规则组成，框架中的每个元素都有其特定目的，其规则把角色、仪式和工件组织在一起，管理它们之间的关系和交互，推动产品、团队和工作环境的持续改进。\n* **Kanban**，来源于丰田生产线的视觉信号机制，借助可视化的工作流、在制品限制以及一些图表工具，开发团队设计、管理和渐进式改进他们的工作系统，实现产品版本的高频次发布。\n* **极限编程**（Extreme Programming，简称XP），包含13项实践方法，是软件开发中相对来说最为具体的敏捷框架，旨在生产更高质量的软件和为开发团队创造更好的生活质量。\n\n除此以外，知识库也包括一些适用于更大规模团队组织工作的敏捷框架，如 Scrum@Scale、SAFe 等。这些框架有助于一些打算转型的团队启动敏捷之旅，但它们并非教条或标准——敏捷的意义始终在于，通过实践持续追求更好的、更适合团队和变化的方法。\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fworktile%2Fwt-wiki-agile","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fworktile%2Fwt-wiki-agile","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fworktile%2Fwt-wiki-agile/lists"}