No tienes acceso a esta clase

隆Contin煤a aprendiendo! 脷nete y comienza a potenciar tu carrera

Adquiere por un a帽o todos los cursos, escuelas y certificados por un precio especial.

Antes: $249

Currency
$219/a帽o

Paga en 4 cuotas sin intereses

Paga en 4 cuotas sin intereses
Comprar ahora

Termina en:

0D
14H
54M
32S

Organizing your time into user stories and tasks

8/25
Recursos

Puedes tener un proyecto muy claro en sus tareas y priorizado, pero la organizaci贸n del tiempo y el esfuerzo a la hora de desarrollarlo depende de ti. Sigue estos consejos para garantizar un gran flujo de trabajo.

Divide las historias de usuario en tareas

鈥淒ivide y vencer谩s鈥 - Julio Cesar 338 (a.C.)*

  • Breaking user stories into tasks adds confidence and accuracy to your estimates and your plan.
  • Tasks really add another level of detail specific to the actual coding you鈥檒l do for a user story.

Utiliza estimaciones para realizar un seguimiento del proyecto de viaje

  • Track your project from inception to completion.
  • It鈥檚 often best to break out tasks from your user stories right at the beginning of the estimation process, if you have time.
  • This will add even more confidence to the plan that you give tour customers.
  • It鈥檚 always best to rely on the task estimates.
  • Tasks describe the actual software development work that needs to be done and are far less of a guesstimate than a coarse-grained user story estimate.

Actualiza tu Backlog

Mantener tu backlog actualizado es parte de la organizaci贸n que debes buscar con tu equipo de trabajo.

  • 鈥淭he Backlog is an ordered list of everything that is known to be needed in the product鈥 (Scrum guide)
  • The Backlog is a prediction about the functionality in the next iteration.
  • Typically has four columns:
    • User Stories
    • To-Do / Pending
    • Doing / In-progress
    • Done
  • Your user stories must be moving continuously, indicating good velocity and effective work.
  • It is very important to keep the Backlog UPDATED, constant communication is essential. This can be done daily to avoid mistakes.

鈥淐lara y constante comunicaci贸n es clave para el desarrollo de software efectivo- Podemos leer emails y mensajes de texto, pero no la mente de las personas.鈥 - Carlos Arriaga


Contribuci贸n creada por: Kevin Fiorentino.

Aportes 37

Preguntas 0

Ordenar por:

驴Quieres ver m谩s aportes, preguntas y respuestas de la comunidad?

o inicia sesi贸n.

I like his enthusiasm. Great class.

This is so true!!! 馃槂

I really like how Carlos explains

User stories into tasks
Adds confidence and accuracy to your estimates and your plan
Adds a level of detail

Estimates to track your project
From inception to completion

Update your backlog
The Backlog is an ordered list of everything that is known to be needed in the product

Columns
- Forecast: Stories planned to cover throughout the iteration
- To-Do: The ones that are next
- Doing: On Work
Done: Finished

I'm really glad with this course

I am learning also some new words in English, I think they are advanced, thanks Carlos

I really like this class 馃挌

Use estimates to track your project:

  • This will add even more confidence to the plan that you give your customer.
  • It鈥檚 always best to rely on the tasks estimates.

Test question: Is it important to update the Backlog?

Que interesante

excellent

Hello

Thanks 馃槉

like
good
great class!!
yes
hellow

Organizing your time into user stories and tasks User stories into tasks
Adds confidence and accuracy to your estimates and your plan
Adds a level of detail

Estimates to track your project
From inception to completion

Update your backlog
The Backlog is an ordered list of everything that is known to be needed in the product

Columns

  • Forecast: Stories planned to cover throughout the iteration
  • To-Do: The ones that are next
  • Doing: On Work
    Done: Finished Break user stories into tasks:

It鈥檚 about how to divide user stories into individual tasks. (You鈥檙e adding confidence and accuracy)
How things and tasks have to be done.
Tasks really add another level of detail specific to the actual coding you鈥檒l do for a user story.
Use estimates to track your project:
Track your project from inception to completion (Beginning to end)
This will add more confidence to the plan that you give to your customer.

I like his enthusiasm. Great class.

Great I like the way that you explain the topics. I love the way that you speak English.

馃憤馃憤馃憤

Break user stories into tasks:

  • It鈥檚 about how to divide user stories into individual tasks. (You鈥檙e adding confidence and accuracy)
  • How things and tasks have to be done.
  • Tasks really add another level of detail specific to the actual coding you鈥檒l do for a user story.
    Use estimates to track your project:
  • Track your project from inception to completion (Beginning to end)
  • This will add more confidence to the plan that you give to your customer.

how to organize your tasks. understand how to break your user stories down into tasks, how to use estimates to track your project, and how to update your backlog.

how you鈥檒l take very large user stories and sometimes have to break them down into individual tasks. When you break down user stories into tasks, you add confidence and accuracy to your estimates and your plan.

if you process your user stories by having those individual tasks, your final product will be great. So the tasks and those individual tasks really at another level of detail, specific to the actual coding you鈥檒l be doing for a user story.

use estimates to track your project, track your project from start to finish Tells me exactly where I am, and that鈥檚 something you need to do with your estimating process. the fact that you have your user stories and that you have an accurate estimate will give you a better chance of being successful and also deliver your software when
your client is waiting for you.

Track your project fron inception to completion. 馃弫

It鈥檚 very important to priorize the differente User Histori in task to complete each iteration.

Good class and good concepts.

You need convert user stories in task, this is a new level of detail.

Good example to describe or track your project: Google Maps!

The user stories is a salad, and the task are the individual ingredients of that salad.

I loved that analogy!

This words, tasks, requests, tests are very hard to pronunce for me jaja, I feel like an idiot sometimes jaja I鈥檒l keep trying, someday I鈥檒l get it

I would love my SM to speak as clearly as you 鉂わ笍

I really love this phrase:
鈥淐lear and Constant Communication is KEY to effective Software Development, we can read emails and text messages, but not people鈥檚 minds.鈥

I really like your pedagogy.

Nice job

kdndnd

Break big projects into little pieces, that鈥檚 the best way to deal with them

A great tool for this is Trello.