学习敏捷基础

[Fanlu91]

• [x] 什么是敏捷

• [x] 用敏捷学习的好处

• [x] 职责分工

• [x] 专有名词 user story/ epic/

• [x] 最佳实践

[Fanlu91]

Agile 的本质是value 和principle的集合（敏捷宣言）。而不是方法论，具体到方法上是非常灵活的。 使用agile的value和principle可以更好的做决定-进而完成任务 决策过程是重要的。 快速响应 快速行动

主要开发方法 scrum 、XP极限 、Lean 精益、Kanban 看板

[Fanlu91]

Scrum

Plan - Build - Test - Review 1 Sprint

3 Roles

• Product Owner responsible for defining the features that are needed
• Scrum Master procting the team and the process
• Team members get works done
• Stakeholder 干系人

3 Artifacts

• Product Backlog, PO create a prioritized list of features (user stories) that could go into the product. This list evolves and changes priority with every Sprint(Sprint Backlog).
• User story, as a ...user用户 I need ...something功能 so that ...reason价值 format
• Burndown Charts

3 Ceremonies

• Sprint Planning
• Daily Scrum yesterday? today? problem?
• Sprint Review / Retrospective

[Fanlu91]

Kanban

Colunm To do , in progress, done cycle time down, throughput up, waste time down

看板原则 可视化

• 可视化队列和工作项（用户价值）
• 可视化端到端的流动
• 可视化问题和阻碍
• 可视化人力资源分配
• 可视化流转规则

限制在制品

• 推迟开始、聚焦完成更多的关注流动，避免同时并行多任务
• 效率而不是资源效率 可视化问题和阻碍，把聚焦点从任务分解、分配和计划制定、执行、跟踪和控制转向价值探索、发现以及如何让价值实现端到端顺畅流动。
• 管理流动

[Fanlu91]

Epic

An agile epic is a body of work that can be broken down into specific tasks (called “stories,” or “user stories”) based on the needs/requests of customers or end users.

Epic is a good way to track complex features progress. Remember that epic is just a placeholder. That can hold multiple user stories which are focused on the specific scope. Think of epic as a book and user stories are its’ chapters.

Since epic is a just a placeholder, User stories from an epic can be spanned across multiple projects. Normally it takes few sprints to finish one Epic. Product Owner can easily determine the completion percentage of an epic by calculating the percentage of associated done user stories.

Epics are almost always delivered over a set of sprints. As a team learns more about an epic through development and customer feedback, user stories will be added and removed as necessary. That’s the key with agile epics: Scope is flexible, based on customer feedback and team cadence.