1) Know the core differences between waterfall and AGILE methodologies and why you might choose one over the other.
2) Know what a scrum is and what should be covered during every Scrum Meeting.
3) Be able to explain the difference between projects and products in terms of internal and external clients and how consulting organizations differ from traditional software companies.
4) Be able to define what go-to-market pressure is and describe its relationship with technical debt.
5) Be able to describe each of the workflows:
6) Be able to describe the differences between functional and non-functional requirements.
7) Be able to discuss the adverse side effects of over/under testing.
8) Be able to discuss code metrics like cyclomatic complexity and LOC and how they can help with testing efforts.
9) Be able to suggest questions that can help gather additional information about a vague requirement.
10) Be able to suggest an appropriate architectural design based on a problem statement.