Tegsoft Technical Process Management

In this article, Tegsoft's Technical Process Management and detailed process operations are described. 

By reading this article, you will have information about

• The technical processes managed in accordance with Agile Software Development principles at Tegsoft,
• The management of projects in Tegsoft and the teams in the process. 

Tegsoft software development processes are carried out by following the Agile Software Development principles. (For detailed information please visit here.)

Development processes are carried out with regular sprint meetings to which technical teams and other related teams join. In these meetings, elimination of important errors, software development processes for approved projects, bug fixes, and making additional developments within the scope of product development activities which are included in the business plan are discussed and related tasks are determined. 

Tasks planned according to man/day effort are started to be worked on immediately upon approval. These task firstly they enter the analysis process; Then, the data set for the necessary accesses, integration needs, and sample scenarios is determined and made ready for the software development process. (Tasks that are not ready for the software development process, cannot be planned within the current sprint.)

Sprints are generally completed within 2-weeks. Completed project tasks are prioritized in the planning. When it is possible, a deployment set is created as soon as the task is completed to deliver and finalize the project. 

Sometimes deployment set can only be created at the end of the sprint. The work is delivered by ensuring that this set is loaded in the first suitable time frame. To upload some task results may be needed to wait for the loading set to be created at the end of the sprint. 

Additionally, the average task completion rate at Tegsoft measured last year was above 85% last year. This rate is above 98% in tasks with high importance. As Tegsoft, we would like to state once again that we are doing our best to improve the quality and speed up the process.

All these Tegsoft Technical Processes are presented in detail in the flowchart below.

1. Customer Onboarding

Customer onboarding process starts with the arrival of a new customer or project without any integration needs to Tegsoft products. Customer needs are analyzed by Tegsoft Project Management (PM) Team or Business Partners and a need-oriented solution is built. Then, it is analyzed whether there is a need for a POC (Proof of Concept) environment. If there is a need for a Cloud POC environment, Tegsoft Operation Team carries out process. If there is a need for an on-prem POC environment, Business Partner carries out process. The PM Team or Business Partner finalize the necessary configurations for the customer and provides a basic introduction. So, the product available to the customer.

2. Maintenance, Integrations & Support

• New Project 

When a new integration or development needs are requested from Tegsoft by the customers, such requests are called a “new project” and a solution is built by working with the PM (Project Management) Team. 

• Ongoing Project

When new requests come to Tegsoft from active customers, these requests are called “ongoing project” and a solution is built by working with the Software Support Team.  

Although the teams that process the requests are different according to the project types, similar processes are carried out. These processes are Development, Testing, Release, and Support whose details are provided in the following sections. 

2.1. Development

Necessary tasks are created according to needs and assigned to developers. Developers work on these tasks and meet the necessary software needs. In addition, the development team also creates API codes and develops the methods of these API codes as needed. 

2.2. Testing

The testing process is the process in which the performance and functionality of the products are checked before they reach the end user. There are four main types of tests: load tests, regression tests, manual tests, and automated tests:

• Load Tests: Load Testing is a non-functional software testing process in which the performance of software application is tested under a specific expected load. It determines how the software application behaves while being accessed by multiple users simultaneously. The goal of Load Testing is to improve performance bottlenecks and to ensure stability and smooth functioning of software application before deployment. 
• Regression Tests: Regression testing is a type of software testing which is to confirm that a recent change in program or code has not adversely affected existing features. Regression Testing is nothing but a full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine.
• Manual Tests: Manual Testing is a type of software testing in which test cases are executed manually by a tester without using any automated tools. The purpose of Manual Testing is to identify the bugs, issues, and defects in the software application. Manual software testing is the most primitive technique of all testing types, and it helps to find critical bugs in the software application.
• Automated tests: Automation Testing is a software testing technique that performs using special automated testing software tools to execute a test case suite. 

2.3. Release

When all of the development and testing tasks are completed, the project release occurs.

The date and time of the Tegsoft New Release is published regularly in the Warnings & Announcements article. Tegsoft users are recommended to visit this article frequently. In addition, this information is shared with posters in all Tegsoft's social media accounts (LinkedIn, Instagram, Twitter, and Facebook).

• Tegsoft Release Notes: Information about new versions and updates are published every two weeks on Tegsoft Docs Website. (https://docs.tegsoft.com/docs/what-is-new)
• Installable Tegsoft Product Test Version Package: After the developments and production tests are completed, installable Tegsoft product test version package is released for customer's real time usage. 
• Installable Customer Specific Product Package: According to the customer’s needs, specific projects and developments are processed and specific installable packages are released.

2.4. Support

After the release, the software support processes begin. Processes such as collecitng customer feedback, new feature needs, bugs and issues are managed by the Tegsoft Support Team.

• Requirement Management System: If Tegsoft products have issues, bugs, etc., the Customer or Business Partner notifies Tegsoft Support Team via e-mail to support@tegsoft.com. The system automatically generates an inquiry number, and the Software Support Team takes care of the situation immediately.
• New Feature Requests: When the customer needs a new feature for a certain Tegsoft product, the Support Team starts the development process to satisfy customer needs. 
• Quality Assurance: Quality assurance is provided by the Software Support Team to prevent errors and defects in active products and avoid problems while delivering products or services to customers.  
• Customer Support: Whenever the customer needs any support about a product, such as APIs or other technical information, the Software Support Team assists the customer.
• Bug Reports: Bugs detected during the use of the product are reported to the Software Support Team. The Support Team reproduces the bug and solves the issue by themselves or with the support of the development team.
• Feedbacks: Necessary improvements are provided according to the customer feedbacks collected by the Software Support Team.