In association with the
Quick Links: Articles MA Blog Community Blog Templates Books BA Humor Events Jobs Interview Questions RSS Feeds
Community Blog Modern Analyst Blog
Written by: adrian 6/23/2007 10:31 PM
2 comment(s) so far...
Re: More on how to deal with bad requirements Requirements never be Bad,If the BA documented well, yes the worst scenario is some one writes Functional Doc and new BA has to study that Doc and interpret it to Technical Team.
Re: More on how to deal with bad requirements
Requirements never be Bad,If the BA documented well, yes the worst scenario is some one writes Functional Doc and new BA has to study that Doc and interpret it to Technical Team.
Re: More on how to deal with bad requirements Bad requirements are a potential problem in any model of development. Bad requirement, i mean.. which are not documented well from the perspective of connectivity in the modules, effects of the developed requirements. I feel these are the two reasons which will lead to wrong interpretations by the technical teams in the projects.The solution could be a good template for requirements documents which should address these issues.
Bad requirements are a potential problem in any model of development. Bad requirement, i mean.. which are not documented well from the perspective of connectivity in the modules, effects of the developed requirements. I feel these are the two reasons which will lead to wrong interpretations by the technical teams in the projects.The solution could be a good template for requirements documents which should address these issues.
Advertising Opportunities | Contact Us