How to get better understanding of the users as a programmer
I work at a company that wants to be agile, but the business analysts often provide us “user stories” that are more solution than problem statement. This makes it difficult to make good design decisions, or in more extreme cases, leaves few design decisions to be made. It does not help the programmers understand the user’s needs or make better design decisions in the future. Our product owner makes an effort to provide us with problem statements, but we still sometimes get solution statements, and that tends toward a “code monkey” situation.
When to stop functional decomposition and commence algorithm design
In all my experience decomposing functional requirements from the top down through a hierarchy and successfully using that hierarchy as the basis for building and implementing some pretty cool systems from the bottom up, it shames me to admit that I do not have a guaranteed method for ensuring that all the levels in the functional decomposition hierarchy are at that perfect place to decompose no further.
When to stop functional decomposition and commence algorithm design
In all my experience decomposing functional requirements from the top down through a hierarchy and successfully using that hierarchy as the basis for building and implementing some pretty cool systems from the bottom up, it shames me to admit that I do not have a guaranteed method for ensuring that all the levels in the functional decomposition hierarchy are at that perfect place to decompose no further.
When to stop functional decomposition and commence algorithm design
In all my experience decomposing functional requirements from the top down through a hierarchy and successfully using that hierarchy as the basis for building and implementing some pretty cool systems from the bottom up, it shames me to admit that I do not have a guaranteed method for ensuring that all the levels in the functional decomposition hierarchy are at that perfect place to decompose no further.
When to stop functional decomposition and commence algorithm design
In all my experience decomposing functional requirements from the top down through a hierarchy and successfully using that hierarchy as the basis for building and implementing some pretty cool systems from the bottom up, it shames me to admit that I do not have a guaranteed method for ensuring that all the levels in the functional decomposition hierarchy are at that perfect place to decompose no further.
When to stop functional decomposition and commence algorithm design
In all my experience decomposing functional requirements from the top down through a hierarchy and successfully using that hierarchy as the basis for building and implementing some pretty cool systems from the bottom up, it shames me to admit that I do not have a guaranteed method for ensuring that all the levels in the functional decomposition hierarchy are at that perfect place to decompose no further.
Functional Requirements, Non-behavioral specifications, Acceptance Criteria and the gap
I am struggling in my brain about what the right answer is here and where the gap in our requirements gathering process is on this team.
Who should write the Technical Design Document? The BA or the Developer? [closed]
Closed 9 years ago.
Who should write the Technical Design Document? The BA or the Developer? [closed]
Closed 9 years ago.
Who should write the Technical Design Document? The BA or the Developer? [closed]
Closed 9 years ago.