Software Project Management-Microsoft(二)

1.Project Management

Application of knowledge, skills, tools and techniques to project activities to meet project requirements.

2. Project Manager

The people who does project management.

3.Project

Temporary endeavor.

Unique product, service or result.

Require resources.

Should have a project sponsor.

4.Program

Group of related projects.

5.Program manager

Translates business to technical requirements, and manages one, usually more projects.

三.Triple constraints

1.It is critical that a PM balance the triple constraints. (Time-schedule,cost-resources,scope-features).

2.You always have at least 3 options.

四.Microsoft Solution Framework

1.Microsoft Team Mode

2. Multi-versioning delivery

1)Force closure on project issues.

2)Set clear and motivational goals with all team members.

3)Manage the uncertainty and change in project scope

4)Encourage continuous and incremental feature delivery

5)Enable shorter time to market

3.MSF project

4. Standard MSF Deliverables

I Envisioning:”Vision Approved” Milestone

1)Vision document

2)Risk assessement

3)Project strcture document

ii Planning:”Scope(调查) complete” Milestone

1)    Functional specification

2)    Risk assessment

3)    Project schedule

4)    Operation and support information systems

Procedures and processes

Knowledge base,reports,logbooks

iii Developing:”Code complete” Milestone

1)    Frozen functional specification

2)    Risk management Plan

3)    Source code and executables

4)    Performance support elements

5)    Test specification and test cases

6)    Master project plan and master project schedule

iv Stabilizing:”Release” Milestone

1)    Golden release

2)    Release notes

3)    Performance support elements

4)    Test results and testing tools

5)    Source code and executables

6)    Project documents

7)    Milestone review

V Deploying:”Deployment comlete” Milestone

1)Documentation repository for all versions of documents, load sets, and code developed during the project.

2)Project close-out(抛售,停止) report

3)Final versions of all project documents

4)Customer/user satisfaction data

5)Definition of next steps

5. PMI vs. MSF(Phase 1)

.Initiating(PMI)

---Business case

---Project Charter

---Preliminary(初步的) scope statement

---Project charter review and approval

.Envision(MSF)

---Value Prop./Vision doc.

---Project startup checklist.

---Solution assessment

---Risk strategy plan

---Role segmentation for Date or Transaction Processing Access.

6.PMI vs. MSF(phase 2)

Planning(PMI)

---Scope definition

---Work breakdown (细节分类)structure

---“Knowledge area” plans

---Overall project plan

---Review and approval of Project plan(baseline)

.Design(MSF)

---Functional spec

---Solution ROI(Return on investment)

---Communication plan

---Technical specs

---UAT(user accept testing) plan

---Training plan

---Change control plan

---Test plan Review & Sign-off

---Baseline Approval & Sign-off

7.PMI vs. MSF(phase 3)

.Executing(PMI)

---Acquire and develop the project team using WBS(Work Breakdown Structure)as a guide

---Request seller responses and select sellers to support external vendor needs

---Distribute information and communicate as noted in communications plan

---Direct and manage project execution

---Perform quality assurance

---Solution delivered

Notes:WBSis also known as work breakdown system. it is a map of the project that identifies the products and work elements involved in a project.WBSis an outline of the project with differernt levels of details,it defines the relationship of the final deliverable to its subdeliverables,and in return, their work packages.
WBShelps to assume project managers that all the work are identified and established.

.Development(MSF)

---Executable code

---Test spec cases & scrīpts

---Complete data inventory(目录) web form

---Deployment plan

---Privacy statement

---Operations support guide

---UAT test cases & review

---Training Validation

---Code complete

8.PMI vs. MSF (Phase 4)

---Monitor and control all project work

---Manage integrated change control as defined in the project plan

---Manage the project team

---Manage project stakeholders

---Report performance

---Monitor and control risk

---Administrate external seller contracts

.Stabilize(MSF)

---User acceptance approval

---Deployment plan

---Contingency (紧急事件,偶然性)plan

---Operations support guide

---Data validation & conversion

---Solution assessment Documentation

---Security & Privacy Comprehensive assessments

---Go/No-Go meeting

9.PMI vs. MSF(Phase 5)

.Closing (PMI)

---Accept deliverables

---Document final lessons learned

---Facilitate closure, including contracts

---Customer Acceptance

.Deploy(MSF)

---Update the Business continuity(连贯性,连续性) & Disaster Recovery Plan

---Post Mortem

---Follow-up with the showcase team

---Go live

---Project closeout

9.Phase 6(MSF only)

.Production(MSF)

---Based on the Microsoft Operations Framework for service management, activities focus on change and release management, system and security administration, support management, and operations optimization.