Agile Management Workshop
敏捷管理实践（2天版）
Course Overview课程大纲
|
|
Module模块
|
Content内容
|
9:00~
10:30
|
Concepts
基础概念
|
l Agile is one of the best tools to solve business puzzle?
敏捷管理是解决商业难题的最佳工具之一？ l Introduction to Scrum, and Scrum vs Waterfall
敏捷介绍，敏捷方法与传统瀑布型的区别 l The Agile Manifesto and principles敏捷宣言与敏捷法则
- Group talk: brief discussionon a real project
小组讨论：完成一个实际项目的初步讨论
|
10:40~
12:00
|
Framework-1
敏捷框架1
|
l Product Owner responsibilities 产品负责人及其职责
l Scrum Master responsibilities 敏捷教练及其职责
lThe Team responsibilities, acquirement, anddevelopment
敏捷团队及其职责、组成和建设 - Group talk: the requirementsand expectation to PO and SM?
小组讨论：对PO的要求和期望，对SM的要求和期望 - Group talk: the ground rulesfor a cross-functional team
小组讨论：跨部门团队合作的基本规则 - Group talk(optional): whathappens to traditional roles in Scrum?
小组讨论（可选）：敏捷环境下传统角色的变化
|
13:00~
14:30
|
Framework-2
敏捷框架2
|
l Artifacts: Product backlog, Sprint backlog, Releases
三个交付件：产品Backlog，Sprints，Releases及燃尽图 l Meetings：Planning, Daily stand-ups, Review, Retrospective
四种会议：规划会、每日站会、评审会、回顾会 - Exercise: Daily stand-upmeeting
练习：每日站会 - Exercise: presentation onthe Scrum framework
练习：对敏捷框架的表述 - Group talk: the questions onthe Scrum details
小组讨论：目前为止最想知道的关于敏捷的三个细节
|
14:45~
17:00
|
Project Initiation
项目的启动
|
l Product ownership and vision产品的责任、愿景
· Understand your customers，market，and personas
理解客户和市场、角色模型 l Stakeholder management and engagement
相关方/干系人的识别和参与管理 l Requirement collection, interview skills
获取需求的多种方法，访谈的技巧 -Exercise: project stakeholders and classification
练习：一个项目的干系人识别和分类 - Exercise: requirementcollection
练习：收集需求
|
第二天
|
9:00~
10:30
|
Sprint规划之用户故事
|
l What is user story? 用户故事的定义和理解
l Epics vs. user stories, splitting 史诗与用户故事，用户故事的切割
l Acceptance Criteria, Definition of Ready (DoR) and (DoD)
接受标准，用户故事就绪和完成的定义（DoR和DoD） l User Story Estimation Using Planning Poker
用户故事的完成时间估算：故事点、计划扑克及Fist-to-Five - Exercise: write epics, userstories, and acceptance criteria.
练习：编撰Epics，用户故事，以及验收标准 - Exercise：planningpoker
练习：计划扑克估算 - Group talk: the role of PO、SM、and Team in u/s and estimating
小组讨论：PO、SM、及Team在用户故事及完时估计过程中的职责工作 - Group talk: other estimatingtechniques
小组讨论：用户故事完时的其它估算方法？类比、参数、三点
|
10:40~
12:00
|
Sprint规划之
Backlog
|
l Steps to creating a product backlog创建产品功能清单的步骤
l Backlog Grooming, Roadmaps, Story Maps, Impact Mapping
产品清单的可视化与修饰，里程碑图、故事图、影响图 lProduct backlog prioritization, MoSCoW, Kanoanalysis
产品清单优先级排序，MoSCoW分析和Kano分析 lImpact of technical debt 技术债及影响
- Exercise：prioritizeuser stories
练习：对用户故事进行优先级排序 - Group talk: the role of PO、SM、and Team in prioritization
小组讨论：PO、SM、及Team在产品清单时的职责工作
|
13:00~
14:30
|
The Sprint
冲刺管理
|
l Implement and processes 实施原则与流程
l The daily scrum 每日敏捷工作
l The task board and the burndown chart任务板和燃尽图
l Team leadership and effective communication
团队领导力及有效沟通 - Group talk: problem analysisand solving
小组讨论：问题分析与解决? - Group talk: Scrum Master’srole in the Sprint
小组讨论：敏捷教练在一个Sprint里做什么？ - Group talk: senior technicalexperts are necessary for Team?
小组讨论：资深技术专家对敏捷团队来说是否必须？
|
14:40~
16:00
|
Sprint Closing
冲刺收尾
|
l Sprint review meeting 评审会议里对实现和未实现的成果进行处理
l Retrospectives 回顾会议里对经验教训的总结，常用工具
- Group talk:the role of PO、SM、and Team in the Review meeting
小组讨论：PO、SM、及Team在Sprint评审时的职责工作 - Group talk:the issues in the Review meeting
小组讨论：评审会的遗留问题怎么解决？ - Group talk:the role of PO、SM、and Team in Retrospective
小组讨论：PO、SM、及Team在Sprint回顾时的职责工作 - Group talk:choose the top-3 improvement items for nextSprint.
小组讨论：如何从下一个Sprint需要改进的十项措施里选择急需的三项？
|
Project Closing
项目收尾
|
l Sprint life cycle 冲刺周期及变化
l Project closing sheets and process 项目收尾的清单和流程
lScrum enhance in the organizationenvironment
敏捷在组织环境内的提升和促进 - Group talk:issues happen in the closing
小组讨论：项目收尾常遇到的问题及解决
|
16:00~
17:00
|
Wrap-up
课程总结
|
l Case study review and closing 敏捷案例的回顾和总结
lTraining closing 培训总结
|
||
