That means you need to put extra emphasis on finding out what users and the business executives truly want and to communicate it effectively. " User requirements, no matter what the development style, must be rigorously developed, detailed and documented," says Frank J. Fanzilli Jr., the former managing director and Global CIO of Credit Suisse First Boston, from which he retired in 2002 after 18 years of service. Rigorous change control processes need to be mutually agreed upon and adhered to, he says.
Kilcourse agrees. "The most important thing to get down is the process, and then the rules and data that the process need. As they say, 'A picture is worth a thousand words,' and there are good tools today that define or describe business processes-often in easy to understand graphic form. Having business operatives and IT'ers working on these together is crucial."
Even a great staff who understands the business functions they support very well is, at the end of the day, just IT folks with a somewhat idealized view of reality, he points out. "Any coder will tell you that it's the exception logic that complicates a program-and the same is true for business processes. So you need the operations professionals to help define what is and what will be. Then IT can start talking about the digital assets needed to get the agreed-upon process to flow."
To get others to buy into your solution, you need to understand them-and there is no substitute for getting to know your users as well as you can, adds Fanzilli. "Developers are very cognizant of the impact that user involvement has on them. Requirements definition, change control, education and the like have a significant impact upon their lives, and they know that by experience. He says, "One problem is that they may not see it as their role to help manage those processes."
Sign up for Computerworld eNewsletters.