---
tags: 軟體工程
title: 第四、五週
---
# Project Planning and Project Management
---
## 專案失敗原因
- Undefined project management practices
- Poor IT management and poor IT procedures
- Inadequate executive support for the project
- Inexperienced project managers
- Unclear business needs and project objectives
- Inadequate user involvement
---
## Project Management
> Organizing and directing other people to achieve a planned result within a predetermined schedule and budget
> The processes used to plan the project and then to monitor and control it.
> 在既定的時辰與預算內，組織與引導專案達成預定的成果
---
## Project Manager
> Great need for effective project managers
> Internally managing people and resources
> Externally conducting public relations
> 對內管理組織
> 對外代表專案進行溝通、爭取資源
---
## Additional Project Stakeholders(利害關係者)
- Client
- the person or group that funds the project
- 花錢的人、資方
- Oversight Committee
- clients and key managers who review the progress and direct the project
- 高層次委員會
- Users
- the person or group of people who will use the new system
- 真正使用此系統的人
---
## Project Management Body of Knowledge (PMBOK)
PMPOK is organized into 10 knowledge areas:
- **Project Integration (統整) Management**
- Integrating all the other knowledge areas into one seamless whole
- **Project Scope (範圍) Management**
- Defining and controlling the functions that are to be included in the system as well as the scope of the work to be done by the project team
- **Project Time Management**
- Creating a detailed schedule of all project tasks and then monitoring the progress of the project against defined milestones
- **Project Cost Management**
- Calculating the initial cost/benefit analysis and its later updates and monitoring expenditures as the project progresses
- **Project Quality (品質) Management**
- Establishing a comprehensive plan for ensuring quality, which includes quality control activities for every phase of a project
- **Project Human Resource Management**
- Recruiting and hiring project team members; training, motivating, and team building; and implementing related activities to ensure a happy, productive team
- **Project Communications (溝通) Management**
- Identifying all stakeholders and the key communications to each; also establishing all communications mechanisms and schedules
- **Project Risk (風險) Management**
- Identifying and reviewing throughout the project all potential risks for failure and developing plans to reduce these risks
- **Project Procurement (採購) Management**
- Developing requests for proposals, evaluating bids, writing contracts, and then monitoring vendor performance
- **Project Stakeholder (利害相關者) Management**
- Identifying and communicating with the stakeholders of the new system
---
## Activities of Core Process 1:
### Identify the Problem
- IS Development Projects usually:
- Respond to an opportunity
- Strategic initiative
- Something that provides competitive advantage
- Resolve a problem
- Operational issues keep coming up
- User needs aren’t being met
- Respond to an external directive
- Legislation requires new form of reporting
- Changes in tax laws or regulations
- System Vision Document
- Problem Description (問題概述)
- What is the problem and idea for the solution?
- System Capabilities (系統功能)
- What are the capabilities the new system will have?
- Helps define the scope
- Business Benefits (商業價值)
- The benefits that accrue to the organization
- Tangible (in dollars) and intangible benefits
---

## System Vision Document (系統願景文檔)
- one type of text document which provides a clear scenario(腳本) about the high-level scope of the project along with the purpose of the entire(整個) project.
- Primarily(主要的) there is a clear statement related to the problems of the project
- there should be a clear discussion(討論) about the mitigation(減輕) process of the problem.
## Cost/Benefit Analysis (成本效益分析)
- 確定一項投資（或決策）是否合理，確定其收益是否超過成本，以及超過金額之估計。
- 為比較投資（或決策）提供基礎，將每個選項的總預期成本與其總預期收益進行比較。
## Feasibility Analysis (可行性分析)
- 經濟上的可行性
- 技術上的可行性
- 時間表上的可行性
- 組織架構上的可行性
## context Diagram
- 矩形
- user
- 其他會與此系統會互動的系統
- 箭頭
- A->B 表式A需要給B什麼東西