Thursday, November 5, 2009

Progressive Elaboration and The Project Management Plan in the PMBOK 4th Edition





Progressive Elaboration and The Project Management Plan in the PMBOK 4th Edition

During last weeks PMBOK course here at Tracasa we covered Chapter 4 and there was a lot of confusion about the process output, Project Management Plan Updates. One of the main reasons for the confusion is that the DFD diagrams show the Plan Updates flowing back to the Develop Project Management Plan process. At first reading, this may seem appropriate but it contradicts a popular interpretation of the integration knowledge area and progressive elaboration of the Project management plan. This interpretation is that you only carry out the process develop project management plan only once per phase iteration. That is to say that the full PDCA cycle is only carried out once per iteration and that the plan updates, which may or may not be subject to change control, update the project management plan directly or in some cases through the directing and executing process.

Several arguments can be made for this way of thinking.
  1. The develop project management plan does not a have a plan updates input
  2. The work of integrating input from the individual knowledge areas which is carried out in develop project management plan process has already been carried out in integrated change control process and hence there would seemingly be redundant work.

An explicit presentation of this view has been made by Muhamed Abdomerovic (thanks for the link to Alberto Goicoechea). We contacted Muhamed and asked if he had gotten input from PMI or PMBOK authors on his conclusion that the DFD flow for Project Plan updates is indeed incorrect in the PMBOK. He tells us that he has not.

We also searched for any other references to this error in the DFD diagrams but so far have not found any.

The more high level view and one more consistent with making the standard more flexible would be that the Develop Project Management Plan can in fact be repeated as needed even in a single phase but it must at least be performed once. Since the PMI view would most likely be that this first use of the process is the most important one, it is this iteration of the inputs and outputs that are focused on and hence diagrammed in the book. If indeed project management plan changes are made they may require re-planning to some degree and this reflects more of a PDCA structure. The Integrated change control would represent the Act phase of the PDCA cycle and the develop project management plan in the follow on cycles of the plan phase.

Which is better? The answer as usual is that it probably depends. In many ways this type of process "short circuit" can be found in other best practices frameworks such as ITIL where some short cuts are taken in the name of efficiency such as the support-operations bridge configuration.

In many real situations there are cases where it may seem like a too costly of an exercise to enter the develop project management plan process for every plan update. On the other hand some plan updates may just be to big and may require it. Maybe this signals a good time to think about using multiple phases in your project.

Wednesday, October 14, 2009

Workshop Gestión de Proyectos, PM Workshop 27 of October




Our friends at TecnoEbro have organized a project management conference on the 27th of October. There are some very interesting talks planned (Full Disclosure: I am speaking about thats right...Trainee programs and certifications ...maybe this will be an exception but I´ll try my best...) in the areas of:
- Case Studies / Experiencias en Gestión de Proyectos
- Methodologies/ Metodologías de Gestión de Proyectos
- Tools/ Herramientas para la Gestión de Proyectos
- Standards and Certifications/ Estándares y Certificaciones para las personas y las entidades

Here is the link to sign up (its free!) http://www.gestoresdeproyectos.es/blog.

Español:

Desde TecnoEbro, junto a CAAR, AERA, IDIA y TECNARA estamos organizando un workshop, cuya participación es gratutita, que tendrá lugar la mañana del día 27 de octubre.

Para realizar la inscripción, así como para conocer todos los detalles de la jornada, les invitamos a visitar el blog preparado a tal efecto:

http://www.gestoresdeproyectos.es/blog

Tuesday, September 29, 2009








