Project Management
IT Project Risk Management Checklist Template
Download Free IT Project Risk Management Checklist Template:
Schedule creation
- Schedule, resources, and product definition have all been dictated by the customer or upper management and are not in balance.
- Schedule is optimistic, ‘best case’, rather than realistic, ‘expected case’.
- Schedule omits necessary tasks.
- Schedule was based on the use of specific team members, but those team members were not available.
- Cannot build a product of the size specified in the time allocated.
- Product is larger than estimated (in lines of code, function points, or percentage of previous project’s size).
- Effort is greater than estimated (per line of code, function point, module, etc.).
- Re-estimation in response to schedule slips is overly optimistic or ignores project history.
- Excessive schedule pressure reduces productivity.
- Target date is moved up with no corresponding adjustment to the product scope or available resources.
- A delay in one task causes cascading delays in dependent tasks.
- Unfamiliar areas of the product take more time than expected to design and implement.
- Read more
- 759 reads
Seven Step to Establish Good IT Project Control
1. Agree the stage breakdown with the Project Board Controls
2. Agree the format of reports to the Project Board
3. Agree the frequency of Project Board reports
4. Establish the frequency of Stage Plan updates
6. Create a Communication Plan covering required input and output information during the life of the project
6. Check that there are suffcient risk and Business Case monitoring activities in the plans
- Read more
- 153 reads
Software Acquisition Process Key Activities
1. Defining the information and system requirements
2. Identifying various alternatives
3. Performing a feasibility analysis
4. Conducting a risk analysis
5. Defining ergonomic requirements
6. Carrying out the selection process
7. Procuring the selected software
- Read more
- 138 reads
Eight basic components of an RFP (request for proposal) documents
How to create a good RFP (request for proposal) documents, here is eight basic components that you should aware:
1. Background information about the company, business problem, and the computing environment. It may also include results of any needs assessment performed.
2. Schedule of important dates such as when the supplier’s RFP response is due, when the decision is expected, when the actual purchase is expected, and when implementation is expected.
3. Contact names and sources for answering questions for the RFP.
- Read more
- 2220 reads
Eight symptom of poor planning and control during the IT project
1. Unclear direction
2. Overworked or underworked staff
3. People and equipment not available when needed
4. Examples of rework or wasted effort
5. The final tasks were rushed
- Read more
- 166 reads