Case studies

Finance & Banking · Japan

Long-term ODC with Pronexus

Starting from a 34 MM pilot (2015), NTQ built a long-term ODC for Pronexus – a Japanese disclosure & IR services company – growing to more than 100 people and moving from system maintenance to upstream (上流) work on product renewal.

Project overview

  • Client: Pronexus (PNX) – a provider of total solutions for information disclosure (Disclosure) & IR
  • Country: Japan
  • Domain: Finance – preparing financial documents for corporate groups and listed companies; providing financial data
  • Scale:
    • 20152016 – Pilot (project-based) & ODC set-up: 34 MM, team of 56
    • 20172021 – ODC Maintain products: 20 MM, team of 1015 → 20 people (04/2017)
    • 2022~present – ODC Maintain & Renew products: 100 MM, team of 34 (04/2022) → ~100 people; 112 NTQ members (06/2023)
  • Project type: Long-term ODC (Offshore Development Center)
  • Scope of work: Maintaining and adding features to the systems; developing supporting tools; taking part from the upstream (上流) phase, with core design & development of new systems

Problem / Challenges

  • The client runs many software systems simultaneously to serve end-clients, with very high data security requirements.
  • It has its own development department but struggles to scale headcount, and had no experience or processes for working with offshore teams.
  • Large systems with complex business logic and only user manuals – no architecture or system design documents; the client had little time to write detailed design documents for offshore.
  • New members took a long time to ramp up; whenever someone left, performance and quality issues easily arose.
  • Renewal phase: the two sides had not aligned on the renewal approach, so NTQ's proposals added limited value; the upstream (上流) phase ran late, delaying the FE/BE code base, increasing re-work effort and lowering team motivation amid rapid growth.

Solution

Phase 1 – Pilot & ODC set-up (2015~2016)

  • The client sent a PM and Tech lead to Vietnam to clarify project management/development processes, understand the offshore environment and build rapport with the team; it also assigned people with deep system knowledge to provide training and answer questions.
  • NTQ shared its software development process and reviewed/tailored it with the client to fit the project; worked onsite in Japan to study the business and systems; applied the process to the pilot project and improved it on both sides.
  • Model: Customer ⇔ BrSE (+PTL) ⇔ Offshore team. The BrSE receives and analyses requirements, transfers them to offshore and reviews the output; the offshore team researches solutions, makes proposals and codes → integration test.

Phase 2 – ODC Maintain products (2017~2021)

  • Learned the business and functions of the systems; designed and developed supporting tools to serve business expansion, through which NTQ gained an overview of the systems.
  • Set up the development process and agreed quality standards.
  • Built an ODC handbook (Knowledge Management System): know-how on the client & business, systems & documents, coding guidelines/conventions/specific rules, test scope & test environment.
  • Training plans for current and new members; developing key members with an allowance scheme for them; exchanges between the Japanese and Vietnamese teams.

Phase 3 – ODC Maintain & Renew products (2022~present)

  • NTQ and the client agreed on the renewal approach (architecture, UI, conventions, existing source code) before building the code structure, code base and BD.
  • When the upstream (上流) phase was delayed, NTQ re-proposed the plan: prioritise reviewing and finalising the code base so it could be rolled out horizontally to other functions, while the remaining members focused on studying and refining requirements instead of coding in parallel. The client prioritised code-base review effort and followed the proposed plan.

ODC organisation & operating model

  • Steering Committee (company level): business collaboration, strategy, handling high-level issues.
  • ODC Management level: master plan, resource plan & allocation, collaboration model & working process, product roadmap. Each side has an ODC Manager; NTQ also has an Account Manager and a Director to handle issues beyond the ODC level, collecting feedback in monthly meetings.
  • Team/Project level: development, maintenance & operation support, technical consulting, QA/QC; leaders on both sides coordinate directly.
  • NTQ team structure (06/2023, 112 people): ODC Manager, Team leader, Bridge SE, Japanese comtor, BA, Frontend Dev, Backend Dev, Tester, BPO.
  • Communication: weekly report (email, Monday), weekly management meeting (1h, Teams, Tuesday), weekly technical/Q&A meeting (1.5h, Teams, Thursday), urgent matters handled via Redmine/Teams; Japanese is the main language, with English used for some technical documents/Q&A to speed things up; translators help with document translation.
  • Onboarding: NTQ provides suitable CVs within 2 weeks and replaces members on request; the client gives 1 month's notice when releasing resources and has full authority to adjust the ODC's structure, members and processes.
  • Team engagement: daily working reports, tea breaks, team building, birthdays, monthly/annual awards, team retrospectives, monthly surveys, ODC anniversaries, internal training (business knowledge and soft skills for working with Japan), reciprocal JP – VN visits, cultural exchanges.

Results

  • A continuous partnership from 2015 to the present, growing from a project-based pilot into a long-term ODC.
  • NTQ team size grew from 56 people (20152016) to 20 (04/2017), 34 (04/2022) and ~100 people; 112 members by 06/2023.
  • The role expanded from maintenance/feature additions to upstream (上流) participation and core design & development of new systems.

Lessons learned

  • For clients new to offshore: run a pilot, have two-way onsite visits and tailor processes together from the start.
  • Large systems without design documents: build a handbook/knowledge base, training plans and a core of key members to retain know-how through staff changes.
  • When renewing systems: agree on the approach (architecture, UI, conventions) before building the code base; finish the code base before parallel rollout to avoid re-work.

Have a similar project?

Contact SSD