|
Offshore Outsourcing
Best Practicesoutsourcing@dataart.com
|
 |
Quality Assurance Methodology
Project leadership approach
DataArt assigns two leaders to its projects:
- Project manager. Project manager is a technical leader for the project. He is responsible for the technical success of the project, he makes sure everything gets delivered on time and with high quality
- Project coordinator. Project coordinator is responsible for all communication and documentation of the project. He is a single point of contact for all client communication issues – reporting, updates to requirements, status tracking and so on. All DataArt project coordinators are fluent English speakers. Project cordinator acts as an advocate of the client's team to the development team and visa versa. Concept of a dedicated project coordinator is unique to DataArt and has worked extremely well in many of our past project.
DataArt's project oversight committee, lead by senior management, monitors all project progress on a regular basis.
Process
DataArt's standard project development process has been mostly influenced by RUP and MSF. At present the process is heavily tailored to the requirements and limitations set forth by the customer, however in general it continues using the main points of the above-mentioned methodologies. Projects are executed iteratively; with most iterations consisting of the following phases (MSF):
- Envisioning
During the envisioning phase, the team and the customer define or refine the business requirements and the overall goals of the project. Alignment of business and IT priorities in this phase is crucial, and the team will spend time understanding how the architecture will be used. During this phase, the team also begins identifying and mitigating risks. The envisioning phase culminates in the vision-approved milestone, which indicates that the team and customer agree on the project direction.
- Planning & Designing
During the planning phase, the team plans the development and makes requirements more specific. The end of the phase is marked by the approval of the project plan by the customer.
- Developing
During the developing phase, the team moves from project planning into the projects themselves.
- Stabilizing
During the stabilizing phase, the team collects and integrates feedback on the released version, resolves project-related issues, enhances the architecture, and prepares for the next version.
We have standards in place for Configuration Management, Code Styles (all code produced follows coding styles) and Project Documentation.
Communication
The project process is completely transparent. Time spent on project is controlled through a web-based instrument (PM), and customer is capable of reviewing it at any moment. DataArt has a very strict policy on filling timesheet records, so the customer can be absolutely sure that the system shows most current information. All contacts in SDC (SDC project managers and coordinators) speak fluent English.
Time difference management
Working day is usually shifted to provide most efficient coverage with US-based customers business day:
- Project manager (technical leader) has at least 4 hours overlap with US business hours
- Coordinator (person responsible for all communications with the customer) has at least 5 hours overlap and is available 24 hours over mobile phone.
- Development team and QA team can work one after another, to take advantage of the time difference.
Requirements management
For remotely implemented projects, it is essential that requirements are assessed, analyzed, and updated accurately and effectively. DataArt has an established requirements-assessment procedure in place. As part of the standard process, the Project Coordinator and Project Manager go from top to bottom, from understanding the client's business processes to creating workflow models of the software to be built and down to creating technical requirements for software. Every step is documented and approved by client along the way.
Rational RequisitePro is used for requirements automation and tracking in many projects.
Requirements Change management
DataArt recognizes the need to accommodate requests to make functional or operational changes to the system. All requests for changes will be submitted through the project supervisor on the client side. DataArt will estimate the cost of the change, schedule and system impact of the change. This analysis is delivered to the Supervisor.
Change procedure standards
DataArt follows certain fundamental principles when making any change:
- Making any change must not affect the integrity of the system
- The system must be consistent, both in the working procedures (i.e. data entry, reporting, etc.) and user interface. Therefore, all changes must be done in alignment with existing system style
- A change must be properly documented and change development must be planned and executed
- A list of changes must be traceable
- Software code repository must permit rolling back to any previous system version
- Deploying an updated system should have minimal or no affect on the normal work cycle
Document sharing and management
All project documentation is maintained in a centralized repository accessible to a client over the web. This repository is supported by Source Safe. Typically, project repository makes use of Microsoft SharePoint team services.
Project tracking
DataArt uses a proprietary Project Tracking tool, which provides the project status in real time. It lists the project tasks with statuses, assigned developers and effort spent. Client has access to this tool over the web.
SEE ALSO:
Services: Quality Assurance (QA)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
