Three Tips to Idenity Project and Program Risks

Technology Project and Program Management

I was reading another article about identifying or handling project risks:

http://www.techrepublic.com/blog/five-tips/five-tips-for-handling-project-risks/534?tag=mantle_skin;content

Although it seems to be presenting activities of risk identification and management, and not tips, it was interesting.

But I would like to present three tips to identify project and program risks

 
Three tips (perspectives) to identify/uncover risks for IT projects and programs.

Identify possible/potential risks based on:

1. The technology being developed and introduced to the organization and user community, impact on the organization, other processes (or systems and their interfaces) and people
2. The project or program scope, its approved budget(s), the project plan and schedules, resources (manpower, money, equipment, etc), procurement and subcontractors/vendors
3. The System/System Development Life Cycle (SDLC) i.e., requirements identification and analysis, Architecture/Detail Design, Development, System Test, Delivery/Deployment)