How to translate the requirements of the user to the actual work that needs to be done?

Question

We work with the scrum method. Let's assume the product owner wants a new functionality that allows the user to search the content of the website.

The total work is 8 points and these would be the user stories:

• the user can input search terms (0 points)
• the search results are displayed to the user (8 points)

I want to gain more insight in the progress of the developer. However I cannot break down these stories any further.

I could however rewrite the stories. I feel reluctant because these stories are technical stories.

• add search text box (0 points)
• create index table in the database (0 points)
• make sure the index table is updated when data ABC changes (3 points)
• make sure the index table is updated when data XYZ changes (2 points)
• get results from the database (1 point)
• compose the correct url per search result (2 points)

How do you handle these situations?

Answer 1

You should not break down the stories into other technical stories any further.

During the Sprint Planning Meeting, the team breaks down the stories into tasks. Those tasks are then estimated in numbers of hours.

During the Sprint, you keep track of the number of remaining hours in the Sprint burndown charts.

The stories are for the end-users.

The tasks are for the team (UI Design, Development, Coding, Testing, Documenting, etc.)