How do you ensure that your project is on schedule to meet the deadline?

Initially while accepting the project we do a SWOT (Strengths, Weaknesses, Opportunities & Threats) analysis for the identification of scope, feasibilities and impediments. After the SWOT analysis, we ensure that the project will be completed within the time and budget.
In a project majorly we are focusing on these three:
Budget
Time
Resources
After accepting the project we will do stakeholder analysis for the identification of SME (Subject Matter Expert) for better clarifications on requirements by using RACI. Then we will do requirement gathering by using elicitation techniques. Later we prepare business requirement documents, functional and non-functional requirement documents and EPIC’s to product backlogs.
Before going to development we will prepare user stories, use cases and activity diagrams with flow charts for a better understanding of the requirements to the technical team.
Then we will prioritize the requirements based on their importance by using the MOSCOW technique.
MustHave – Mandatory for the development
Should Have – Important & add significant value to the development
Could Have – Nice to have, if left it has a small impact
Would Have – We can skip for this time being

We do product grooming for backlogs
PRODUCT GROOMING: Also known as backlog refinement it is a recurring meeting where backlog items are reviewed and re-prioritized by product managers
Product backlogs are categorized into the given project time frame. These are developed in sprints.
KPI: It is another checklist we look into, key performance indicator it is a measurable performance over time for a specific objective. KPIs provide targets for teams and milestones to check progress.
We categorized functionality into SCOPE & SCOPE CREEP:
In Scope – functionalities/features that are being developed
Out of Scope – functionalities/features that are mentioned additionally which are not going to be developed or not covered or not related to.
Scope Creep – which cannot be completed in the given time and budget.

Before starting the sprint we do sprint grooming or refinement.
After every sprint we ensure that assigned backlogs have been completed or not.
We will be updating the sprint burn-down chat and product burn-down chart regularly.
SPRINT: It is a time-bound event. It is a metric used for software development.
In general 2 weeks is one Sprint. The working condition of the User Story should be the Outcome of a Sprint.
And everything we update in PI after sprint completion
PI (PRODUCT INCREMENT): In the case of development, testing is done and the function is ready to use then it will be delivered in the middle of the project.
Post development, after testing (clearing of impediments) we cross-check with RTM regarding requirements.
IMPEDIMENTS/ROADBLOCKS: Issues faced by the teams. All challenges faced by the team will be logged in this impediments log.
TEST CASE: For each user story a document given by the QA team after the completion of testing, will be cross-checked with RTM.
RTM: It captures all requirements proposed by the client. The main purpose of RTM is to validate that all requirements are checked via test cases so that no functionality is missed during Software testing.
Finally, we hand over the project within the timeframe.