cio

Apple to CIOs: Don't buy Macs

I'm not sure why Apple has suddenly decided to make the future support of Mac Java uncertain (see "Mac Java deprecated; Did Apple just kill Mac Java?", and "Mac Java is deprecated: What it means"), but if I'm a CIO or CTO working at a company that has invested any money at all in Java development, Apple just sent a very clear message:

Don't buy any more Mac computers in the enterprise.

Early software cost estimating using FPA (Part 2)

 

Using FPA, I quickly worked through several of our largest projects to determine our productivity rates, and also noted who worked on the projects, what technologies were used, along with a few other details. In short, in a few days I was able to create a database of our historical software development speed.

Early software cost estimating using FPA

A lot of times when a project is in its earlier stages (the conceptualization phase), the people that control the money at an organization (the CEO, CFO, CIO, Business Manager, etc.) want the best estimate they can get regarding the time and cost of a software development project. Again this may be very early in the project lifecycle, some time just after someone said, "That sounds like a good idea" and well before the project begins. In short, they want the best "back of the envelope" ("ballpark") cost estimate you can give them.

Syndicate content