Controlling the time and cost schedules of major projects continues to be a significant problem in the Engineering field for project managers and directors today. The biggest challenges are categorizing and evaluating the critical points of failure. With C-BRAT™, you can assume control of certain risks, saving significant funds and allowing you to allocate funds when there needed, where there needed. C-BRAT™ is designed to accommodate non-technical management, is easy to use and is platform
dependent.
There are 13 risk elements that C-BRAT™ uses to evaluate and assess project risk.
- Mission and Goals - Project fit in relation to customer's organization, perception and work flow
- Program Management - Identifies goals, conflict, resource conflict, leadership, program definition
- Decision Drivers - Political influences, the use of attractive technology, and short term solutions
- Organization Management - Organizational stability, organizational roles and responsibilities, policies and stands, project objectives.
- Customers / Users - User involvement, user experience, user acceptance, user justification.
- Project Characteristics - Project size, budget constraints, delivery commitment, development schedule.
- Product Content - Requirement stability, design difficulty, system dependencies.
- Deployment - Response or other performance factors, customer service impact, data migration required.
- Development Process - Alternative analysis, quality assurance approach, use of defined development process, early identification of defects, change control for work products.
- Development Environment - Physical facilities, vendor support, contract fit, disaster recovery.
- Team Members - Mix of team skills, team communication expertise with application area, experience with project process, team productivity.
- Technology - Technology match to project, technology experience of project team, availability of technology expertise.
- Maintenance and Support - Design complexity, vendor support and personnel.
|