How We Manage Projects

How We Work

D3S takes direct responsibility for its projects, even when employing the support of partners and subcontractors. We make sure our staff are available as needed for face-to-face meetings and discussions, either in person or remotely.

Each member of the project management team has clearly defined roles and responsibilities. Key management roles include:

  • Sponsor (typically an executive staff member)
  • Supervisor (typically a business director)
  • Project Manager (typically a development director)
  • Requirements Manager (typically an account manager)

For less complex projects, Account Managers might serve as both the project and requirements manager, with the development director responsible solely for assignment and delivery of technical work packages.

What We Deliver

  1. Software product meeting all of a customer’s requirements for “functional fit” — resulting from development, customization, configuration and set up
  2. User documentation including manuals and guides
  3. End-to-end data migration covering data import and issue resolution
  4. End-to-end interface service covering all critical 3rd-party systems
  5. Integration testing covering all integrated components and services
  6. User acceptance testing (usability tests)
  7. User training and mentoring
  8. Project Management (guidance, consultancy, project leadership and execution)

What We Expect From Our Customers

Ideally, our customers will always give us complete and detailed descriptions of their requirements. How, we know it’s not always possible for a customer to do this, so we work with them to get as much detail as we can.

Based on a rigorous needs assessment, we try to get as clear a picture as possible of the following:

  • Business and End-user Requirements describing all known requirements. These include both high-level business requirements as well as detailed user requirements. High-level requirements often include the company’s security requirements and the business processes that need to be supported. User requirements mostly address the features and workflows required for “functional fit.”
  • Core (or “common”) Data Structures including but not limited to core build definitions for activities, transactions and data processes. These data structures should be easily replicable with only minor modification/adjustment for individual installation instances.
  • Clear Rules for all defined processes to be implemented as part of the core and within installation instances (e.g. country-level deployments). These can be delivered in the form of policies and SOPs reflecting company rules and expectations, or other forms of written guidance. They can also be provided orally by responsible business managers during scoping discussions and project meetings.
  • Human Guidance throughout the lifecycle of the project. We hope our customers will be actively involved in our running projects. We depend on clients to answer questions, provide clarifications and data, and facilitate 3rd-party cooperation when needed.
  • 1st Level Support for end users in local markets (however, if customer-internal 1st-level support is not available D3S can provide this for additional charge in markets where D3S resources are available).
Share on facebook
Share on twitter

Request a Personalized Demo

Learn how to improve customer engagement and boost sales team performance with Inception CRM.

Inception CRM for Pharma

Get in touch for a personalized demo to see how Inception CRM can improve your sales

Inception CRM saves sales teams time while increasing their productivity, effectiveness, and efficiency.