Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Yes, this is something that your software development method determines, unless it does not talk bout it; there is no <em>right</em> answer, and the <em>better</em> answer depends on your project and people.</p> <p>The task that you are describing is the functional decomposition, where you take each requirement in the business analysts' requirements specification and break it up into the functionality that implements that requirement. This is also known as <em>functional design</em>, so you are talking about a functional designer.</p> <p>You may choose to document your functional design directly in the description of the <em>New Feature</em> JIRA issues, as we sometimes do, or you may have an intermediate <em>functional requirements specification</em>. In the latter case, splitting up the functionality into developer tasks may be more straightforward (in the sense of not being a design activity) and might be done by the project manager or technical lead who assigns work to developers, or alternatively by developers who assign work to themselves.</p> <p>In every case, this task is about translating from the business analyst's perspective to the developer's perspective. How you need to do this, and in how many steps, depends on how well the writer can put it in the developer's terms, and how well the developer can understand requirements written in the analyst's terms. Fewer steps cost less time and introduce less noise, but require people with better understanding and communication skills.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload