3 ms·
The problem is difficulty in developing the business requirement. I have to plead with Product owners to give me more than a few sentences about what it is they
by 88913527 4y ago
The problem is difficulty in developing the business requirement. I have to plead with Product owners to give me more than a few sentences about what it is they want to built. It makes no difference what the tool we use to express requirements is if we cannot have a firm grasp of the requirements themself.
- burlesona 4y agoThis is actually the strongest case in favor of "no code" tools IMO. Get the PM to spend time actually modeling what they want, as close as they can get, in no-code tools. They get to bash their head against the wall for a while until they give up and bring in engineering. But now (a) the PM actually has some intuition around how complex things are, and (b) their no-code solution is probably a better approximation of a spec than they would have written.
- pessimizer 4y agoThat's an interesting perspective. No-code tools to enable businesspeople to write good specs.
- soco 4y agoThat's just the start. Soon the business people will become overwhelmed and pass ALSO this task to the developers.
- ianmcgowan 4y agoMuch the same experience using Excel - people describe a problem in English with a lot of glossing over of details, but asking them to mock something up in a spreadsheet brings home some of the complexities.