Skip to main content

Does Sr. Management need to know? Program vs Project Management

One of my favorite topics in organizational management is organizational structure and it seems little do people realize that organizational hierarchy/structural planning are key valuable components that are inter-linked with the functions of strategic planning and implementation along with the over arching  vision, mission, purposes and goals of an organization. In practice however we see many organizations creating titles and roles on the fly or whim or by the seat of their pants in decision making. I heard once that in a organization that the President had a bright idea of expanding the senior management positions to 12 Vice Presidents (on the fly) out of nowhere, a decision from the hip without knowledge of structures (I am sure he as some knowledge of structure) or following the costing and science behind it.

In relation however at first I want to concentrate on the idea of how program management is different from project management. To outline the differences we first need to know the definition of Project management:

Project management consists activities of  planning, organizing, directing, and controlling of company resources (like time, financial capital, human capital) to achieve a the goals of a project and its implementation for a given period of time and thereafter those resources being dismantled after the project is done.

It is clear from the definition that project management is concerned with allocation, utilization and direction to members on a team to achieve the objectives of the project as lay out in the project charter under the constraints and adherence to budgets, schedules and resources.

However Program management or in the life of the program manager/director the major responsibility is to ensure that the work effort achieves the outcome specified in the organization and the implementation of the IT strategies. Since this blog has a concentration of it in the background I will use the term 'IT strategies'. So the way I see the program manager's roles is like a guy who bridges the vision from senior management and stakeholders and tells the team members and project managers of how to realize or accommodate this vision. The role is not just accommodating, it will mean maintaining and it will mean enhancing. Those Program managers received periodic summary of reports and briefings of funding consumption and have to approve budgets their main concentration if a deviation has occurred from the overall strategic vision.  Though it seems the roles of program management and project management have almost parallel functions of planning, organizing, directing and controlling they are again at different levels in the organizational structure. The program manager job seems to be on going and never ending, the project manager on the other hand has a start date and an end date. Objectives at hand may be more defined whereas for the program manager they are broadly defined.
I took these two examples to work my way up, as you go higher up in the organization structure the definitions, functions, strategizing and envisioning though they become broader, yet the top owner (stakeholders or senior management) not knowing what all the details are for all the activities, should still have the fair idea as to what is entailed in those activities and make change decisions or allow participative decision making that eventually empower him/her in the organization. 


Cheers, 


Sam Kurien 

Comments

Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…