跟讀練習: Intro to Scrum in Under 10 Minutes - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
122 句
如果句子過短或過長，請點選 Edit 進行調整。
1
Hi, this is me.
2
My name is Hamid Chodjai
3
and I've been involved with a number of software development projects over the years at a number of different companies
4
and I've come to recognize Scrum as one of the best agile development practices in use today.
5
In this fast-paced video, I want to show you why Scrum is
6
so great and how you can get started with Scrum in under 10 minutes.
7
I'll cover all the core Scrum concepts like product backlogs, team roles, sprints, turn-down charts, and more.
8
So get ready to be bombarded with information.
9
Let's say this is the product we want to build.
10
For this product, we get all kinds of feature requests from customers, executives, or even other team members.
11
In Scrum, features are written from the perspective of the end-user.
12
Therefore, features are known as user stories.
13
The collection of all these user stories is called the product backlog.
14
Another way to think of the product backlog is to think
15
of it as a wish list of all the things that would make this product great.
16
Once we have our wish list or the product backlog, we need to start planning which specific user stories we're going to be putting into a particular release of our product.
17
But we're getting ahead of ourselves.
18
Let's back up a bit.
19
To build this product, we need to have one
20
or more people in our team who are going to play a variety of roles.
21
First, we need her.
22
She plays the role of product owner and helps make sure the right features make it into the product backlog, representing the users and customers of the product.
23
She helps set the direction of the product.
24
Then we need this guy.
25
He's the scrum master and his job is to make sure the project is progressing smoothly
26
and that every member of the team has the tools they need to get their job done.
27
He sets up meetings, monitors the work being done and facilitates release planning.
28
He's a lot like a project manager but that's such a boring title
29
so we'll call him a scrum master to imply he knows some jujitsu.
30
And the rest of the team has similar roles to other development processes.
31
These guys build the product while these guys test it to make sure to make sure it works right.
32
These guys use it and hopefully pay for it.
33
And these guys, they generally get in the way, but it turns out you can't build many products without them.
34
But let's get back to this, release planning.
35
To plan a release, the team starts with this, the product backlog, and they identify the user stories they want to put into this release.
36
These user stories then become part of the release backlog.
37
The team then prioritizes the user stories and estimates the amount of work involved for each item.
38
Sometimes larger user stories are broken down into smaller, more manageable chunks.
39
The collection of all the estimates provides a rough idea of the total amount of work involved to complete the entire release.
40
A quick side note about estimates.
41
There are a lot of techniques for creating good estimates.
42
Some prefer estimating in story points, where estimates are made relative to building a small component with a known level of difficulty.
43
Unfortunately, story points don't answer the question of, when will my project ship?
44
I've found that the best technique is to estimate work in hours, but to use some standards in how estimates are done.
45
For example, things that take less than a day to complete will be estimated as 1 hour, 2 hours, 4 hours, or 8 hours.
46
Every item will fall into one of those buckets.
47
There will be no 3-hour estimates, for example.
48
A 3-hour item would fall into the 4-hour bucket.
49
Larger items will be estimated as 2 days, 3 days, 5 days, or 10 days.
50
Again, all estimates in between will fall into the next larger bucket.
51
Extremely large items are similarly estimated in months.
52
1, 2, 3, or 6 months.
53
But the reality is that such items will need to be broken down substantially before work actually begins.
54
We'll come back to these estimates in just a minute.
55
But for now, let's get back to this, the release backlog.
56
With a prioritized set of user stories and the estimated amount of work at hand, we're now ready to plan out several sprints to get the work done.
57
Sprints are short duration milestones that allow teams to tackle a manageable chunk of the project
58
and get it to a ship ready state.
59
Sprints generally range from a couple of days to as much as 30 days in length, depending on the product's release cycles.
60
The shorter the release cycles, the shorter each sprint should be.
61
And you'll want to have at least two to as many as a dozen sprints in a given release.
62
So at this point, we can take our release backlog and split it up into several of these, sprint backlogs.
63
One of the most important things to remember about sprints is
64
that the goal of each sprint is to get a subset of the release backlog to a ship-ready state.
65
So at the end of each sprint, you should have a fully tested product with all the features of the sprint 100% complete.
66
Since sprints are a very short but a realistic representation of part of the product, a late finish of the sprint is a great indicator
67
that the project is not on schedule and something needs to be done.
68
Therefore, it's extremely important to monitor the progress of each sprint with this, a burndown chart.
69
The burndown chart is the number one reason for scrum's popularity
70
and one of the best project visibility tools to ensure a project is progressing smoothly.
71
The burndown chart provides a day-by-day measure of the amount of work that remains in a given sprint or release.
72
In this graph, you can see that the amount of work remaining bounces up and down from day to day, but is generally trending towards zero.
73
Because historical information is provided in the burndown chart, it's easy to see if the team is on the right track.
74
Using the burndown chart, the team can quickly calculate this, the slope of the graph, which is also called the burndown velocity.
75
This is the average rate of productivity for each day.
76
For example, a team's rate of productivity might be that on a typical day they finish approximately 50 hours of work.
77
Knowing that, it's possible to calculate an estimated completion date for the sprint, or even for the entire release based on the amount of work remaining.
78
What's great about the burndown chart is that we can compare our actual velocity
79
and projected completion date to what the team needs to do in order to finish on time.
80
This is perhaps the most useful piece of knowledge that any team member, product owner, or product executive can have about the project.
81
Because knowing whether
82
or not the project is on track early in the schedule
83
can help teams make the proper adjustments necessary to get the project on track.
84
The burndown chart provides empirical proof that the project is on track or if it's going to be late.
85
So let's talk a little about where the data for this incredibly useful burndown chart comes from.
86
As you recall, part of the release planning process was to create an estimate for each user story in the release backlog.
87
The collection of these estimates for a given sprint represents the total amount of work
88
that must be done to complete that sprint.
89
As each team member goes through and makes progress on one or more of the user stories, they simply update the amount of time remaining for each of their own items.
90
So the total amount of time remaining on the group of user stories
91
that make up a sprint changes on a day-by-day basis, hopefully going downward until it hits zero when the sprint is complete.
92
The burndown chart aggregates the remaining work data and shows it visually.
93
It's brilliant because it communicates a massive amount of information in just a few seconds.
94
And that brings us to this, the daily scrum.
95
The daily scrum is an essential tool to having communication flow freely between team members.
96
The idea is to have fast-paced, stand-up meetings where team members quickly list the work they have completed since the last meeting and any obstacles in their way.
97
By meeting daily, it ensures the team is always in sync
98
and any major issues are dealt with as soon as they are known.
99
Finally, as each sprint comes to a finish, it's important to have a sprint retrospective meeting where the team can reflect on what went right and areas of improvement.
100
After all, Scrum is a flexible, agile development method that needs constant improving and tweaking for every team.
101
So there you have it, Scrum in under 10 minutes.
102
You now know all the essential concepts to start implementing Scrum inside of your organization.
103
But wait a second, what about tools to help you implement Scrum?
104
Well, it just so happens that I've spent the last 10 years building such a tool, with a lot of help from these guys, a group of genius coders and design ninjas.
105
The tool is called OnTime, and it helps you manage your products, your backlogs, your team, releases and your sprints.
106
It gives you project visibility with burndown charts and always answers the question of who is working on what.
107
You can get started with it for free at Axiosoft.com.
108
Of course, you could use a giant whiteboard, some note cards, and a bunch of different spreadsheets to track everything.
109
You could also use an abacus instead of a calculator to do math, but we're getting a little off topic.
110
So let's quickly review everything.
111
In Scrum, you work with this, a product backlog, which is nothing more than a list of features that we call user stories.
112
You then break down the product backlog into one or more release backlogs.
113
And for a given release, you further break up the release backlog into a number of sprint backlogs, which are essentially short duration milestones throughout your project.
114
You then monitor the progress of each sprint using these, burndown charts, and have daily scrum meetings to ensure everything is on track.
115
After each sprint, you have a retrospective meeting to fine-tune everything.
116
And if you want a tool to implement scrum, you can use OnTime.
117
It'll help you ship software OnTime.
118
That's all there is to it.
119
Oh, and one last thing.
120
Whether you loved or hated this video, I'd love to hear from you.
121
You can reach me on Twitter or via email if you have any feedback.
122
Now get going, create a great team, collaborate, and ship software on time.
FOR YOU
推薦影片
C1480 句
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
C16
44 句
Scrum Events
Business EnglishUniversity StudentsWorking Adults
C18
24 句
Introducing Automations: always-on coding agents
Business EnglishUniversity StudentsWorking Adults
C12
30 句
C++ in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C11
83 句
How an Agile Coach can help Product Owners
Daily ConversationUniversity StudentsWorking Adults
C12
213 句
The Technical, Business and UX Skills Every Product Manager Needs
Business EnglishUniversity StudentsWorking Adults
C13
260 句
【TED】優れたリーダーはどうやって行動を促すか/サイモン・シネック （日本語字幕）
Business EnglishDaily ConversationUniversity Students
C14
206 句
New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets
British AccentBusiness EnglishUniversity StudentsWorking Adults
C19
25 句
10 Usability Heuristics: From Theory to Practice | Course Preview
Business EnglishUniversity StudentsWorking Adults
B228
29 句
How to build a startup in one month | Pieter Levels and Lex Fridman
Business EnglishUniversity StudentsWorking Adults
C19
117 句
Atomic Habits: How to Get 1% Better Every Day - James Clear
Business EnglishUniversity StudentsWorking Adults
C11
28 句
Kubernetes Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
關於本課
在這一節課中，學習者將會了解Scrum這一靈活開發實踐的基本概念，包括產品待辦事項、團隊角色、衝刺以及如何進行釋出計劃。我們將通過關鍵的使用者故事來理解Scrum的工作流程，幫助學習者在短時間內掌握這些概念，提升其英語口語能力，尤其是在與專案管理和軟體開發相關的領域。
關鍵詞彙與短語
- 使用者故事 (User Stories): 從終端使用者的角度書寫的功能請求。
- 產品待辦事項 (Product Backlog): 所有使用者故事的集合，是產品的願望清單。
- 衝刺 (Sprints): Scrum中按時間劃分的工作週期，通常為1-4周。
- 釋出計劃 (Release Planning): 團隊確定並優先順序安排要在特定釋出中包含的使用者故事。
- Scrum Master: 確保專案順利進行的團隊角色，類似於專案經理。
- 功能請求 (Feature Requests): 來自客戶或團隊成員的產品功能建議。
- 評估工作量 (Estimating Work): 對工作量進行評估的重要步驟，通常以小時或故事點的形式進行。
- 軟技能 (Soft Skills): 在團隊合作和專案管理中所需的非技術技能。
練習技巧
為了提高您的英語發音，建議學習者採取shadow speak的方法練習。這意味著您可以模仿聲調、停頓和語速，以提高英語口語練習的自然性。由於影片內容快速且資訊量大，您可以：
- 分段收聽：將影片分成小段，每段集中注意力，模仿說話者的語氣。
- 停頓重聽：在聽到重點內容時，可以暫停並重復說一遍，以糾正自己的發音。
- 記錄對話：使用錄音裝置記錄自己的發音，與原聲對比，識別需要改進的地方。
- 練習時間：每天安排15-30分鐘專注於提高英語發音，定期使用相關材料進行練習。
通過這些方法，您將能夠更有效地進行英語口語練習，特別是在與Scrum及軟體開發相關的對話中，幫助您在職業生涯中更自信地進行溝通。
影片中的語法
說話人最常用的結構，並附上影片中的原話：
| 結構 | 影片中的用法 |
|---|---|
| 被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的 | I've been involved · be bombarded · are written |
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | I've been involved · I've come · I've found |
| 定語從句 who / which + 從句 — 補充說明人或事物 | graph, which is · backlog, which is · backlogs, which are |
什麼是跟讀法？
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。