Category: Project Management


As we continue to face the realities of social distancing, isolation, and quarantining in the wake of the COVID-19 pandemic, health care organizations are seeking effective and timely solutions for addressing epidemic situations. Ideally, these solutions would greatly reduce the risk of exposure to infection for vulnerable populations and health care workers while still allowing for the provision of adequate care to patients. Telehealth is an ideal solution for the management of communicable diseases –aiding in remote assessment and provision of care for the infected as well convenient access to routine care for patients who are not infected (Smith, Thomas, Snoswell, Haydon, Mehrotra, Clemensen, & Caffery).  Zhou, Snoswell, Harding, Bambling, Edirippulige, Bai, and Smith also cite the psychological side effects of COVID-19 that potentially could affect patients as well as clinical and nonclinical staff – stress, anxiety, burnout, depressive symptoms, and the need for sick or stress leave. These all underscore the need for the provision of mental health support to aid well-being and cope with acute and postacute health requirements more favorably – aspects that telehealth has been shown to treat (Zhou, Snoswell, Harding, Bambling, Edirippulige, Bai, & Smith). Additional motivating factors include the decision of The Centers for Medicare & Medicaid Services (CMS) to issue an 1135 Waiver and expanded telehealth coverage for all Medicare patients during the COVID-19 pandemic, clearing the way for evaluation and management of most patients (Lee, Kovarik, Tejasvi, Pizarro, & Lipoff).

While all of these factors further the argument for adoption of telehealth treatment, some significant barriers to implementation may exist in your organization that may need to be addressed. These include the existence of suitable technology within the organization, provider willingness to accept this technology as a solution, provider credentialing, billing and reimbursement considerations, as well as lack of a supporting infrastructure within the hospital.  I list these considerations in order to promote the analysis of the readiness of your organization to implement telehealth as not only a short-term solution for the current COVID-19 crisis, but as an ongoing strategy to meet crises in the future.

 

Lee, I., Kovarik, C., Tejasvi, T., Pizarro, M., & Lipoff, J. B. (2020). Telehealth: Helping Your Patients and Practice Survive and Thrive During the COVID-19 Crisis with Rapid Quality Implementation. Journal of the American Academy of Dermatology.

Smith, A. C., Thomas, E., Snoswell, C. L., Haydon, H., Mehrotra, A., Clemensen, J., & Caffery, L. J. (2020). Telehealth for global emergencies: Implications for coronavirus disease 2019 (COVID-19). Journal of Telemedicine and Telecare, 1357633X20916567.

Zhou, X., Snoswell, C. L., Harding, L. E., Bambling, M., Edirippulige, S., Bai, X., & Smith, A. C. (2020). The role of telehealth in reducing the mental health burden from COVID-19. Telemedicine and e-Health.

There are many implications involved with ignoring the data or choosing to overlook the outcome knowledge at one’s disposal. However, we often punish bad outcomes without truly understanding the bad decisions that led to them. See the story of Husband E. Kimmel, Commander in Chief of the United States Fleet during the Pearl Harbor attack in 1941, who was summarily relieved of his command ten days later. Fischoff wrote of experiments conducted in which subjects were asked to judge historical events that, “a past which is inordinately barren of surprises provides an inordinately weak test of the hypotheses applied to it (Popper, 1965). The judge who perceives a relatively surprise-free past may feel little compulsion to change the hypotheses which guided him in viewing that past. Thus, the very outcome knowledge which gives him the feeling that he understands what the past was all about may prevent him from learning anything from it.” (Fischhoff, 1974). Something to consider as we read Lynda Bourne’s Beware the Dangers of Technical Debt.

Fischhoff, B. (1974). Hindsight-foresight: The effect of outcome knowledge on judgment under uncertainty. PsycEXTRA Dataset, 1-29. doi:10.1037/e459202004-001

From Voices on Project Management:
By Lynda Bourne

