By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData Collective
  • Analytics
    AnalyticsShow More
    predictive analytics in dropshipping
    Predictive Analytics Helps New Dropshipping Businesses Thrive
    12 Min Read
    data-driven approach in healthcare
    The Importance of Data-Driven Approaches to Improving Healthcare in Rural Areas
    6 Min Read
    analytics for tax compliance
    Analytics Changes the Calculus of Business Tax Compliance
    8 Min Read
    big data analytics in gaming
    The Role of Big Data Analytics in Gaming
    10 Min Read
    analyst,women,looking,at,kpi,data,on,computer,screen
    Promising Benefits of Predictive Analytics in Asset Management
    11 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-23 SmartData Collective. All Rights Reserved.
Reading: The true scope is unknowable, a priori
Share
Notification Show More
Latest News
ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence
ai in omnichannel marketing
AI is Driving Huge Changes in Omnichannel Marketing
Artificial Intelligence
ai for small business tax planning
Maximize Tax Deductions as a Business Owner with AI
Artificial Intelligence
ai in marketing with 3D rendering
Marketers Use AI to Take Advantage of 3D Rendering
Artificial Intelligence
How Big Data Is Transforming the Maritime Industry
How Big Data Is Transforming the Maritime Industry
Big Data
Aa
SmartData Collective
Aa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Business Intelligence > CRM > The true scope is unknowable, a priori
CRM

The true scope is unknowable, a priori

Editor SDC
Last updated: 2009/02/05 at 3:27 PM
Editor SDC
6 Min Read
SHARE

The best question asked this week: What, exactly, are you trying to prove?

Reg, nailing it as usual.

Hey, I am not blaming customers. They don’t know what they want because nobody really knows what the optimum finished software looks like before development begins. Not the Customer, not the Developers, and not even the “Architects,” “Product Managers,” “Business Analysts” or anybody else who think they are a requirements expert.

Software development is a process of discovery, for the customer, for management, and for development. As information is acquired—through inquiry, inspection, or experience gained from misadventure—our understanding of what we are trying to accomplish is refined. In that respect, every tool, be it a programming language, a development process, or a testing practice, must be judged for its contribution to the transformation of both the requirements and the software over time.

More Read

data lineage tool

7 Data Lineage Tool Tips For Preventing Human Error in Data Processing

5 Types of Business Technology Every Entrepreneur Should be Using
CRM’s Have a Big Data Technical Debt Problem: Here’s How to Fix It
What Data-Driven Marketers Must Know About Salesforce & CRM
Call Center Improvement Strategies that Work: 4 Ways to use Data And Win

Yes. And that’s why processes designed around a priori assumptions about either the nature of the so-called “software development lifecycle”, or the knowability of scope, will probably never cease to make our lives miserable and …

The best question asked this week: What, exactly, are you trying to prove?

Reg, nailing it as usual.

Hey, I am not blaming customers. They don’t know what they want because nobody really knows what the optimum finished software looks like before development begins. Not the Customer, not the Developers, and not even the “Architects,” “Product Managers,” “Business Analysts” or anybody else who think they are a requirements expert.

Software development is a process of discovery, for the customer, for management, and for development. As information is acquired—through inquiry, inspection, or experience gained from misadventure—our understanding of what we are trying to accomplish is refined. In that respect, every tool, be it a programming language, a development process, or a testing practice, must be judged for its contribution to the transformation of both the requirements and the software over time.

Yes. And that’s why processes designed around a priori assumptions about either the nature of the so-called “software development lifecycle”, or the knowability of scope, will probably never cease to make our lives miserable and fail to achieve their stated goals. The analogy to “building a bridge” (or a skyscraper, or whatever) — perhaps even the overall analogy linking the creation of software to engineering — seems flawed. The physical laws of the universe constrain a customer, requesting the design and construction of a physical object, from changing their mind about the scope very often, and they can almost never make fundamental changes (“Oh, but we want the skyscraper to have 20 more floors”) downstream. The physical laws of the universe get in the way. Software is thoughtstuff. Those same physical laws do not apply (at least not in the same way or to the same degree). Customers can, and do, change their minds on a near constant basis, including changes in the fundamental nature of the thing under construction. They get away with this because they can, and they know it. Many of the “process” ideas that have grown up to support the idea of “software engineering” can be seen, from this perspective, as attempts to constrain the design and construction of software in such a way that the situation becomes analogous to that of physical objects.

Are we supposed to be surprised that customers resist this? Whether they’ve bought into the software engineering analogy or not, they will still strive fiercely — almost instinctively — to exercise all options open to them to change their minds.

Can we make “the process of discovery” that Reg describes “rigorous”? Can we make software in such a way that we’re not simply making it up as we go along? Perhaps. But no process that fails to acknowledge the core aspects of its steps and participants can ever really be successful. Thus, it behooves us to find a way to make the malleability of software and the unknowability of scope (a priori) first class artifacts in our processes.

“Agile” has balkanized, and the individual cults have — in some cases — become religions that are just as bad as the things they intended to replace. But at the outset, the interesting thing about “agile” (the only interesting thing about it, in my opinion) was that it was an attempt to acknowledge this reality, to address it explicitly, to deal with it. That was a good idea. We should keep striving away at it.

Editor SDC February 5, 2009
Share this Article
Facebook Twitter Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence
ai in omnichannel marketing
AI is Driving Huge Changes in Omnichannel Marketing
Artificial Intelligence
ai for small business tax planning
Maximize Tax Deductions as a Business Owner with AI
Artificial Intelligence
ai in marketing with 3D rendering
Marketers Use AI to Take Advantage of 3D Rendering
Artificial Intelligence

Stay Connected

1.2k Followers Like
33.7k Followers Follow
222 Followers Pin

You Might also Like

data lineage tool
Big Data

7 Data Lineage Tool Tips For Preventing Human Error in Data Processing

6 Min Read
5 Types of Business Technology Every Entrepreneur Should be Using
CRMMarketing AutomationSocial mediaSoftware

5 Types of Business Technology Every Entrepreneur Should be Using

5 Min Read
CRM

CRM’s Have a Big Data Technical Debt Problem: Here’s How to Fix It

8 Min Read
big data marketing crm and salesofrce automation system
Big Data

What Data-Driven Marketers Must Know About Salesforce & CRM

9 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 chatbots
AI Chatbots Can Help Retailers Convert Live Broadcast Viewers into Sales!
Chatbots
ai in ecommerce
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US

© 2008-23 SmartData Collective. All Rights Reserved.

Removed from reading list

Undo
Go to mobile version
Welcome Back!

Sign in to your account

Lost your password?