Skip to main content
1 of 5
user22
  • 215
  • 1
  • 3

How should we handle extra cosmetic features in scrum sprints

I was reading the scrum documents and it says that the tasks in sprint should be ship ready

But i am confused with this. Suppose in sprint 1 the task was user registration form

Now i can add as much detail in that like

For example

  1. i can show the simple form with feilds without any fancy styling and mark them as done

  2. I can just do client side validation as mark as done but server side is also the option or both

  3. i can also add some jquery fancy toll tip , hover over , captha, colors labels for the form

4.Then there is whole lot of styling about how to show error messages on screen

I can do endlessly on one topic. So how do we divide that and when i can think of that as shipping ready.

Or do i need to write each smallest possible thing like showing errors , popup or light box text as subtasks and put them as sprint. This would lead to 1000s of tasks for whole project.

I mean then again if some work for IE and some for FF then again do i need to divide those as tasks as well. because time has to be spent on them and when manager asks me what u did in those time then i wont have any task to tell but in reality they all are part of User registration

user22
  • 215
  • 1
  • 3