Skip to main content
spelling, grammar
Source Link
Jalayn
  • 9.8k
  • 4
  • 41
  • 58

At work we use a task for preparing the environment. It might be confusing for some people but the task we use is very much the same task as the task from a user story. The task dodoes not belong to a user story but do have estimatesis estimated in hours and it has to be agreed on by the product owner to complete in a particular sprintssprint. 

We also use the task for architectural work that does not have an "apparent" business value but considered for properthat adds quality to the product particularly for an existing product with a large code base. 

These might not apply in your work environment but it worked well for us.

At work we use task for preparing environment. It might be confusing for some people but the task we use is very much the same task as the task from a user story. The task do not belong to a user story but do have estimates in hours and it has to be agreed on by product owner to complete in a particular sprints. We also use the task for architectural work that does not have an "apparent" business value but considered for proper product particularly for an existing product with a large code base. These might not apply in your work environment but it worked well for us.

At work we use a task for preparing the environment. It might be confusing for some people but the task we use is very much the same task as the task from a user story. The task does not belong to a user story but is estimated in hours and it has to be agreed on by the product owner to complete in a particular sprint. 

We also use the task for architectural work that does not have an "apparent" business value but that adds quality to the product particularly for an existing product with a large code base. 

These might not apply in your work environment but it worked well for us.

Source Link

At work we use task for preparing environment. It might be confusing for some people but the task we use is very much the same task as the task from a user story. The task do not belong to a user story but do have estimates in hours and it has to be agreed on by product owner to complete in a particular sprints. We also use the task for architectural work that does not have an "apparent" business value but considered for proper product particularly for an existing product with a large code base. These might not apply in your work environment but it worked well for us.