(two answers) Which TWO are common non-technical risks in migration projects?

Non-technical risks in migration projects are related to people, processes, and project management rather than technology or hardware. A lack of stakeholder alignment is a critical non-technical risk, as it can lead to conflicting objectives, scope creep, and inadequate support, jeopardizing the project's success. Insufficient staff training is another major non-technical risk, as it creates a skills gap that can result in configuration errors, operational inefficiencies, and an inability to manage the new environment effectively post-migration. Both are rooted in organizational and human factors.

C. Cabling tray shortages: This is a technical or logistical risk related to the physical infrastructure and supply chain, not a non-technical issue concerning personnel or management.
D. Missing LED faceplates: This is a minor technical risk involving a specific hardware component. It falls under equipment and material logistics, not non-technical project management.

1. HPE Pointnext Services - Technology Consulting Services: Official HPE documentation frequently emphasizes that successful transformation and migration projects depend on aligning people, processes, and technology. The "people" aspect directly covers stakeholder management and staff competency. The "HPE Transformation Program for Cloud" service, for example, explicitly includes "Organizational change management" and "Skills transformation" as key components to mitigate non-technical risks. (Source: HPE Pointnext Services Portfolio documentation, specific focus on Transformation and Migration services).

2. Project Management Institute (PMI) - A Guide to the Project Management Body of Knowledge (PMBOK® Guide): While not an HPE-specific document, its principles are foundational to HPE's project management methodology. The PMBOK® Guide categorizes risks, clearly distinguishing between technical risks (e.g., technology, performance) and non-technical risks such as project management (e.g., planning, communication) and organizational risks (e.g., resources, stakeholder support, training). This standard framework validates that stakeholder and training issues are non-technical. (See PMBOK® Guide, Section 11: Project Risk Management).

3. Wallace, L., & Webber, D. (2017). The CIO's Guide to IT Transformation: Strategy, Sourcing, and Satisfaction. This academic and professional text discusses IT project risks, identifying stakeholder buy-in and workforce skills as primary non-technical challenges that frequently cause projects to fail. It notes that "without stakeholder alignment, the project is doomed" and that "a failure to plan for training and skills development" is a common pitfall. (Chapter on Risk Management).