Showing posts with label Scrum Poker.Story Point. Show all posts
Showing posts with label Scrum Poker.Story Point. Show all posts

Wednesday 1 March 2017

Giving Estimation using Story Point

What is Estimation in Agile:-

How much time/effort is going to be taken to do a particular task or requirement Viz User Stories is known as Estimations.
Estimation is a very tricky task.A wrong estimated User Story can defeat the purpose of delivering any working project.

Who all are involved in estimation:-

Different stakeholders such as Product Owner, Developers, QA, UI/UX designer, and other higher management can estimate their effort in sprint planning once the backlog has been prioritized by the Product Owner requirement/story has been groomed.

Estimation Difference within Member’s, Why??

We cannot deny the fact that every member will have different estimations.
This is because every member is taking their individual effort recounting their past experiences or by self instinct that how much time they will take to do that task.
Something may take time for the developer to implement but the same thing can be easy to test for Testers. The same goes for UI/UX designers.

How to estimate a user story from a QA perspective??

Let’s say we have any user story like sorting the price of flights and the Acceptance Criteria as below:-

As a traveler, I can sort flight having price from low currency to high currency.




Acceptance Criteria

i. The flight search should be in ascending order
ii. When no flight available display the message “Please search using different combination”
iii. If two flights are having the same price search then display the flight in alphabetic order

Estimating the above story using story points:-

When we are estimating any story using story points we are using a judgmental approach and define the complexity of the story rather than manual effort in days.
The judgmental effort are done using some progression formula like Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100.

We can use https://www.planningpoker.com/ to estimates our user story which is interactive and easy. Let us suppose the team after the meeting came to the conclusion that the above story is of 5 Story points

Now to estimate the above story as a QA I would take into consideration the following point.

1) As per acceptance criteria, I will write the test case and upload it on Test Management Tool “1 Hour”.
2) To test the whole according to AC I will take another one “1 Hour”.
3) To test on 4 different browsers like Chrome, Firefox, IE 10, and Safari “15 Minutes” each which counts 15*4= 1 Hour.
4) If the change is reflected on webview of Android and iOS application then “15 Minutes” to install the build on each OS and “15 Minutes” each to verify the functionality on each OS. The time will increase if the devices list will increase. Therefor 15 Minutes*4= 1 Hour
5) Now adding 1 Hour to the total estimated task.
There fore total time taken is 1H+1H+1H+1H+1H=5Hours

Interview Experience with AMAZON for the role of Quality Assurance Tester

This role was for Digital/ IoT/Mobile Application based testing :)  Amazon is a dream company and everyone wants to work for that company a...

Popular Posts