Eseye Simple Object API - Project Management Plan

Document
Eseye API Development- Project Management Plan
Title
Document Current Date of 22-Mar-
DOC-1011 1.2
Id Version Release 2024
Classificatio Storage
Internal
n Location
Author Manohar Lal Chauhan
Reviewed Name Surendra R.
by Designation Project Lead
Approved Name Maheswari G
by Designation Account Manager

Document Distribution
S# Name Department Designation
1 Maheswari Guntupalli Account Account Manager
Manohar Chauhan
2 PM TDM

Surendra Rachakonda Project

3 Developer Lead/Scrum
Master
4 Sownjanya Mekala Testing Test Analyst
5 Kunal Jiwtode Testing Test Analyst
6 Bharath Nathala Developer Software Engineer

.
 7 Shailesh Padalwar Developer Software Engineer

8 Ratna Mounika Polisetty Developer

Software Engineer

Revision History
Description of
Version No Date of Release Pages Affected
Change
Initial draft
V1.0 22-Nov-2023 0
version
Incorporated
V1.1 10-Jan-2024 Multiple comments from
Maheswari
Incorporate review
V1.2 16-Jan-2024 Multiple pages comments from
Surendra
Scope and team
V1.3 22-Mar-2024 Multiple Pages
members change
V1.4 18-Jun-2024

Table of Contents
1. Objective..............................................................................................................................
1.1. Project Overview.....................................................................................................
1.2. Acronyms................................................................................................................
2. Assumptions and Dependencies..........................................................................................
 2.1. List of Assumptions................................................................................................
2.2. List of Dependencies..............................................................................................
3. Project Details......................................................................................................................
3.1. Organisation...........................................................................................................
3.2. Overview of Project Lifecycle.................................................................................
3.3. Roles and Responsibilities.....................................................................................
3.4. Project Requirements.............................................................................................
3.4.1. Hardware.....................................................................................................
3.4.2. Software.......................................................................................................
3.5. Project Work Products...........................................................................................
3.6. Reusable Components............................................................................................
3.7. Project Meetings.....................................................................................................
3.8. Project Escalation Matrix.......................................................................................
3.9. Project Milestones..................................................................................................
3.10. Project Documents..............................................................................................
4. Project Environment Details................................................................................................
4.1. Development Environment Details........................................................................
4.2. Test Environment Details......................................................................................
5. Integration Plan...................................................................................................................
6. Project Test Plan..................................................................................................................
6.1. Testing Tools Used in Project.................................................................................
6.2. Types of Testing......................................................................................................
6.3. Test Entry Criteria..................................................................................................
6.4. Test Exit Criteria....................................................................................................
6.5. Defect Lifecycle.......................................................................................................
6.6. Defect Categorization.............................................................................................
6.7. Suspension and Resumption Criteria....................................................................
6.8. Defect Management Tool.......................................................................................
6.9. Testing Artifacts.....................................................................................................
7. Metrics Collection and Reporting.........................................................................................
8. Configuration Management Activities.................................................................................
8.1. Naming and Numbering Convention.....................................................................
8.1.1. Naming Convention for Automated Test Cases:.........................................
8.1.2. Naming Convention for Software Release..................................................
8.2. Tools, Environment, and Infrastructure................................................................
 8.3. Identification of Configuration Items....................................................................
8.4. Configuration Control............................................................................................
8.5. Configuration Audits..............................................................................................
8.6. Backup and Retrieval.............................................................................................
8.7. Training..................................................................................................................
9. Risk Management................................................................................................................
1. Objective
The purpose of this document is to provide comprehensive project plan overview for Simple Object API
Project

Project Overview
Ideabytes is now leading Eseye API Project for the development of objects that willl be
consumed by different platform and application in Eseye.
It is a cloud service that gives developer APIs to integrate in Eseye products which would fullfil
needs in SIM application management

Out of Scope
 Performance and Security test
 CI/CD Configuration for any env under test
 DB definition and Field description for YAML file
Acronyms

Acronym Meaning
CMP Configuration Management Plan
PMP Project Management Plan
SoW Statement of Work
TA Technical Analyst
CR Change Request
CC Configuration Controller
PM Project Manager
SA Software Architect
C&M Connect and Manage

