Please enable JavaScript.
Coggle requires JavaScript to display documents.
Top 5 Mistakes in Requirements Practices and Documentation (Lack of…
Top 5 Mistakes in Requirements Practices and Documentation
Lack of collaboration and review of requirements
Lack of review
Reviewed, but missing critical stakeholders and consumers of requirements
Reviewed but as a formality, and stakeholders struggle to truly understand requirements documentation
BA is often assigned to the project after business needs and values have already been discussed
Not differentiating between capabilities, rules, project tasks, and design
requirements documents lifting project tasks, detailed technical design, and business rules without listing the context and capabilities needed
Business rules listings without the context of processes, people, data definitions, sets projects up for missed requirements
Lack of context and visuals
text is processed in a more linear fashion in our brains
why do so many requirements documents lack visuals and context that would help readers comprehend and retain the information
Too much focus on the as-is current state
never defining the gaps between the As-Is and future state
sometimes all of the context and visuals are about the current state with nothing showing the context or visuals for the future state
why we would document requirements for the future the way the system works today when 60-80% is not even used today?
Allocating requirements too early to the applications they will be implemented in
requirements are being allocated to software applications before the requirement itself has much context or elaboration
assigning the technology to a requirement before the BA is assigned or before the requirement is vetted defeats the purpose of business analysis
If the requirements process has already allocated the requirement, it takes a change request to change that