Separation of what is how - design in a flexible environment

Question

In a flexible environment (scrum), how do you get product management to create small enough elements or stories without design, which is not their specialty? In other words, how do you separate what (business requirements) from how (design) in agile development?

Answer 1

With scrum, product management should be one person: the owner of the product.

What you want to do is done during sprint planning , where the whole team should be present (product owner, architect, developers).

, . , - .

. StackOverflow,

, . , , , () .

, , , . , . , .

Answer 2

, , Scrum Projects, , . , , /itens/business needs/features - , , , .

, , .

PO , - , INVEST. I , N , V, , E, S mall T.

, , -:

" - - - - -."

: " stackoverflow, , ".

PO- Sprint Backlog, , , .

:

" "

" "

, stackoverflow . , , .

Answer 3

, ( , ,..), , ​​ (.. 2 21), 13 8 .

Answer 4

() ( ) , . , ( ), , / , .

As a result of this, the final discussion will help you work with the Product Owner to separate their requirements into meaningful and appropriate detail.