Assumptions and Dependencies

List of Assumptions
Below is the list of assumptions for the project
 Key Stakeholders should be available and accessible during various project activities.
 Personnel, equipment and Materials are available as planned during the entire project
duration

List of Dependencies
Below is the list of dependencies for the project
 CI/CD Configuration for all envs – QAN, Staging and Production
 DB Definition objects in scope
 Table field description for Swagger
 Test Environments including hardware, software and network configurations must be set up
before testing can commence
 Configuring and setting up of testing tools is completed before using them for test
execution.
Project Details
Organisation
Below is diagram of the project organization indicating the reporting relationships.

Overview of Project Lifecycle

Delivery life cycle, the overall working model and wokflow are detailed here.

Roles and Responsibilities

Name Role (in Project) Responsibilities

Srinivas Katta Department Head Business and CRM

Guntupalli Account Manager Resource Allocation, Change Management Board
Maheswari
Manohar Chauhan TDM/PM Project Planning, Timeline Management, Scope
Management, Documentation, Deployment and
Implementation.
Rachakonda Project Lead & Team Management,
Surendra Application Developer Planning and Organizing, Communication and
Collaboration, Team Performance Management,
Application Design, Programming and
Development
 Sownjanya Mekala Testing Test Planning, Test Case Development, Test
Execution, Bug Reporting and Defect Tracking, Test
Data Management, Test Documentation.
Kunal Jiwtode Testing Test Case Development, Test Execution, Bug
Reporting and Defect Tracking, Test Data
Management, Test Documentation.
Bharath Nathala Developer API Development using Python and deployment
using CI/CD
Shailesh Padalwar Developer API Development using Python and deployment
using CI/CD
Ratna Mounika Developer API Development using Python and deployment
Polisetty using CI/CD

Project Requirements
Hardware
o 16B Ram
o Notebooks with I5 Processors
o 128 GB Hard disks

