Project Management

Effective Customer Communication

A dedicated project manager is assigned to each project, who acts as a liaison between the customer and us. He is responsible for work planning, management, and tracking of progress. We normally expect that a contact person, e.g. a Project Coordinator will be assigned from the customer side that will communicate and resolve all issues through our project manager. These two individuals will be the core channels of communication between the two sides. Communication is carried out regularly, using any and all possible means of communication, including email, IM, phone, videoconferencing and personal meetings.

Planning and Reporting

A detailed plan is created at the beginning of each phase and is updated by Project Manager weekly or more frequently if necessary. This allows transparent tracking of the project status and provides a clear vision of the project costs at every stage.

Requirements Management

From experience we know that creation of a visual prototype of the future solution (GUI, look and feel, real controls and navigation) at the requirements gathering stage is an effective practice. Its purpose is to let the customer “feel” the future solution and probably adjust the requirements at the very beginning.The customer will be better informed and our team will have a guideline to work upon.

Change Management

All requests are sent to the change requests pool accessible to both the customer and EqualPartners managers. The pool serves as a base for planning of the future iterations’ scopes. This approach allows the customer to easily control the timeline and budget of the project. The following procedure is applied that enables us to integrate any changes without affecting the overall schedule.

  •  
    • Execute as per plan.

    • Track the status / Progress of the project using the appropriate tools.

    • Follow the established communication for reporting / escalation of issues.

    • Forecast based on the progress over the period. Plan necessary action in terms of additional resources, logistics, infrastructure etc. based on the forecast in order to achieve schedule adherence

    • Conduct compliance checks at various location

    • Collect appropriate metrics to measure the health of the project. (Defect metrics, Design metrics etc.)

    • Periodic senior management reviews and quality audits

Risk Management

To make offshore engagements as low-risk as possible multiple factors should be taken into account. Inexperienced offshore vendors tend to ignore them which leads to failures of software development projects. Our experience of efficient risk management and an advanced risk mitigation policy ensure safe, predictable relationships and allow avoiding the pitfalls and delivering the project on time and on budget.

Competence Transfer

Competence transfer involves both documentation and knowledge transfer, including specifications, design, test, release, guideline documents and user manuals and end-user or administrator trainings. The core activities undertaken are as follows:

  •  
    • Decommission links; Revoke security access rights on both networks; Return loaned software licenses; Return loaned hardware

    • Ramp-down resources

    • Perform reverse knowledge transfer to identified resources (If applicable)

    • Prepare closure report; Discuss and get sign-off from all the stakeholders

    • Prepare engagement post-mortem report

    • Document learning from the engagement and leverage them in the subsequent engagements with Customer