Waterfall Scrum

Introduction to Scrum [Scrum vs Waterfall]

Waterfall

Planà Buid àTestà Review àDeploy

瀑布式开发通常会花几个月时间来规划产品

Waterfall typically goes through a lengthy planning process, which could take several months，

然后再发几个月时间研发产品

fallowed by building the product which again could take many months.

接着进行产品测试，评审，最终发布产品.

and then testing the product, reviewing, and eventually deploying the product.

重点是，如果市场需求或技术环境发生变化，你此时研发出的产品很可能无法满足市场需求

At this point, you may end up bringing the wrong product market if market demand or technology has changed since the original plan was developed.

瀑布式开发在遇到这种变化会出现很多问题。

There are several problems with this method.

首先，产品规划师必须早余后续工作之前完成,

First of all, the planning must be completed before any work begins,

绝大部分案例中，规划环节结束时并没有完全理解项目，但研发工作已经完成了。

and in most cases, the planning has done without entirely understanding the project, once development is being done.

通常情况下，整个项目必须送回规划阶段，然后从头再来，【没理解需求，返回plan】

否则，研发人员就会因为不明白产品规划而受到批评. 【测试不过打回给研发】

Oftentimes things get sent back to the planning phase, and the project either needs starts over, or the developers are just criticized for not understand the plan.

这种情况会反复出现，比如研发完成了，进行产品测试，发现问题就得重新开发,

【测试不过打回给研发】

This cycle can happen many times when development is done building the product, it gets thrown over the fence to test,

有时甚至要重新规划产品

where, when problems are encountered, it bounces back to development and sometimes back to planning.

再接下来的及格步骤中，也会出现同样的问题，

The same issues occur in the next few steps with lots of back stepping in doing over,

这很可能会导致产品发布时间跳票，短则几个月，长则数年

Scrum

Planà Buildà Testà Review

This can lead lag times and many months to several years in order to get a product out the door.

当我们用Scrum 来实施敏捷开发时就大不相同了，整个项目会被分解成不同的小部分。

With Scrum, an implementation of agile, the process is broken up into smaller pieces.

首先，我们围绕最小化产品的特性进行产品规划

First, we do just enough planning to get started with building the minimal feature set.

然后把最小可行化产品开发出来

We build what was planned.

接下来，我们测试和评审这个产品，直到准备发布

Next, we test and review that small feature set and get it ready to ship

循环这个过程，我们就会得到一个可发布的产品

When that cycle is complete, we end up with a potentially shippable product,

这个过程通常指需要一到三周左右

This process usually occurs in a time period of one to three weeks.

我们不断重复这个过程,以减少冲产品规划到开发测试每个阶段的时间。

This is then repeated time and time again, reducing the time from planning to development to testing, each time through the planning process.

我们去做详细的规划来完成下一个增量式发布

We’re doing just enough planning to complete the next incremental release,

而你此时得到了几个增量式版本，成为Spring(冲刺)

you end up with several incremental releases called Sprints,

一个Spring通常需要一到三个星期，而你只是不断重复Sprint直到你的产品功能齐全

A Sprint usually takes from one to three weeks and you just keep repeating the Sprints until your products is feature complete.

有时你可能会在第二次Sprint之后，或者第三次、第四次，甚至更久的时候，最终构成你的产品。

Sometimes you may end up shaping your product after the second Sprint, or the third or the fourth or even further.

但不管怎么说，最后你有了一个可发布的版本。

But you eventually end up with a shipping product.

3 Roles : Product Owner Scrum Master

在Scrum的方法结构体系内，有三个关键角色能帮助团队工作地更好

In Scrum, there are three key roles that are needed for the framework to work well.

首先是产品经理，负责产品特性，同时产品经理会提出产品亮点。

First, the product owner, this is the first person responsible for defining the features that are needed in the product, the product owner has the bright ideas that turning to products.

Scrum Master 是整个团队的负责人,负责帮助团队尽可能完成工作

The Scrum Master is a servant leader to the team, responsible for protecting the team and the process,

