3 ms·

> What if the software requires a lot more work before it becomes valuable? Then you haven't broken the problem into small enough pieces. You're not trying to

> What if the software requires a lot more work before it becomes valuable? Then you haven't broken the problem into small enough pieces. You're not trying to deliver a finished product, only something that can allow vested interests to gain a better picture of what is being built, enabling them to provide feedback early. If you are building ChatGPT and deliver a simple speaker amplifier that will be used to allow the humanoid robot to be able to provide sound, someone can say "That's neat, but how about a text field in a web browser instead?" If you wait years until the entire humanoid robot is working, you've wasted all that time before getting the feedback that all you really needed was a text field in a web browser. > What if the software is running in a car? A plane? A bank? A pacemaker? A power plant? What if? If you are working on developing software for a car, you don't think you won't have a car to install it on to allow the vested parties to see it? Or, at very least, some kind of car simulator that achieves the same effect?

tguvot 4y ago
>Then you haven't broken the problem into small enough pieces. You're not trying to deliver a finished product, only something that can allow vested interests to gain a better picture of what is being built, enabling them to provide feedback early. This is called roadmap. Client provide feedback to roadmap. There can be few iterations. Interests of multiple clients are taken into consideration. Based on roadmap products are build. I worked in companies that made telecom software. The kind that manages both business processes and operational aspects. There are no "smaller pieces" that can be delivered to show process. There are also no people who will care about it on side of telecoms, because they know what will be delivered. Those systems are upgraded once, maybe twice a year after very long verification processes. They influence how things are working for hundreds of millions of people. Sometimes stuff that life can depend on, like 911 calls for example. I also worked in multiple companies that made telecom network hardware and various network security appliances. It's same story. Clients know roadmap. Roadmap implemented. If this is new product, maybe a few key clients will get some alpha/beta hardware to start working on integration into their systems. Besides this, people on client side are busy with their day to day work and don't have time or interest to provide continuous feedback, because they know scope of product to be delivered.
- randomdata 4y ago
  > This is called roadmap. It's a way to execute on a roadmap, sure. The roadmap may change as development progresses.
  - tguvot 4y ago
    Sometimes roadmap has fine adjustment or shift in priorities. Yeap. Yet, everything else that I wrote remains. No incremental deliveries, interaction with end users, etc.
    - randomdata 4y ago
      There are indeed different ways to skin the cat. None better than others, just different tradeoffs – like always.

tguvot 4y ago

>Then you haven't broken the problem into small enough pieces. You're not trying to deliver a finished product, only something that can allow vested interests to gain a better picture of what is being built, enabling them to provide feedback early. This is called roadmap. Client provide feedback to roadmap. There can be few iterations. Interests of multiple clients are taken into consideration. Based on roadmap products are build. I worked in companies that made telecom software. The kind that manages both business processes and operational aspects. There are no "smaller pieces" that can be delivered to show process. There are also no people who will care about it on side of telecoms, because they know what will be delivered. Those systems are upgraded once, maybe twice a year after very long verification processes. They influence how things are working for hundreds of millions of people. Sometimes stuff that life can depend on, like 911 calls for example. I also worked in multiple companies that made telecom network hardware and various network security appliances. It's same story. Clients know roadmap. Roadmap implemented. If this is new product, maybe a few key clients will get some alpha/beta hardware to start working on integration into their systems. Besides this, people on client side are busy with their day to day work and don't have time or interest to provide continuous feedback, because they know scope of product to be delivered.

randomdata 4y ago
> This is called roadmap. It's a way to execute on a roadmap, sure. The roadmap may change as development progresses.
- tguvot 4y ago
  Sometimes roadmap has fine adjustment or shift in priorities. Yeap. Yet, everything else that I wrote remains. No incremental deliveries, interaction with end users, etc.
  - randomdata 4y ago
    There are indeed different ways to skin the cat. None better than others, just different tradeoffs – like always.