0.6/字_潤__短文_1500字_20130424 - 翻譯

[必]我已經讀過置底版規、參考費率、發文必讀公告，並願意遵守規定：

YES

──────────────────────────────────────
[必]工 作 量： 2000字
[必]工作報酬：0.6/EN
[必]涉及語言： EN
[必]所屬領域： 履歷 自傳
[必]文件類型： 一般文章
[必]截 稿 日： 4/28
[必]應徵期限： 4/25
[必]聯絡方式： 站內信
[必]付費方式：完稿後2天內付清。
案主跟譯者需協定何時及如何付款，以避免日後爭議。）
──────────────────────────────────────
[選]工作要求：（若未提供請勿刪除）
[選]參考段落：（提供部分段落讓譯者評估難度，若未提供請勿刪除）
[選]試 譯 文：（100-200字，並不超過全文1/10。嚴禁私下試譯。若未提供請勿刪除）
balabala........As I was the lead in the team, I knew that there would be some
risks for avoiding the component. Some approaches we can do as to fight back
for the out of scope component and transfer the risk back
to the developer team or contain the additional component but we would need
to work overtime for dealing with the additional part.
The decision I made was to adopt XXX method. I checked the
previous release information to find the most impact and most often happened
issues. So I added the information in the plan to inform developer that
we will only cover the most problem area part instead of taking them all.
During the project, because of the testing for the additional part on the
early stage, the issues can be fixed on time. so at last, our projects
finally completed without working overloading and retain for good quality.

[選]其他事項：（若未提供請勿刪除）

──────────────────────────────────────

--