Have you ever experienced technical debt on a project? As the debt builds up, everything looks good from the outside. However, when the crunch comes and that debt has to be repaid, a major reversal in fortune can occur.

Technical debt refers to the costs of having to go bac…

from
Voices on Project Management https://ift.tt/32zYfyZ

I was recently posed the question as to whether I thought electronic medical records will improve healthcare data collection. As an advocate for technological innovation, I believe that electronic medical records do have the potential to improve data collection. There are some hurdles to overcome, however, in order for that potential to be fully realized. My day-to-day interactions with various healthcare leadership groups have made me aware of the multitude of pressures they face requiring accurate data to make well-informed decisions. Strome states in the book, Healthcare Analytics for Quality and Performance Improvement that, “improving quality in a modern health care organization to the extent and at the pace necessary without the benefit of the information derived from Health Information Technology would be an onerous task” (Strome, 2013, p.7). Electronic medical records can put the information into leaderships’ hands. However, implementation of an EMR is not an end, necessarily, but the means. The roadblocks to effective utilization of these systems, in my opinion, include a health system’s ability to manage the voluminous data collected, to be able to identify and focus on the key data elements necessary for measure, and the ability to share this information across the health care system.

Strome, T. L. (2013). Healthcare analytics for quality and performance improvement. John Wiley & Sons.

I have enjoyed the sport of running for many years, but I am a virtual neophyte when it comes to the analytics of the activity. Several years ago, I invested in a simple, wrist-worn gps device that doubles as a heart-rate monitor, and have been routinely logging my runs via a web-based application. It is only recently, however, that I have taken to analyzing my progress, and it has allowed me to set goals to try and improve my outcomes. As I set about monitoring my PR’s, it occurred to me that I had been contributing to the proliferation of the internet of things, or the connection of a myriad of physical, smart objects to the internet. This particular, personal connection allows for access to remote sensor data. The promise of this type of analytics has lead to a vision of a global infrastructure of networked physical objects with unprecedented connectivity and the gathering of massive amounts of data. The internet of things is ubiquitous, and its implications with regard to healthcare data, of which I have been closely involved with over the past several years, have not escaped me. Consider what types of data the medical community is on the cusp of collecting now: from infant monitors to insulin injection and prescription pill trackers – to what will one day be collected outside of the domain of the hospital on a personal level via the internet of things. This technology represents a highly diverse volume of data driven by a large number of potential participants and a wide range of measured variables. Digitized medical data has become so voluminous that it threatens to become unmanageable. Like my wrist-worn, running gadget, the consequence of a wearable, consumer-level, health data collecting device is the propagation of a large amount of “big data” that is complex, diverse, and timely. Debate concerning big data itself has become dernier cri, and it has been the subject of both sanguineness and condemnation. But, will we ever really be able to do anything with the data, particularly from a healthcare standpoint, and do we really understand how it might change the world?

