赞
踩
It’s light-weight, simple to understand but difficult to master.
敏捷是轻量化的,容易理解但很难掌握。
Light-weight & People-based (rather than Plan-based)
敏捷一般是小量迭代的,适应快速的市场变化的
Product Owner
The Development Team/ Core Member
The Scrum Master
Keeps the team focused on using Scrum properly (“servant-leader”)
主要分为以下五个部分 按顺序进行 缺一不可
该阶段的成果就是Sprint Backlog,通过开会从Product Backlog中选择出这次Sprint需要完成的任务。
每天进行的回忆,一般都是Stand-up Meeting - 站着开会 时间短快速进行。简单来说就是每人问自己三个问题:
昨天我做了什么?今天的我要做什么?我是否看到/遇到了什么困难阻碍?
这部分主要是core member的开发,跟随sprint backlog中自己被assign的任务去做。如果遇到了困难需要通知Product Owner。最重要的一步就是做完以后将Sprint Backlog中的In Progress的任务拖拽到Done栏。
这是一个主要围绕demo演示的阶段。
在此阶段中,Core Member 向我们的客户演示功能。只需要展示经过测试的完整功能(Product Owner已认可),例如框架选择,数据库设计,持续集成(Jenkins)这种不需要展示。
客户会提出他们的观点和反馈,团队成员一定要将这些记录下来,后续需要讨论加入Product Backlog里。
这个阶段的成功就是 Product Owner需要修改Product Backlog 为下次iteration做准备。
Opportunity for the Scrum team to inspect itself and create plan for improvements
Purpose
Inspect how the last Sprint went with regards to people, relationships, process, and tools;
Identify and order the major items that went well and potential improvements;
Create a plan for implementing improvements to the way the Scrum Team does its work
这个阶段比较好理解,就是回顾这次Sprint,我们哪些做得好哪些做得不好。
Retrospective meetings (max. 1-2 hours)
The Scrum Master and the Dev. team (maybe product owner)
Each person answer two questions:
The Scrum Master notes improvements that should be added to the Product Backlog (non-functional items)
Output: identified improvements to be implemented in the next Sprint (adaptation)
Scrum Master需要记下改动帮助,这个阶段的成果就是Scrum Master帮助Product Owner确认好需要的改动,更好地进行紧接着的Sprint Planning。
刚入门容易对这两个东西有混淆,其实不难理解。
Set of all features and sub-features (items) needed to build the product. Maintained by the Product Owner, and it evolves over the time and never complete.
The items ordered by priority - value to customer.
包含所有的需要完成这个项目的功能,用优先级排序,优先级由这个东西对用户的价值决定。
Simple spreadsheet - 可以是Excel表格
Set of Product Backlog items selected for the Sprint, and a plan for delivering the product increment and realize the Sprint Goal
看完Product Backlog,这个就很简单了。不过是从Product Backlog中挑选出来,只为当前Sprint使用的东西,或者说这次Sprint需要完成的任务。
Typically divided into 3 sections; To Do, In Progress, Done.
分为这三个栏,简单易懂,详情可以参考GitHub的Project Board。
Progress Monitoring
“Burndown” chart tracks the amount of estimated effort remaining in the a sprint
Velocity tracks the amount of work from Sprint to Sprint
Copyright © 2003-2013 www.wpsshop.cn 版权所有,并保留所有权利。