Insurance companies are critically dependent on IT resources and system assets. The tools and processes outlined in Novarica's "IT Estimation Best Practices Checklist" can improve performance over time while reducing the barriers between functional organizations that need to closely collaborate, Novarica said. There are a range of factors that contribute to the effectiveness and accuracy of any modeling effort related to things as complex as the systems, people and products that comprise the typical insurance carriers operations. By carefully considering these factors as part of a holistic system of interrelationships, IT executives can significantly improve their organizational performance, especially with respect to estimates, Novarica said. "Unfortunately, many carrier IT organizations have become painted as being poor performers in this area. In discussions with CIOs, weve found that they are similarly frustrated with the process for putting estimates together and are concerned about the impact on their own credibility," said author of the report Rob McIsaac. "Treating this as a we/they" issue will be a losing proposition for IT organizations who may find themselves marginalized if they dont take serious action to improve in this dimension. With that in mind, we developed our latest report to help CIOs and their teams focus on practical, real-world actions that they can take which position them for success." The following is a checklist of 10 items that insurance IT units should bolster before expecting precise operations.
Vector togetherness concept illustration. People symbol chain. Elements are layered separately in vector file.
Suat Gürsözlü/sgursozlu - Fotolia
1. Relationships
Foster a strong working relationship with key business partners.
taka - Fotolia
2. Transparency
There are few situations where there is truly only one absolutely correct answer. By being open to the dialogue about how estimation tools and models work, IT organizations may learn things that have been hiding in plain sight due to pervasive organizational or functional silos.
NAN - Fotolia
3. Reporting
Develop a reporting history of estimation vs. actual results performance.
Abakus mit bunten Perlen, Symbolfoto für Finanzen, Kalkulation und Rechnungswesen
Routine reporting to show results and evaluate performance over time should become the norm rather than the exception.
Kzenon - Fotolia
5. Dedicated Funding
Consider funding a project team designed solely to develop meaningful estimates for large projects.
Human resources, CRM, data mining and social media concept - officer looking for employee represented by icon. Gender discrimination in employees selection.
Jakub Jirsak/Jakub Jirsák - Fotolia
6. Communication
Formalize and review a software development lifecycle and consider clarification of highly technical terms and key events to ensure appropriate participation and ownership.
Business Man Writing Good governance diagram on touch screen
thampapon1 - Fotolia
7. Governance
Build a clear, controlled IT governance process so that business sponsors feel shared ownership for and investment in its success.
Hand turning the word Unprepared into Prepared with red marker isolated on white.
Ivelin Radkov/Ivelin Radkov - Fotolia
8. Change Management
Work, and rework, with groups as they evolve an understanding of an end-state and its inherent implications, which can be a slow, expensive but worthwhile process.
Four main steps for a software process cycle
By-line/Yabresse - Fotolia
9. Agile
Agile development practices have significant benefits for improving the overall delivery of functionality, but ongoing integration with an existing model requires care and collaboration.
idea concept with light bulbs on a orange background
peshkova - Fotolia
10. Learnings
Lessons learned from each major project are important to gather and should be a routine part of moving an effort from inception to closure and post-production support.