Mostrando entradas con la etiqueta Project Management. Mostrar todas las entradas
Mostrando entradas con la etiqueta Project Management. Mostrar todas las entradas

12 feb 2013

Herramientas de comunicación web 2.0 en la Dirección de Proyectos

Estos días, por razones académicas, principalmente, me estoy poniendo al día de mis artículos, publicaciones y contribuciones, en diferentes eventos, congresos y libros en los que he tenido ocasión de participar, durante los últimos años.

Y me he dado cuenta de que todavía no había compartido, a través de mi blog, el documento “Herramientas de comunicación web 2.0 en la Dirección de Proyectos”, que presenté en el 3r Congreso de Ingeniería de Organización, en septiembre de 2009, en Terrassa / Barcelona, junto con Vicenç Fernández, mi director de tesis doctoral y Josep M. Sallan, tutor del doctorado.

Aprovecho, también, para incluir el esquema resumen del documento y que fue la base de la sesión de pósters en la que participé

11 abr 2012

Las tecnologías de la comunicación y la colaboración en los proyectos (Material)

Esta tarde he tenido ocasión de impartir una ponencia sobre ‘Las tecnologías de la comunicación y la colaboración en los proyectos’ enmarcada en el ciclo de conferencias sobre ‘Gestión de Proyectos’ de las Escuelas Universitarias Gimbernat i Tomàs Cerdà (www.eug.es).

Aprovecho para compartir tanto los diferentes videos utilizados durante la sesión como el material de apoyo de la presentación.

 

La comunicación los proyectos (y sus dificultades – humor)

Uso de comunicaciones unificadas en el día a día de una organización

Herramientas de colaboración aplicadas a proyectos

Herramientas colaborativas para un trabajador en movilidad

30 jun 2011

Material “10 aspects to be considered in order to improve success in project management”

Material I prepared and used in the “Project Management” event, this morning, at Foment del Treball (Barcelona).

 

image

I hope it will be interesting for you.

The 10 aspects:

1.Global Vision: “More than PM”

2.Change Management: “Because change is need”

3.Business Case: “Business value of projects”

4.Methodology: “A standard way to do PM”

5.Integrated PM: “A holistic vision of projects”

6.Risk Management: “Be prepared for Murphy”

7.Project Manager: “More than technical skills”

8.Stakeholders: “the human side of projects”

9.Change Management: “Because change is need”

10.IISS: “More than scheduling software”

12 oct 2010

Material of PGPSI classes at University (Project Management)

