- #ORF09 An introduction to the RETE algorithm
- #ORF09 Playing With the Rules Presentation
- #ORF09 Rule Patterns and Features Presentation
- #ORF09 Early Alert System Presentation
- #ORF09 Engineer’s perspective on Rule Technology Keynote
- #ORF09 Enterprise Architecture Presentation
- #ORF09 Enterprise Architecture Presentation Part II
- #ORF09 Model Driven Approach for BRMS Presentation
- #ORF09 Production Rule Systems
- #ORF09 Graph Based Knowledge Bases and Rules Presentation
- #ORF09 Truth versus Useful Lies Presentation
- #ORF09 Automated Verification of rules Presentation
- #ORF09 Agile Business Rule Development Presentation
- #ORF09 Rule Classification First Presentation
- #ORF09 Rule Violation and Over-Constrained Problems Presentation
- #ORF09 Generating Rules from UML presentation
- #ORF09 What’s Different about Rules in CEP Presentation
- #ORF09 Measuring your Rules’ KPI Presentation
- #ORF09 Designing a System of Rule Based Agents Presentation
- #ORF09 Extending General Purpose Engines Presentation
- #ORF09 Programming Rules using a spreadsheet interface
- #ORF09 Practical and Modern RBE Presentation
- #ORF09 Temporal Reasoning Presentation
- #ORF09 Business Rules in the Cloud Presentation
- #ORF09 October Rules Fest Think Tank
- #ORF09 October Rules Fest Think Tank – Part II
- #ORF09 CLIPS implementation of RETE Presentation
- #ORF09 Complex Event Processing Models Presentation
- #ORF09 Distributed Programming with Agents Presentation
- #ORF09 making Parallelism Available to Rule Developers Presentation
This morning, Hafedh Mili was presenting on Agile Business Rule Development. He started by putting Agile development in contrast with Business Rules development and showed that there are contradictions between the two approach.
There is a need to balance agility and discipline. There is no silver bullet to try and resolve the difficulties of software development (complexity, conformability, changeability, invisibility). There is a “home ground” for each methodology (agile methods and plan-driven methods).
Build your method up, don’t tailor it down. Focus less on methods, more on People, Values, Communication, Expectations management.
Agile Business Rule Development (ABRD) is a methodology developed by Jerome Boyer from ILOG/IBM. There is a book coming on the subject sometime in 2010 and a web site at XXXXXXXXXXXXXXXXXX . He then linked back to the Agile manifesto and showed that ABRD does fit in an Agile perspective and highlighted some ABRD principles.
ABRD Cycles
- Harvesting (Discovery and Analysis)
- Prototyping (Discovery, Analysis and Authoring)
- Building (Discovery, Analysis, Authoring and Validation)
- Integrating (Rule Deployment)
- Enhancing (Discovery, Analysis, Authoring, Validation and Enhancing)
ABRD has been implemented as an extension of OpenUp (which is part of the Eclipse process framework).
This methodology works well at the start of the project but needs to mature along 3 aspects later on: rule governance, rule structure, integration infrastructure. He spent a couple of minutes discussing the governance and what it entails. Basically all his topics are in line with the series I wrote on Business Rules Governance and Management which is process of being released… 
(See the first post here)
It is interesting to see a presentation on a methodology that I have been using for a while in a real project and for which we are going through the exact steps outlined here, and the fact that we are in the process of working on the rules governance portion just as it was highlighted in the presentation.
Tags: Business Rules, Conferences, ORF09