Software
o Windows 10 / 11
o Python
o Tosca Commander
o Tosca - Orchestrated Service Virtualization
o JMeter
o MySQLWorkbench – To Access Tigrillo/Oncilla DB
o Postman – For API’s
o Visual Studio –Framework Activities
o Cisco AnyConnect
o General Softwares (Chrome, Firefox, etc
o AWS Platform & Services, Terraform

Project Work Products

S.No Work Product Author Reviewer Approval Location

Name
1 PMP TDM Project Internal / Client PMP
Lead/Account
Manager
2 Epic/Feature/User Business Project Internal / Client Backlog in Jira
Story Analyst Lead/TDM

3 Code Developer Team/Project Client GitLab

Lead
4 Access Project TDM/Client Client JIRA/GitLab
Management Lead

5 Design Document Team Project Client OneNote

Lead/TDM
 6 Test Plan Test Lead TDM / Client Internal / Client Test Plan
7 Test Summary Test Lead Test Architect QA Head JIRA
Report
8 Automation Test Testers Test Lead Internal / Client EseyeCoEReposi
Scripts tory
9 Test Cases Test Quality Analyst Internal / Client project in Jira
Analyst
10 Quality Metrics Project TDM/Account Internal / Client Metrics
Lead Manager
11 Weekly Status Leads TDM/Account Internal / Client Weekly Reports
Report Manager

Reusable Components
S.No. Components Description Location
1 Automation Framework Tosca tool integration with Tosca Repository and
Gitlab and JIRA for complete Gitlab
automation
2

Project Meetings

Meeting Frequency Organizer Attendees

Sprint Planning Bi-Weekly TDM TDM/BA, Scrum Master, Project
Team Members
Daily Scrum Meeting Daily Scrum Master Project Lead, Project Team
Members

Backlog Grooming Weekly TDM BA, Scrum Master, Project Team

Members

Sprint Review Meeting Bi-Weekly TDM BA, QA Head, Scrum Master,

Project Team Members

Sprint Retrospective Bi-Weekly TDM BA, QA Head, Scrum Master,

Meeting Project Team Members
Weekly Status meeting Weekly TDM QA Head, Scrum Master, Project
Team Members

Project Escalation Matrix

Within Company
Escalation Type Primary Point of Secondary Point of Remarks
Contact Contact

Level 1 Project Lead/Test TDM Immediate

Architect
Level 2 TDM Account Manager Critical
 Level 3 Account Manager Department Head Emergency

At Client End
Escalation Type Primary Point of Secondary Point of Remarks
Contact Contact

Level 1 QA Head QA Head

Level 2 QA Head, CTO, HOE QA Head

Project Milestones
Iteration / Deliverable Name Date of Internal/External Internal/External
Release Level Completion Reviewer Approver
Sprint 2 Five objects in QAN 21/Feb/2024 BA, TDM, QA Head Client Manager -
env CTO
Sprint 3 Four objects in QAN 7/Mar/2024 BA, TDM, QA Head Client Manager -
env CTO
Sprint 4 Four objects in QAN 20/Mar/2024 BA, TDM, QA Head Client Manager -
env CTO
Sprint 5 Two objects in QAN 3/Apr/2024 BA, TDM, QA Head Client Manager -
env CTO

Project Documents
Below is the list of documents that project team maintain, if applicability of a document is “No” team
must update the remarks columns with appropriate information
S.No Document Name Applicability Artifact Remarks
(Yes or No) Location
1 PMP Yes PMP
2 Requirements Yes JiraBoard
Document Pla
3 Automation Test Scripts Yes Tosca
Commander
4 Test Plan Yes JiraTestBoard
5 Test Cases Yes JiraBoard
6 Release Note Yes Email
7 Metrics Yes ShrePoint
8 Access Management Yes SharePoint

Project Environment Details

Development Environment Details
Development and unit test will be done in QA env.

Test Environment Details

 Project Testing Environments Path / URL Links
Details
Eseye API QAN Infinity Portal: https://siam.qan.aws.eseye.io/auth/login

Eseye API Stage https://siam.stage.aws.eseye.io/auth/login

Eseye API Production https://infinity.anynetiot.com/auth/login

Development Environment Details

Environments Path / URL Links
INT Infinity Portal:
https://siam.int.aws.eseye.io/auth/login

Integration Plan

 Sprint development and Integration in INT branch

 Pre-Prod integration & deployment after sign-off in QAN env

Project Test Plan

Testing Tools Used in Project
 Tosca Commander
 Tosca OSV
 JIRA with Xray
 Postman
 CI /CD
 Gitlab

Types of Testing

Test Type Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

Functional Test √ √ √ √
Automation Test √ √ √ √ √
Regression Test √ √ √
Performance
Test NA NA NA NA NA NA
Security Test NA NA NA NA NA NA
UI Test NA NA NA NA NA NA
Test Entry Criteria
Below are the various entry criteria that are to be met before Test execution
 Unit test is passed
 Test case review completed
 Test Data and SQL query availability
Test Exit Criteria
Below are the various exit criteria that are to be met to Sign-off
 Test case execution completed
 Met quality standard defined for project
 Open defects recorded in JIRA

Defect Lifecycle

Defect Categorization

Severity Definition
Highest Blocker and test cannot be proceeded for module
High Blocker with workaround to continue test
Medium Less impact on System
Low Minor in nature and continue testing
Lowest Aesthetic changes, no impact on release

Suspension and Resumption Criteria

S.No Suspension Criteria Resumption Criteria

1 Costs exceeding the Project Budget adjustments are approved
approved budgets by a predefined to address the extra costs incurred
percentage or amount

2 The Project requirements and All Key Stakeholders should agree

priorities gets changed often via to the changes or conditions for the
various key stakeholders Project Successful resumption
3 Unavailability of specialized tools. The specialized tools are to be
made available to continue the
work effectively

4 Delays in getting various Project Project should be resumed after

related regulatory approvals getting the regulatory approvals

5 Unforeseen technical challenges Technical challenges should be

which require extra time and resolved allowing the project to
resources beyond the initial project progress as planned.
plan.

Defect Management Tool

All the defects will be tracked in JIRA
Testing Artifacts
 Test Plan
  Automation Regression Test Suite Packs
 Requirement Traceability Matrix
 Sanity Test Suite Pack
 Defect Summary Reports
 Test Summary Reports
 QA Sign-off Reports
Metrics Collection and Reporting
Objective of Metrics measurement is to provide valuable insights into the efficiency and effectiveness.
Refer JIRA Dashboard and SEPG Metrics
Configuration Management Activities
The Configuration Controller maintains the CMP and has the authority to propose any changes to the
plan. All changes will be reviewed and approved by TDM. CC will review the CMP while performing the
CM audits or as part of preparation for internal or external audits.

Naming and Numbering Convention

Naming Convention for Automated Test Cases:
The naming convention for each Automated Test cases should be named as given below:
Infinity| Portfolio Management| Login is Name of web portal and Module name, Sub Functionality name.
 First part letters, Infinity for the Web Portal Name.
 The second part of the letters stands for Module Name.
 The third part of letters stands for Sub functionality Name.
Below image displays the naming convention

Naming Convention for Software Release

The naming convention for API release is followed as per client standard and Ideabytes will follow the
same standards and procedures. Also, the baselining guidelines are as per client standards and
procedures only. 00. Branching, Workflow, Route to live (Web view)
Tools, Environment, and Infrastructure
CM Tools
Technology Tool
Automation Scripts (TOSCA Tosca Commander
scripting)
Database Queries MySQL Workbench
Project Management/Bug tracking Jira
 API Manual Testing Postman
Source code GitHub
Ticket Management Jira

Environment Details

Testing Level Details Environments Path / URL Links

Eseye API QAN Infinity Portal:
https://siam.qan.aws.eseye.io/a
uth/login
Eseye Tosca Repository QA/QAN EseyeCoERepository

Identification of Configuration Items

Phase Configuratio Document Owner Point of Degree of Change

Definition n Item Attribute Start Control Approval
of degree
of control Planning Project Project Project Planning Released AccountMa
1. Management Management Manager Phase nager/
Plan Plan Client
(Sharepoint)
Require Epic and Requirement Business Requirem Released Project
ment related docs Document Analyst ent Phase Manager
given in that (JIRA)
(Jira)
Coding Gitlab Source Code Dev Team Dev Phase Work in Project
Progress Lead
Test Test Plan Test plan Test Lead Dev Phase Work in Project
Planning (Jira) progress Lead
Impleme Manual Test Test Script Test Team Testing Work in Project
ntation Scripts & Phase progress Lead
Automation
Test Scripts
(Jira & Tosca)
Conclusi Test Result Test Test Lead Test Work in Project
on (Jira) Summary Closure Progress Manager/C
Reports lient

Uncontrolled: Anyone can make changes to the configuration item

2. Work in progress: Author control changes to the configuration item
3. Released: A designated authority authorizes, and controls changes, and relevant
stakeholders are notified when changes are made to the configuration item
Configuration Control
Storing the automation scripts in respective folders in customer server based on environment and
version of software product as current automation tool not able to store automation scripts based on
versioning.
 Test events are assigned to those test sets and updated those test event names in customer CI/CD
pipelines for deployment process.
Configuration Audits
The Configuration Management audit will be performed by CC identified in the project-by-Project
Manager as per the audit plan below. The entire project configuration items must be
audited as part of configuration audits. A configuration audit checklist will be used for the
audit purpose.

As part of configuration audits, CC will perform configuration audit once in every 6 months during which
existence of artifact is verified at the designated location and during functional configuration audit the
completeness and correctness of the artifact is verified.

S. No. Name of Work Product / Artifact Auditor

1 Requirement Document or User Stories CC
2 Design Document CC
3 Code CC or Tech Lead
4 Automation Scripts CC or Tech Lead
5 Test artifacts (test plan, test cases, test CC
summary report)
Backup and Retrieval
This project will follow Eseye data retention policy -
https://documentcloud.adobe.com/spodintegration/index.html?locale=en-us
 GitLab for developed code
 Tosca server for Automation script
 JIRA for Product Backlog
Training
All the new employees must undergo Eseye KT Sessions as part of joining formalities, during
this session an overview of Project management practices followed in Ideabytes are
explained by the trainer.

Any additional requirement or practices of the project are informed by Project Manager
or CC

Risk Management

Please refer RiskTrack Log