Back in 1999, when I was getting started with Siebel 99 and things were very simple. I will be able load database, application server, tools and the client all in 1 machine and do it all by myself. Any configuration changes or customizations will only take few days to a week. The IT team size were usually small with 4 to 5 resources handling requirements to developing specifications to developing the code to deployment. For a small scope of changing fields and business rules, I was directly working with business users to gather requirements, develop design documents, develop the code, work with business users to test the functionality and deploy them to production all by myself in matter of days. At that time there were no SOX compliance , lengthy IT policies and procedures, segregation of duties, IT hierarchy to get no. of signatures, architects to satisfy and coordination between several different teams to satisfy business changes.
In the last decade IT organizations have grown, matured, and become hierarchical to deal with. "Not that there is anything wrong with that" but the business users feel the pain when they go through any scope change for field additions, business rules changes or minor enhancements. In the CRM enterprise world it is categorized as release changes. It takes months to make those changes and wait until the next release windows occurs.
With Fusion CRM that is going to change. Fusion CRM comes with application composer that can be leveraged by non IT users to make those changes and have it reflected in the system immediately rather than waiting for IT or release cycle. This will increase the user adaption since CRM system evolves over a period of time.
Runtime Vs Design time customizations
Runtime customizations are done by non IT user using Fusion CRM application composer. These customizations and extensions are surfaced to all or to a subset of Oracle Fusion Applications users, and range from changing the look and feel of a UI page, to customizing standard business objects, adding a new business object and associated pages and application functionality, changing workflows, defining security for new objects, and customizing reports.
Design time customizations and extensions include more complex changes, such as creating SOA composites or creating new batch jobs, and they require deployment into the runtime environment. Design time customizations are most often done by Java developers using Oracle Jdeveloper.
In my 10+ years of CRM experience, I will categorize 60 - 70% of changes are runtime customizations if you are adhering to out-of-box functionality. I'm not saying open up runtime customizations to all business users. But define a role/team within business who are experienced with the tool and comfortable in making the changes. This will dramatically reduce the turn around time for changes, increase user adaption and bring IT closer to business.
Check it out for yourself in this demo: http://www.youtube.com/watch?v=9RREIVNxYkM
Feel free to add your comments.