my name is christopher cudoll. i rise to comment on the peril of system development. first the rule of thumb for system development, projects take 3 times the estimated development time. projects cost 3 times more money than the original estimate. projects only certify 1/3 of the requirement jz 1/3 are stated. why? there is the rule of dumb. systems are comicated but orezs are not. organizations are 1/3 as intellgents of the people involved. 1/3 on a very very good day. members once having some measure of system expertise i offered to this board february 2, 2010 a comment suggesting my city and county of san francisco create a data dictionary basely list persons roles and resources pertinent to had operations mptd if you set that up all the controller would have had to do to set opnew finance system is pull out the dictionary, compare with a known set of future needs prioritize the absolutely necessary, make a list and work to it. don't change requirements. if you forgot something there is always a inevtable phase 2. finally there is the rule of numb. people are numb