<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>敏捷 on Jeanphilo Blog</title><link>https://shio-chan-dev.github.io/jeanblog/zh/tags/%E6%95%8F%E6%8D%B7/</link><description>Recent content in 敏捷 on Jeanphilo Blog</description><generator>Hugo -- 0.159.2</generator><language>zh-cn</language><lastBuildDate>Sat, 24 Jan 2026 13:35:15 +0800</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/%E6%95%8F%E6%8D%B7/index.xml" rel="self" type="application/rss+xml"/><item><title>敏捷宣言的两句核心话：个体与协作的优先级</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-manifesto-values/</link><pubDate>Sat, 24 Jan 2026 13:35:15 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-manifesto-values/</guid><description>讨论“个体与交互重于过程和工具”“客户协作重于合同谈判”的含义与落地方式。</description></item><item><title>向 CEO 解释看板：为什么值得投资</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/kanban-explained-to-ceo/</link><pubDate>Sat, 24 Jan 2026 12:50:25 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/kanban-explained-to-ceo/</guid><description>用商业视角解释看板的价值与投入产出，适合向管理层沟通。</description></item><item><title>敏捷 vs 瀑布：最大差异与适用场景</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-vs-waterfall/</link><pubDate>Sat, 24 Jan 2026 12:47:45 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-vs-waterfall/</guid><description>对比敏捷与瀑布的核心差异，并给出选型建议。</description></item><item><title>什么是敏捷（Agile）：原则、实践与误区</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-basics/</link><pubDate>Sat, 24 Jan 2026 12:47:45 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/management/agile-basics/</guid><description>解释敏捷的核心原则、常见实践与落地误区。</description></item></channel></rss>