付款。推介服務：課堂錄影隨時睇
(在家觀看 = 0%，在校觀看 = 100%)
(在家觀看 = 0%，在校觀看 = 100%)
100% 在校觀看日期及時間：
自由選擇，點選以下地區觀看辦公時間及位置
不限：$3,680 (地點沒有限制)報名
#(另加 $4,020 考試費)
# 請注意：PRINCE2® 官方授權機構硬性規定，報讀 PRINCE2® 課程時必須同時繳交相應的考試費
費用 ($3,128 / $3,312 / $3,496 + $4,020) 已經包括考試所需的費用
課時： 18 小時
享用時期： 6 星期。進度由您控制，可快可慢。
課堂錄影導師：Franco
在校免費試睇：首 1 小時，請致電以上地點與本中心職員預約。
本課程提供在校免費重睇及導師解答服務。
推介服務：課堂錄影隨時睇
(在家觀看 = 33%，在校觀看 = 67%)
(在家觀看 = 33%，在校觀看 = 67%)
33% 在家觀看日期及時間：
每天 24 小時全天候不限次數地觀看
67% 在校觀看日期及時間：
本中心辦公時間內自由選擇，點選以下地區觀看辦公時間及位置
旺角：$3,680 報名 phone
電話：2332-6544
觀塘：$3,680 報名 phone
電話：3563-8425
北角：$3,680 報名 phone
電話：3580-1893
沙田：$3,680 報名 phone
電話：2151-9360
屯門：$3,680 報名 phone
電話：3523-1560
#(另加 $4,020 考試費)
# 請注意：PRINCE2® 官方授權機構硬性規定，報讀 PRINCE2® 課程時必須同時繳交相應的考試費
費用 ($3,680 + $4,020) 已經包括考試所需的費用
課時： 18 小時
在家及在校觀看： 在家觀看首 6 小時，在校觀看尾 12 小時。
享用時期： 6 星期。進度由您控制，可快可慢。
課堂錄影導師：Franco
在校免費試睇：首 1 小時，請致電以上地點與本中心職員預約。
本課程提供在校免費重睇及導師解答服務。
PRINCE2 是一種在全球廣為認可的項目管理方法。它是一種系統化的項目管理方法，從眾多過去的項目中獲取洞見，並結合了來自多元持分者的知識和觀點，包括項目贊助人、項目經理、項目團隊、學者及顧問。
本中心的 PRINCE2® 7 Foundation 國際認可證書課程認可導師 Franco 會用自行編制的 PRINCE2® 認可教材來授課，課程內容覆蓋 PRINCE2® 7 Foundation syllabus 的所有內容，同時亦會針對考試重點來授課，使同學能通過考試。
| 課程名稱： |
PRINCE2® 7 Foundation 國際認可證書課程 - 簡稱：PRINCE2 Training Course |
| 課程時數： | 共 18 小時課堂 (共 6 堂) |
| 適合人士： | 對項目管理有興趣的人士 |
| 授課語言： | 以廣東話為主，輔以英語 |
| 課程筆記： | 本中心導師親自編寫英文為主筆記，而部份英文字附有中文對照。 |
| 1. PRINCE2® 認可導師： | 專業 PRINCE2® 認可導師教授。 |
| 2. PRINCE2® 認可教材： | 本課程會使用本中心編制的 PRINCE2® 認可教材教授。 |
| 3. 內容針對考試需要： | 本中心的 PRINCE2® 課堂內容針對考試需要，並提供充足的練習題及模擬考試題目，幫助同學通過考試。 |
| 4. 提供模擬考試題目： | 本中心為學員提供約 100 條 PRINCE2® Foundation 的模擬考試題目，每條考試題目均附有標準答案。而較難理解的題目，均會附有導師的解釋。 |
| 5. 免費重讀： | 傳統課堂學員可於課程結束後三個月內免費重看課堂錄影。 |
學員可以選擇在本中心或在家應考 PRINCE2® Foundation 考試。
選擇本中心考試的學員，請學員必須聯絡本中心職員以作安排。
- 電話：3580-1893
- 辦公時間：一至五：14:15 - 22:00；六及日：12:15 - 20:00 (星期三及公眾假期休息)
選擇在家考試的學員，學員需要自行準備電腦考試，而考試環境和電腦需要符合以下的要求。
考試環境要求:
- There is only one doorway for access in and out of the room.
- The room is private, and you can be sure you will be alone for the entire exam.
- The walls and desk/table(s) are clear of all unnecessary and/or unauthorized items (e.g., posters, post-it notes, papers and books).
- Where note paper or other resources are allowed, you can and should have this available on your desk for your exam onboarding. You must show these authorized items to the Proctor on request, so they can ensure there is nothing on them that could provide an unfair advantage.
- No screens are visible, other than the screen which is being used to take the exam.
- There is adequate light to ensure the Proctor can see you clearly throughout the exam. Light should not be directed toward the webcam.
考試電腦要求:
- Windows® 11, Windows® 10 version 17763 or later (Windows 10S is not supported), Windows® 8.1, Windows® 8.
- Internet Explorer version 10 or greater.
- Dual-core 2.4GHz CPU or faster with 2GB of RAM (Minimum requirements).
- Active Full-Time/Broadband internet connection of at least 4Mbps.
- 16-bit monitor (at least 15") with screen resolution 1024 x 768 or higher.
- Speakers and microphone.
- Keyboard and mouse or another pointing device (keyboard set to English characters).
- A single web camera you can rotate.
- Cameras are clear and free from obstruction.
- You can rotate your webcam 360 degrees, low and high, to show all areas of the room, including under the desk, the desk surface and any other areas that may pose a risk to exam security.
- The computer sound settings are set to Speakers and Microphones. Headsets are not allowed during the exam.
- The screen and webcam are positioned so that you and the doorway of the room are fully visible to the Proctor through the webcam.
- You are sat comfortably and can maintain the same position, in full view of the Proctor, throughout the exam.
|
課程名稱：PRINCE2® 7 Foundation 國際認可證書課程 - 簡稱：PRINCE2 Training Course |
1 Understand key concepts relating to projects and PRINCE2 [Syllabus Reference: 1]
1.1.1 the definition of the integrated elements of PRINCE2: principles, people, practices, processes and the project context [Syllabus Reference: 1.1a]
1.1.2 the definition of a project and project management [Syllabus Reference: 1.1b]
1.1.3 the aspects of project performance to be managed [Syllabus Reference: 1.1c]
1.1.4 the definition of delivery approaches: linear-sequential iterative-incremental, hybrid [Syllabus Reference: 1.1d]
1.1.4.1 Linear-sequential approach
1.1.4.2 Iterative-incremental approach
1.1.4.3 Hybrid approach
1.2.1 the common reasons why project management is used [Syllabus Reference: 1.2a]
1.2.2 the characteristics of a project [Syllabus Reference: 1.2c]
1.2.3 the common challenges that PRINCE2 is designed to address [Syllabus Reference: 1.2b]
1.2.4 projects in context/project environment [Syllabus Reference: 1.2d]
1.2.4.1 Organizational context
1.2.4.2 Commercial context
1.2.4.3 Sustainability context
1.2.4.4 Scale
1.2.5 the features and benefits of PRINCE2 [Syllabus Reference: 1.2e]
2 Understand how the PRINCE2 principles underpin the PRINCE2 method [Syllabus Reference: 2]
2.1 Explain the PRINCE2 principles [Syllabus Reference: 2.1]
2.1.1 Ensure continued business justification
2.1.2 Learn from experience
2.1.3 Define roles, responsibilities and relationships
2.1.4 Manage by exception (with tolerance concepts)
2.1.5 Manage by stages
2.1.6 Focus on products
2.1.7 Tailor to suit the project
2.2 Explain how and why the principles provide the basis of applying PRINCE2, and which factors influence the way the PRINCE2 method can be tailored and applied, who is responsible, and how tailoring decisions are documented [Syllabus Reference: 2.2]
3 Understand the importance of people in successful projects [Syllabus Reference: 3]
3.1.1 Organizational ecosystem
3.1.2 Project ecosystem
3.1.3 Change management
3.1.4 Stakeholder
3.1.5 Culture
3.1.6 Collaboration and co-creation
3.1.6.1 Collaboration
3.1.6.2 Co-creation
3.1.7 Leadership
3.1.8 Management
3.2.1 People within the project and people affected by the project
3.2.2 Leadership and management
3.3.1 Change management and why it is important
3.3.2 Stakeholder engagement
3.3.3 Communication
3.3.4 Effective teams, including diversity, capability and competence
3.4 Explain the purpose of the management products required to support the people element of projects [Syllabus Reference: 3.4]
3.4.1 PID: change management approach
3.4.2 PID: communication management approach
3.5 Explain how people aspects integrate with other PRINCE2 elements [Syllabus Reference: 3.5]
3.5.1 People and PRINCE2 principles
3.5.1.1 Ensure continued business justification
3.5.1.2 Learn from experience
3.5.1.3 Manage by stage
3.5.1.4 Manage by exception
3.5.1.5 Focus on products
3.5.1.6 Tailor to suit the project context
3.5.2 People and PRINCE2 practices
3.5.3 People and PRINCE2 processes
4 Understand the PRINCE2 practices and how they are applied throughout the project [Syllabus Reference: 4]
4.1 Explain the purpose of PRINCE2 management products, including [Syllabus Reference: 4.1]
4.1.1 PID
4.1.2 Project log
4.2 Explain the purpose of the ‘business case’ practice [Syllabus Reference: 4.1.1]
4.3 Describe the key relationships between the ‘business case’ practice and the principles [Syllabus Reference: 4.1.2]
4.4 Explain the purpose of the key management products required to support the ‘business case’ practice [Syllabus Reference: 4.1.3]
4.4.1 Project brief
4.4.2 Business case
4.4.3 PID: benefits management approach
4.4.4 PID: sustainability management approach
4.5.1 Output
4.5.2 Outcome
4.5.3 Benefit
4.5.4 Dis-benefit
4.5.5 Business objective
4.6 Describe the guidance for effective management of the business case, including [Syllabus Reference: 4.1.5]
4.6.1 Business case lifecycle
4.6.2 Aligning products to business objectives and tolerances
4.6.3 Establishing business justification
4.7 Describe the PRINCE2 technique for the ‘business case’ practice [Syllabus Reference: 4.1.6]
4.8 Explain the purpose of the ‘organizing’ practice [Syllabus Reference: 4.2.1]
4.9 Describe the key relationships between the ‘organizing’ practice and the principles [Syllabus Reference: 4.2.2]
4.10 Explain the purpose of the key management products required to support the ‘organization’ practice [Syllabus Reference: 4.2.3]
4.10.1 PID: project management team structure
4.10.2 PID: role descriptions
4.10.3 PID: commercial management approach
4.11.1 Project board
4.11.2 Project team
4.12 Describe the guidance for effective organizing of [Syllabus Reference: 4.2.5]
4.12.1 The three project interests
4.12.1.1 Business and project executive
4.12.1.2 User and senior user
4.12.1.3 Supplier and senior supplier
4.12.2 PRINCE2 roles
4.12.2.1 Project assurance
4.12.2.2 Project manager
4.12.2.3 Project support
4.12.2.4 Team manager(s)
4.12.3 Work breakdown structure / WBS
4.13 Describe the PRINCE2 technique for the ‘organizing’ practice [Syllabus Reference: 4.2.6]
4.14 Explain the purpose of the ‘plans’ practice [Syllabus Reference: 4.3.1]
4.15 Describe the key relationships between the ‘plans’ practice and the principles [Syllabus Reference: 4.3.2]
4.16 Explain the purpose of the key management products required to support the ‘plans’ practice [Syllabus Reference: 4.3.3]
4.16.1 Work package description
4.16.2 Project product description
4.16.3 Plan (including project, stage, team & exception plan)
4.17.1 Schedule
4.17.2 Dependency
4.17.3 Project plan
4.17.4 Stage plan
4.17.5 Team plan
4.17.6 Exception plan
4.17.7 Scope
4.18 Describe the guidance for effective management of plans [Syllabus Reference: 4.3.5]
4.18.1 The planning horizon
4.18.2 Project stages
4.18.3 Product-based planning
4.18.4 Using tolerances to manage constraints
4.18.5 Delivery sustainability
4.19 Describe the PRINCE2 technique for the ‘plans’ practice [Syllabus Reference: 4.3.6]
4.20 Explain the purpose of the ‘quality’ practice [Syllabus Reference: 4.4.1]
4.21 Describe the key relationships between the ‘quality’ practice and the principles [Syllabus Reference: 4.4.2]
4.22 Explain the purpose of the key management products required to support the ‘quality’ practice [Syllabus Reference: 4.4.3]
4.22.1 Product description
4.22.2 PID: quality management approach
4.22.3 Project log: quality register
4.22.4 Project log: product register
4.23.1 User quality expectations
4.23.2 Acceptance criteria
4.23.3 Quality specifications
4.23.4 Requirements
4.24 Describe the guidance for effective management of quality [Syllabus Reference: 4.4.5]
4.24.1 Quality planning
4.24.2 Quality control
4.24.3 Quality assurance
4.25 Describe the PRINCE2 technique for the ‘quality’ practice [Syllabus Reference: 4.4.6]
4.26 Explain the purpose of the ‘risk’ practice [Syllabus Reference: 4.5.1]
4.27 Describe the key relationships between the ‘risk’ practice and the principles [Syllabus Reference: 4.5.2]
4.28 Explain the purpose of the key management products required to support the ‘risk’ [Syllabus Reference: 4.5.3]
4.28.1 PID: risk management approach
4.28.2 Project log: risk register
4.29.1 A risk: threat or opportunity based on uncertainty
4.29.2 Risk appetite
4.29.3 Risk tolerance
4.29.4 Risk cause, event and effect
4.29.5 Risk exposure
4.29.6 Risk owner and risk action owner
4.29.7 Risk probability
4.29.8 Risk impact
4.30 Describe the guidance for effective management of risk [Syllabus Reference: 4.5.5]
4.30.1 Risk planning
4.30.2 Risk analysis
4.30.3 Risk control and recommended risk response types
4.30.4 Risk culture and Understand decision bias
4.30.5 Use of data
4.31 Describe the PRINCE2 technique for the ‘risk’ practice [Syllabus Reference: 4.5.6]
4.32 Explain the purpose of the ‘issues’ practice [Syllabus Reference: 4.6.1]
4.33 Describe the key relationships between the ‘issues’ practice and the principles [Syllabus Reference: 4.6.2]
4.34.1 PID: issue management approach
4.34.2 Project log: issue register
4.34.3 Issue report
4.35 Describe the guidance for effective management of issues [Syllabus Reference: 4.6.5]
4.35.1 Issue (including types of issue: change, problem/concern, business opportunity, request for change, off-specification)
4.35.1.1 Issue
4.35.1.2 Change
4.35.1.3 Problem/concern
4.35.1.4 Business opportunity
4.35.1.5 Request for change
4.35.1.6 Off-specification
4.35.2 Project baseline
4.35.3 Change control
4.36 Describe the PRINCE2 technique for the ‘issues’ practice [Syllabus Reference: 4.6.6]
4.36.1 Baselines
4.36.2 Issue resolution
4.36.3 Change control
4.36.5 Change budget
4.37 Explain the purpose of the ‘progress’ practice [Syllabus Reference: 4.7.1]
4.38 Describe the key relationships between the ‘progress’ practice and the principles [Syllabus Reference: 4.7.2]
4.39 Explain the purpose of the key management products required to support the ‘progress’ practice [Syllabus Reference: 4.7.3]
4.39.1 Checkpoint report
4.39.2 Highlight report
4.39.3 End stage report
4.39.4 End project report
4.39.5 Lessons report
4.39.6 Exception report
4.39.7 Project log: daily log
4.39.8 Project log: lessons log
4.39.9 PID: digital and data management approach
4.40.1 Forecast
4.40.2 Exception
4.40.3 Tolerance
4.40.4 Event-driven and time-driven controls
4.41 Describe the guidance for effective management of progress [Syllabus Reference: 4.7.5]
4.41.1 Tolerances for progress control
4.41.2 Types of control
4.41.3 Reviewing progress and lessons
4.41.4 Reporting progress and lessons
4.41.5 Forecasting
4.41.6 Escalating
4.41.7 Use of data and systems in progress management
4.42 Describe the PRINCE2 technique for the ‘progress’ practice [Syllabus Reference: 4.7.6]
5 Understand the PRINCE2 processes and how they are carried out throughout the project [Syllabus Reference: 5]
5.1 Overview of PRINCE2 processes
5.2 Explain the purpose of the PRINCE2 processes [Syllabus Reference: 5.1]
5.2.1 Starting up a project
5.2.2 Directing a project
5.2.3 Initiating a project
5.2.4 Controlling a stage
5.2.5 Managing product delivery
5.2.6 Managing a stage boundary
5.2.7 Closing a project
5.3 Explain the objectives of the PRINCE2 processes [Syllabus Reference: 5.2]
5.3.1 Starting up a project
5.3.2 Directing a project
5.3.3 Initiating a project
5.3.4 Controlling a stage
5.3.5 Managing product delivery
5.3.6 Managing a stage boundary
5.3.7 Closing a project
5.4 Explain the context of the PRINCE2 processes [Syllabus Reference: 5.3]
5.4.1 Starting up a project
5.4.2 Directing a project
5.4.3 Initiating a project
5.4.4 Controlling a stage
5.4.5 Managing product delivery
5.4.6 Managing a stage boundary
5.4.7 Closing a project