Understanding begins with a definition. Big data is data that exceeds the storage and processing capacity of conventional database systems. Think in these terms: the total accumulation of data over the past two years—a zettabyte—dwarfs the prior record of human civilization (Shaw, 2014). Because it so unwieldy, new procedures must be found to process it (Dumbill, 2012). An important distinction is that that Big Data not only exists in massive amounts, but that it is highly dynamic: it comes in many different forms (structured, unstructured and semi-structured), its content is constantly changing, it exists in many locations throughout electronic space, and it is stored in perpetuity. It is not intended to answer a single question, but the queries against it are protean. The term “big data” was first coined by NASA researchers Michael Cox and David Ellsworth, who wrote in Application-Controlled Demand Paging for Out-of-Core Visualization for the proceedings of the VIS97 IEEE Visualization ’97 Conference that “data sets are generally quite large, taxing the capacities of main memory, local disk, and even remote disk. We call this the problem of ‘big data’” (Cox & Ellsworth, 1997). Fast-forward to 2008, when researchers Bryant, Katz, and Lazowska estimated that big data’s revolutionary effect would equal that of the advent of search engines and the manner in which technology has transformed how we access information. “Big data computing,” They write, “can and will transform the activities of companies, scientific researchers, medical practitioners, and our nation’s defense and intelligence operations” (Bryant, Katz, & Lazowska, 2008). Considering the size and breadth of the healthcare sector, one realizes that it is an industry that has historically generated large amounts of data. In the last five years alone, it has witnessed an explosion of information from sources as diverse as decision support systems, electronic health records, sensor and monitoring systems, and social media. “Data from the U.S. healthcare system alone reached, in 2011, 150 exabytes,” report Raghupathi, Wullianallur, and Raghupathi, “at this rate of growth, big data for U.S. healthcare will soon reach the zettabyte (1021 gigabytes) scale and, not long after, the yottabyte (1024 gigabytes)” (Raghupathi, Wullianallur, & Raghupathi, 2014). It will also increase costs: Burke reports that 2013 spending on big data was projected to top U.S. $34 billion (Burke, 2013). However, this is offset by the significant benefits that are expected to be realized by healthcare organizations. It is estimated that big data analytics stands to enable more than $300 billion in savings per year in U.S. healthcare, “two thirds of that through reductions of approximately 8% in national healthcare expenditures” (Raghupathi, Wullianallur, & Raghupathi, 2014, p.2). The majority of savings is projected to come in the areas of clinical operations, R&D, public health, decision support, and device/remote monitoring.

The potential savings associated with healthcare data analytics makes it an attractive pursuit. However, in order to realize these benefits, organizations seeking to leverage data provisioning must overcome a number of challenges. An introduction to big data considerations in healthcare can only touch upon some of these demands, but specific solutions must be sought after in order realize the value from data. It is important for organizations to know the history of given data, and, ultimately, how trustworthy it is. Data is useless if its validity and reliability cannot be confirmed, and it is important to understand the background and conditions the information was collected under. Organizations must also be prepared to allocate the necessary resources and expertise to manage big data analytic initiatives. Solutions must be scalable such that they can handle massive growth of data or are interoperable with other systems and can exchange and interpret shared information. Addressing these and other considerations is the point of departure to changing the way healthcare decisions are made and, potentially, redefining the industry.

 

 

Bryant, R., Katz, R. H., & Lazowska, E. D. (2008). Big-Data Computing: Creating Revolutionary Breakthroughs in Commerce, Science and Society.

Burke, Jason. Health Analytics: Gaining the Insights to Transform Health Care. Vol. 69. John Wiley & Sons, 2013.

Cox, M., & Ellsworth, D. (1997, October). Application-controlled demand paging for out-of-core visualization. In Proceedings of the 8th conference on Visualization’97 (pp. 235-ff). IEEE Computer Society Press.

Dumbill, E. (2012). Big data now current perspectives from O’Reilly Media. (2012 ed.). Sebastopol, CA: O’Reilly Media.

Raghupathi, Wullianallur, and Viju Raghupathi. “Big data analytics in healthcare: promise and potential.” Health Information Science and Systems 2.1 (2014): 3.

Shaw, J. (2014, March). Why “Big Data” Is a Big Deal. Understanding big data leads to insights, efficiencies, and saved lives. Retrieved from http://harvardmagazine.com/2014/03/why-big-data-is-a-big-deal

 

AtekPC Project Management Office Case Study

Part One. What were the changes in AtekPC’s business environment that caused the company to introduce a PMO? Based on your assigned readings and research do these appear to be appropriate reasons for developing a PMO? Why or why not? Limit your response to one page.

