10 Best & Free Job Portals

I want to talk about important Free job portals to apply for a suitable Job..

When you are ready to attend the interviews, and you want to apply for jobs, here are the some important Free Job Portals to apply.

Job Portals

  1. Indeed: This is very important site. When you are updating your profile ensure to enter correct skills and keywords in required columns.
  2. Naukri – This is very important site. When you are updating your profile ensure to enter correct skills and keywords in required columns.
  3. LinkedIn: Try to increase connections with your relevant field. Here we can directly interact with recruiters.
  4. Monster: This portal also plays major role to get job.
  5. Shine – You can find good jobs from IT, Engineering, Banking, Marketing sector.
  6. Timesjobs – You can find good jobs from IT, Engineering, Banking, Marketing sector.
  7. Glassdoor: Best for Employer Insights, here we can read employ reviews and all.

Other important job portals to apply. 

• FlexJobs:
• The Ladders:
• AngelList:
• Jobrapido
• Freelancer
• Freejobalert
• Splashfind
• Click.in
• Freshersworld.com
• Sarkari Naukri
• Egovtjobs.in
• recruitmentresult.com
• Scouted:
• Snagajob:
• Recruit.net
• Iimjobs.com

Once you updated your profile in portals, ensure to update the profile frequently. Always recruiters prefer for updated resumes only. Ensure to update before business hours.

Tips to update the profile in Job portals: 

  1. Heading:   

    Resume Headline plays a very important role in short listing your resume by the Recruiters. Concentrate on Resume Heading and ensure it should proper.

  2. Keywords and Skills:

    Ensure to add all your Key skills, for example you are applying for Business Analyst then skills as below.

Business Analysis, Documentation, Prototyping, User stories, Requirements Analysis etc..

If you have strong domain knowledge on any particular domain then you should mention the same also. Ex : Banking, Healthcare, Telecom etc.,

  1. Update your Resume

    Update your resume frequently, at least weekly twice or thrice. So not think to much to update your resume i.e., what to update and all. Just modify any simple data and click on update.

  2. Certifications:

    Ensure to update the certifications if you have any, it will add benefit to your resume. Some organization will look for certified candidates only.

  3. Identity

Add your photo to your profile.

Provided these Free Job Portals from various channels and based on my Experience.

Start Apply and get job.

All the best.

What Is Sanity Testing?

I want to talk about what is SanityTesting and who will do the sanity testing and few advantages by performing SanityTesting. There are many testing methods; SanityTesting is one of the method.

What is Sanity Testing

Topics Covered

1. What Is SanityTesting?

2. Who will do the SanityTesting?

3. The Best Way To Do SanityTesting?

4. SanityTesting Steps

5. Advantages Of SanityTesting

1. What Is SanityTesting?

In SanityTesting, once development is completed, build will be generated and same will be released for testing. User tests the functionality of the software build, whether the functionality is working as per requirement or not. User tests whether critical functionalities are working or not. In simple terms we can tell, Sanity Testing focuses on testing specific functionality after making changes to the code and fixing any bugs.

The aim is to make sure that any reported bugs have been fixed and that the specified functionality works correctly.

2.Who will do the Sanity Testing?

It depends on the organization, in some organizations Business Analyst will do the SanityTesting to ensure no bugs or less bugs in application. It helps Business Analyst to understand the Application functionality.

Here we need not to execute all the test cases, we can test some important and critical test cases. Or else we can review the test case results if this is done by QA team.

3. The Best Way To Do Sanity Testing

As we discussed in above point, it is up to the team and organization that how to perform sanity testing. There is no particular method or document to perform sanity testing.

4. Sanity Testing Steps

As we discussed there is no particular order or steps to perform SanityTesting. But we will try to follow some tips to ensure critical functionalities of the application are working.

  1. Identify : First understand the requirement and functionality of the application. Then identify what needs to be tested. It is required for any type of testing. This includes functionality, features, and modifications that were introduced to the relevant code or build.
  2. Validate : The testers will check and validate all of the identified functionality, features, and modifications from the above step.
  3. Testing : Team will test all the functionalities, features and modifications from the above step. This ensures that application functionality is working as expected.

