There are some situations.
If a QA team missed some bugs and it's even not founded by anyone since last one year or more than that.
Do we need to consider it as a bug and should we lock it as a bug in sprint or as a story as per agile development methodology ??
I would look at the risk and impact the so called "bug" relates to.
If it's critical and blocks functionality, take it as a bug in the sprint, of it seems more that functionality could be improved I would likely create a story and place it on the backlog.
There the wieght can be determined by the team and see if its relevant to be picked up and implemented.
Even if it's critical, if something is missed by QA team and issue is there in production environment for approx over 2 years.
What is the flow of agile?
So for now according to agile do we need to consider it as a bug or as a story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agile is a guideline, not a strict framework.
Use it to the extend you companies proces is using or the way you within the company see fitting.
Determine your guidelines and process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.