Development Management checklists (2)-planning project

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

The previous article introduced the checklists of the project charter.
With the project charter, each team member can make a clear pre-plan for what they want to do-or, early, know that they have no clear aspects. With project planning, you can focus the attention of team members on the expected project output.

1. planning to enable the project to be started

What is the plan when the Charter is ready? The management wants to know when the team will develop the features. How to measure the progress? When will the project be completed?
1. Use Time boxes to restrict and start planning activities
Timebox refers to a specific time length, which is used by an individual or a team to complete a specific task. The workload completed by an individual or a team during this period is the foundation of the subsequent work of the project. If necessary, individuals or teams can reduce the scope of work to ensure that work is completed within the "time box ".

 

2. Development project planning template

Project planning template:
1. Product intent
Briefly describe the product. Why does the company develop this product and what benefits it can bring to the company?
2. History
If you are managing a later version of a product, such as version 4.2 After version 4.3, you must review the previous or related version history. This historical record can indicate any previously known technical debt
3. Release Conditions
The key deliverables of the project products should be listed in detail. To identify them, let's ask: "If we don't do that, can we still release products ?"
To cover all functional, performance, and quality requirements

4. Objectives
Known targets may belong to the following categories.
1. The product goals may include such requirements. They have already been set with priority, but do not promise to be completed in the current release version. This list may already exist in the product's to-do list.
2. The project goals may be performance standards and the requirements for them will be higher than the general requirements, or "during product delivery, to reduce the number of unresolved defects from 50 to 40 ". Especially when a project is managed, the target of each subitem must be specific to the region where the project is located. The project team may also be able to address certain technical debts.
3. The team's goal can be to "Increase the percentage of automated smoke testing for products ". The team may want to improve the performance or reliability of a specific feature.
4. The goal of an organization can be to "reduce project time consumption to improve organizational agility ".

5. Project Organization
1. Clearly define the assignment of responsibilities of the team in the project, specify how the project manager uses the life cycle to organize the project work, what key practices should be adopted, and whether the decision makers can influence the current project
2. Describe the general operation mode of the project. For example, when the project is started, the whole project team should be strengthened, new recruits should be recruited, complete functions including code and documentation should be developed, all code should be compiled, and check (at that time) what can be recorded, and so on?
6. Calendar Overview
A calendar overview should be created, marked with major milestones, and what people can get from these milestones. If iterative or incremental development is used, you need to explain the duration of iteration (or incremental) and the expected output after each iteration (or incremental ).
For example:

Java code

1. Date milestone
2. The project was launched in February 1.
3. The Web interface prototype was displayed to the customer in February 15.
4. The first round of iterative development was conducted in February 30.
5. Web interface for internal delivery in March 15.
6. Release the beta version in April March 30 to allow customers to try it out.
7. Beta testing started on April 9, April 1.
8. The beta test was completed on April 9, April 30.
9. The system was launched in May 30.

7. Staffing (Personnel curve)
Many project managers cannot control the staffing of the project team. If everyone is called in place on the first day of the project, don't be surprised when there are personnel changes. If you need to move people from other groups or teams, you need to make it clear here: When and what type of personnel are needed

8. Recommended calendar
The project manager should list the major milestones based on understanding
9. Risk list
In project planning, at least the top 10 risks should be recorded. You must also regularly monitor these risks and update the list at the right time. If you feel that there are less than ten risks in the project, you can sit down with the project team and brainstorm

<Development Management checklists> by dylove98 @ Development Management checklists