Project Management (ii)-Planning project

The previous article introduced the Checklists of the Project Charter, and with the project charter, each team member could have a clear-headed pre-planning for what he was going to do next-or perhaps knew early on that he didn't have a clear idea. With the project planning, the team members ' attention can be gathered to the expected project output.

A plan that makes the project enough to start

What is the plan for the Constitution? Management wants to know when the team is developing what features. How do I measure progress? When will the project be completed?
1, use the time box to limit and start planning activities
A Time box (Timebox) refers to a specific length of time that an individual or team uses to accomplish a particular task. The amount of work the individual or team has done during this time is the basis for the project's next job. If necessary, individuals or teams can reduce the scope of work to ensure that work is done in the "Time box"

II. Development Project Planning Template

Project Planning Template:
1. Product Intent
Simple description of the product, why the company to develop this product, it can bring benefits to the company
2. Historical records
If you are managing a later version of a product, such as version 4.3 after 4.2, review the history of the previous or related version. This history can illustrate any previously known technical debt
3. Conditions of Release
The key deliverables of the project product are to be listed in detail. To identify them, ask: "If not, can we release the product?" ”
To include functionality, performance, and quality requirements

4, Target  
            The known targets may be subordinate to the following categories.  
           1) product goals may include requirements that have been prioritized, but are not committed in the current release version. This list may already exist in the backlog of products. &NBSP,
           2) project objectives may be targets such as performance standards that require more than general requirements, or "when the product is delivered, To reduce the number of unresolved defects from 50 to 40 ". Especially in the case of managing a project, the goal of each subproject is specific to the field in which the project is located. The project team will be able to address certain technical obligations and may also serve as a target for the project.  
           3) The team goal can be "increase the percentage of automated smoke testing for your product." The team may want to improve the performance or reliability of a particular feature.  
           4) organizational goals can be "reduce project time-consuming to increase organizational agility".

5. Project organization
1) clearly describe the team's responsibilities in the project, indicate how the project manager uses the life cycle to organize the project work, what key practices to adopt, and whether there are decision makers who can influence the current project
2) to describe the general mode of operation of the project. For example, strengthen the overall project team awareness during project startup, recruit new recruits, develop full functionality including code and documentation, write all the code, and check what can be recorded (at that time), and so forth.
6. Schedule Overview
You should create a schedule overview, marked with major milestones, and what people can get from those milestones. If you are using iterative or incremental development, explain the duration of the iteration (or increment) and indicate what outputs you can expect after each iteration (or increment) ends
For example:

Java code

2. Date Milestone
4. February 1st project started.
6. February 15th to show customers the prototype of the Web interface.
8. February 30th The first iteration of the development.
10. March 15th internal delivery web interface.
12. March 30th release beta release for customers to try
14. April 1st beta test started.
16. April 30th end beta test.
18. May 30th System online.

7. Staffing (Personnel curve)
Many project managers have no control over the staffing of the project team. If all the people are in place on the first day of the project, don't be surprised if there is a change in personnel. If you need to mobilize staff from other groups or teams, make it clear here: when and how many people to

8. Recommended Schedule
The project manager lists the major milestones according to the level of understanding
9. Risk List
At least the top ten risks are documented in the project planning. Also monitor these risks regularly and update the list at the right time. If you feel that the project currently has less than 10 risks, you may want to sit down with the project team and have a brainstorming session.

Project Management (ii)-Planning project