Software Project Management 2007 The Project Management and Information Technology Context

1. Software Project Management 2007The Project Management and Information Technology Context Gao Zhisheng School of Computer Software Engineering

2. Review of chapter 1 • What is project, what is project management • The key elements of the project management framework • Stakeholders • Knowledge areas • Tools and techniques • Project success factor • The role of the project manager, and what skills they need Software Engineering

3. Learning Objectives • Understand the systems view of project management and how it applies to information technology projects • Analyze a formal organization using the structural, human resources, political, and symbolic organizational frames(运用四种组织形式分析一个正规的组织) • Explain the differences among functional, matrix, and project organizational structures • Explain why stakeholder management and top management commitment are critical for a project’s success Software Engineering

4. Learning Objectives • Understand the concept of a project phase and the project life cycle • Distinguish between project development and product development • Discuss the unique attributes and diverse nature of information technology projects Software Engineering

5. Outline • Opening case • A system view of project management • Understanding Organizations • Stakeholder Management • Project Phase and the Project Life Cycle • The Context of Information Technology Projects Software Engineering

6. Opening case(开篇案例) • Tom Walters accepted a new position at his college as the Director(主任，主管) of Information Technology • College introduction: • small, private college • A variety of programs in the liberal arts(文学) and professional(专业技术) areas. • Include 1500 full-time traditional students and about 1000 working-adult students attending and evening program • Many instructors supplemented their courses with information on the intranet and course Web sites. • Did not offer any distance-learning programs • A few classrooms on campus with computers • A few more with just instructor stations and projection systems Software Engineering

7. Opening case(开篇案例) • Tom’s work • With two other colleagues visited a local college that had required all students to lease(租) laptops in the class for the past three years. • Tom and his staff developed plans to start requiring students to lease laptops at their college the next year • Tom sent an e-mail to all faculty(教员) and staff(职员) in September, which briefly described this plans. Software Engineering

8. Opening case(开篇案例) • Effect(效果) • Tom did not get much response • In the February faculty meeting, when he described some of the details of this plan, the chairs of the History, English, Philosophy, and Economics departments all voiced their opposition to the idea. The idea was ludicrous(荒谬） • 计算机系主任认为已经有了最好的台式机，不乐意支付费用租用配置更低的笔记本 • 成人教育部主任也担心成人班的学生不会再愿意增加学费了 • Tom was in shock to hear his colleagues’ responses, especially after he and his staff had spend a lot of time planning details of how to implement laptops at their campus. Software Engineering

9. Opening case(开篇案例) • Question • What should he do? • What wrong he was? You will find answer in the flowing parts Software Engineering

10. Outline • Opening case • A system view of project management • Understanding Organizations • Stakeholder Management • Project Phase and the Project Life Cycle • The Context of Information Technology Projects Software Engineering

11. A system view of PM • Projects Cannot Be Run In Isolation • Projects must operate in a broad organizational environment（项目管理活动离不开组织的管理模式、企业文化等内部环境以及国家的政策法规和市场规则等外部环境。） • Project managers need to take a holistic(全盘) or systems view of a project and understand how it is situated(处于) within the larger organization. • Examples（你是否遇到这样的情况？） • 公司缺乏系统规范的项目管理体系，项目经理往往是从技术骨干中提拔出来的； • 在项目人手十分紧的情况下，公司领导事先没有征得你的意见就突然将个别骨干抽调到其他项目组； • 在项目已经正常验收之后，客户找各种借口不支付应给的项目款。 Software Engineering

12. A system view of PM • What is a system approach? • System approach emerged in the 1950s to describe a holistic and analytical approach to solving complex problems that includes flowing three parts.(解决复杂问题的整体分析方法) • Three parts include • Systems philosophy(系统观念) • 指一整套系统地思考事物的思维模式View things as systems, interacting components working within an environment to fulfill some purpose • Systems analysis(系统分析) • problem-solving approach, 这种方法通过确定系统的研究范围，将其分解为各个组成要素，然后识别和评价各要素存在的问题、机会、约束和需求。然后分析人员要检查一些能够对现状进行改进的解决方案，设法找到一个最优的或至少是满意的解决方案或行动计划，并将起放在整个系统中考察其可行性。 • Systems management • Address business, technological, and organizational issues before making changes to systems（系统变革时解决…) Software Engineering

13. A system view of PM • Using a system approach is critical to successful project management. • Top management and project managers must follow a systems philosophy to understand how projects relate to the whole organization • Use systems analysis to address needs with a problem-solving approach. • Use system management to identify key business, technological, and organization issues related to each project in order to identify and satisfy key stakeholders and do what is best for the entire organization. Software Engineering

