Ok, so a lot of folks nowadays will type their meeting notes directly into their laptops, and that’s not a bad thing. It certainly saves time. However, there are situations where the old pen and paper is not a bad […]
Numerous professional studies have shown that poorly understood software requirements are the number one cause of schedule and budget overruns and ultimately project failure. Studies have also shown that the earlier in the SDLC that scope is understood, and defects […]
So, what exactly is a Business Analyst? What is the role of the Analyst in the software development lifecycle? If you don’t want to be completely confused, don’t bother trying to get a conclusive definition by just “Googling” it. There are dozens of variations on the BA role depending on the company, and on the software engineering methodology used.
“Functional specifications documents lead to an illusion of agreement. A bunch of people agreeing on paragraphs of text is not real agreement. Everyone is reading the same thing, but they’re often thinking something different.”
One of the main challenges in drafting requirements is to state “what” the solution must entail, and not “how” the solution must be tailored. I found the excerpt below from a paper authored by Ivy Hooks very helpful.