Ten10 Process

Ten10 Define

Our first stage is called DEFINE in our process, we complete the following:

  1. NDA/MOU
  2. MSA
  3. BRS [from the client side, whatever they can give as inputs, in whatever formats]
  4. SOW [High Level Scope/Estimation/Budget] with Annexures [to be filled in 5D stage]
  5. High Level Project Plan
  6. Quick POC to demonstrate value
  7. Solution Architecture Workshop [blueprint]

The end result of this Define phase will be a clear understanding of the your business requirements at the macro and micro levels.

Ten10 Discovery

We take 2 days to 2 weeks to know your business requirements in detail We conduct discovery meetings with key stakeholders, subject matter experts and end users to understand the client’s business requirement, pain points, business rules, existing IT system, legacy data, workflow definitions, compliance, regulations and integrations to other systems, data migration, project charter, rollout approach, existing data, reports and forms.

The end result of this Discovery Phase will be a clear understanding of your business at the macro and micro levels and also a cohesive working relationship with your team [SME, users] and tremendous buy in from everyone who will be involved in the project.

Discovery Tools

Discovery Deliverable

  • Business requirement specifications
  • Story Board
  • RTVM
  • Functional specification
  • ER Diagram
  • Solution Architecture Document
  • Test cases with test data
  • Report Templates
  • Chart of Accounts

Discovery Non – Deliverables

  • Audio files [sound recordings of meetings]
  • Video files [Discovery and design Discussion videos]
  • Images – [Images of white board discussions]
  • Organization chart
  • Access control List
  • Active directory services Information
  • Technical requirements [hardware environment]
  • Minutes of the meeting

Ten10 Development

We plan for monthly milestones and 2 iterations for a milestone.

Milestones releases are structured in a way considering both business priority as well as product implementation sequence. We complete development, perform testing in the local testing environment. The test cases in the test case document are executed and released to customer for UAT testing.

Development Tools

Development Deliverable

  • Source code
  • Schema changes
  • Functional test cases
  • Configuration plan

Development Non – Deliverable

  • AD specification
  • Technical specification
  • Situation Problem Solution document
  • Code review document

Ten10 Design

It will take us 2 to 4 weeks to convert your business requirement into functional and technical design and arrive at an implementation plan that will suit your needs.

We document use cases, functional requirements, analyze, identify and map the fits-gaps into the product model. Build test cases to ensure the business, functional, technical requirements are met and delivered as per the scope at the end.

The design phase will ensure the priority, implementation sequence, critical path issues, risks and constraints that need to be handled during the development and deployment phases. The end result of the Design Phase will be a fixed scope, time, cost, resource, project plan for a successful delivery of your project.

Design Tools

Design Deliverable

  • ER Diagram
  • Solution Architecture Document
  • Test cases with test data
  • Report Templates
  • Chart of Accounts

Design Non-Deliverable

  • Audio files [sound recordings of meetings]
  • Video files [Discovery and design Discussion videos]
  • Images – [Images of white board discussions]
  • Organization chart
  • Active directory services Information

Ten10 Deployment

We make releases for each iteration in the client environment [UAT]. These releases are planned with the customer, providing the time to customer to test and feedback for every release.

Upon successful acceptance of the UAT release for major milestones, we deploy the software in pre-production and seek acceptance from the customer.

We provide appropriate release notes, configuration manual, schema changes and code changes for every release to the customer.

Deployment Tools

Deployment Deliverable

  • Source code
  • Release Notes
  • Daily user work flow videos
  • Binary – Installation Kit
  • Shell scripts

Deployment Non – Deliverable

  • Code review document
  • SQL review document
  • Patch update sheet
  • Audit checklist

Ten10 Dedicate

After a period of 2 – 6 weeks after Go Live, we provide Operations and support service for the software we delivered. The service level agreement and standard operating procedures will be defined for the dedicate service.

In Operations & Support stage, we will cover the following:

  1. Incident Management system will be setup [ticketing helpdesk]
  2. Go LIVE : Training, Documentation, Codebase, Installation guide, Admin support, Data Migration will be carried out here
  3. Once the solution is gone live, 15 to 30 days of support is given free for all Incidents Management

Incident Management: Three types of incidents will be categorized under Deploy or Dedicated O&S stages.

a.) Support Request:
Any issue, bugs, configuration, training, admin, install, upgrade, patches, fixes will be done here

b.) Change Request:
Any change requested by the customer which requires changes to existing scope to meet the demand

c.) Enhancement Request:
Any new feature/module/integration/extensions requested will be carried out

* Change Request, Enhancement Request both are extra charged during Deploy & Dedicated O&S stage.
* Each incident marked as CR, ER during Deploy or Dedicated O&S will be highlighted to client, separately approved for new time, resources budget to accomplish the work.

Dedicate Tools

Ten10 Quality

Incorporating patterns always helps attain the destination or design we ought to arrive, within a minimal time’s effort. When a pattern is followed, the output can be expected to fulfill the requirement within a short period with high quality. This mantra has been incorporated in our quality services.

Dynamic market trends like increase in supply chain complexity, more customer demand and ever changing technology induces Business and its software applications to adapt these changes really quick and compete in the market.

TenthPlanet’s Quality Service ensures highest quality of software is delivered to our clients by managing Source Code Integrity, Build Early Build Often activity, readymade Testing Stencil and Test Automation process and finally by performing a 24 Point Audit Checklist before every release.

Ten10 Quality Framework

Ten10 Practices

Our Quality team is involved right from the beginning phase of the project and ensures the test coverage meets the requirement scope. Hardware, Software environment replication is done and a prototype is tested in the replicated environment.

The software licensing related queries are discussed upfront to know the nature of production environment. Project test data is configured using the client’s legacy data.

We manage software installations by periodic releases to UAT, Pre-production and Production environment. Software review and sign off from client side business analyst in each of the release environment is a must. We plan agile iterative releases and thus requirements, scope deviations if any, are captured during the early stages of the project. Every release is well documented and adheres to strict release version policies.

A centralized incident management portal is maintained at both ends (offshore & onsite) to effectively track the internal and client side incidents.

Ten10 Activities

Source Control Integrity

Quality team is responsible for managing the source control (Branching, Tagging). Developers are provided with the access credentials to connect the source control system to check out and check in the project’s files. Source Control is scheduled with nightly and daily backup.

Build Early and Build Often

Our Build early, build often (BEBO) practice helps to address source code integration challenges upfront and avoids last minute code discrepancies.

24 Point Audit

Right from the release plan until the production deployment, all process and the deliverables are audited. Auditing covers source code merging, source code tagging, source code review, test cases and testing verification.

Test cases review, approval by TFG, approval by customer and impact analysis in case of any changes happened will be audited under test cases verification. Testing status update on all test environments like Local, UAT, Pre-production and Bugs posting will be audited under testing verification.

Auditing also verifies that unit testing is executed by the developer with updated with test results, FS and ER diagram.

All people involved in the project release reviews and signs the audit checklist.