A good user story comprises a description as well as set acceptance criteria. It should be a piece that can be completed in a SPRINT and has the fewest dependencies POSSIBLE. Within the sprint's constraints, the team should be able to build and test while also delivering estimations. In a nutshell, the INVEST principle is followed by good user stories.

• I stands for Independent - The user story should be such that the team members are less reliant on others
• N stands for Negotiable - It should describe the functionality and is subject to AGREEMENT between the Team and the PRODUCT Owner.
• V stands for Valuable - It should add value to the customer's experience.
• E stands for Estimable - It should be such that the time requirement can be approximately estimated.
• S stands for Small - It should be small enough so that the team can complete it in a sprint.
• T stands for Testable - It should have good acceptance criteria.

During backlog REFINEMENT or sprint preparation, the scrum master can assist the team in producing good user stories so that they can be picked up for the commitment.