メンバーからの修正・訂正指摘を20%削減する
見積の15%以内でコーポレートファンクションをリリースする
チームとして99.9%のアップタイムを確保する（年間ダウンタイム8.7時間）
NPSで7以上を1度以上獲得する
保留中の考え方
職種の中でもさらに細かく分ける？
（ex.エンジニア→インフラエンジニア/フロントエンドエンジニア/バックエンドエンジニア）
各職種ごとのFPでは記載を分けても良さそう
上場企業とかだとL7〜9とかあるところはある
評価
53
翻訳 / 英語
- 2024/05/14 01:27:34に投稿されました
Reduce corrections and revisions from team members by 20%.
Release corporate functions within 15% of the estimate.
Ensure a 99.9% uptime as a team (which equates to an annual downtime of 8.7 hours).
Achieve a score of 7 or higher on the NPS at least once.
Pending concepts
Further subdividing job categories?
(For example, Engineer → Infrastructure Engineer/Frontend Engineer/Backend Engineer)
It might be good to separate the FP descriptions for each job category.
For publicly traded companies, there are places with levels L7 to L9.
tech_fundさんはこの翻訳を気に入りました
Release corporate functions within 15% of the estimate.
Ensure a 99.9% uptime as a team (which equates to an annual downtime of 8.7 hours).
Achieve a score of 7 or higher on the NPS at least once.
Pending concepts
Further subdividing job categories?
(For example, Engineer → Infrastructure Engineer/Frontend Engineer/Backend Engineer)
It might be good to separate the FP descriptions for each job category.
For publicly traded companies, there are places with levels L7 to L9.
評価
50
翻訳 / 英語
- 2024/05/14 01:42:52に投稿されました
Reduce 20 % of modifications or corrections pointed out by members
Release corporate function within 15 % of estimates
As a team, maintain 99.9 % of uptime (8.7 hours of down time per year)
Get 7 or higher in NPS once or more
Pending idea
Should divide into more small pieces also among job types?
(ex. engineer ->infrasturucture engineer / front-ende ngineer / back-end engineer)
In FP of each job types, Might be better to describe separately
Possibility of Exist L7 to 9 in listed companies and so on
tech_fundさんはこの翻訳を気に入りました
Release corporate function within 15 % of estimates
As a team, maintain 99.9 % of uptime (8.7 hours of down time per year)
Get 7 or higher in NPS once or more
Pending idea
Should divide into more small pieces also among job types?
(ex. engineer ->infrasturucture engineer / front-ende ngineer / back-end engineer)
In FP of each job types, Might be better to describe separately
Possibility of Exist L7 to 9 in listed companies and so on
