Michael Hugos over at CIO magazine had an interesting post today - The System Builder Drives IT Agility. He makes five suggestions on which I thought I would follow-up:
- Understanding business operation - shared understanding presumably despite the different perspectives of business and IT
- Inclusive process - one like concurrent business engineering, for instance
- Tolerate not knowing - both because you need to investigate the issues and because those issues change
- Simple underlying pattens - rule templates, for instance, to empower business users to maintain their own rules
- Simple combinations - for instance, when decisioning is called for use decision services to keep everything clean and packaged
He also referenced this one - The 30-Day Blitz, IT Agility in Action - and I think business rules and decision services are often a very effective way to add value to existing systems quickly and without completely re-writing the systems concerned. Check out this legacy modernization story, for instance, or posts in the legacy modernization category.
Technorati Tags: agility, business rules, change time, CIO, CIO Magazine, decision automation, decision service, Michael Hugos, business agility
Subscribe to this blog by RSS
Leave a comment