The AtekPC Project Management Office Case Study presents a business entity faced with decreased sales and profitability due to a maturing Personal Computer market. AtekPC, once profitable and an industry leader, found itself behind the curve in areas of new technology such as mobile phones, PDA’s, and web-based applications. Costs were up, resources were becoming limited, and competition among pc manufacturers grew fierce. Harold Kerzner points out in his book, “Using the Project Management Maturity Model: Strategic Planning for Project Management”, that to be to be truly successful, management must have a repeatable process in place: “As economic conditions deteriorate, change occurs more and more quickly in business organizations, but still not fast enough to keep up with the economy. To make matters worse, windows of opportunity are missed because no project management methodology is in place” (Kerzner, 2005). Atek realized it was necessary to begin strategically placing itself for the future.
The environment that AtekPC has found itself in has accelerated the company’s maturity level, therefore making the development of a PMO a viable option. As J. Kent Crawford points out in his book, “The Strategic Project Office”, a PMO should be considered a suitable solution for a struggling company in AtekPC’s environment because, “they allow companies to make the most of slim resources: streamlining the portfolio, accurately forecasting resource availability, and allowing changes in strategic focus necessitated by economic factors to be seamlessly carried out because the project portfolio management processes add nimbleness to the organization” (Crawford, 2011).

References for Part One:
Crawford, J. K. (2011). The strategic project office. CRC Press.
Kerzner, H. (2005). Using the project management maturity model: Strategic planning for project management . (2 ed., p. 11). Hoboken, NJ: John Wiley & Sons.

Part Two. Draft a program charter for AtekPC utilizing your reading assignments, outside research, and the guidelines and model charter linked to this week’s lecture and attached below). Limit your responses to 3 pages, not including end notes, supporting documentation and refererences.

Program Charter Document
AtekPC
________________________________________
Program Sponsors Organization Role Contact Information
Xxxx Xxxxx CEO (xxx) xxx-xxxx
Xxxx Xxxxx Senior Vice President (xxx) xxx-xxxx
Mark Nelson PMO Manager (xxx) xxx-xxxx
John Strider CIO (xxx) xxx-xxxx
Richard Steinberg Dir. Of Application Development (xxx) xxx-xxxx
Steve Gardner Manuf. Systems Manager (xxx) xxx-xxxx
Larry Field Dir. PM Support Group (xxx) xxx-xxxx

Program Charter History
Version Date Author Change Description
x.xx xxxx John Strider Created 3/3/2007
x.xx xxxx Mark Nelson • [revision.1 xx/xx/xxx]
• [revision.2 xx/xx/xxx]
• [revision.3 xx/xx/xxx]

Introduction and Background
AtekPC is a mid-sized U.S. PC manufacturer founded in 1984. 2006 sales equaled $1.9 billion. The company employed 2100 full-time employees and an additional 200 part-time workers. By 2007, AtekPC found itself in the midst of an industry-wide decrease in sales and profitability. PC makers in general were forced to deal with a transition from a growth industry to that of a maturing industry by seeking out new markets for growth opportunities. Due to this environmental change and to remain competitive, it has become necessary for AtekPC to refocus its efforts in areas such as cost control, manufacturing efficiency, resource allocation, and project management methodology. Historically, the latter had been accomplished in an informal manner, with Lead Analysts acting as impromptu project managers. Senior Management realized that a centralized, Project Management Office was necessary to focus efforts in the areas of improvement and enhancement via project management and coordinate the organization’s enterprise-oriented functions.
________________________________________
Program Organization and Governance
The Project Management Office will report directly to the AtekPC CEO. The Senior Vice President will act as Executive Sponsor. Program Sponsors include Larry Field, Richard Steinberg, and Steve Gardner. Mark Nelson will oversee the Program Management Office as the Program Manager.
________________________________________
PROJECT SCOPE
Goals and Objectives
Goals Objectives
The Project Management Office will provide company-wide project management support through consulting, mentoring, and training while promoting portfolio management and PM standards, methods, and tools. 1. Reduce costs and more effectively utilize resources.
2. Work within the AtekPC culture in order to promote Project Management methodology and overcome cultural resistance.