5. Advantages Of Sanity Testing:

  • As team tested end to end functionality, it helps to avoid escalation from the client.
  • As functionality has fewer bugs or no bugs, it improves client satisfaction.
  • As team tests on concentrated functionality, it is easy to identify the bugs.

There are many testing methods, Functional testing, and integration testing (SIT), Black box testing, regression testing, smoke testing and all.

The Dos and Don’ts for Business Analyst.

I want to talk about Dos and Don’ts of Business Analyst. As Business Analyst is the person who speaks with client, he/she should know Do and Don’ts. This is part of Business Analyst Role and Responsibilities.

Dos and Don'ts for Business Analyst.
Dos and Don’ts for Business Analyst.

Let us

observe here some of important Dos and Don’ts for Business Analyst..

1. Never say No to client.

When client is explaining his problem or giving requirements, listen carefully and try to understand what  he/ she is trying to explain, and never say “No” to client affront, because here client is explaining his problem and he expects some solution from us.

So rather than say “No” we can provide alternate solution after speaking and discussing with our internal teams.

2. Never imagine anything in terms of GUI

Never imagine the requirements by seeing graphical representation ask right questions to client and get clarity on the requirements.

Login page may same for most of the websites but functionality is different.

For example: If you want to login to any website we need to enter correct user id and password to login the page. Here user id and password is common, but password length and validations differ from website to website based on the client requirement.

Example: Password should be 10 characters and it should have at least 1 capital letter and 1 special character.

3. Question Everything

Never feel bad to ask questions, ask the right questions and get clarity from the client. You can ask the questions till you get clarity. Sometimes client may not tell the complete requirement unless you ask the questions.

Example : Client will say I need login page. But here you need to ask multiple questions to client to get clarity. Let us see some sample questions here.

  • What are the validations required,
  • Terms and conditions are required or not.
  • And when this button should be disabled or enabled.
  • Which type of error message should be shown on the screen if user enters wrong password or user id.
  • Password length should be how much and all.

4. Consult an SME for clarifications in Requirements

If requirement is not clear and you need more clarity on the requirement, then we can discuss with SME (Subject Matter Expert). And ensure to document the requirements what you discussed with SME and get approval from solution owner. And explain to him what you understand by discussing with the SME.

5. Every problem of client is unique.

Every problem of Client is unique, so talk to the client with a open mind with no assumptions from your previous experience.

Never come to any conclusion before listening or understanding all the aspect of requirement from client, if you have a slight amount of doubt about any demand or change it’s always preferable to clear it with the client, subject matter expert, or with your team member.

6. Do not interrupt the client, when he/she is giving you the problem.

Listen very carefully and completely to the client as well as to the end user and then ask question, don’t interrupt them in between.

7.Maximum try to extract the leads to solution from the client itself.

8.Never try to give solutions to client straight away with your previous experience and assumptions.

9. Should not be hurry.

Should not gather the requirements in hurry, conduct a meeting in a convenient time and take your own time to understand the requirement or gather the requirements. Because if you are in a hurry to capture the requirement then there is a chance to misunderstand the requirement, it may lead to project failure.  As a Business Analyst you should be have open mind when you are gathering requirements.

10. BA should focus on “what” and “when” to develop rather than focus on “how” to develop.

As a Business Analyst our responsibility is to understand what to deliver and when to deliver the project, how to develop is the responsibility of development team or development manager. We need not to concentrate on this part and need not to worry. Always have a prior discussion with your project manager and sponsor before conducting a meeting.

11. Should not miss any requirement

Make sure that you have gathered all the requirements from the stakeholder for your project, missing out any information can results to unwanted redo the work as well as delay projects and increase cost.

12. Should know what the Scope of the Project is.

