Boundary activities and readiness for ... - Projekti-Instituutti
Boundary activities and readiness for ... - Projekti-Instituutti
Boundary activities and readiness for ... - Projekti-Instituutti
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Theoretical background<br />
organizational development programs (Dietrich, 2007). In a similar<br />
manner, Gray <strong>and</strong> Bam<strong>for</strong>d (1999) describe plat<strong>for</strong>m programs that aim to<br />
improve an organization’s infrastructure.<br />
It is worthwhile to note that program management is a <strong>for</strong>m of multiproject<br />
management, but the two terms are not synonymous. Particularly,<br />
project portfolio management refers to the process of systematically<br />
analyzing, prioritizing, selecting, <strong>and</strong> overseeing projects that share the<br />
limited resources of an organization (Archer & Ghasemzadeh, 1999;<br />
Cooper, Edgett, & Kleinschmidt, 1997). Although the management of scarce<br />
resources is often an essential element in programs, the temporary nature,<br />
common goal <strong>and</strong> close connections between the program’s projects make<br />
program management distinct from project portfolio management<br />
(Pellegrinelli, 1997; Turner & Müller, 2003). Some programs may resemble<br />
a portfolio in the sense that they are <strong>for</strong>med by grouping loosely related<br />
projects under the same umbrella (Gray, 1997; Pellegrinelli, 1997).<br />
However, the present study focuses on goal-oriented programs<br />
(Pellegrinelli, 1997) that consist of related projects <strong>and</strong> actions that aim at a<br />
shared goal <strong>and</strong> require collective ef<strong>for</strong>t.<br />
Goal-oriented programs consist of multiple projects that typically are at<br />
least to some extent interdependent through their goals, deliverables,<br />
methods, or resources (Dietrich, 2006, 2007; McElroy, 1996). The key roles<br />
in the typical program organization include the program manager, who is in<br />
charge of the operational management <strong>and</strong> coordination of the program,<br />
<strong>and</strong> the project managers, who are each responsible <strong>for</strong> managing a project<br />
in the program. The program manager’s tasks <strong>and</strong> responsibilities include<br />
program-level planning, coordinating the projects’ work <strong>and</strong> deliverables,<br />
supporting project managers in project execution, <strong>and</strong> maintaining<br />
alignment with the business objectives (Ferns, 1991). In a typical program,<br />
project managers report to the program manager, who further reports<br />
upwards to the program steering group (or a steering committee or<br />
program board), led by a program owner, program director or program<br />
sponsor, or an alternative executive body who represents the wider<br />
organization (ibid.). The program owner (or director or sponsor) has the<br />
ultimate responsibility <strong>for</strong> the realization of the anticipated benefits (Office<br />
of Government Commerce, 2007; Pellegrinelli, 1997). While delivery<br />
projects or programs have external clients, the client of an organizational<br />
change program is internal. The program owner may represent the client in<br />
the internal program. A program (support) office can also be established to<br />
support the program management, to facilitate in<strong>for</strong>mation management at<br />
the program level, <strong>and</strong> to provide procedures, tools, training, <strong>and</strong> support<br />
21