HMS System Pvt. Ltd

A successful development initiative is dependent to a great extent on a Project Management Plan and its plan. The plan deploys the basic tenets of management and control of structured application development, i.e., initiating, planning, executing, controlling and documenting the phases of each project. Through its unique Project Management Methodology, HMS can provide a roadmap for the successful development and deployment of each the applications we create.

Any development initiative is thoroughly analyzed to put together a project management plan that addresses every minute detail of that initiative. Our project management methodology encompasses:

Scope Management

Each project has a specific scope. The scope clearly identifies boundaries related to the development of the project. The scope management may involve a single system or multiple systems. The scope of a project will also exclude what is not within the purview of the scope analysis.

Time Management

User requirements and the actual design clearly identify the timeline(s) and deliverable(s) for any project. Each deliverable is qualified using a timeline. Managing these timelines is an essential part of time management.

Resource Management

Each deliverable has one or more resources that determine delivery. HMS Project Managers ensure that resources being allocated to a project remain available throughout its lifecycle. HMS also pre-qualifies additional resources. These will be implemented if the team size has to be escalated or a specific resource has to be replaced.

Development Infrastructure Management

Development infrastructure and communications are an absolute part of any offshore delivery. Our hybrid model and project management approach ensures that there is a strong synergy between the stakeholders, the Onsite Team or "OT" and Offshore Development Center or "ODC". The success of any offshore development initiative depends on the development infrastructure and its accessibility, as well as effective communication between all onsite and offshore team components.

Each project will have a development approach ideally suited to its execution. Iterative development where part of a process can be isolated and moved offshore is an important facet of our offshore development model. We will work in tandem with a Customers Internal Team or "CIT" to storyboard a plan. That plan provides us with the schema of the development infrastructure realistically required to support the project initiative. The development infrastructure will include any or all of these significant aspects:

	Remote access to the customer's environment through secure, high-speed connection to the customer's gateway and VPN.
	Isolation of modular systems for offshore development. These systems are independent of other subsystems. They can be programmed independently.
	Replicated or mirrored environments wherever possible. NOTE: This alternative may not be viable for highly distributed component architecture applications that involve intense information exchange with other systems.
	Remote component testing
	Performance testing.
	Onsite development, deployment, integration and testing.

Project Status Management

Project Status would be monitored during each phase of development. The activities to manage the status of each project are summarized here:

Tracking And Monitoring

The Onsite Team "OT"and Offshore Development Center "ODC" tracks and maintains records of problems and technical issues related to any stage of application development. Our project teams ensure that these issues are evaluated, remedied, and closed within appropriate timeframes.

Joint Reviews

Joint reviews will be conducted according to schedules listed in the chart of events and the project management execution plan. These reviews discuss project schedules, deadlines, constraints, risks, change requests, or introduction of any new functionality and its impact, together with any other project aspects that may warrant intervention. Such joint reviews will be scheduled at the onset of the project. HMS wants participants to be informed well in advance of any review meetings and are available during the dates specified.

Status Reports

HMS has a reporting mechanism to communicate the status of a project effectively to all participating teams viz. CIT, OT, ODC and the steering committee. The reports will include summary information on:

	Project Schedule, i.e., milestones and deliverables
	Constraints and risks
	Minutes of previous meetings
	Change in management issues
	Over-all summary of tasks completed during the reporting period.

Escalation

The escalation path clearly establishes the channel of communication. If resolution to a problem is required on a priority basis, the CIT can escalate the issue, starting with the project manager and ranging to the level of engagement manager.

Configuration Management

Each project requires an environment that supports its development. A matrix will be prepared to finalize the elements both in terms of hardware; software and licensing that are required to develop the applications for the customer. Our team regularly documents a detailed configuration management plan that details:

Hardware and software infrastructure available to a team before execution.

A schema for the software components under development.

A list of deliverables-also designated teams for each set(s) of deliverable(s) and a timeline for delivery.

A summary of the guidelines necessary to secure the software being developed against potential damage or loss.

Any software licensing requirements that require intervention of the stakeholder or any additional expenditure by HMS

Quality Management

Quality control is an important part of our development philosophy. Our Quality management plan defines the quality control mechanisms that protect our development processes. Our Quality Management methodology provides guidelines that assure the quality of procedures, work instructions, standards, testing, review and development. These guidelines will also ensure compliance as per ISO 9001/CMM 5 guidelines. Our Quality Management methodology covers those personnel involved in the administration, development, implementation, and execution of the product or application we are developing.

Change Management

After the scope of work is finalized, any additions and/or changes will be requested in writing. HMS will evaluate and communicate the effect that each change will have on the project schedule and provide an effort estimate and cost to our customer. HMS will incorporate the changes into the design document, but only after authorization by the customer. Change Management issues will also be reviewed routinely between OT and CIT.

Top