大三下信管只起到参考作用具体复习看老师放假lifecycle_第1页
大三下信管只起到参考作用具体复习看老师放假lifecycle_第2页
大三下信管只起到参考作用具体复习看老师放假lifecycle_第3页
大三下信管只起到参考作用具体复习看老师放假lifecycle_第4页
大三下信管只起到参考作用具体复习看老师放假lifecycle_第5页
免费预览已结束,剩余31页可下载查看

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

1、KXO231 ICT Project ManagementLecture 3: Project Lifecycle & Organisational InfluencesContentsSchool of Engineering & ICTOrganisational InfluencesProject Stakeholders and GovernanceProject TeamProject Management FrameworksProject Management LifecyclesOrganisational InfluencesCultures and StylesCommun

2、icationsStructuresProcess AssetsProcesses and ProceduresCorporate Knowledge BaseEnvironmentCultures and Styles“Organisations are systematic arrangements of entities (persons and/or departments) aimed at plishing a purpose, which may involve undertaking projects,” (PMBOK 2013). Shared visionsPolicies

3、MotivationRisk toleranceOperating Environments CommunicationsEmailTestingInstant MessagingSocial MediaVideoWeb ConferencingOrganisational Structure(PMBOK 2013: 21)Process AssetsPlansProcessesPoliciesProceduresKnowledge BasesEnvironmentCorporate GovernanceGeographyInfrastructureExisting Human Resourc

4、esMarket ConditionsPoliticsExisting technologiesUnderstanding the organisationWho are they?Where do they want to go?What do they want to achieve?What do they currently do?How do they currently do things?We can use maps and models to assist in gathering and representing this information9School of Eng

5、ineering & ICTProject Stakeholders and Governance“A stakeholder is an individual, group, or organisation who may affect, be affected by, or perceive itself to be affected by a decision, activity, or e of a project,” (PMBOK 2013: 30)SponsorCustomersUsersSellersBusiness PartnersFunctional ManagersOthe

6、rsProject TeamProject ManagerProject Management StaffSupport ExpertsUser/Customer RepresentativesVendorsBusiness PartnersProject Management FrameworkFrameworks/standards: describes best practices for what should be done to manage a project, but not how to do projectsIn Project Management, the guidin

7、g framework is PMBOK (Project Management Body of Knowledge)Identifies 10 PM Knowledge areas:Scope managementTime managementCost managementQuality managementHuman resource managementCommunications managementRisk managementProcurement managementProject integration managementProject stakeholder managem

8、entProject Management LifecyclesA collection of logical phases that maps the life of a project from its beginning to its end.It helps to identify the stages required to define, build and deliver the product of a project. Traditionally, project management includes a number of elements: four to five p

9、rocess groups, and a control system. Regardless of the methodology or terminology used, the same basic project management processes will be used. School of Engineering & ICTPMLC and Software DevelopmentProject Management Life Cycle Systems Development Life CyclePlanningAnalysisDesignImplementationMa

10、intenance and SupportInitiationPlanningExecutionClosureWaterfall lifecycle modelThe stages of software development are viewed as a cascading waterfall from one to anotherRequirements analysisSystem designProgram designCodingUnit testing and integrationSystem testingAcceptance testingOperation and ma

11、intenanceWaterfall lifecycle with feedbackRequirements AnalysisSystems DesignImplementationIntegration and DeploymentOperation and MaintenanceProductUserAnalysisDesignCodingTestingIntegrationPrototypingPrototypingWaterfall model with prototypingPrototyping is a sub-processA prototype is a partially

12、developed productTo examine some aspects of the systemTo ensure the quality of the systemCodingProgram designUnit & integration testingSystem testingAcceptance testingSystem designRequirement analysisOperation MaintenanceVerify programVerify designValidate requirementsV ModelPhased DevelopmentThe ti

13、me between when the requirements were written and when the system was delivered is called cycle timeOne way to reduce the cycle time is to use phased development: system is delivered in piecesdeveloperuserRelease 1Release 2Release 3Iterative DevelopmentDeliver a full system at the very beginning and

14、 change the functionality of each sub-system with each new releaseRelease 1Release 2Release 3Incremental DevelopmentThe releases are defined by beginning with a functional sub-system and then adding functionality with each new releaseSpiral ModelIncorporate the practices of risk minimisation and pro

15、totypingAgile Software Development“Conventional” requirements analysis is replaced in agile development by user stories features that the customer would like the system to support. “Conventional” system design and implementation are replaced in agile development by a combination of acceptance tests,

