PBS (English)

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Inputs

  • WBS chart

Box-Out.png
Outputs

  • Products obtained in each task.
  • Graphical representation of the different ordered tasks.
  • Significant achieving goals.
  • Identification of work packages belonging to the task.

Star.png
Solution

process-descending-24px.png
Process

PBSenglish2.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 4 hours.
    • To create the Product Pattern: 1 day.
    • To apply the Product Pattern: 2 hours.

bricks.png
Related Patterns

Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • None

stuff.png
Examples

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in any project and used as a tool for organizing, monitoring and estimation. It is a prerequisite to planning the same project, in which starting from the definition of project objectives, you come to the structuring of the different activities and products obtained.

end-flag.png
Resulting context

The project manager will initially have a graphical representation of the different activities that must be carried out for the realization of a project, where such activities will be grouped by work packages, each task will have associated the products obtained.

cloud.png
Issue

The project manager will be able to know that products obtained during each task.

forces.png
Restrictions (Forces)

  • 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.
  • Heuristics for use: If you need urgent application or dispose of some of its functionality.

roles.png
Roles

  • Project Leader

lightbulb.png
Lessons Learned

  • None

award.png
Maturity level

  • Not applicable

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Software requirements definition
  • Background information on Logic Programming and Software Engineering I
  • Accustomed to using a particular paradigm

help-24px.png
Abilities

  • Capacity of Abstraction.
  • Capacity of Analysis.

Information-Sources.png
Information Resources

  • Gonzalo, Agustín y de Amescua Antonio.Gestión del proceso software. Ed. Centro de Estudios Ramón Areces. 2002.
  • DeMarco, Tom. Controlling software projects. Ed Yourdon Press. 1982.
  • Sommerville, Ian. Ingeniería del software. Ed. Addison-Wesley. 2002.
  • Dolado, J.L. y Fernández, L. Medición para la gestión en la ingeniería del software. Ed. RAMA. 2000.
  • McConell, Steve. Desarrollo y gestión de proyectos informáticos. Ed. Mc Graw Hill. 1997.
  • Pressman, R. Ingeniería del Software, Un enfoque práctico, 6ª edición. Ed. Mc Graw Hill. 2005.
  • López-Cortijo y Amescua. Ingeniería del Software: Aspectos de Gestión. Ed. Instituto Ibérico de la Industria del Software. 1998.
  • Garmus, David y Herron, David. Measuring the software process: a practical guide to functional measurements. Ed. Yourdon Press computing series. 1995.