Review the Business Case, Risk Analysis, Impact Score
Software Development Life Cycle
Have a Discovery session with the BU to uncover details of their request.
Identify requirements in KeyStone tables, scripting, interfaces, etc., in order to build specification docs. QA involved. BU signs off.
ESTABLISH TEST PLAN
CREATE TEST CASES
BUSINESS UNIT TEST
Meeting with who exactly? BA, QAA, Programmer?
Assigned programmer reviews the specs delivered by a BA.
Time, hours, days programming, other requirements. Put in Sprint cycle.
Assigned programmer builds the script, report, etc. Other?
QAAs review the requirements to verify that they're unambiguous, clear and testable.
QAAs create the test cases needed which will cover each of the requirements.
Click or hover on commentary cell below for QA detail.