Home | Glossary | PrjMgt | EHL | ERM | HLU | PAT | HDI | HLP | CTL | Disclaimer | Copyright

DEPARTMENT EDUCATION - DIRECTOR ITD PROJECT MANAGEMENT OFFICE [PMO]

SELECTION CRITERIA - KNOWLEDGE, SKILLS AND EXPERIENCE REQUIRED - ERM

B	Experience in risk management and the ability to apply risk management 
	principles in an ITD environment

According to Wikipedia

"Risk management is the identification, assessment, and prioritization of 
risks (defined in ISO 31000 as the effect of uncertainty on objectives, whether 
positive or negative) followed by coordinated and economical application of 
resources to minimize, monitor, and control the probability and/or impact of 
unfortunate events or to maximize the realization of opportunities. 

Risks can come from uncertainty in financial markets, threats from project 
failures (at any phase in design, development, production, or sustainment 
life-cycles), legal liabilities, credit risk, accidents, natural causes and 
disasters as well as deliberate attack from an adversary, or events of 
uncertain or unpredictable root-cause. 

Methods, definitions and goals vary widely according to whether the risk 
management method is in the context of project management, security, 
engineering, industrial processes, financial portfolios, actuarial assessments, 
or public health and safety."

I have consistently demonstrated with the multiple ITD projects developed 
for the Open Interchange Consortium [OIC] since 1997 that the RUBAC Project 
Management Methodology provides the process to ensure that projects are 
developed on time and below budget.

This is particularly the case if these projects are developed as "Software-
as-a-Service [SaaS]" projects whereby the project particpants receive long-term
royalties based on Internt hits rather than one-off payments for developing 
the software 

Many Internet Applications are now developed as "SaaS" projects because they 
have a very low project development costs as they provide long-term Royalties
to the project participants

Examples of "SaaS" Contracts include the Shorelink libary network in 2009 

However there are different risk factors for each stage of a project:

The stages of a project can include:

A	Proposal for a project - who requires the project, timescale and resources

B	Research into similar projects - using the Internet and library resources

C	A detailed project plan or specification

D	Production of a tender

E	Acceptance of tender and contract

F	Monitoring progress with contracts and sub-contractors

This is one of the reason TIMS was commissioned in 1998 and developed for electronic 
tenders which then had a number of eAspects to consider as part of the eProject 
lifecycle including:
 
A	E-Tenders
B	E-Resource - partners and sub-contractors
C	E-budgets
D	E-quotation
E	E-contract
F	E-contract variance
G	E-performance
H	E-payment
I	E-support and enhancement

With Project Management software like PMBoK the advice is to establish Committees 
and Work Groups to identify and manage the risk factors at each stage of a project

This is where effective Project Management benefits from using Group Support Services [GSS] 
to communicate effectively with Stakeholders and members of the Committees and Work Groups 
electronically on the risk factors and progress with each stage of a project .

This is one of the reasons the OIC commissioned the development and implementation of 
Electronic Committee Information Management [ECIM] with guidelines for effective 
committee/work group  management using the RUBAC Project Management EII Methodology

This is now a very viable methodology for Project Management as every subcontractor and 
employee now use mobile phones and all sub-contractors now use computersied systems for 
responding to Request for Quotations [RFQ] and Request for Tenders [RFT] and submitting 
reports for progress payments

Home | Glossary | PrjMgt | EHL | ERM | HLU | PAT | HDI | HLP | CTL | Disclaimer | Copyright