2020.02.05
英文メールの書き方：開発チームに必要な資料について確認する
こんなシチュエーション、お仕事でありませんか？
ソフトウェア開発に携わるのは初めてなので、開発チームに依頼されて用意した資料会っているか確認したい。
英文メールで「開発チームに必要な資料について確認する」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
みなさま、
先ほどの会議ではありがとうございました。
今週中に用意しなければならない要素をリスト化しました。プロジェクトのダッシュボードをご確認ください。まだソフトウェア開発のプロセスを勉強中の身のため、開発チームのみなさまが必要なものを網羅しているか少し不安ですが。
不足しているものがあればご指摘ください。よろしくお願いします。
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:05.250,0:00:06.250
Hello everyone.
0:00:06.250,0:00:07.520
Welcome to E-mail Picks.
0:00:07.520,0:00:12.460
I am now leading a software development project,
and it’s actually my first time to work
0:00:12.460,0:00:16.440
closely with people in the IT team.
0:00:16.440,0:00:20.990
Also, it’s my first time to work with our
IT engineers in the Philippines office.
0:00:20.990,0:00:25.550
Everyone’s really pleasant to work with,
and I wouldn’t mind doing this again even
0:00:25.550,0:00:27.210
though the deadline is pretty tight.
0:00:27.210,0:00:32.669
Now we’re basically developing a web application,
but I am not an IT engineer, so I cannot write
0:00:32.669,0:00:37.280
any code, but I do have a part to play in
the development.
0:00:37.280,0:00:45.300
I need to get and share all the information
the development team needs to know exactly
0:00:45.300,0:00:51.950
what to create; information like what text
to display to the user and what should happen
0:00:51.950,0:00:54.289
if this button is clicked or that button is
clicked.
0:00:54.289,0:00:59.980
So I have a dozen of things I need to prepare
for the team, and I put them into a list.
0:00:59.980,0:01:05.850
Today, I want to announce to the dev team
that I have made the list, and ask them to
0:01:05.850,0:01:08.600
see it and tell me if I am not missing anything.
0:01:08.600,0:01:12.290
So here’s the e-mail I’m going to write.
0:01:12.290,0:01:13.460
Hi everyone,
0:01:13.460,0:01:15.650
Thanks for a productive meeting earlier today.
0:01:15.650,0:01:19.060
I have listed out the elements I need to provide
within this week.
0:01:19.060,0:01:21.330
Please have a look at the project dashboard.
0:01:21.330,0:01:25.720
As I’m still learning the software development
process, I wasn’t 100% sure if this list
0:01:25.720,0:01:27.619
covers everything you’ll need.
0:01:27.619,0:01:30.520
Please let me know if there’s anything missing.
0:01:30.520,0:01:31.520
Thanks!
0:01:31.520,0:01:32.520
Kyota
0:01:32.520,0:01:36.810
OK, so I started with a common opening - I
thanked everyone for participating in our
0:01:36.810,0:01:38.670
last meeting.
0:01:38.670,0:01:42.119
And then I mentioned where they could find
the list I made.
0:01:42.119,0:01:48.090
Here, I’m kinda asking for everyone’s
patience for my not being the most confident
0:01:48.090,0:01:49.390
project leader.
0:01:49.390,0:01:56.090
I wrote “As I’m still learning the software
development process, I wasn’t 100% sure”
0:01:56.090,0:02:01.740
to ask them to take it easy on me because
it’s my first time to work in software development.
0:02:01.740,0:02:04.590
And then I closed with another common sentence.
0:02:04.590,0:02:06.479
Please let me know bla bla bla.
0:02:06.479,0:02:07.899
So that’s it.
0:02:07.899,0:02:12.980
An e-mail to confirm necessary material with
a development team.
0:02:12.980,0:02:17.290
I am really impressed with how efficient our
IT team is, and I’m learning a lot and
0:02:17.290,0:02:18.900
I'm enjoying working with them.
0:02:19.280,0:02:22.940
So that's it for today. Thank you for watching and I'll see you next week.
Hello everyone.
0:00:06.250,0:00:07.520
Welcome to E-mail Picks.
0:00:07.520,0:00:12.460
I am now leading a software development project,
and it’s actually my first time to work
0:00:12.460,0:00:16.440
closely with people in the IT team.
0:00:16.440,0:00:20.990
Also, it’s my first time to work with our
IT engineers in the Philippines office.
0:00:20.990,0:00:25.550
Everyone’s really pleasant to work with,
and I wouldn’t mind doing this again even
0:00:25.550,0:00:27.210
though the deadline is pretty tight.
0:00:27.210,0:00:32.669
Now we’re basically developing a web application,
but I am not an IT engineer, so I cannot write
0:00:32.669,0:00:37.280
any code, but I do have a part to play in
the development.
0:00:37.280,0:00:45.300
I need to get and share all the information
the development team needs to know exactly
0:00:45.300,0:00:51.950
what to create; information like what text
to display to the user and what should happen
0:00:51.950,0:00:54.289
if this button is clicked or that button is
clicked.
0:00:54.289,0:00:59.980
So I have a dozen of things I need to prepare
for the team, and I put them into a list.
0:00:59.980,0:01:05.850
Today, I want to announce to the dev team
that I have made the list, and ask them to
0:01:05.850,0:01:08.600
see it and tell me if I am not missing anything.
0:01:08.600,0:01:12.290
So here’s the e-mail I’m going to write.
0:01:12.290,0:01:13.460
Hi everyone,
0:01:13.460,0:01:15.650
Thanks for a productive meeting earlier today.
0:01:15.650,0:01:19.060
I have listed out the elements I need to provide
within this week.
0:01:19.060,0:01:21.330
Please have a look at the project dashboard.
0:01:21.330,0:01:25.720
As I’m still learning the software development
process, I wasn’t 100% sure if this list
0:01:25.720,0:01:27.619
covers everything you’ll need.
0:01:27.619,0:01:30.520
Please let me know if there’s anything missing.
0:01:30.520,0:01:31.520
Thanks!
0:01:31.520,0:01:32.520
Kyota
0:01:32.520,0:01:36.810
OK, so I started with a common opening - I
thanked everyone for participating in our
0:01:36.810,0:01:38.670
last meeting.
0:01:38.670,0:01:42.119
And then I mentioned where they could find
the list I made.
0:01:42.119,0:01:48.090
Here, I’m kinda asking for everyone’s
patience for my not being the most confident
0:01:48.090,0:01:49.390
project leader.
0:01:49.390,0:01:56.090
I wrote “As I’m still learning the software
development process, I wasn’t 100% sure”
0:01:56.090,0:02:01.740
to ask them to take it easy on me because
it’s my first time to work in software development.
0:02:01.740,0:02:04.590
And then I closed with another common sentence.
0:02:04.590,0:02:06.479
Please let me know bla bla bla.
0:02:06.479,0:02:07.899
So that’s it.
0:02:07.899,0:02:12.980
An e-mail to confirm necessary material with
a development team.
0:02:12.980,0:02:17.290
I am really impressed with how efficient our
IT team is, and I’m learning a lot and
0:02:17.290,0:02:18.900
I'm enjoying working with them.
0:02:19.280,0:02:22.940
So that's it for today. Thank you for watching and I'll see you next week.
