1. User Stories
These are basically product features, requirements, or tasks that add value to the end customer. By adding value, it means, whatever it is, it is something that the end customer would actually pay for. If it is something that does not add value then it should remain a task, subtask, or a requirement.
Example of how a user story is written?
As a customer (user), I want to be able to use my google login credentials so that I don’t have to create a new account.
2. Product Backlogs
In agile, user stories are created for all project requirements and features that add value to the customer and we add them to the product backlog. A product backlog contains all user stories that will be a part of the project but of course in Agile that can be a changing list. Agile follows an iterative process approach so user stories list need not be always the same and there could be an addition to it during the different sprints.
3. Sprint Backlog
A few user stories are taken from your product backlog and added to the sprint. So basically, it is the amount of work you will be doing in the coming two weeks.
4. Story Point
A story point is a metric used to estimate the difficulty of implementing a given user story, which is an abstract measure of effort required to implement it. In simple terms, a story point is a number that tells the team about the difficulty level of the story. The difficulty could be related to complexities, risks, and efforts involved.
An Epic is a big chunk of work that has one common objective. It could be a feature, customer request, or business requirement. It can also be called as a big user story which will usually take more than one sprint to complete
The velocity of an agile project is the number of story points the team delivers over a sprint. After a few sprints, you will be able to average the number of story points your team delivers during a sprint and that is your velocity. Velocity is not what you have planned it is actually what you have delivered.
7. Swim Lanes
Swim lanes are visual representations of the status of user stories on the Agile Kanban Board.
8. Minimum Viable Product
Minimum Viable Product or MVP is the bare minimum that you can deliver to meet your customer expectation.
A Release as the name implies is when you move your user stories to a production environment I.e. when you make them live.
Sprint is a period of time in which the team will deliver a set of stories. A sprint is usually of two weeks but in some cases, it can be for 3-4 weeks as well.