4) How to build
I. Evolution to the plan
Transform the way to the plan
Find each team role responsible for planning input
Develop corresponding different quantities and complexity plans based on project characteristics
Don't confuse project plans and Project files
Ii. Program is a team event
Typical plan
Drive role
Communication plan
Product manager
Development Plan
Developer
training program
user experience
Security plan
Developers and release managers
Test Plan
Testers
Budget plan
Program manager
Deployment plan
Release manager
Purchase and Promotion Plan
Release manager and program manager
Trial operation plan
Release manager
2) When do you plan to generate?
I. Schedule
Use the duration of the task to estimate the created schedule
Including long vacation, short vacation and resources available
Ii. Schedule is a group activity
Each role group contributes to his own work contribution schedule information
Typical schedule
Drive role
Communication schedule
Product manager
Development schedule
Developer
Training schedule
user experience
Test schedule
Testers
Budget progress table
Program manager
Deployment schedule
Release manager
Purchase and promote progress table
Release manager and program manager
Trial operation schedule
Release manager
III. Suggestions for effective schedules
Apply risk-driven method to develop a schedule
Use the time box when appropriate
Keep the idea of active on time
Arrange buffering time as a previous task of a primary milestone
IV. Synthetic and synchronization timetable
Solve the timetable conflicts between each role
Excessive resource
Unreasonable task arrangement relationship
Unreasonable or expired resource allocation
Program manager role creates a comprehensive project plan
Temporary milestone: The main project plan schedule is set up baseline
3) Prepare to develop and test the environment
I. Development and test environment
The development and test environment must be representative of the product environment
Isolation products, development and test environments are key
Ii. Prepare environment
Establish development and test environments
l Place the standard setting of the development and test plan
Consider logistics when generating and running development and testing environments
l Power and air conditioning
l Bandwidth and network access
l capacity
l Physical access and security
Iii. Establish and maintain a known situation
The development phase is only started after the baseline established for the development and test environment.
Implement configuration management and change control for tracking known shape
Synthetic development and test environment
IV. Review the milestone and delivery of the planning stage
Technical verification completion -> Customize the baseline of the specification -> Customized the baseline of the main project plan -> The baseline of the main project schedule is set -> The development and test environment has been established
Delivered product:
l Specification
l master project plan
l master project schedule
V. Standards for successful planning phase
Investors and teams agree on the following points:
l Solution Submit Component
l Key project milestone date
l How to generate
Development and test environment
The change control and configuration management process begins
Sponsor and key investors formally passed the commitments and get these entries
4) Summary of modules
The goal of the program phase is the architecture and design, project plan, schedule of the program.
Specifications are composed of detailed requirements, detailed scenes and design documents
Recommended estimation skills are discrete tasks with a downward estimate and allocation buffer time
For the program phase, submitted items are specifications, primary project plans, and master project time