16、 refactoring, and test-driven development. test-driven development or intentional programming the developer programs his/her intent in an acceptance test before s/he implements it. frequent refactorings improvements to the structure of the system without changing its behavior.Agile development encou

17、rages other practices, such as pair programming and collective ownership. “Conventional” integration and deployment is replaced in agile development by continuous integration and short cycles. The Project LifecycleMajor process groups generally include:Klastorin 2004Formulation & SelectionScheduling

18、 and ControlPlanningImplementation & TerminationDefine the ProjectLaunch the PlanDevelop Detailed PlanMonitor/Control Project ProgressClose Out the ProjectWysocki 2007Initiating ProcessesExecuting ProcessesPlanning ProcessesMonitoring and Controlling ProcessesClosing ProcessesSchwalbe 2008Define Pro

19、ject GoalExecute Project PlanPlan ProjectClose ProjectEvaluate ProjectMarchewka 2009InitiationThe initiation phase typically begins with the assignment of the project manager and ends when the project team has sufficient information to begin developing a detailed schedule and budget.Activities durin

20、g the initiation phase include:project kickoff meetingsidentifying the project teamdeveloping the resources needed to develop the project planidentifying and acquiring the project management infrastructure (space, computers)School of Engineering & ICTPlanningThe planning phase includes the developme

21、nt of more detailed schedules and a budget. The planning also includes:Developing staffing plansDeveloping procurement plansDeveloping project controls plansThe emphasis of the planning phase is to develop an understanding of how the project will be executed and a plan for acquiring the resources ne

22、eded to execute itPlanning activities occur during the entire life of the project.School of Engineering & ICTExecutionThe execution phase includes the major activities needed to plish the work of the project. This phase involves coordinating people and resources, as well as integrating and performin

23、g the activities of the project in accordance with the plan. This phase also addresses the project scope that has already been defined and implements approved changes.School of Engineering & ICTMonitoring & ControlThis phase is related to observing project execution so that potential problems can be

24、 identified in a timely manner and corrective action can be taken, when necessary, to control the execution of a project.This phase includes:Monitoring the ongoing project activities against planning and project performance indicators;Influencing the factors that could circumvent integrated change c

25、ontrol so that only approved changes are implemented.School of Engineering & ICTClose OutThe closeout phase represents the final stage of a project. Activities include:Project staff transferred off the projectArchiving of project documents the final few items or punch list is completed. The project

26、client takes control of the product of the project, and the project office is closed down.School of Engineering & ICTStrategy & Project Management MethodologiesFrameworks and lifecycles describe WHAT should be done; Methodologies describe HOW things should be done. Process-based methodologies: Tradi

27、tional methodology Informal, linear, process-based but not all stages are always used, projects may not follow structured planning and monitoring, customised context-specific templates. Most respondents use only a small number of methods, tools and techniques with project management software and Gan

28、tt charts being the most widely used aids. PRINCE2 A process-based and structured approach to project management, most popular methodology and template set in industry today. Identifies key inputs and outputs for each stage, and specific activities to be carried out and goals to be achieved from eac

29、h stage. Adaptive methodologies: Agile Project Management An iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner. Scrum is an iterative and incremental agile software development framework for managi

30、ng software projects and product or application development. Its focus is on a flexible, holistic product development strategy where a development team works as a unit to reach a common goal as opposed to a traditional, sequential approach. 30School of Engineering & ICTStrategic Planning & Project S

31、electionStrategic planning involves determining long-term objectives, predicting future trends, and projecting the need for new products and services.As part of strategic planning, organizations:Identify potential projectsUse realistic methods to select which projects to work onFormalize project ini

32、tiation by issuing a project charterSchool of Engineering & ICTProject Management MethodologiesFrameworks and lifecycles describe WHAT should be done; Methodologies describe HOW things should be done. Methodologies define the processes, responsibilities and workflows needed to achieve an objective.

33、Part of creating a PM methodology includes the creation and use of templates.Project Management MethodologiesProcess-based methodologies:Traditional methodologyInformal, linear, process-based but not all stages are always used, projects may not follow structured planning and monitoring, customised c

34、ontext-specific templates.Most respondents use only a small number of methods, tools and techniques with project management software and Gantt charts being the most widely used aids. PRINCE2A process-based and structured approach to project management, most popular methodology and template set in industry today. Identifies key inputs and outputs for each stage, and specific activities to be carried out and goals to be achieved from each stage. PRiSM A process-based and str

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论