Ayer cumplí un hito en el proceso de formación en gestión de proyectos que vengo relizando desde septiembre de 2008 de la mano Mans Shapshak. Este hito ha sido la obtencion de la acreditación Comptia Project+ (http://www.comptia.org/certifications/listed/project.aspx).
No os cuento nada nuevo si os digo que el estudio para este examen exige un esfuerzo suplementario al que requiere la lectura y comprensión de los términos propios de esta disciplina. Sobre todo en lo referente a la metodología basada en el PMBOK del PMI, áreas y procesos de la gestión de proyectos, entradas y salidas a los procesos, roles y responsabilidades...

Personalmente me ha ayudado a:
  • Ordenar las prácticas que venía aplicado a la gestión de proyectos y conocer los riesgos que tiene el no aplicarlas.
  • Ubicar cada una de las tareas que vengo realizando en una de las 9 areas de experiencia y en uno de los 5 grupos de procesos.
  • Poner en práctica algunas de las técnicas que he estudiado.
  • Darme cuenta que todavía me queda mucho por aprender.

Sunday, July 5, 2009

Projects, Programs and Portfolios and the PMO Service Catalog





In the latest edition (4th) of the PMBoK the framing of Projects, Programs and Portfolios has been expanded. Some of the highlights which I found most interesting include:
  • An implication that program managers actively manage project managers while portfolio managers are less hands on and only provide coordiantion.
  • it is normal to have a mixture of individual projects and programs in a Portfolio.

Also there is an expanded section about the Project Mangement Office (PMO) with a basic Service Catalog. We have developed a similar service catalog with basically the same content as can be found in section 1.4.4 :
  • Managing shared resources (This will true for a Strong Matrix or Project Organization)
  • Developing a Project Management Methodology for our Corporate Domains (One of our Favorites)
  • Monitoring Compliance with project management standards, policies and procedures (Normally coordinated with quality departments)
  • Coaching and Training
  • Developing organizational process assets
  • Coordinating Communication across projects (Program and Portfolio Roles)







Tuesday, April 7, 2009

Cuestiones sobre Comptia Project+



Voy a poner aquí algunas cuestiones que he desarrollado en la preparación para la certificación en Comptia Project +. Me ayuda a fijar conceptos y a vosotros a refresarlos.


1- Un WBS es:
A. Una descomposición de trabajos para el proyecto
B. Una lista de tareas a realizar concatenadas en el tiempo
C. Una descomposición de trabajos orientada a entregables
D. Una descomposición de trabajos orientada a presupuesto

2- Cuales de las siguientes frases son correctas respecto a la estimación de costes basada en “phased gate” (Elige varias opciones)
A. Es la forma más rápida de obtener un presupuesto.
B. Es la forma de que el presupuesto sea lo más exacto posible.
C. Siempre aprobarán un presupuesto preparado con esta técnica.
D. La estimación está basada en el WBS

3- La ley de los rendimientos decrecientes (Law of Diminishing Returns) considera:
A. Al aumentar los recursos asignados a una tarea disminuye la duración de la misma.
B. Al aumentar los recursos asignados a una tareas aumenta la duración de la misma.
C. Al aumentar los recursos asignados a una tareas no disminuye proporcionalmente la duración de la misma.
D. Al aumentar los recursos asignados a una tarea disminuye proporcionalmente la duración de la misma.

4- Para la estimación de la duración de una tarea se puede utilizar la técnica PERT. Con esta técnica que entradas se deben obtener.
A. La estimación optimista y la pesimista
B. La estimación máxima y mínima
C. La estimación superior e inferior
D. Ninguna de las anteriores

5- En la elaboración de un presupuesto cuales de estos casos se deben contemplar (elegir varios)
A. Adquisición de Hardware
B. Actualización del Hardware
C. Adquisición de Software
D. Siguientes versiones de Software
E. Instalación del software en los equipos
.
.
LAS SOLUCIONES ESTÁN EN EL SIGUIENTE COMENTARIO
.
.

Sunday, March 29, 2009

PMO 2.0 Survey Report Podcast




Here is a great PM podcast with Cornelius Fichtner, PMP about the PMO 2.0 Survey Report which talks about how the PMO is becoming a "Business Management Center".  Just a few key points to wet your appetite:
  • Many PMOs are getting involved with operations (This seems like an obvious and welcome step to me since so much of operations is actually continuous improvement where each PDCA cycle is really a well .... project. See ITIL and MOF literature for more.)
  • You really need more than 4 people to get an PMO off the ground. (Did somebody say critical mass. Even Dr. House has a staff of 4 ;-) )
Lots more excellent details in the report.

Sunday, March 15, 2009

Project Management is a "sweet spot" of CMMI




Just ran into this excelllent CMMI presentation. Here Keith Heston, a Senior Manager at Accenture, puts CMMI in perspective from a complete quality program. 

For software development point of view with a Microsoft flavour we can even blend in MSF and MOF (actually Keith mentions ITIL). But elements of Six Sigma and product development and general business strategy are also mentioned.

Of course the question comes up "What is the benefit to me for implementing CMMI and how long is it going to take me to implement it.". And natually the Keith answers "it depends." 

And he specifically mentions that it depends on:

  • Where you are starting from as an organization
  • What you priorities are
  • How many resources you want to devote
  • How complex your organization is
  • How many sites do you have
  • How mnay project do you have.

He focuses that Project Management as a "sweet spot" of CMMI.

You can find the audicast of an interview with Kieth Heston here.