Program Boundaries, Constraints, and Assumptions
There are a number of critical factors to the success of the PMO. The PMO must gain executive support and authority from leadership. It must also gain support across functional lines and end-users. There are a number of Boundaries, Constraints, and Assumptions that will effect the outcome of these factors:
• PMO purpose and responsibilities must be clearly defined
• Inconsistent executive support for the PMO initiative
• Company culture limitation.
• The PMO has a small window of time to prove its value – it cannot provide a quick fix to immediate problems that require long-term solutions.
Project Deliverables
Deliverable
• Obtain input on the program charter from stakeholders and sponsorship
• Present a refined Program Charter
• Strategic Planning Process within first six months
Stakeholder Expectations
Stakeholder Expectations
Leadership/Sponsorship Gain and maintain support for the PMO and resolve discrepancies and conflicts, particularly in the areas of budgeting and resources. PMO initiatives will reduce costs and improve efficiencies.
Project Manager Responsible for setting the standards and policies for the various projects. Plan and execute the work of the project.
Department Heads Provide staff members to the project effort
End User PMO will not be a barrier to “doing real work”
________________________________________
Finance and High Level Budget
According to a 2012 survey conducted by Project Management Solutions, Inc., PMO’s directly contributed to a 15% cost savings per project, or an average of US$411,000 savings per project. Additionally, 25% more projects were delivered under budget where a PMO was involved (The state of, 2012). With these figures in mind, the PMO must set a realistic baseline based on the organizations current state, define goals for improvement, and measure results(Fister Gale, 2011).
Project Risks
Unable to meet goals due to Inadequate Resources
Cultural and political environment not conducive to PMO success
PMO unable to prove its value in short time frame

References for Part Two:
The state of the pmo 2012. In (2012). A PM SOLUTIONS RESEARCH REPORT. Project Management Solutions, Inc.

Fister Gale, S. (2011, August). The pmo: Something of value. PM Network, 25(8), 37.

Assignment 1 asks us to consider several questions concerning NBT, a large satellite development project which primarily services the National Oceanic and Atmospheric Administration (NOAA). The case focuses on the plight of Sarah, recently hired as the project’s Deputy Project Manager for Resources (DPM/R). Sarah faces many issues as she takes over the beleaguered project, including an Inspector General audit involving a year’s worth of uncosted residual funds from nine previous fiscal years which has come under congressional scrutiny.

Question 1. In the NBT case, how realistic is the budget request that was given to NOAA prior to Sarah’s arrival on the project? Describe how you would determine the actual budget based on the facts given and drawing upon the tools and techniques from your prior project management courses:

The budget request given to NOAA prior to Sarah’s arrival on the project is not necessarily unrealistic, in my opinion, despite the positive residual funds from recent years. NBT could benefit from the implementation and commitment to earned value project management. Sarah must follow the steps in developing an earned value project baseline, as defined by Quentin W. Fleming and Joel M. Koppelman in their book, “Earned Value Project Management”. Those steps are:
• Define the project scope
• Plan and schedule the work
• Allocate the resources
• Form the project baseline
In order to carry out these steps, Sarah must gain the commitment of vendors such as Acme Space Company to update the detailed schedules and drawings so that the contractor’s master schedule would reflect the true status of the project. As Fleming and Koppelman point out, “earned value is dependent upon the project’s scheduling system to provide the mechanism for measurement of performance. A project scheduling system will, by definition, reflect the project’s scope of work, and then place all the defined works tasks into specific time frame for execution” (Fleming & Koppleman, 2010). These activities lead to the establishment of the Performance Measurement Baseline and allow for the management of reserve funds.

Question 2. How could a well organized Project Management Office (PMO) have avoided the problems that arose in the NBT Project? In responding to this question draw upon the various strategies and best practices for PMOs discussed in Kendall and Rollins. Explain how as a Program Manager you would have structured your PMO so these problems could have been identified and dealt with early on. Would you recommend an Authoritative PMO as discussed in chapter 2 of Kendall and Rollins, or would another type of PMO work better? How would you convince your CEO that a PMO would have prevented the problems that arose in the NBT project?