Sometimes non functional requirements of client are not feasible because of budget or time constraint, so it’s always better to liaison with your PM to find out what is out of scope so that all will be in the same page and avoid misunderstanding.

What is a BRD (Business Requirements Document) ?

I want to discuss about what is a BRD and how to prepare BRD?

Topics Covered in this Article:

  1. What is a BRD or Business Requirements Document?

  2. Who will prepare the BRD and who is Responsible for BRD?

  3. Objectives of a business requirement document?

  4. Business Requirements Document- Key elements

  5. How to prepare BRD?

  6. Business Requirement Document Template – Sample Template.

  7. Tips for writing a business requirements document?

What is a BRD
What is a BRD

1.What is a BRD or Business Requirements Document?

BRD is a Business Requirement Document, in some organizations it is also called as Business Requirements Specifications Document. By seeing the name we can understand in this document we will capture all the requirements and how we are going to provide solution to the client. We can say it is the communication document between Business and Technical Team.

In simple words we can say, BRD indicates what the business wants to achieve.  The BRD indicates all the project deliverable and the inputs and outputs associated with each process function. This document will have customer needs and expectations.

BRD definition: “A Business Requirement Document (BRD) focuses on the business perspective as it holds the details of the business solution for a project.”

2.Who will prepare the BRD and who is Responsible for BRD?

Business Analyst prepares this document with the help of respective stakeholders. While creating Business requirements document, we should include the project stake holders, and the Business stake holders, that means we should invite or include all the stake holders who are needed to complete this project smoothly.

In some organizations client prepares the BRD and share with IT organization to deliver their changes or requirements, once IT team receives the BRD then they will do the feasibility analysis and release FSD or FRD based on the BRD.

Who should be involved in business requirements document creation?

A number of teams and partners should create the BRD:

  1. Core team of the project (BA, Development Team, QA and all)
  2. Business partner’s or stake holders
  3. Process owner(s) or representatives
  4. Subject matter experts
  5. Change/project/product management, quality department and/or IT management as needed or available
  6. Change Management Team.

3. Objectives of a business requirement document?

  1. To get an agreement and common understanding among all the stakeholders
  1. Communicate to the technology server provider, the business needs, the customer needs, and what the solution needs to provide to satisfy business and customer needs
  2. Describe in details of the customer needs or requirements.
  3. Describe clearly what solution we are going to provide.

4.Business Requirements Document- Key elements

A Business Analyst or Project Manager prepares the Business Requirement Document as they have good understanding on the client requirements and if there is any ambiguity or clarification required from client, then they are the persons can reach the Business stake holders.

The most important and critical component of a Business Requirement Document is the scope of the project.  We (Project Managers and Business Analysts) should understand the restrictions and constraints.

  • Why project initiated
  • What is the goal or objective of the project?
  • What are the problems which the business wants to solve?
  • What are the restrictions?
  • What are the limitations?
  • Is it worth to invest the time and money required for the project?

5.How to prepare / Business Requirement Document BRD?

We should take care of few important things before creating BRD.

  • We should define the need or requirement of the company or organizations.
  • We should ensure all the stake holders involved.
  • We should identify the phases of the project.
  • We can use a suitable template to capture the requirements.

6. Business Requirement Document Template – Sample Template.

  • Document revision
  • Approvals
  • Introduction
  • Business goals and objectives
  • Stake holders
  • Business rules
  • Project background
  • Project objective
  • Project scope
  • In-scope functionality (Requirements)
  • Out-scope functionality (Requirements)
  • Business requirements
  • Data requirements
  • Functional requirements
  • Non_functional requirements
  • Assumptions
  • Constraints
  • Risks
  • Business process overview (modeling diagrams for instance, Use Case and Activity Diagram)
  • Legacy systems
  • Proposed recommendations
  • List of acronyms
  • Glossary of terms
  • Related documents
  • Dependencies of existing systems

This document may vary depends on the organizations, some organizations may have their own template and format. If no standard template or format not available in your organization then you can use the suitable template as per your client requirements.

