Page 158 -

134 Chapter 4 • Development Life Cycle

Project
Role/Title Reporting Team Members
• Identify and plan activities needed to complete task assignments.
• Work with functional analysts to understand business needs related to reporting.
• Translate business requests for information into technical report specifications. Develop
new reports according to technical specifications using identified reporting tools.
• Develop unit tests scripts (i.e., test data, test scenarios, expected results).
• Follows all development and documentation standards and best practices as defined.
• Identify and escalate technical issues to the technical infrastructure team.
• Modify existing or build new summarized reporting tables as needed.
• Modify existing or build new reporting table data refresh programs.
• Provide status updates to reporting lead.
Skills • Thorough knowledge of systems functionality and navigation.
• Solid understanding of technical processes and relevant business processes.
• Team leadership skills. Ability to work effectively across business organization.
• Issue resolution skills. Ability to obtain resolution by team consensus when
differences in business processes are discussed.
• Excellent communication skills.
• Experience in all phases of the project life cycle: design, prototype, construction,
and deployment.
• Solid development experience.
• Relational database experience.
• Experience with reporting tools.
• Solid understanding of the business organization and infrastructure.
• ERP implementation experience preferred.
Reports To Reporting lead

Project
Role/Title System Test Team Members
Role Definition System test team members are responsible for completing the tasks related to
system test effort.
Responsibilities • Review, test, and understand delivered ERP capabilities.
• Define test conditions based on functional requirements that the testing should
satisfy and group them logically into test cycles, subcycles, or cycles and subcycles.
• Prepare test scripts based on the test conditions, cycles, subcycles, or cycles and
subcycles.
• Create test data and expected results.
• Execute the test cycles or subcycles, or both.
• Check the actual results against the expected results.
• Log any unexpected results in the system investigation request (SIR) database.
Analyze these unexpected results (SIRs).