About Us

Shortcuts


Please Select Industry
Please Select Service

Contact Us

Request Proposal

Project Management

Our Project Management is one of our key success factors. US-India – Project coordination on both sides, but still get hands dirty. Close project liaison through US-experienced offshore project professional Daily, Weekly, and Monthly Status reports Weekly conference calls, daily SCRUM On-site visits by India project managers to ensure project is well understood (as required) Importance of key India resources to have US exposure

Delivey Model - SOMA + RUP + SCRUM

  • Resource Allocation - technical leads identify appropriate resources / teams and map processes between solution architects, engineers, developer resources, etc and role responsibilities.
  • Inception Phase (technical) - requirements definition will break business down to detailed component view model. Detailed identification and prioritization of services to support / expose business process. The the lead will define software development plan and development templates / guidelines and charter (vision) document will include scope, business justification, budgets, ROI, risks
  • prototyping!

Methodology

Methodology

Elaboration Phase (technical)

  • outline cases, functional designs, prototypes
  • component processes get choreographed
  • map business goals to processes using component business model method
  • choreography, business process, data, and integration models documented / prototyped
  • abstraction / object model implemented within the technology stack
  • features and services cataloged in service repositories (WSRR, SDO repositories, etc)
  • incremental daily meetings at 2 hour intervals
  • 24 hour project development lifecycle begins includes offshore functional / technical leads with handoffs every 12 hours between teams

Methodology

Construction Phase (technical)

  • development build continues
  • instant messaging / skype conferencing
  • (international) project whiteboards
  • tasks / project tracking systems
  • integrated source repository (SVN)
  • features and services cataloged in service repositories (WSRR, SDO repositories, etc)
  • alpha / beta systems
  • deployment / integration build plans
  • (off hours) offshore support ramped up end user documentation, configuration manuals (examples available upon request)

Transition Phase (technical)

  • beta testing / parallel testing
  • conversion of data / feeds
  • services / components refresh
  • final service bus (esb) regression test
  • release notes / migration planning
  • release defects at minimum 95%
  • next release planning
  • (customer) customer service support training
  • post production planning / next phase
  • release management / product lifecycle

Communications

Feedback Loops – Customer Collaboration / Customer Access

  • incremental daily status reports (DSR) documenting SCRUM meetings.
  • SCRUM minutes used to develop weekly status reports.
  • quarterly project review / client satisfaction surveys
  • steering committee meeting once per month
  • steering committee reviews satisfaction / progress metrics
  • support disaster recovery plans
  • all collaboration documentation made available (and searchable) online
  • all tasks, issues, support trouble tickets available online.
  • 24x7 customer access to staging sites.
  • VPN / IPSEC tunneling services included

Quality Assurance

  • Test Plan and Test Cases - We develop a complete testing plan based on the requirements. The test plan includes unit testing, integration testing, user acceptance testing and post go-live review. The test plan includes all the test cases that typically cover functionality, error handling, performance, scalability, and fail over, among other required tests. The test plan and test cases are validated with the client during the early stages of a project, and are refined and enhanced during the downstream activities (detailed design and coding).
  • Traceability Matrix - During the software lifecycle we trace the requirements to the design components, to the code modules, and to the test cases. This enables us to track changes to the requirements and to validate the test plan covers all requirements and all design elements.
  • Peer reviews of designs and code - Depending on the size and duration of a project, we conduct design and code reviews with architects and engineers from outside the project. These reviews provide an opportunity for valuable feedback and independent perspective.
  • Acceptance Plan - At the beginning of each iteration of a project, we develop a detailed acceptance plan that describes all the expected deliverables during or at the end of the iteration. The client signs off on the acceptance plan to indicate agreement on the expected results.

The quality engineers staffed on a project are responsible for implementing, tracking and adjusting the quality assurance plan to make sure that it is completed successfully by the delivery date. They often use test automation tools to help them in conducting the required testing and establishing a complete regression test suite for the product that is as automated as possible.