Skip to main content

Let's Blog

 
PM-Now
PM-Central
K-Base
Let's Talk
Let's Blog
  
PM-The Model > Let's Blog > Peer Paper Abstracts  

Peer Paper Abstracts

Modify settings and columns
 
 
 
 
 
  
View: 

Andre Augusto Choma PMP

Ten Ways to SINK a Project

Many projects face problems for multiple reasons: scope problems, lack of planning and bad risk assessment are frequent nightmares on the project manager’s life. The root causes of the problems are diverse, but some difficulties are common to many projects, and, for this reason, should get more attention from the project manager and his/her team. When fighting against the most frequent project enemies, the project manager reinforces his/her risk response planning and increases the chances of success.

This paper shows ten situations that can bring a project to failure, with the objective of alerting the project managers about some risks that are frequently ignored during project planning and execution. In a very humorous manner, this presentation approaches the common causes of problems, and remembers the project manager’s greatest responsibility in risk prevention as the decisive factor of success. This paper also presents suggested course of actions that can be taken from the project manager to face each one of the 10 risk situations to keep the project “above water”.

Outline:
1. Introduction
2. How to sink a project
  2.1 Be vague;
  2.2 Begin the execution as soon as possible;
  2.3 Focus on the team’s work;
  2.4 Don’t document the changes;
  2.5 Exceed the client’s expectations;
  2.6 Risk Management? Counting on your luck is the only way out!
  2.7 The care for quality appears only on the final project stage;
  2.8 Avoid bureaucracy – filling forms are a waste of time!
  2.9 Make the team work hard to avoid delays;
  2.10 Get rid of the paperwork after the project close out!
3. Working towards the success: the project manager’s responsibility on risk prevention;
4. Conclusion

Learning outcomes:
At the end of the presentation, the attendee will be able to:
- understand that the preventive work against risks is crucial for the success of any project, and it must to be done by the project manager. A reactive behavior can cause the project failure, allowing the major risks to happen and 'sink' the project;
- verify some of the main causes that can take the project to failure - some problems are common and can be avoided with the use of the Lessons Learned from the past projects;
- identify practices that must be avoided, and observe how the project manager should place him or herself to challenge some of the common obstacles to success. As the project's leader, the project manager will observe in this presentation how to fight against the 10 presented risks to keep the project 'above water'.


Biography

André is a qualified Civil Engineer, with post graduation studies in Construction Management. His professional experience encompasses Industry Construction and IT Projects, consulting and training.
André is the author of “How to Manage Construction Contracts With Contractors” (PINI, 2005 – www.gestaodeempreiteiros.com.br). He works as a project manager, consultant and instructor on Euax Gestão de Projetos, Joinville-SC-Brazil. Currently, André is working as a consultant on a one-year project in Angola.

James Prater

When Yes doesn’t really mean Yes!

(How do you manage a project when you have team members in 3 countries, who work for 4 different companies?)
Over the last 5 years, Santos, a large oil and gas company based in Adelaide Australia, has been aggressively focusing on growing its business by investing in countries overseas.
As part of this strategy, two off-shore facilities were commissioned in 2006/07 and this paper will discuss the cultural issues associated with project managing the IT components of these projects.
Outline of the presentation

This presentation will discuss the significant cultural and logistical challenges of managing a project, where different parts of the project had to be undertaken in the following countries
• Singapore
• Indonesia (including Jakarta and Batam)
• United Arab Emirates
Whilst the project manager was located in the head office of Santos in Adelaide and the project team were also spread through out the world and finally the engineering component of the project was a production platform, located approximately 40 kms offshore from regional Indonesia.
 
Learning Outcomes
The major outcomes learnt from this project included
• Recognising that the application of cultural norms from Australia to project team members from overseas is fraught with danger
• Recognition that email/sms are useful communication tools but do not replace face to face contact to develop relationships.
• Overseas business travel is not all that it is cracked up to be, nor are some other forms of transport.
• Not to underestimate the logistics of simply getting to the project site, especially once it has commenced production.
• Instilling within the project team a common goal when each of the team members were employed by different vendors is a significant challenge and in some cases impossible to do so.
• How to say yes in a variety of languages!

 
Biography 

Eight years in IT project management roles within the Resources and Manufacturing industries. Currently, employed as a Project Consultant with Santos specialising in managing projects that linking a variety of controls systems to web based reporting software.
Prior to Santos, part of the IT management team at FH Faulding and managed the installation and configuration of the IT systems required for a new warehouse.
Qualifications
Master of Business
Bachelor of Business (Management Information Systems)
Diploma of Computer Programming
Diploma of Business
PMP Certification
PRINCE2 Certification
ITIL Foundation Certification
Professional Memberships
Petroleum Exploration Society of Australia  (S.A. Branch). – National Award for Meritorious Service.
Member of the Australian Computer Society.
Member of the inaugural EDS Mentoring program.
Alumni Association of the University of South Australia
Former Board Member of the Institute of Information Management
Project Management Professional.
 
Marcelo Jenkins

An IT Project Management methodology based on CMMI and PMBOK
 
Several international organizations and bodies of standardization have published a series of models and standards that may serve as guidelines to improve the Information Technologies (IT) processes. For information technology organizations in particular, two models stand out: the Software Engineering Institute's (SEI) Capability Maturity Model Integration (CMMI) and the Project Management Institute's (PMI) Project Management Body of Knowledge (PMBOK).
Both the CMMI and PMBOK are models, not methodologies or processes. Thus, IT managers can use them as guidelines to incorporate good practices into their organizations, but those practices have to be adapted and then adopted into the organizational process.
This presentation describes the experience gained by a large organization in combining the CMMI and the PMBOK to establish and maintain a combined IT project management methodology that comprises practices from both models. We explain how we designed and implemented the methodology, how the practices proposed in these two models were tailored to the needs and available resources in the organization, and summarize the benefits obtained thus far from its use. Our experience shows that the project management practices proposed by the CMMI and the PMBOK are compatible and sometimes complementary. Hence, they can be merged straightforwardly to develop a combined software project management methodology as we did. This design must be performed carefully though since the resulting product must be consistent, non-redundant, and suitable for the organization's environment.
The issues discussed in this presentation should interest organizations that need to improve their project management capabilities. Attendants will learn how to:

