Articles
The BA can be the PM too Conundrum
by Cheryl Hill, PMP
"I know that you’re the business analyst but why can’t you also be the project manager during the scope and requirements phase? I mean, how hard can it be to wear two hats?" Oh if I had a nickel for every time a customer asked THAT question!!!
I have seen projects where the the PM and BA roles were separate and I have seen projects where the roles of PM and BA were combined. My advice? Avoid the PM/BA combo. Let me explain why.
Full Article
Requirements Definition Phase - Are we done yet?
by Cheryl Hill, PMP
People often ask me "how do we know when we are done with the requirements phase?" My opinion? You are never completely done with requirements
but criteria do exist by which you can assess the completeness of your requirements and gauge your readiness to proceed with design.
Full Article
Three Mistakes a Business Analyst Should Avoid
by Ivy Hooks
The Business Analyst (BA) has the responsibility to elicit business requirements and to communicate them to the development team in a way that makes it clear exactly what is needed and what must be verified. For a project to be successful, the BA must avoid these common mistakes. Full Article
What is the difference between a Requirement and a Specification?
by Ivy Hooks
I have been asked this question, or some variation of it, many times. By clarifying some common terms, this article provides answers to this and a number of related questions:
- What is the difference between a Requirement and a Requirement Specification?
- What is the difference between a Requirement Specification and a Design Specification?
- What is the difference between a Requirement and an existing product's Spec Sheet?