Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
    data driven insights
    How Data-Driven Insights Are Addressing Gaps in Patient Communication and Equity
    8 Min Read
    pexels pavel danilyuk 8112119
    Data Analytics Is Revolutionizing Medical Credentialing
    8 Min Read
    data and seo
    Maximize SEO Success with Powerful Data Analytics Insights
    8 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Decision Management and software development I – Agile
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Business Intelligence > CRM > Decision Management and software development I – Agile
Business IntelligenceCRMData MiningPredictive Analytics

Decision Management and software development I – Agile

JamesTaylor
JamesTaylor
5 Min Read
SHARE

Last week I posted Focusing on decisions to improve the software end product and I decided that this week’s posts would be a series of follow-ups on how decision management can and should impact software development. Today on how it should impact/be a part of Agile, tomorrow on Model-Drive Engineering and Thursday on DSLs (Domain Specific Languages).

In the article I started to discuss the incongruity of developers claiming to follow the Agile tenets and yet still insisting on writing procedural code that no business user could possibly read. In particular, how can you collaborate with someone who can’t read what you are writing and how can you be responsive to change if any change requires a development cycle, even an Agile one?

If, in contrast, you applied decision management in an Agile environment you would see some real differences:

  • Business users, business analysis and programmers could collaborate around the same code (business rules) and everyone could understand what it did.

    Because business rules languages are declarative and verbose, business users and analyst…

More Read

Faceted Search Presentation at New York CTO Club
IT HANG 5: The Ride of Our Lives on the IT Wave
At an event in its Hawthorne, NY research facility, Big Blue…
Is AI Complicating Our Ability to Purchase Rare Items?
Predictive Analytics World Addresses Risk and Fraud Detection


Copyright © 2009 James Taylor. Visit the original article at Decision Management and software development I – Agile.

Last week I posted Focusing on decisions to improve the software end product and I decided that this week’s posts would be a series of follow-ups on how decision management can and should impact software development. Today on how it should impact/be a part of Agile, tomorrow on Model-Drive Engineering and Thursday on DSLs (Domain Specific Languages).

In the article I started to discuss the incongruity of developers claiming to follow the Agile tenets and yet still insisting on writing procedural code that no business user could possibly read. In particular, how can you collaborate with someone who can’t read what you are writing and how can you be responsive to change if any change requires a development cycle, even an Agile one?

If, in contrast, you applied decision management in an Agile environment you would see some real differences:

  • Business users, business analysis and programmers could collaborate around the same code (business rules) and everyone could understand what it did.

    Because business rules languages are declarative and verbose, business users and analysts can read and write them. No errors of transmission, no confusion as to what the “code” means.

  • Business users and business analysts could be empowered to make some of their own changes so that the whole system was more responsive to change.

    Business rules management systems provide all sorts of tools for exposing all or some of the rules and all or some of their structure to business users to modify. A BRMS also handles updates of these rules so there is no (or at least much less) need for the whole specify/code/test/deploy cycle.

  • The business logic would not need any documentation even for the business users as they could read the logic as written in the business rules.
  • The business rules would be the specification so that there was only a single source for the logic – the rules themselves.

    And of course a BRMS manages these rules in a repository with versioning, audit trails, impact analysis and more.

  • For many decisions the developers would simply create the shell of the decision and then let the business users and analysts create, modify and evolve the business rules for themselves.

I am sure that developers who claim they are following the Agile tenets while using traditional code mean well, but are they really Agile? Personally I doubt it. Unless the business is part of the project in a meaningful way they cannot be and with most coding languages that’s just not possible.

Decision management makes Agile software development truly Agile.


Link to original post

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

AI and data mining
What the Rise of AI Web Scrapers Means for Data Teams
Artificial Intelligence Big Data Exclusive
power supplies for ATX for data scientists
Why Data Scientists Should Care About SFX Power Supplies
Big Data Exclusive
AI for website optimization
Free Tools to Test Website Accessibility
Artificial Intelligence Exclusive
Generative AI models
Thinking Machines At Work: How Generative AI Models Are Redefining Business Intelligence
Artificial Intelligence Business Intelligence Exclusive Infographic Machine Learning

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

smart data for business cost reduction
Big Data

3 Massive Cost-Saving Benefits of Smart Data for Businesses

4 Min Read

True Value Index

1 Min Read

Data Governance: Managing Data as an Asset

5 Min Read
openAI
Artificial IntelligenceExclusive

OpenAI and Dota 2 Change the Face of Gaming Forever

5 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots
data-driven web design
5 Great Tips for Using Data Analytics for Website UX
Big Data

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?