Home / BA / How do you ensure that your project is on schedule to meet the deadline

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


You are more likely to meet your project deadlines if your team agrees upfront that things will change from when the deadline was cast and when the deadline date arrives.

Before the project completion project will start by below steps 

1. Gather requirements using elicitation techniques

2. Documents the requirement using UML

3. Model the requirement to the technical team.

4. Tracks the requirements during the development stage.

5. Handle change requests

6. Facilitates UAT (User Acceptance Testing)

In the above first step Gather requirements not only gather the requirements ba will decide the priorities of that requirement.

Requirement definition

It is a process in which scattered requirements are put together and redundancy is removed the inter-related conditions are linked.

Key task is

Define Stakeholder Needs

Identify business needs and divide them into functional and non-functional requirements

Create a group of similar requirements

Create supporting artifacts

A. priorities the requirement 

1. Factors that influence

Importance, risk, cost, benefit, time, and strategy

3 main actors



Business owners

2. Moscow technique –

Is a prioritization technique used in business analysis and software development to reach a common understanding with stakeholders on the importance they place on delivering each requirement also known as Moscow prioritization?

Must- must have this requirement to meet the business needs

Should – should have this requirement if possible, but project success does not rely on it.

Could – could have this requirement if it does not affect anything else in the project.

Won’t – I would like to have this requirement later, but it won’t be delivered this time

Also apart from this technique for validating requirements BA will use the below technique

1. Functionality –feature set

2. usability- human factors

3. Reliability – frequency /severity of the failure

4. Performance – speed, efficiency

5. Supportability – testability adaptability.

SWOT analysis

1. strengths- anything that the assessed group does well may include experienced does well.

2. weakness- those things that the assessed group does poorly or not at all.

3. opportunity- external factors that the assessed group may be able to take advantage of.

4. Threats – political effects? Environmental effects?

Gap analysis –

A comparison of the current state and desired future state of an organization to identify differences that need to be addressed.


Feasibility study – possibility of doing a project within some constraints like technology, Budget, and Time.

Idea – can it be turned into technology?

Change request –

As the project progresses through time (like a month or a year or longer), some things will inevitably change that affect your project and so your requirements may also change exchange management will impact on project scope

And as a BA will make for

UML Diagram

Use case

Use case specification

Activity Diagram


1. Domain model



4. DFD


BA will use some framework 




The business Analyst will make some artifacts and refer from others which are below 

1. URD

2. BRD

3. FRS

4. SSD

5. RTM

6. SRS

7. HDD

8. ADD


About Sushil Rajendra Mahadar

Check Also

What is the requirement elicitation? Have you ever participated in these elicitation meetings?

Introduction Requirement elicitation is a critical process in the field of business analysis. It involves …

Leave a Reply

Watch Dragon ball super