全部

1·This also helped with scope management.

这对我们的管理也有所帮助。

2·The reason was scope management, but read on.

理由是范围管理，但是继续向下看。

3·Introduction, Project Scope Management, Project Integration Management.

引论，项目范围管理，项目集成管理。

4·Requirements can only be imported as a requirement in the Scope Management view.

需求只能被作为 “requirement” 导入到 Scope Management 视图中。

5·The Scope Management view displays in the main pane of the GUI, as shown in Figure 4.

在 GUI 的主面板中显示的 Scope Management 视图如图4所示。

6·Scope Management - view and work with change requests, risks, issues, defects and requirements

范围管理（Scope Management）—— 查看并处理变更请求、风险、问题、缺陷以及需求。

7·Poor management (including inability to manage and prioritize risks, and poor scope management).

糟糕的管理(包括不够好的管理能力、风险的优先级划分和糟糕的项目范围管理)。

8·Through the above analysis, some references are hoped to be given for scope management of similar projects.

通过上述分析，希望能够为类似工程开展范围管理工作提供一定的借鉴和参考。

9·Figure 18: scope Management drill-down from an Investment Map: Pie chart showing distribution of project scope items.

图18：从Investment Map得到的Scope Management：饼图表显示了项目范围条目的分布信息。

10·Act as project lead to drive and manage the transition projects introduced by Scope Management, including but not limited to.

作为项目主管，主导和管理由服务拓展小组引入的转移项目，包括但不仅限于。