14. A system view of PM • Opening case analysis • Tom did not use a system approach. Members of the IT department did all of the planning • 发送了EMAIL，但对项目组织上的事情只字未提，而且秋季开学老师很忙，绝大数老师没有看完 • Tom对项目对其它部门的影响一无所知，根本没有弄清项目相关的那些业务、技术和组织事宜。 Software Engineering

15. The Three-Sphere Model for Systems Management Software Engineering

16. Outline • Opening case • A system view of project management • Understanding Organizations • Stakeholder Management • Project Phase and the Project Life Cycle • The Context of Information Technology Projects Software Engineering

17. Understanding Organizations Human resources frame:重点在于形成组织需要与个人需求之间的平衡与协调 Structural frame: Focuses on roles and responsibilities, coordination, and control. Organization charts help define this frame. Political frame:主要描述组织团体和个人的政治，企业组织是由各种人和利益集团组成的联合体，存在团体和个人争夺权利和领导地位的斗争. Symbolic frame: Focuses on symbols and meanings related to events. Culture is important. Software Engineering

18. Organization Structures • Many discussions of organizations focus on organizational structure.(集中于组织结构） • Many new managers try to change organizational structure when other changes are needed. • Three basic organizational structures: • Functional: Functional managers report to the CEO. • Project: Program managers report to the CEO. • Matrix: Middle ground between functional and project structures; personnel often report to two or more bosses; structure can be a weak, balanced, or strong matrix. Software Engineering

19. Figure 2-2. Functional, Project, and Matrix Organizational Structures Software Engineering

20. Functional Software Engineering

21. Functional Software Engineering

22. Project Software Engineering

23. Project Software Engineering

24. Matrix Software Engineering

25. Matrix Software Engineering

26. Matrix Software Engineering

27. Matrix Software Engineering

28. Matrix Software Engineering

29. Table 2-1. Organizational StructureInfluences on Projects 项目经理 /项目群经理 项目管理 /行政人员 Software Engineering

30. Example: Microsoft Software Engineering

31. Example: Microsoft Software Engineering

32. Website Project Organizational Structure 商务模型专家 应用域专家 高层领导 合同管理者 项目经理 质量保证组 系统开发组 内容管理组 项目支持组 Software Engineering

33. 案例题 你的项目管理的经验告诉你，你的基本职责就是通过授权，将任务分配给团队的成员，依靠它们的力量开发出项目计划要求的可交付成果。由于你的项目不是项目型组织，因此你不能直接参与人力资源管理的工作（它们是职能经理和人力资源经理的主要工作），因此，你需要 • A) 从外部筹集资源来完成项目工作 • B) 确保项目人员认识到为了保证项目的顺利完成，服从行政管理是必要的 • C)希望职能经理不要过多的管理项目团队的成员 • D)请求人力资源主管亲自批准项目人员分配计划 Software Engineering

34. Organization Culture • Organizational culture is a set of shared assumptions, values, and behaviors that characterize the functioning of an organization. • 岳母刺字 -“精忠报国” • Many experts believe the underlying causes of many companies’ problems are not the structure or staff, but the culture. • “小企业看老板，中企业看制度，大企业看文化” • 企业竞争可以分为四个层次：产品竞争、营销竞争、战略竞争和文化竞争 Software Engineering

35. Organization Culture • 企业文化其实就是老板的文化 • 海尔文化中最突出的是执行力强 .海尔内部流传着一个寓言，说一只狮子领导的一群绵羊可以打败一只绵羊领导的一群狮子,海尔在张瑞敏领导下，只要认准了的事，就能够得到强有力的执行 . • TCL文化中最具特色的是内部企业家精神，TCL受广东文化的影响，市场意识、业绩导向非常明显。公司开会，业绩好的单位代表自动坐在前面，业绩不好的单位代表自动地坐在后排。李东生并没有压制其它企业家的产生，而是鼓励其它企业家的产生。 • 联想比较突出的特色是"亲情文化"，柳传志 Software Engineering

36. Ten Characteristics ofOrganizational Culture • Member identity(成员一致) • The degree to which employees identify with(把…看成) the organization as whole rather than with their type of job or profession(主人翁精神 ) • Group emphasis • The degree to which work activities are organized around groups or teams, rather than individuals • People focus • The degree to which management’s decisions take into account the effect of outcomes on people within the organization. Software Engineering

