Earned Value in Psp 1.1

De productpatterns_wiki
Revisión a fecha de 16:33 22 feb 2015; PfcEsther (Discusión | contribuciones)

(dif) ← Revisión anterior | Revisión actual (dif) | Revisión siguiente → (dif)
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Inputs

  • Tasks and duration
  • calendar
  • Actual planning of the project's evolution.

Box-Out.png
Outputs

  • Evaluation of project progress.
  • Difference between planned and evaluation of project progress, both in costs and deadlines.

Star.png
Solution

process-descending-24px.png
Process

Actividad Valor ganado.jpg

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 6 hours.
    • To create the Product Pattern: 2 days.
    • To apply the Product Pattern: 2 hours.

video-24px.png
Explanatory Video

    • Not applicable

bricks.png
Related Patterns

Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in any project that uses Psp1.1 to facilitate an adequate view of real progress. real.

end-flag.png
Resulting context

The user will get differences between planned and conducted, an evaluation of project progress and templates Psp1.1 Tasks of Planning Tasks and planning Calendar are completed.

cloud.png
Issue

The user will need to monitor the project after making a detailed planning. Progress measures must be collected periodically and differences will be found. In certain milestones progress to take corrective action is reviewed.

forces.png
Restricciones (Forces)

  • System Type: It applies to all types of systems.
  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • System Type to develop: This product can be used in projects in which user requirements are changing.
  • Type of Customer: It must exist or be achieved, the target area development business being involved in achieving it.
  • Programming Paradigm: OO (Object Oriented).

roles.png
Roles

  • Analyst
  • Customer
  • Project Manager
  • System Users

lightbulb.png
Lecciones Aprendidas

  • If a task is not completed during the planned day, when recording earned value every day in the template Planning Calendar, their livestock is 0. When the task is completed, the next day it has the previous won value.

award.png
Maturity level

  • Not applicable

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Accustomed to using a particular paradigm.

help-24px.png
Abilities

  • Capacity of Abstraction.
  • Capacity of Analysis.

Information-Sources.png
Information Resources

  • Cabezas, Luis y otros. EVM: Teoría, práctica e implementación. Ed. INTA. Enero 2008.