3 Reasons Rules Architects Are Adopting Decision Modeling: #3 Using Agile Not Waterfall to Write the Rules
Earlier this month I started a series on decision modeling for Rules Architects by describing how a decision model in DecisionsFirst Modeler engages the business and extends traceability and impact analysis. Wrapping up this week I’m going to talk about the importance of agile development and how traditional rules approaches force a waterfall approach.