On April 6th, CAST held a user group meeting on the topic of function point analysis and software productivity measurement. The meeting gathered more than 20 software measurement professionals from major companies in the banking, IT consulting, telecom, aviation and public sectors for a two-hour working session to discuss the benefits of function point analysis testing.
The event featured presentations including:
An IBM case study on how they worked with CAST to integrate and secure an Automated Function Point (AFP) approach with a big player in the aeronautic sector within TMA Systems
Functional sizing case study
Updates on the new CISQ standards for Automated Function Points
The importance of internal and external benchmarking
Last month in this space I wrote about the importance of optimizing the cost-effectiveness of Captives (i.e., Global In-House Centers) by setting metrics and enhancing process transparency for better management of them. For these management methods to work, though, an organization needs to employ automated function points as a way to way to gain insight about current costs and supplied value, which can then be used to enhance received output from current or future providers.
For Jay Ferro, CIO of the American Cancer Society, his employer’s mission hits far closer to home than those of most others in his position. The father of three boys, Ferro lost his 36-year-old wife, Priscilla, to cervical cancer in January 2007. In her memory, he founded Priscilla’s Promise, a non-profit organization that brings greater awareness to cervical cancer.
Inspired by his personal experience with the disease, Ferro joined ACS as CIO in 2012 with the mission of applying his abilities as a savvy technology leader who understands how to apply IT solutions to achieve business goals. He was driven to ensure that in addition to supporting the organization’s infrastructure, IT also furthered its causes.
During last week’s webinar on IT Transformation featuring Marc Cecere, vice president and principal analyst for Forrester Research, many questions presented by participants went unanswered due to time constraints. Because these questions are likely being asked by many in the IT arena, we asked Marc’s webinar co-host, Pete Pizzutillo of CAST to provide answers to the three most frequently asked questions.
In today’s software-driven business world, IT transformation has become an enormous component of business transformation and software risk management. This is one of the key messages delivered by Marc Cecere, Vice President and Principal Analyst for Forrester Research, during a webinar held recently on Business Transformation, which was sponsored by CAST, Inc.
Cecere explained that business transformation involves fundamental changes to major business processes, structure, models and culture, noting that most transformations require changes to structure and the roles of personnel, as well as collaboration between divisions or departments in the business. However, the biggest changes in these transformations come in the form of major system integration and technology changes.
Last week, CAST celebrated the third edition of its CIO Conference in Spain examining the tandem between IT risk management and productivity improvement. CAST has captured the greatest moments and posted the pictures from the conference here!
The objective of the conference was to analyze the importance of measuring quality improvement programs and productivity. It has become apparent that the quality of software is crucial to the success of IT organizations and the lack of it has a great impact in the customer experience in the TTM and IT efficiency.
Finding the right tools for the right challenge
The growing cost of most software development efforts can be traced back to one underlying cause – the lack of visibility into the software. As the size and system complexity grows for business critical applications — along with the complexity of sourcing environments — there is an increasing need for app owners, architects, and developers to truly understand their codebases. Without visibility into the implementation, it is hard for a developer to understand all the nuances of the code. This explains the disproportional amount of time that is needed for developers to identify the root cause of defects.