|
We take our best practices and combine them with industry-accepted standards (CMM, ISO, Rational UP, etc.). This approach applies to our Project Management, Development and Quality Assurance practices.
Typical Team Configuration
Project Methodology/ Project Types
XIM Pricing Structure
- Monthly
- Hourly
- Fixed Bid
- Time and Materials
- “Shared Risk/ Shared Reward”
Project Types
Project Type |
Project Description |
Proof of Concept (POC) |
A company wants to build a prototype of a new product
or module for its client base but does not want to incur
large development costs. |
“Build-Operate-Transfer” (BOT) |
A decision is made to go offshore but the company
does not want to assume the up-front risk. A tech center
is built and operated by XIM and then handed over after
an agreed upon period of time (see: Dedicated Offshore
Technology Centers) |
Tactical |
A task oriented project where the client is looking
to fix a relatively pressing problem fast that was either
not budgeted for or simply falls out of the core competency
of the company |
Strategic |
A shared strategic product is being planned and developed
by the client and the vendor (XIM). |
Risk Management
Risk Assessment
Addressing local laws and regulations
Assessment of current political and economic conditions
Financial and accounting rules and procedures, banking, currency
Physical, network and other security
24/7 Communications availability
Local expertise and resource availability
Overall ‘Risk vs. Cost’ assessment
Risk Mitigation
Knowledge of the local market in Russia and the U.S.
Long-term presence in both countries
Track record of successful projects
Secure office premises
Trained technical and management staff
Legal and regulatory compliance review
Project Management risk assessment
Contingency Planning
Secondary (backup) resources availability
Emergency relocation plan, with a periodic review
Secondary (backup) communications channels
Periodic onshore knowledge and Intellectual Property transfer
Change and Quality Management
Change Control
Installed and followed change control procedures
Change control documentation
Sources of Change identification (business, user, tech,
PM)
Defined change control cycle
Defined change control roles
Quality Control
Defined quality process
Immediate availability of quality control artifacts:
- Documentation
- Templates
- Process definitions
Quality control defined for all team members at all levels
|