组织日常会议和保障其他工作。

Responsible for protecting the team and the process。

Scrum团队的成员由开发人员、测试人员、文案以及其他帮助研发的人组成

The team can be made up of developments, testers, writers and any one else that helps in building the product.

团队成员经常扮演多种角色，有些时候开发人员可能把测试昨晚，或者测试人员把文案写完

Team members often play multiple roles. Some days developers may end up doing test or testers may end up writing.

无论哪种方式，团队都在努力让产品完成

Either way, the team works to get the product done.

3 Artifacts: product backlog, User stories, Burndown charts

在Scrum中有三种常见的可视化文档。

There are three artifacts are documents that are used in Scrum.

第一种文档是，产品需求列表

First, the product backlog

产品经理会先从众多用户故事中刷选出优先项，并把它们列入产品开发列表中

This is where product owner create a prioritized list of features known as user stories that could go into the product.

需求列表会随着每次的Sprint迭代和更改

This list evolves and changes priori with every Sprint.

用户故事，是一种表达产品需求的语言风格,格式为【作为一名__用户,我需要__什么功能，所以__能够】

User stories are a way of describing a feature set that follows the as a user I need something so that reason format,

as a __

I need__

So that__

产品经理通过用户故事来了解需求的细节,为Scrum 团队合理定制任务优先级

this way of phrasing a user story allows the product owner to specify the right amount of details for the team to estimate the size of the task,

最优项的用户故事将进入Sprint代办列表,剩下的继续评估优先级，交到下次Sprint中。

the highest priority user stories go into the Sprint backlog, these get estimated for size and are committed to for the next Sprint.

燃尽图，用以展示整个Sprint代办列表的进度

Burndown charts, show the progress during a Sprint on the completion of tasks in the Sprint backlog.

当燃尽图曲线接近于0时，也就意味着这次Sprint即将完工

This chart should approach zero points as the work is being completed.

3 Ceremonies

Scrum方法中有三种不同形式的会议需要级别

There are three ceremonies that make up Scrum, think of these as meetings or discussions

Sprint计划会议，是产品经理，Scrum Master和开发团队碰头的会议,用户讨论用户故事并估算任务量。

Sprint planning is where the product owner, Scrum Master team meet to discuss the user stories and estimate the relative sizes.

每日例会，也就是我们所熟知的站会,整个团队会简述工作进度,并且讨论是有任务需要搁置或者加派人手

The daily Scrum is a brief standup meeting where the team discusses where they have completed since the previous meeting what they’re working on and anything that might be blocked or need help.

Sprint 临近尾声时，我们会进行Sprint回顾会议,

The Sprint review and retrospective occurs at the end of the Sprint.

这时研发团队会向产品经理演示开发好的功能。

This is where the team demonstrates to completed work to the product owner,

然后整个团队讨论是否需要改进的地方

and then the team discusses what they can to improve the process going forward.

我们一起回顾下Scrum工作流程

Let’s bring it all together and take a look at the Scrum work flow.

首先，产品经理把那些需要上线的产品特性，做成产品需求列表

Start with the product backlog and features that could go into the product,

然后由产品经理甄选最优项，准备交给整个团队讨

the product owner prioritizes the list and brings the top items to the team

第二阶段，召开Sprint 规划会议,研发团队、产品经理和Scrum Master讨论用户故事优先项

Sprint planning is where the team, product owner and Scrum Master discussed the top priority user stories,

并且决定下次Sprint要研发的需求项

determining what can go into the next Sprint.

第三阶段，根据Sprint规划会议制定Sprint需求列表

The output from Sprint planning meeting is the Sprint backlog/

这个列表就是指通过团队讨论后的用户故事，用户下次的Sprint，

This is a list of user stories that have been committed to for the next Sprint，

会议结束后，整个研发团队和产品经理必须要对每个用户故事有深刻的理解。

the entire team and product owner have a solid understanding of what each of the user stories involves, based on the discussions from the Sprint planning meetings

第四阶段，研发团队要在一到三周时间里开发完成Sprint列表中的需求

