Project Management (v)-risk Test form

The article Project Risk monitoring Table is a supplement to the risk management of the previous article that can be used to identify risks and can be focused to identify known and predictable risks in the following common subtypes:

1. Development environment

The Software engineering environment supports project teams, processes, and products, but if the environment is flawed, it can become an important source of risk.

The barcodes in the following risk checklist identify the risks associated with the development environment:

(1), whether there are software project management tools available;
(2), whether there are software process management tools available;
(3), whether there are analysis and design tools available;

(4), whether there is a test tool available;
(5), whether there is a software configuration management tools available;
(6) Whether the members of the project team have received training in each of the tools used;
(7), whether there is a special development tool management
If the answers to the above questions are mostly negative, then the software development environment is weak and highly risky.

2. Organizational risk

(1) Whether there is sufficient support for the project (Manpower support, management, QA, testing or other external personnel)
(2), whether the project is the largest project of the enterprise
(3), whether the project management has a clear definition of the process

3. Risk of personnel

(1) Whether sufficient personnel can be obtained
(2) whether they have sufficient skills and experience
(3), whether or not they worked together, whether the configuration between them is reasonable
(4) Whether they believe the project will be successful
(5) Whether there is a professional understanding of the experts
(6), whether there are special personnel to contact customers
(7), whether there is the best personnel available;
(8), whether the personnel in the technical support;
(9) Whether there is sufficient personnel to be available;
(10), whether the developer can participate in the whole project work from beginning to finish;
(11), whether some personnel in the project can only work part time;
(12), the developer of their own work has the right expectations;
(13), whether the developer has received the necessary training;
(14), whether the flow of developers can still guarantee the continuity of work;

4, the duration of the risk

(1), whether the timetable specified is realistic
(2), whether the function can be scale management in order to meet the timetable
(3) How strict is the requirement for delivery date

5. Risk of project size

Project risk is directly proportional to the size of the product. The entries in the following risk checklist identify common risks associated with product (software) Size:

(1), whether the success of the project can be evaluated
(2), whether there is agreement on how to evaluate the success of the project
(3), whether the demand is fairly stable and has been fully understood
(4), the scope of the project is unlimited or continuous expansion
(5), the project development time range is too short, not flexible?
(6), whether the size of the product is estimated by LOC or FP;
(7), the degree of trust in estimating the size of the product;
(8), the number of users of the product;

6. Technical risks

(1), is this technology new for your company?
(2), whether the technology is outdated
(3), whether the reuse of technology is reasonable
(4) Whether the current technical framework available is reasonable
(5), whether there are particularly harsh technical requirements
(6) Whether or not to rely on untested new technologies, services or unproven hardware, software
(7) Whether the technology used has a special dependency
(8), whether the demand for products requires the use of a specific user interface;
(9), whether there is excessive performance constraints on the product in the demand;
(10), the customer can determine the required function is feasible?

7. Risk of external dependencies

(1), whether the project depends on other development platform
(2), whether the project depends on external products or external development of the construction
(3), is success dependent on successful integration with development tools and implementation technologies? Is there an alternative plan to deliver the project without these technologies?

There are other things like software process management technology, customer risk, business risk, money management, and so on, we only discuss the development aspect for the time being.

Project Management (v)-risk test form