1. Combine the CMMI and the PMBOK to design and implement a project management methodology.
2. Compare and contrast the project management practices proposed by CMMI and the PMBOK.
3. Tailor the CMMI and PMBOK practices to the organization’s environment and available resources.

Several international organizations and bodies of standardization have published a series of models and standards that may serve as guidelines to improve the Information Technologies (IT) processes. For information technology organizations in particular, two models stand out: the Software Engineering Institute's (SEI) Capability Maturity Model Integration (CMMI) and the Project Management Institute's (PMI) Project Management Body of Knowledge (PMBOK).
Both the CMMI and PMBOK are models, not methodologies or processes. Thus, IT managers can use them as guidelines to incorporate good practices into their organizations, but those practices have to be adapted and then adopted into the organizational process.
This presentation describes the experience gained by a large organization in combining the CMMI and the PMBOK to establish and maintain a combined IT project management methodology that comprises practices from both models. We explain how we designed and implemented the methodology, how the practices proposed in these two models were tailored to the needs and available resources in the organization, and summarize the benefits obtained thus far from its use. Our experience shows that the project management practices proposed by the CMMI and the PMBOK are compatible and sometimes complementary. Hence, they can be merged straightforwardly to develop a combined software project management methodology as we did. This design must be performed carefully though since the resulting product must be consistent, non-redundant, and suitable for the organization's environment.
The issues discussed in this presentation should interest organizations that need to improve their project management capabilities. Attendants will learn how to:
1. Combine the CMMI and the PMBOK to design and implement a project management methodology.
2. Compare and contrast the project management practices proposed by CMMI and the PMBOK.
3. Tailor the CMMI and PMBOK practices to the organization’s environment and available resources.


Biography

Marcelo Jenkins obtained a B.S. degree en Computer and Information Sciences at the University of Costa Rica in 1986 and a M.Sc. and Ph.D. degrees from the University of Delaware, USA, in 1988 and 1992 respectively.

Since 1986 he has been teaching computer science at the University of Costa Rica. From 1993 until 1998 he coordinated the Graduate Committee and from 1998 through 2001 he was the Chairman of the Department of Computer and Information Sciences.
His research interests are in software engineering, software quality assurance, project management, and object-oriented programming. He has authored more than 30 technical papers on these subjects.

As an independent consultant, he has worked with some of the largest software companies in the Central America region in establishing software quality management systems. In the last 12 years, he has taught several seminars on software quality assurance and software project management in 7 different countries.

Dr. Jenkins is an ASQ Certified Software Quality Engineer (CSQE) and a member of the ASQ Software Division, the IEEE Computer Society, and the Project Management Institute (PMI).

Danny Burns
 
Titan - The journey so far!
Applying requirements management to complex telecommunications network transformations

Phase 1 - Introduction:
The Titan program is a multi year, multi million dollar program within Telstra's Next Generation Network (Wireline transformation) program. 
To support this vast and complex program required creating change. To that end Telstra selected Alcatel - Lucent as Telstra's strategic partner for this program and at the same time introduced a new way of achieving delivery through an Outcome Agreement.
 
Phase 2 - How the Outcomes Agreement (Contract)  Created Change
During this phase we will discuss and focus on a new programme delivery approach with:
" The introduction of an requirements based contract;
" Required Program Level controls for multi year program; and
" The  Outcomes agreement requires the program (people) to facilitate a change of Operating Methodology and culture within both organisations.
Phase 3 - Delivering improvements to infrastructure
During this phase we will discuss what, how our project management approach and tools contributed to improvements to Telstra's Next Generation Network:
" Introduction of a  Systems Engineering Technical Forum;
" Improvement in the Integrated Logistics Support;  and
" Tighter controls around effective change management that limited the changes to entire network.
Phase 4 - Delivering improvements to organisations
During this phase we will discuss why we had a major shift in our approach to project/program delivery:
" Introduced the concept of Capability Releases ( grouping of requirements ) for delivery;
" Introduction of common objectives to support teamwork approach overcoming the traditional customer supplier model
Phase 5 - Conclusion
During this phase we will discuss the learning/benefits delivered by Titan:
" Benefits of a Requirements vs Fixed contract model ;
" Tight configuration control of requirements and change, minimising commercial confrontation;
" Improvements in Programme management and methodology has increased the delivery capability 3  fold with less than double the resources; and


Biography

After a successful career in the RAAF spanning fifteen years working on Mirage and F/A 18 Hornet aircraft Danny joined British Aerospace in 1989 working in the Middle East on Tornado aircraft. During his time in the Middle East Danny was part of Gulf War 1, where he received the Queens Medal while working for the Royal Saudi Air Force.
On returning to Australia in 1993 Danny worked for Defence related companies - such as Australian Defence Industries and RLM  a (Joint Venture between Lockheed Martin and Tenix ) in the areas of training, logistics engineering  before moving into business development.
From there Danny move to Melbourne and in 2003 joining Telstra and is currently the Project Director Delivery - Capability Release for the Titan Program.

 
 
 
Contact Us
Deploy Pty Ltd © 2009
The Noshan Group Pty Ltd