The Sprint is a one to three week time box where the work committed to in the Sprint backlog has worked on through to completion

在Sprint期间,每日站会用户团队来交流他们做完了什么，正在做什么，以及遇到的问题

During the Sprint, the daily Scrum occurs as a standup meeting where the team discusses what they have completed and what they are working on, as well as any blocked items.

Sprint的产出是一个可以发布的产品版本,是否可以发布由产品经理决定

The outcome of the Sprint is a potentially shippable product.

Potentially shippable means that the product owner can decide if it is ready to ship,

也可以在发布前增加新功能

or if there are any additional features needed before its ships.

第五阶段，在Sprint结束时举行Sprint回顾会议

At the end of the Sprint, a Sprint review and Sprint retrospective meeting occurs.

Sprint回顾阶段，由研发团队向产品经理做案例演示，同时团队一起反思工作中需要改进的地方

The Sprint review is where the team show cases their work to the product owner，

and the retrospective is where the team works on what they can do to improve their process

每次的Sprint结束后要进行回顾

Repeat this work flow for each Sprint

Waterfall Scrum相关推荐

2022软件质量与管理-考题复习
最下面有2022的软件工程与管理考题~ 简答题 [2021]估算的要点(10分) 尽可能划分详细一些: 建立对估算结果的信心: 依赖数据: 估算是利益相关者达成共识的过程,而不是结果. [2021]基 ...
敏捷之道Scrum篇
从去年我一直设想能够在公司的整个开发部门有机会在成型开发团队尝试中小范围的敏捷开发.这个想法其实也是由来已久.或者是说源自于自己在工作中深受传统瀑布开发模型一些弊端的切身感受. 作为一个软件工程师不断 ...
为什么用scrum_为什么Scrum糟糕于数据科学
为什么用scrum Scrum is a popular methodology for PM in software engineering and recently the trend has c ...
scrum 开发方式学习笔记
Scrum vs Waterfall waterfall 开发流程: Plan -> Build -> Test -> Review -> Deploy 缺点: Plan 需要 ...
Agile: 为什么要使用 scrum 而不是瀑布?
Scrum方法需要改变传统方法的思维方式.中心焦点已经从瀑布方法的范围转变为在Scrum中实现最大的商业价值.在瀑布中,改变成本和进度以确保达到预期的范围,在Scrum中,可以改变质量和约束以实现获得 ...
Scrum指南更新：Ken Schwaber、Jeff Sutherland访谈
为了更好的反应Scrum的本质并澄清一些误解,Ken Schwaber和Jeff Sutherland更新了Scrum指南.Scrum可以用于构建软件产品,可以应用于软件之外的许多其他领域.Scrum ...
scrum 和敏捷介绍（概念、流程、自己的理解）
scrum 和敏捷介绍背景本文介绍 scrum 框架,基于自己的理解,有些可能不够准确,请评论反馈 scrum是敏捷中的一种,比较出名的一种,但并不是所有 scrum的规模是比较小的,通常都是小团 ...
GitChat·DevOps | 如何结合 Scrum 和 Kanban
来自吴穹.申导.侯伯薇在 GitChat 上精彩分享原文:如何结合 Scrum 和 Kanban 更多IT技术分享,尽在微信公众号:GitChat 技术杂谈背景介绍 by 吴穹这篇文章背后的 ...
Scrum Master Mock Test (1)
Scrum Master 的模拟考试试卷之一, 虽然对考试这种形式深恶痛绝,但是不得不说这个也是检验和深化理解的一种较好方法,从MockTest上找到了3个test,简单逆向分析一下试卷上所谓的最佳实 ...
GitChat · DevOps | 如何结合 Scrum 和 Kanban
来自吴穹.申导.侯伯薇在 GitChat 上精彩分享原文:如何结合 Scrum 和 Kanban 更多IT技术分享,尽在微信公众号:GitChat 技术杂谈背景介绍 by 吴穹这篇文章背后的 ...

Waterfall Scrum

Waterfall Scrum相关推荐

最新文章

热门文章