The problem with the greatest potential to cause the largest overrun for the project, in my opinion, is the lack of commitment to proper earned value management of the project by the Acme Space Corporation and individuals such as Sam, the NBT Deputy Project Manager. There is not one single issue, but a number of them that feed into this problem. These issues include Acme’s master schedule not always reflecting the true status of the project, the lack of documentation of outstanding engineering changes that should have been facilitated by Sam, NBT’s Deputy Project Manager, and the fact that Acme Space Company would not reflect proposed changes in the performance measurement baseline until they were negotiated. Referring to Fleming and Koppleman, “controlling a baseline requires both information and an information retrieval system. Each action that alters or potentially alters the approved baseline needs to be carefully tracked, so that the project manager may make a conscious decision to approve or reject each change” (Fleming & Koppleman, 2010, p. 109). As stated previously, Sarah must gain a commitment from all parties involved to log any changes that may impact the project’s performance baseline. In order to gain this commitment, Sarah must rely on her collaborative relationship with project sponsorship in order to leverage the required behavior from Acme. Authors Ian Sutherland and Kevin McGreal define the leadership component of project sponsorship as the use of “influence, power and authority to facilitate the resolution of strategic issues and risks that the Project Manager is unable to control or mitigate” Further, sponsorship can assist in, “defining the expected values and behaviors that should guide the management of the project” (Sutherland & McGreal, 2005).
Question 3. NBT lacks what Kendal & Rollins describe in their book, Advanced Project Portfolio Management and the PMO: Multiplying ROI at Warp Speed, as “a centralized organization dedicated to improving the practice and results of project management” (Kendall & Rollins, 2003 p. 7). The project relies on individual management – with little or no collaborative effort designed to facilitate the management of projects on one level, and improvement of management of the entire enterprise in order to afford an organizational focus on improving the management of projects, programs, and portfolios. NBT requires a cultural change throughout the organization (Crawford, 2011). Kendall & Rollins point toward the importance of looking at “the entire collection of an organization’s projects (the project mix) and how it is linked to achieving the goals of the entire organization, not just one functional area” – this is an area where NBT is lacking (Kendall & Rollins, 2003). With this consideration in mind, I would structure a Project Management Office primarily with the task of facilitating access to and communication between NBT Leadership and the Project Managers – and the Project Managers and the Functional Managers within the vendor organizations. It is clear that the project lacks maturity with respect to project management tools and, with respect to this fact, the PMO should emphasize commitment to development of a work breakdown structure and earned value management. Considering the issues that NBT has experienced, particularly the uncosted residual funds, structuring the PMO with an emphasis on through-put, rather than cost containment, would have a better chance of bringing the project back on track.
NBT’s problems are, most likely, not unusual for large-scale projects and illustrate a common lack of commitment to the procedures, methodology, and standards for managing a project. The principle obstacle that Sarah faces is the difficulty in effecting a cultural change within NBT in order to establish commitment to the monitoring and controlling aspects of project management.

References:
Crawford, J. K. (2011). The strategic project office. (2nd ed.). CRC Press.
Fleming, Q. W., & Koppleman, J. M. (2010). Earned value project management. Project Management Inst.
Kendall, G., & Rollins, S. (2003). Advanced project portfolio management and the pmo: Multiplying roi at warp speed. J Ross Pub.
Sutherland, I., & McGreal, K. (2005). Defining effective sponsorship for complex projects. Paper presented at Pmi global congress proceedings, Edinburg, Scotland

