Project management:

1. Refining Project Methodology (for major projects as well as other ongoing dev related
activities). I.e. Scrum / Kanban / or mix. Also, which of these methodologies to
choose for which type of activities.
2. Improving Project Reporting Framework, to periodically & proactively keep HQ
updated with all projects' status & dev pipeline updates.
3. Coordinating with all stakeholders in PK & HQ as the focal point for any major
campaign or dev related requirement or project
4. Create & maintain all dev activities track through the industry-best ticketing solution.
(e.g. Jira / Basecamp / ClickUp, etc).
Business Analysis:
Refining Business Analysis framework, including the following

 Establishing process & info flows for any requirements flowing into dev, including
documenting the holistic Software Development process / guidelines
 Preparing templates for all required documentation deliverables, e.g. User stories,
traceability matrix, functional / requirement specs, etc.
 To meet ISO needs, preparing & coordinating any required documentation artifacts


Implementation Roadmap of Commencing PM and BA practices

Project Management:
Refining Project Methodology (Implementation Roadmap):
To implement the project methodology, we can opt hybrid project Methodology.
Hybrid project Methodology will be Combo of frameworks of Agile-Scrum and
KANBAN.
As In RD we have multiple projects in line we will be leveraging and utilizing both of
framework to find best fit.
As by the observation, I was able to understand the 5 types of work which we are
performing across all the projects.

SR Work Package Type

1 Feature Enhancement
2 New Feature Development
3 Revamping/ Migration on New Stack of Technology
4 Removal of a feature
5 Bug Fixing

As project Timelines are tightly estimated in all the projects and cannot be missed due
high opportunity cost. I believe we should go for dual approaches.

SR Work Package Type Methodology

1 Feature Enhancement KANBAN
2 New Feature Development Agile Iterative Approach
3 Revamping/ Migration on New Stack of Agile iterative Approach
Technology
4 Removal of a feature KANBAN
5 Bug Fixing KANBAN

Reasons:

1. Feature Enhancement:
 One of the reasons I am choosing Feature Enhancement is continuous Delivery,
Kanban promotes a continuous delivery approach, allowing you to release features as
soon as they are ready.
 It is highly flexible and allows you to adapt to changes quickly. You can easily
reprioritize features and adjust the workflow as needed without disrupting the entire
project.
2/3. New feature Development/ Revamping

 Predictable: Provides a predictable cadence of delivery with fixed-length Sprints.

  Self-Reflection Transparency: Scrum Meetings (Standup, Retrospective, Sprint
Planning etc)
 Time-boxed iterations (Sprints) to Meet Tight deadlines.

4. Removal of Feature & Bug Fixing

 I would like to use kanban methodology for removal of feature and bug fixture as they
are highly flexible, and requirement can be changed at any time in process.
 Limit the work feature as one user can work on one thing at one time so they can
focus on the quality of work.
 Kanban promotes a continuous delivery approach, allowing you to release features as
soon as they are ready.

2nd Point About the Project Reporting framework.

 we will Standardized the project Documentation and Reporting to give project Insight
to Project stakeholders.
 we will be automating Reporting Processes By providing daily Project reports.
Reports could be from JIRA Extracted or Excel based. Reports Automation will
ensure that the HQ Team stay updated on Every aspect of the projects.

3rd Point About Coordinating with all stakeholders.

 Through open Communication

 Aiming to Establish open feedback channels.
 Keeping stakeholders Informed
 Establish Single Source of Truth (By using a single Tool to manage Project)

4th Pointer: Maintaining JIRA

 Create Tickets
 Assigning them
 Tracking Them
 Logging Bugs into the System
 Creating Sprints
 Creating project Dashboards

BA Role Expectations roadmap.

As pe BA following shall be my Road map of Improvements:
 Prepare and Implement Requirement Gathering Template to pass any requirement
to Dev or any other Team.
 Stakeholder Identification and Analysis by creating Stakeholder Mapping,
Power/Interest Grid.
 Requirement Elicitation by Using techniques such as brainstorming, user stories,
use cases, and prototypes.
 Creating High Level workflows for Existing process and suggest changes into
process make process leaner.
 Creating Detailed Process flows of L2/L3 to capturing current state and develop
future state process flows.
 Establish Requirement Review and Approval process and obtain formal sign-off
on requirements from all relevant stakeholders to avoid any ambiguity.
 Write Use cases for every Feature or requirement and make it a part of project
Artifact for Future references.
 Break every user Story into use cases and associate those documents with work
packages on JIRA.
 Create Document Templates for Software Requirement Specifications, Business
requirement Documents, RACI matrix, Use cases, Design Definition Documents.