1) How will you receive the requirements?
A) I receive the requirements through the following steps:
Stakeholder Meetings: Attending project initiation or sprint planning meetings where
stakeholders explain the business needs, goals, and expectations.
JIRA Tickets: Requirements are often documented as user stories or tasks in JIRA. I review
these tickets to understand the scope and details.
Kick-off Calls or Workshops: During initial phase of the project, requirements are explained
in detail by the client or Product Owner.
Clarification Sessions: If anything is unclear, I follow up with the client or internal teams to
get clarity before moving forward.
2) How do you monitor the project performance after Go-Live?
A) Track Defects/Issues – Log and monitor any bugs or incidents via JIRA or support tools.
Collect Feedback – Gather feedback from end-users and stakeholders.
3) Tell me some lessons learned
A) Clear requirements upfront reduce rework.
Regular stakeholder communication avoids misunderstandings.
Daily stand-ups improve team coordination.
4) can you tell me your day-to-day activities?
Track ongoing sprint activities using JIRA (sprint planning, backlog grooming, ticket
assignments).
Monitor progress of deliverables and update dashboards.
Attend daily stand-up and hiring calls.
Share Minutes of Meeting (MoM) and follow up on action items.
Collaborate with stakeholders to resolve blockers or clarify requirements.
Prepare daily, weekly, and monthly reports on project progress, resource utilization, and
compliance.
Maintain key documents like RAID logs, project plans, and change requests.
Participate in retrospectives and implement feedback for process improvements.
5) How do you prioritize the stories?
A) I prioritize user stories based on business value, urgency, dependencies, and team capacity.
During backlog grooming and sprint planning sessions, I work closely with the Product
Owner and stakeholders to:
Understand the business impact – Features that deliver the most value or are time-sensitive
are prioritized first.
Identify dependencies – Stories that unblock other tasks or are prerequisites are given
higher priority.
Assess risks and blockers – High-risk or critical items are scheduled earlier to allow time for
resolution.
Consider team capacity and velocity – Ensure stories are realistic for the sprint, based on
past performance.
We use JIRA to maintain and rank the backlog so the team always works on the most
valuable items first.
6) Sample Project Charter.
A) Project Charter
Project Title:
Cloud Infrastructure Automation for XYZ Application
Project Sponsor:
John Smith, VP – Technology, XYZ Ltd.
Project Manager:
Gopi Navuluri
Project Start Date:
August 5, 2025
Projected End Date:
December 20, 2025
Purpose / Justification:
The purpose of this project is to automate the cloud infrastructure provisioning and CI/CD
deployment processes for the XYZ application to reduce manual efforts, improve deployment
accuracy, and accelerate time to market.
Project Objectives:
Automate infrastructure setup using Terraform.
Implement CI/CD pipelines using Jenkins and GitHub Actions.
Containerize application using Docker and deploy via Kubernetes.
Improve monitoring and alerting using Prometheus and Grafana.
Ensure cost optimization and security compliance on AWS.
High-Level Requirements:
Terraform scripts for infrastructure provisioning.
Git-based version control for all code repositories.
Jenkins/GitHub integration for CI/CD automation.
Docker images stored in ECR or private registry.
Monitoring dashboards and alerting setup.
Assumptions:
Team members will be available as planned.
Necessary cloud and tool licenses are already procured.
Business requirements will be finalized within the first sprint.
Constraints:
Fixed budget of ₹12 lakhs.
Project must be delivered by Dec 20, 2025.
Security policies must align with XYZ Ltd. governance rules.
Key Stakeholders:
Sponsor: John Smith
Project Manager: Gopi Navuluri
DevOps Lead: Priya Verma
Security Analyst: Ravi Iyer
QA Lead: Sneha Rao
Approval Signatures:
Name Role Signature Date
John Smith Project Sponsor ________________ 05/08/2025
Gopi Navuluri Project Manager ________________ 05/08/2025
7) Sample Project Plan
Here’s a simple sample project plan you can adapt for interviews or documentation.
📄 Sample Project Plan
1. Project Details
Project Name: Dashboard Automation Implementation
Project Manager: [Your Name]
Sponsor: [Sponsor Name]
Start Date: 01-Sep-2025
End Date: 31-Dec-2025
2. Objectives
Automate weekly project status dashboards using real-time JIRA and timesheet data
Reduce manual reporting time by 50%
Improve accuracy of project metrics
3. Scope
In-Scope:
JIRA integration with dashboard tool
Timesheet system integration
Dashboard design and deployment
UAT and Go-Live
Out-of-Scope:
Changes to JIRA workflow
Hardware procurement
4. Milestones
Milestone Target Date
Requirements Sign-off 15-Sep-2025
Development Complete 15-Oct-2025
UAT Start 20-Oct-2025
UAT Completion 05-Nov-2025
Go-Live 15-Nov-2025
Project Closure 31-Dec-2025
5. Roles & Responsibilities
Role Responsibility
PMO Analyst Tracking, reporting, stakeholder comms
Developer Build integrations & dashboards
QA Test and report bugs
Product Owner Approve deliverables
6. Timeline (High-Level Gantt)
Phase Start Date End Date
Initiation 01-Sep-2025 10-Sep-2025
Planning 11-Sep-2025 20-Sep-2025
Execution 21-Sep-2025 10-Nov-2025
UAT 20-Oct-2025 05-Nov-2025
Go-Live 15-Nov-2025 15-Nov-2025
Closure 16-Nov-2025 31-Dec-2025
7. Risks
Risk ID Description Impact Mitigation
R1 Delay in integration High Early API testing
R2 Data mismatch in UAT Medium Parallel manual checks
8. Communication Plan
Weekly Status Reports: Every Friday
Stakeholder Meetings: Bi-weekly
UAT Updates: Daily during UAT phase
8) Total Revenue of your project per year
A) In the range of $ 3 to 5 million yearly (5-6 Crore).
