Managing after a failure

[buddye]

I have some two very bitter and disappointing experiences with software system failure. When I worked on FAA's Reroute Air traffic Control System, the FAA told us to take our system out of the Chicago Air Traffic Control center and to start over planning and writing requirements.

Also when BOBII was released in 2005, BOBII was considered a failure at least by me and many other players.

I now consider both the FAA and BOBII a success because new management software procedures and stronger testing (unit , subsystem, and system), and smaller incremental development.

To correct a system failure, requires a new management approach who will focus on a strong software development process, enforced priorities, and a stronger testing approach. The development plan must also take smaller incremental steps that can be tested, released for testing to a strong volunteer beta test group.

Without a change in management approach and focus there is a good chance that history will repeat itself on the new BOM System.

I do wish 1C the very best of luck on both the quality and profit of BOM.