Aún no tienes acceso a esta clase

Crea una cuenta y continúa viendo este curso

Review: organize your tasks!

11/27
Recursos

In this lesson you will read and remember the Concepts we have studied so far.

Challenge: read the Concepts and definition of what we have covered so far to reinforce your knowledge.

Aportes 8

Preguntas 0

Ordenar por:

¿Quieres ver más aportes, preguntas y respuestas de la comunidad? Crea una cuenta o inicia sesión.

Achievable Development Plan: It is always important to align your goals with the Customer’s goals. Stay focused on your Customer’s requirements.

Defining Iterations: It is important you define your Iterations with your team. Iterations should be short, about 30 work days, that way you can catch mistakes quickly.

VELOCITY-Productive time: Velocity is how fast your team can actually work. In other words velocity is a percentage. Given X number of days, how much of that time is Productive work.

Backlog: The backlog is actually just a big board on the wall of your office. You should Use it to keep track on what work’s in the pipeline, what’s in progress, and what’s done.

Milestone 1.0: It is your FIRST MAJOR release, you show your Customer your working, functional Software and you expect to get paid for it.

Break User Stories into tasks: Divide the work into smaller, achievable tasks. By Breaking User Stories into tasks you add confidence to your Estimates and your plan.

Use estimates to track your project: Track your project from Inception to Completion, it is always smart to know exactly where you are and how you are doing.

Update your backlog: Your User Stories and tasks must be moving from the Pipeline to “in progress”, to “completed” all the time. It is important to update the Backlog daily.

Standup Meetings: Small daily meeting you have with your team to inform others of your progress, general feelings and difficulties.

Analyze and Design: Analyzing and designing your software , and pivoting when necessary is going to be an Integral part of the Software Development Process.

Modeling your Design: Once you know you need to adjust remember you must adjust your Backlog, User Stories and Estimates too.

Hi everyone:

This is an example of a sprint Backlog:

Achievable Development Plan
2. Defining Iterations
3. VELOCITY-Productive time
4. Backlog
5. Milestone 1.0
6. Break User Stories into tasks
7. Use estimates to track your project
8. Update your backlog
9. Standup Meetings
10. Analyze and Design
11. Modeling your Design

These reviews are great! More courses should follow this method. It makes it easier for me to refresh some concepts.

Se esta trabajando mucho el curso, incluso cambiando de servidor.

Hi everyone, i want to say that the teacher carlos is too great explaining and also teaching. I understand him everything and finally i think is too usefull the reviews that he mades to us. thanks teacher.

Thank you for the lesson.

The PDF is wonderfull, a good review.