37. Ten Characteristics ofOrganizational Culture • Unit integration(部门融合） • The degree to which units or departments within an organization are encouraged to coordinate with each other. • Control • The degree to which rules, policies, and direct supervision(监督) are used to oversee and control employee behavior • Risk tolerance • The degree to which employees are encouraged to be aggressive(有闯劲的）, innovative, and risk seeking. • Reward criteria(标准) • The degree to which rewards, such as promotions and salary increases, are allocated according to employee performance rather than seniority, favoritism, or other nonperformance. Software Engineering

38. Ten Characteristics ofOrganizational Culture • Conflict tolerance • The degree to which employees are encouraged to air(气氛) conflicts and criticism(批评) openly. • Means-ends orientation(目的手段倾向） • The degree to which management focuses on outcomes rather than on techniques and processes used to achieve results • Open-systems focus • The degree to which the organization monitors and responds to changes in the external environment Software Engineering

39. Outline • Opening case • A system view of project management • Understanding Organizations • Stakeholder Management • Project Phase and the Project Life Cycle • The Context of Information Technology Projects Software Engineering

40. Stakeholder management • Project stakeholders are the people involved in or effected by project activities. See chapter 1. • Project managers must take time to identify, understand, and manage relationships with all project stakeholders. • Using the four frames of organizations can help you meet stakeholder needs and expectations Software Engineering

41. Stakeholder management • Opening case • Tom Walters seemed to focus on just a few internal project stakeholders. He viewed only part of the structure frame of the college. The did not even involve the main customers for this project- the students at the college. • Organizational chart: academic(学院 ) department heads and members of different administrative areas. • Human resources frame: identify individuals who would most support or oppose requiring laptops. • Political frame: considered the main interest(利益) groups that would be most affected by this project’s outcome. • Symbolic frame: what moving to a laptop environment would really mean for the college. Software Engineering

42. Importance of Top Management Commitment • Several studies cite top management commitment as one of the key factors associated with project success. • Top management can help project managers: • Secure adequate resources.(扼杀一个项目的最佳方式是断奶） • Get approval(批准) for unique project needs in a timely manner. (Especially halfway needs) • Receive cooperation from people throughout the organization. • Learn how to be better leaders. Software Engineering

43. Need for Organizational Commitment to IT • If the organization has a negative attitude toward IT, it will be difficult for an IT project to succeed. • Having a Chief Information Officer (CIO) at a high level in the organization helps IT projects. • 安排一些非IT人员全职参与一些大项目，以促进系统基层用户的参与。 Software Engineering

44. Outline • Opening case • A system view of project management • Understanding Organizations • Stakeholder Management • Project Phase and the Project Life Cycle • The Context of Information Technology Projects Software Engineering

45. Project Phases and the Project Life Cycle • A project life cycle is a collection of project phases.(一系列项目阶段的集合) • What work will be performed in each phase. • What deliverables will be produced and when. • Who is involved in each phase. • How management will control and approve work produced in each phase. • Characteristics of project phases • Each project phases is marked by completion of one or more deliverables(可交付的成功). • The conclusion(结论) of a project phase is generally marked by a review of both key deliverables and project performance to date. Software Engineering

46. Project Phases and the Project Life Cycle • Checkpoint • 在规定的时间间隔内对项目进行检查，比较实际与计划之间的差异，并根据差异进行调整。 • 常见的间隔是每周一次，项目经理需要召开例会并上交周报。 • Milestone • 完成阶段性工作的标志，不同类型的项目具有不同的里程碑。 • Baseline • 基线是指一个或一组配置项在项目生命周期的不同时间点上，通过正式评审而进入正式受控的一种状态。 Software Engineering

47. Project Phases and the Project Life Cycle • The project life cycle serves(提供) to define the beginning and the end of a project. • In the early phases of a project life cycle: • Resource needs are usually lowest. • The level of uncertainty (risk) is highest. • Project stakeholders have the greatest opportunity to influence the project. • In the middle phases of a project life cycle: • The certainty of completing a project increases. • More resources are needed. • In the final phase of a project life cycle: • The focus is on ensuring that project requirements were met. • The sponsor approves completion of the project. Software Engineering

48. Project Phases and the Project Life Cycle Software Engineering

49. Project Phases and the Project Life Cycle • Distinguishing project life cycles and product life cycles • The project life cycle applies to all projects, regardless of the products being produced • Product life cycle models vary considerably based on the nature of the product • Most large IT products are developed as a series of projects • Project management is done in all of the product life cycle phases(产品生命周期的所有阶段都要进行项目管理) • Project phases vary by project or industry, but some general phases include • Concept（概念阶段） • Development（设计阶段） • Implementation（实施阶段） • Close-out（收尾阶段） Software Engineering

50. Project Phases and the Project Life Cycle 最终工作包 经验教训 预算成本分析 初步成本分析 确定的成本估计 绩效报告 Software Engineering