7.Tips for writing a business requirements document

Here I am trying to give some simple tips to write Business Requirement Document.

  • Engage stakeholders:Encourage all the project stakeholders to get involved in elicitation techniques such as brainstorming, surveys, focus groups, interviews, and ideas for prototyping.
  • Include mockups:Include visuals and graphical representations, such as charts and diagrams, when necessary, as they can be powerful in making your point. We can use so many open source tools to draw diagrams and to create process flow diagrams and charts.
  • Do feasibility research:Research some of the past projects to determine the feasibility of your BRD. Evaluate your project to understand whether the solution desired can be developed within the constraints of time & cost.
  • Use Simple Language:Don’t use complex words rather use simple easy to understand language that encourages action.
  • Validate the Document and contents:After writing the business requirements document, have it reviewed thoroughly before distribution. Obtain validation of the information and the contents–including the assumptions–and ensure that all errors are corrected.

8. What are the differcnes between BRD and FRD?

What is RACI Matrix?

I want to discuss about RACI Matrix, what RACI Matrix is and what the advantages are by using this in this article.

What is RACI Matrix
What is RACI Matrix

Topics Covered in this Article:

  1. What is RACI matrix?

  2. What is a RACI chart?

  3. What does RACI stand for?

  4. RACI definitions

  5. Advantages of a RACI chart

  6. When to use a RACI matrix

  7. How to create a RACI matrix: Example & template

  8. RACI matrix rules

What is RACI matrix?

I will try to explain in simple words, when we are working in an organization or in a project, we should know who Responsible is for what tasks and who is Accountable. It helps to track the project that particular task is pending with whom or assigned to whom. So to understand that,  will prepare RACI chart.

What is a RACI chart?

A RACI chart is a simple matrix used to assign roles and responsibilities for each task, or decision on a project. By clearly mapping out which roles are involved in each project task and at which level, you can eliminate confusion and answer the project question,  who’s doing what?

What does RACI stand for?

RACI stands for ResponsibleAccountableConsultedand Informed. We can observe each letter represents the tasks responsibility.

RACI definitions

  • Responsible: Team member does the work to complete the task. Every task needs at least one Responsible member, but as per project we can assign more.
  • Accountable: This member assigns the work. And this member reviews the completed task before delivery. On some tasks, the Responsible party may also serve as the Accountable We should ensure to each task should assign to one Accountable person.
  • Consulted: These members provide inputs based on their domain experience or knowledge.  They can also provide inputs on how it will impact on future project.
  • Informed: These team members simply need to be marked in the loop on project progress.

Advantages of a RACI chart

  • A RACI matrix helps us to set clear expectations about project roles and responsibilities.
  • It helps us to avoid multiple people work on same task.

When to use a RACI

If you want to know who is performing which task then RACI will help you to understand easily. It avoids the confusion in team.

  • The decision-making or approval process could hold up the project.
  • There’s conflict about task ownership or decision-making.
  • The project workload feels like it’s not distributed evenly.

And please understand we need to create RACI matrix based on the project and team. This is not same for all the projects and teams. We need to assign the roles as per our requirement and our project.

How to create a RACI 

We can create a RACI matrix easily and quickly with using Excel. We need not to learn any new software or technology to create RACI matrix. However we need to understand the roles and who is going to own that particulars tasks to prepare.

  1. Enter all project roles or team member names across the top row.
  2. List all tasks, milestones, and decisions down the left column.
  3. For each task, assign a responsibility value to each role or person on the team.

RACI chart Example

RACI Matrix Definitions

RACI Rules.

Once your RACI chart is complete, review it to be sure it follows these simple rules:

  • Every task has at least one Responsible person.
  • There’s one (and only one!) Accountable party assigned to each task to allow for clear decision-making.
  • No team members are overloaded with too many Responsible tasks.
  • Every team member has a role on each task.
  • If we have a lot of Consulted and Informed roles on our matrix, then we can share the common link to access the project.

Enjoy this blog? Please spread the word :)