I’ve published all the material I use in my classes at Technical University of Catalonia – UPC (www.upc.edu), teaching “Project Management and IS Planning and Managament” at the Informatics Enginerring degree (http://www.fib.upc.edu/en.html)

27 ago 2010

Importance of Change Management in IT Projects

Are you concious about the need of change management in IT Projects? No?

CIOs do…

Top 10 CIO Strategies 2013 (From Gartner)

  1. Delivering projects than enable business growth (mission enhancement)
  2. Expanding use of information and intelligence in operations, products or service
  3. Linking business & IT strategies and plans
  4. Leading enterprise change initiatives
  5. Developing or managing a flexible technology infraetructure
  6. Attracting, developing and retaining IT personnel
  7. Building business skills in the IT organization
  8. Building a business process centre of excellence
  9. Improving the relationship between IT and the business (relationship managers,…)
  10. Applying business performance metrics to IT

At last, projects are the way organizations deliver change

17 ene 2010

Smart communications (3) … during telephone/video conferences

Following the recomendations I published in previous posts about smart communications (with emails: http://www.pgpsi.com/2010/01/smart-communication-with-emails-1.html and on the telephone Smart communications … on the telephone (2)) in this one I will cover some rules to apply during telephone and video conferences.

Telephone and video conferences are a very important tools to facilitate virtual communications and hold virtual meetings.

So:

  • Are you organizing the conference? Then familiarize yourself with the technical aspects beforehand. This way you have one less stress factor during the meeting.
  • Related documents should be distributed in advance. Ideally, you have a participant at the other location with whom you can go through possibles critical or difficult points in advance.
  • Even if the agenda is tight, give everyone the opportunity at the beginning to acquaint themselves with each other. Personal contact is an important basis for future positive teamwork.
  • The conference should be conducted in English it the participants are multinational. Avoid side conversations in your mother tongue. This is even more irritating than during a normal meeting and, moreover, impolite.
  • Make sure that only one person speaks at a time. Conciously speak loud and clear, avoing background noises.
  • Minutes should be distributed within three working days (maximum), answering the quetions “Who is to do what and when?”

16 ene 2010

Smart communications … on the telephone (2)

In a previous post in this blog (http://www.pgpsi.com/2010/01/smart-communication-with-emails-1.html), I shared with you a set of ‘good practices’ proposal to improve communications wiht the email.

As I said, email is one of the most used tools in communication processes in companies and projects. And of course, the other is telephone.

In this second post, I want to cover the use of telephone in these processes:

  • Say at the beginning what the call is about and which points you want to address. Give notice of longer phone calls.
  • Prepare important documents. If they could be of use, send them in advance to your counterparts. What objections or questions could the person have?
  • Verbaly summarize the outcome and measures at the end of the phone call. Briefly record the details in writing.
  • Turn on your answerphone when absent from your desk for a longer period. If you have a business cellular phone enter the number in the ‘notes’ address book.
  • When making overseas calls pay attention to the time zone where your counterpart is located. Think beforehand about the English terminoloy you may need.
  • Should you have problems getting in contact with someone abroad by telephone? Try reaching a third person! Call a different person you know at the same place.

24 dic 2009

About Project Management (usefull for CompTIA IT Project + and PMP certifications)

Recently, I found a very interesting web with a lot of resources about official certifications, including CompTIA IT Project+ and PMP (PMI).

They have published a lot of definitions that are very interesting and usefull in order to prepare these two exasms.

I can assure you.

Let mi share with you, some links of its content, grouped by the different subjects of ‘Project Management’.

About Scope Management

About Time Management

About Risk Management

About Stakeholders

About Change Management

About Cost/Finantial Mangement

About Quality Management

About Procurement Management

About Team Management

About Monitoring a project

13 dic 2009

“Earned Value Management”

Extret del blog http://ramoncosta.blogspot.com

One of the most important area in project management is Cost. Project Managers are responsible to identify and manage the budget of the project and its costs.

One of the main techniques to monitor and control costs in a project is the ‘Earned Value Management'.

I will try, in this post to explain some concepts related to this tecnique (EVM).

The actual cost of the project is the sum of the collection of:

  • amount charged on invoices from vendors and consultants
  • the ‘money’ amount assigned to the team members’ hour or the tasks the are completing.

A commited cost is the amount of money approved and assigned to a portion, or the entirety, of a project.

The comparison of the actual and commited cost should reflect on the cumulative budget cost for the entire project.

The key to controlling finances within your project is to safeguard your budget and react to cost variances as soon the appear. When cost variances happen (and sooner or later they will), you will need a plan to analyze the costs and see what offsets may be made to control the total actual costs for the project.

Earned Value (EV) is an excellent system to test, in an ongoing process, if the work completed on a project is in allignment with the budgeted costs of a project. Earned Value is a  measure for project performance.

Earned Value Management (EVM) has a few fundamental values:

  • Budget at Completion (BAC). The amount of money budgeted for your project prior to the start of the project implementation phase. This is the expected cost of the project.
  • Planned Value (PV). It is how much the project should cost to get to a specific point in the schedule. Planned Value used to be known as the Budgeted Cost of Work Schedule (BCWS). For example, if a project has a budget of 100.000€ and month six represents 50% of the project work, the PV for month six is 50.000€.
  • Earned Value (EV). It is representative of the work completed to date regardless how long it took to accomplish it. Earned Value used to be known as the Budgeted Cost of Work Performed (BCWP). The value of the work performed (Earned value i a ‘money’ amount assigned to the value of the work performed by the project team or vendors). The percentage of the work completed allows the project manager to compute the amount of the Earned Value for the work unit. For example, it a project has a budget of 100.000€ and the work completed to date represents 25% of the entire work, its EV is 25.000€.
  • Actual Costs (AC). The amount of money actually incurred by the project to date. Actual Costs is the actual cost of monies the project has required to date. For example, if a project has a budget of 100.000€ and 35.000€ has been on the project to date, the AC of the project would be 35.000€.
  • Cost Variance (CV). The  difference in the amount of budgeted expense and the actual expense. A Cost Variance occurs when the actual cost of the project is different than the EV. For example, your EV is calculated to be 25.000€, but you had to spend 35.000€ to get there.
  • Schedule Variance (SV). A Schedule Variance occurs when the EV is less than the PV. For example, the project is supposed to be worth 75.000€ in month six; however, at month six your EV is only 45.000€. You’ve got a whopping SV of 30.000 €.

Earned Value (EV) can be calculated a few different ways, but the most accessible formula is simple “EV=% of work complete over BAC”. For example, if the project’s BAC is 200.000€ and the work is 10% complete, the EV is 20.000€.

The primary benefit of predicting Earned Value is than project manager can predict if the project is going to be in finantial trouble early on the implementation phase.

To apply the formula, project manager needs to first have completed all the planning stages. The project manager must have the WBS completed with accurate predictions fo the amount of time required for each of the work packages.

Le't’s take an example:

“We have a project that has a budget of 250.000 €. The project is 15% complete, but it should be 20% complete by this point in the calendar and, in addition, the project manager has had to spend 43.000 € of his budget just to get to this point in the project.

Let’s calculate the different values:

  • Budget at Completion (BAC): 250.000 €
  • Actual Costs (AC): 43.000 €
  • Earned Value (EV): 37.500 € (15% of 250.000 €)
  • Planned Value (PV): 50.000 € (20% of 250.000 €)
  • Cost Variance (CV): AC – EV = 43.000 – 37.500 = 5.500 €
  • Schedule Variance (SV): PV – EV = 50.000 – 37.500 = 12.500 €

At last, we have two other indicators (Cost Perfomance Index and Scheduled Perfomance Index) that we can use in order to predict the result of the project.

  • The Cost Performance Index (CPI) is a reflection of the amount of actual cumulative dollars spent on a project’s work and how close that value is to the predicted budgeted amount. To compute the CPI, we divide EV by AC. CPI = EV / AC.
  • The Scheduled Performance Index (SPI) is a formula to calculate the ratio of the actual work performed versus the work planned. The SPI is an efficiency rating of the work completed over a given amount of time. SPI = EV / PV

For example,

  • A project has a budget at completion (BAC) of 209.300€, amnd to date the project has spent 34.500€ on Actual Costs (AC). Based on the percentage of the completed project, which is 15%, the EV is 31.395€. The Planned Value (PV), however, is 36.000€. The project also has a Cost Variance of 3.105€.
    So, the Cost Perfomance Index (CPI) is EV/AC = 31.395/34.500 = 0,91, which means the project is 9% off the target rate of spending for this stage in the project.
  • If the EV is 18.887€ and PV is 20.875€, the SPI (Scheduled Performance Index) is 0.90 (EV/PV) which is less than one, so this project is not on schedule

To predict how much harder you and your project team will need to work to finish the project on time and on schedule, you’ll need to calculate the TCPI (To-Complet Performance Index). If this index is greater than 1, you’ll have to buckle down and work harder. If the result is 1 or less you can make it on your current schedule.

The formula is TCPI = Budget – Earned Value (EV) / EAC – AC, where EAC is Estimated Cost at Completion

Let’s do an example:

  • Let’s assume the BAC of our project is 75.000€ and EV is 5.000€. The Estimated Cost at Completion is 75.000€ and the AC is 7.500€. The TCPI is (75.000-5000)/(75.000-7500) = 103.7%. It means that the project team will have to work 3.7% harder than originally planned to finish on time and on budget.

I know it is hard to understand the first time, but it is easy when you realize the meaning of echa index and value.

Good luck!

19 ago 2009

Microsoft Project Portofolio

Dentro de la Solución "Enterpriser Project Management" de Microsoft, se incluye una potente herramienta, el "Microsoft Office Project Portfolio Server" para poder gestionar la cartera de iniciativas, proyectos y programas de nuestras organizaciones.


Microsoft Office Project Portfolio Server 2007 ayuda a las organizaciones a tomar conciencia de su potencial identificando, seleccionando, administrando y proporcionando carteras que se adaptan a sus prioridades estratégicas.


Office Project Portfolio Server 2007 es un componente principal de la solución Microsoft Office Enterprise Project Management (EPM) y ayuda a obtener visibilidad, comprensión y control de sus carteras de proyectos, programas y aplicaciones.
Office Project Portfolio Server 2007 se integra con Microsoft Office Project Server 2007 para dotar a las organizaciones de una solución de administración de carteras de proyectos, de extremo a extremo.
La puerta de enlace bidireccional permite a los administradores vincular varios servidores Office Project Server a Office Project Portfolio Server 2007, con el fin de proporcionar a los ejecutivos una vista consolidada de todos los proyectos de la organización.

Automatización y cumplimiento de los procesos de administración PPM
Un diseñador de flujos de trabajo intuitivos ayuda a definir y automatizar rápidamente sus procesos de gestión de la administración de la cartera de proyectos (PPM):

  • Definición de flujos de trabajo para someter cada proyecto a los controles de gestión adecuados a lo largo de su ciclo de vida.
  • Aplicación de métodos de prácticas recomendadas y utilice plantillas predefinidas para administrar eficazmente todas las carteras de proyectos, programas y aplicaciones.

Consolidar y estandarizar la recopilación de datos

  • Personalización de los formularios para agilizar y estandarizar la recopilación de datos acerca de las inversiones de su organización.
  • Definición de plantillas para estandarizar la recopilación de datos y los parámetros de cada inversión: proyecto, programa y aplicación.
  • Consolidación de todas las inversiones en un repositorio central para ayudar a garantizar que los ejecutivos obtengan visibilidad, comprensión y control en toda la cartera.
  • Captura de todas las solicitudes de proyectos y desarrollo de casos prácticos detallados de acuerdo con los procesos de gestión de su organización.

Priorizar y evaluar eficazmente las inversiones competitivas

  • Uso de técnicas de prácticas recomendadas para derivar automáticamente las puntuaciones de prioridad y desarrollar gráficos intuitivos para ayudarle a evaluar eficazmente las inversiones competitivas desde diversos ángulos.
  • Definición y priorizació, objetivamente, de la estrategia de negocios de su organización.
  • Derivación, automáticamente, de las puntuaciones de prioridad como el valor estratégico, el valor financiero, el riesgo, la adecuación a la arquitectura y el rendimiento operativo para evaluar objetivamente los proyectos, programas y aplicaciones.
  • Uso de puntuaciones de prioridad para generar gráficos intuitivos y evaluar eficazmente las inversiones competitivas incluidas en la cartera.

Seleccionar las carteras que mejor se ajusten a la estrategia de negocios

  • Optimización y selección de las carteras que mejor se ajusten a las prioridades estratégicas de su organización. La interfaz es fácil de usar; además, los métodos incrustados de prácticas recomendadas y técnicas de análisis le ayudan a asegurarse de que selecciona las inversiones adecuadas para su empresa.
  • Empleo de sofisticados algoritmos de optimización para seleccionar la mejor cartera bajo diversas limitaciones presupuestarias, como costos y equivalentes a tiempo completo (FTE).
  • Identificación de las restricciones que impiden que la cartera alcance la frontera de eficiencia.
  • Calculo automático del nivel de ajuste de la cartera con la estrategia de negocios de su organización.
  • Obliga a utilizar un enfoque racional en vez de emocional para seleccionar las carteras.

Administrar eficazmente el rendimiento de la cartera

  • Permite medir y realizar un seguimiento del rendimiento de cada inversión a lo largo de su ciclo de vida para ayudar a asegurarse de que se consiguen los beneficios previstos.
  • Crear varias tarjetas de puntuación de las carteras para administrar las carteras activas y realizar un seguimiento de las mismas.
  • Ver detalles desde el nivel de cartera para obtener el informe de estado más reciente de cada inversión.
  • Realizar informes de estado periódicos para medir el rendimiento de un proyecto, programa o aplicación a lo largo del tiempo.
  • Utilizar flexibles generadores de informes para crear y publicar plantillas que sirvan para estandarizar y agilizar la elaboración de informes en toda la organización.

Y algunos links por si queréis más información:
http://office.microsoft.com/es-es/epmsolution/HA101655113082.aspx
http://office.microsoft.com/es-es/products/HA101656493082.aspx?pid=CL101729493082
http://office.microsoft.com/es-es/projectserver/FX100739843082.aspx
http://office.microsoft.com/es-es/epmsolution/HA101656443082.aspx?pid=CL101935313082