xevple eleata mikelena
Shawna Erholm
Mr. Bachana began his career in the late 1980's at the New York Times in its Production Technology Group. He furthered his career at the Associated Press as technical services manager for AP AdSend, the digital delivery system from advertisers to AP member newspapers.
Mr. Bachana went on to be senior Project Manager at I.M.A.G.E. Inc, then Senior Account Manager at Inacom, before founding DPCI in April, 1999.
A native of New York, Mr. Bachana is a graduate of both Brown (BA) and Columbia (GS) Universities and holds PMP certification from the Project Management Institute. Mr. Bachana holds certification from Acquia as a a Drupal Site Builder.
A Drupal project will begin with a meeting between the DPCI project manager, technical lead, and the core client stakeholders. Once objectives are clarified, the project manager will create a project plan that allows the team to track progress. This plan is integrated with our internal timesheet database so that hours logged by project team members are directly related to the project-specific tasks.
Throughout the engagement, the project manager will serve as the single point of contact to facilitate all communication with your team, including regular status reports and constant updates regarding the status of open issues. To this end, the project manager will set up a project portal dedicated to the project that will give all team members, including client stakeholders, access to the latest versions of deliverables, status reports, the project plan, and all technical bug reports.
A few years ago, I observed a project manager with a long list of successful projects absolutely struggle with a project. As I looked around, I noticed that often times project managers who do superb jobs on some projects will fail on others. What causes this to happen? Why were project managers successful on some projects but struggling on others?
Even though all projects are by definition unique, there are attributes that are common among projects that allow the characterization or profiling of a project. We can look at just two project attributes and develop some understanding of the project. A large project that will be executed in at least three locations will have a very different profile from a small project that will be executed in one location. These two attributes - size and location - provide information about the project that will enable a manager in the parent organization to assign a project manager with the appropriate knowledge and skills. We can then develop an execution approach to increase the likelihood of success.
Project managers have not always been assigned to projects based on their skills and the skills required by the project. Research by the Construction Industry Institute indicated that the number one criterion for assignment of a project manager to a project was availability. Even if available, the ideal project manager for a large construction project may not be a good fit for a software development project. The technical knowledge needed to manage these projects is not the same and having the wrong technical knowledge may make the difference between a successful project and project failure.
Even within the same industry, like the construction industry, different skills are needed by the project manager for different projects. For example, the construction of an office building in downtown Philadelphia is a very different project from the construction of a chemical plant in Mexico. The differences in these projects require different skills and different execution approaches. Organizations have not had good tools for understanding and matching the needs of a project with the project manager who has the right skills and experience. Developing a project profile is one method for developing an understanding of the project that will allow a systematic approach to developing an execution plan based on the profile of the project and selecting a project manager who has the right kind of experience and skills.
Project profiling is the process of extracting a characterization from the known attributes of a project. The characterization will provide a more comprehensive understanding of the project that should result in developing an appropriate execution approach and the assignment of organizational resources. In different terms, project profiling is a process that summarizes what is known about the attributes of a project and places the project into a category with other projects that have similar characteristics. For example, you can characterize a project as a large project or a small project. The size of the project becomes the profiling attribute. You can characterize a project as domestic or global, and the location of the project becomes the profiling characteristic.
Aaron J. Shenhar and Dov Dvir developed a typology - classification or profile - of engineering projects that reflected two dimensions. The first dimension reflected the technological uncertainty and ranged from low tech, medium tech, and high tech to super high tech. Although projects involve the use of various levels of technology, Shenhar and Dvir develop criteria for each type of technological uncertainty that enabled the project to be typed. The second dimension reflected the system scope. The system scope dimension ranged from assembly projects that dealt with building a single component, to system projects that included interactive elements, to array projects that included a wide dispersal of interactive systems and subsystems.
Shenhar and Dvir observed that the project execution approach was connected to the project type. The study identified different management patterns associated with project type as well as different management tools and practices. As the project system scope became more complex and the system scope of the project became larger, more sophisticated management tools were put in place to reduce project uncertainty. As project technology increased, project managers became more invested in processes to manage technical issues such as redesign and testing. As projects increased in system scope, project managers became more invested in formal planning and control issues. In later research, Shenhar developed recommendations for adjusting the project management approach based on the project typology - systematic classification or profile. For example, project managers will use more risk management techniques.
Robert Youker identified basic differences in project types. Among the attributes he used were the uncertainty and risk, level of sophistication of the workers, the level of detail in the planning, the newness of the technology, and the time pressure. Youker also looked at project size, duration, industrial sector, geographic location, number of workers, cost, complexity, urgency, and organizational design as attributes that help determine a project profile.
Understanding and managing complex systems like a project require some systems concepts that have been developed in other disciplines and applied to project management as a tool to make complex projects manageable.
When is a project complex? The answer to this question depends on how you define complex. One way to explore this question is to look at complexity models in various disciplines for insights that may apply to project management. In biology, the simplest plant is composed of one cell. As the cellular structure increases in number of cells and the number of connections to other cells increases, the plant life is seen as more complex. In the animal kingdom, the single cell ameba is the simplest animal, and life becomes more complex as the numbers of cells combine to form muscles and organs.
The complexity of a system is usually determined by the number of parts or activities, the degree of differentiation between the parts, and the structure of their connections. Heterogeneous and irregularly configured systems are complex, such as organisms, airplanes, and junkyards. Order is the opposite of complex. Ordered systems are homogenous and redundant, like an interstate toll booth or a production line in a factory. Complex systems have multiple interacting components whose collective behavior cannot be simply inferred from the behavior of the components.
In addition to the number of parts, the degree of differentiation between parts and the number, type, and strength of relationships between parts also influences the degree of complexity. For example, the transistors in a computer have three connections to other parts of the computer, but each nerve cell in the human brain can be connected to thousands of other cells in the brain, which is why the human brain is more complex than a computer. Complexity is context dependent. A project is more or less complex in relation to the number of activities, the type and strength of relationships to other project activities, and the degree and type of relationships to the project environment.
Projects are complex adaptive systems. A complex adaptive system is a system consisting of a large number of parts or activities that interact with each other in numerous and various ways. A complex adaptive system is adaptive if the activities adjust or react to the events of the environment. Successful adaptive systems adjust in a way that facilitates or allows the system or project to achieve its purpose.
The dependence of the project on the activities, the interdependence of the activities, and the specialization of the activities underscore the relationship dependence of project activities. This relationship dependence is a key aspect of complex adaptive systems. The nature of complex adaptive systems can be probed by investigating the impact of change in one activity and the effect on other activities and the behavior of the whole. Activities must be studied and understood as interrelated, connected parts of the whole. If you remove a computer chip from a computer and the computer powers down, do not assume the purpose of the chip was to provide power to the computer. If you remove or shorten a project kickoff activity, do not assume the project will finish earlier because of the dependence of later project activities on project kickoff activities. Any change to the kickoff activities will impact other activities and the project as a whole.
c01484d022