One of my favorite quotations associated with projects and project management is a passage in author James P. Lewis’ book, “Fundamentals of Project Management, Developing Core Competencies to Help Outperform the Competition” in which Lewis refers to quality expert Dr. J. M. Juran’s definition of a project as “a problem scheduled for solution”.  Juran’s definition refers to the temporary nature of a project, but it also touches upon what I believe to be one of the fundamental, underlying strengths of project management:  its ability to solve problems.  We know through popular culture that NASA’s project to save the crew of Apollo 13 began with the fateful words, “Houston, we have a problem”.  Lewis reminds us that “a problem is a gap between where you are and where you want to be, with an obstacle that prevents easy movement to close the gap” (Lewis, 2002).   Project management can be viewed as a methodology that utilizes knowledge, tools, and skills to help avoid the obstacle and a stakeholder as anyone with an interest in the opportunity gap being closed. Indeed, project management utilizes project risk management principles in order to help reduce problems, thereby ensuring a stakeholder’s investment in a project is fully maximized (Kanabar & Warburton, 2008).

Strong leadership is a necessary attribute that a successful Project Manager should possess, and one can demonstrate leadership by being an effective problem-solver, among other things. There are a number of problems, or obstacles, encapsulated within the microcosm of the project that must be effectively handled, whether they be logistical, cost-associated, or interpersonal. Certainly, every manager is faced with these constraints. In order to evaluate a given strength of project management, one must accept that it is a means to an end.  Each stakeholder recognizes that a gap exists between where the organization is at present and where it wants to be (the problem).  Not all problems are bad – was it Bob Maynard who said, “All problems are opportunities in disguise”? So, project management becomes a means to achieve the desired outcome. Like a journey from one destination to another, PM provides a clear and concise road map. It maps out the intended route, the conveyance that will be utilized to make the trip, and a metric for determining when the destination will be achieved and how successful the team was in achieving it. All of this folds back into my very generalized analysis of strength as success factors that help determine whether the gap is closed and the desired outcome is achieved.

Kanabar, V., & Warburton, R. D. H. (2008). Mba fundamentals project management. New York: Kaplan.

Lewis, J. P. (2002). Fundamentals of project management, developing core competencies to help outperform the competition. AMACOM/American Management Association

Project managers and project teams that function globally must develop a sound communication strategy in order to ensure success. Author Jean Carlo Binder, in his book, “Global Project Management: Communication, Collaboration and Management Across Borders”, extols the virtues of developing a good strategy early on in order to “reduce misunderstandings between stakeholders from different country and company cultures communicating over distance. The main interested parties must work together to define this strategy, creating the project communications management plan”(Binder, 2007). Binder lists the three main steps to prepare a global communications strategy as “identifying the types of information to be communicated, gathering the communication requirements from the key stakeholders, and determining how the communication will effectively happen” (Binder, 2007).  Just as organizations have learned that “effective communication among people from the same culture is often difficult; ours and other businesses must accept that it is extremely difficult when attempting to communicate with people from a different culture who do not speak English, and have different attitudes, ideas, assumptions, perceptions, and ways of doing things. One’s chances for miscommunication increase enormously “(Adekola & Sergi, 2007).

Adekola, A., & Sergi, B. (2007). Global business management: a cross-cultural perspective. (p. 173). Ashgate Publishing Group.

Binder, J. C. (2007). Global project management, communication, collaboration and management across borders. (p. 101). Burlington, VT: Gower Publishing, Ltd.

I came across an interesting article by Lynn Crawford and Anat Hassner Nahmias entitled,” Competencies for Managing Change”, in which the authors discuss which discipline is best suited to manage organizational change.  The authors contend that there is a degree of enmity  that exists between Project Managers, Change Managers, and, to a certain extent, Senior Management as to who should be managing business change.  Competencies from both the project management arena and those of change management are analyzed and an attempt is made to identify a synthesis of the two fields.  That synthesis includes the following characteristics: Leadership, Stakeholder management, Planning, Team selection/team development, Communication, Decision-making and problem-solving, Cultural awareness/skills, and Project management skills (Crawford & Nahmias, 2010). Considering the Authors’ analysis, who is best suited to lead organizational change and is it worthwhile for PM’s to adopt change management’s “theory-rich” skills?

Crawford, L., & Nahmias, A. H. (2010). Competencies for managing change. International Journal of Project Management, 28(4), 405–412.