Job description
Job Purpose: Responsible for the planning, execution, and delivery of a software development or systems integration project.
Responsible for directing and supervising project development, in accordance with the requirements of the client.
In charge of managing and tracking scope, schedule, costs, and quality on a day to day basis for large-sized projects.
A Senior Project Leader should be able to identify issues, detect unstated assumptions, resolve interpersonal conflicts, as well as use systematic management skills.
This position usually requires 10 – 13 years of relevant experience.
• Requirements understanding : Understand and verify the functional Requirements of the software.
o Understand the non-functional Requirements of the software.
o Agree with systems analyst on the different methodologies of requirements gathering and analysis.
o Determine the existence of any conflicts within the Requirements of the software.
o Ensure the commitment of the development team to the requirements.
o Refer to the Requirements’ Owner in case any changes are needed in the requirements due to technical issues to ensure that the change has no negative impacts on the customer from the business perspective.
o Perform risk assessment on the requirements.
o Agree with systems analyst on requirements priorities and dependencies.
o Could validate the requirements to ensure stakeholders need and expectation, ex.
prototypes could be used.
o Ensure proper understanding and review of requirements document by stakeholders.
o Ensure proper understanding of Change requests by stakeholders and communicates with client when needed.
o Is responsible for defining and controlling the scope of the project.
• Software Construction o Own the project deliverables, i.
e. Requirements specs, design document, schedule, code, etc.
o Review unit test cases and makes sure the developers’ understanding of the requirements is correct.
o Ensure that the product integration procedure follows the established project schedule, and acceptance criteria that is defined in the testing plan • Software Design o Review design and design document to ensure its compliance with the client requirements and internal systems.
o Review make-buy-reuse analysis (DAR).
o Conduct meeting with graphics team to arrange for the requested Graphic Design job and verifies output with requirements.
• Customer o Has a direct impact on customer retention through on time high quality project delivery.
o Manage the relationship between project cost and deliverables to maximize delivered customer value.
o Add customer value through understanding customer business domain and nature.
• Change Management o Implement re-estimates if the projects’ requirements are changed due to incompletion, ambiguity, etc.
o Receive a change request from the client, documents the issues and ensures clear understanding with the client of the Change Request (CR) through meetings, emails, etc.
o Meet with Change Control Board (CCB) defined in the Project Plan document to evaluate the Change Request issue(s), to determine the feasibility and impact on the project.
o Perform sizing for Change Request according to its requirements.
o Identify risks that would affect the external commitments with the o Identify risks that would affect the external commitments with the client.
o Send the CR Effort Estimate to the SDM and EM to review, then to the client for approval before proceeding with implementation.
• Project Management o Identify Project Team Structure and Allocate Needed Resources.
o Review project plans, activities, and work products (project plans, prototype, test cases, QE measurement reports, project code, user manual and guide etc) for their consistency with requirements of the project.
o Update project plans and work products resulting from changes or additions to the requirements’ baseline.
o Track the progress of the project through updating project plans and schedule regularly.
o Make use of DAR process for resolving issues faced in the project.
o Track the status of testing activities, through the reports submitted by QE and through meetings between them.
to Update task status on Changepoint.
o Hold Closure meeting with all team members and stakeholders to discuss and analyze what went right or wrong, and to produce final views, reports and lessons learnt.
o Update CV at project closure.
o Ensure that team members updated their skills and CV with the project Ensure that team members updated their skills and CV with the skills learnt in the project.
• Configuration Management: Select the suitable development, testing and deployment environments for the project.
o Verify that the building environment is ready.
o Review project baselines.
o Review packages/documents to be delivered.
• Communication Management o Identify the communication plan to cover both internal & external communications.
o Schedule regular meetings/e-mails to communicate the project status to the project team, and plan for upcoming project tasks defined in schedule.
o Communicate with different parties (i.
e. graphic designer, technical writing) to complete project.
o Report status of the project and the work products to client, Engagement manager and Service Delivery Manager regularly.
o Communicate with the SDM through meetings or emails to review the external commitments.
o Communicate with the EM the external delivery milestone schedule to be reviewed and approved.
o Communicate with EM or SDM any change requests’ impact on cost, estimate, and schedule.
• Risk Management o Identify, develop, and analyse project risks and create plans for integrating them.
o Continuously follow-up on risk management plan to ensure it is up to date.
o Perform risk assessment on the requirements.
o Regularly add project risks during project execution.
o Manage risk of estimate overruns due to change requests.
• Schedule Management o Determine the work involved in the project, and organizes it into phases, milestones, and tasks.
o Establish the project structure; work breakdown structure, then defines task priorities and dependencies.
o Ensure that the critical path in the project schedule is identified to highlight risks.
o Monitor and update weekly project schedule and scheduled tasks.
o Abide by project schedule.
o Responsible for updating the project schedule whenever there are new commitments or changes to existing commitments.
• Measurements Management o Identify metrics that will be used to monitor project objectives and sub-processes performance.
o Analyse and track bug count, closure rate, and rejection rate.
o Measure project cost/effort weekly (actual vs.
estimate). o Measure project Time weekly (actual vs.
estimate). o Check the defect density metric from QPM tool to analyse the data and meet with team members to identify the problem root cause and define the appropriate action items.
o Identify triggers and actions needed to be taken on identifying problems based on measurements.
• Quality Management o Plan for periodical functional audits to assure work product consistency with requirements and changes.
o Plan for peer reviews and review activities according to project milestones defined in the project schedule.
o Responsible for reviewing and assigning bugs to different team members and checks the root cause for different types of defects.
o Responsible for following up on bug closure.
• Team Management o Request adequate human resources & hardware/other resources to achieve project completion.
o Ensure team motivation to achieve required project deadlines, and complete deliverables.
o Conducting performance evaluations for the team members of the project.
This job post has been translated by AI and may contain minor differences or errors.
