Introduction to task decomposition

Introduction to task decomposition

 

This series of articles is written by ex_net (Zhang jianbo). Please indicate the source for reprinting. Http://blog.csdn.net/ex_net/article/details/8741982author: Zhang jianbo mail: 281451020@qq.com Phone: 13577062679 welcome to contact us!

 

Before talking about task decomposition, let's take a look at the summary.

Work Breakdown Structure)
WBS is also known as Work Breakdown system. it is a map of the project that identifies the products and work elements involved in a project. WBS is an outline of the project with different levels of details, it defines the relationship of the final deliverable to its subdeliverables, and in return, their work packages.
WBS helps to assume project managers that all the work are identified and established.

----- From Baidu encyclopedia

 

As a manager, when getting a specific project, you should close the door and quietly think about how to complete this task and what tasks need to be done to complete this project, what resources are required to complete these tasks? When the series are all straightened out, the scheduling period begins. What is done first and what is done later. The time limit for completing each task.

 

My team and I use a project management software. The software is open-source. Interested friends can download from http://www.dotproject.net/here. Use PHP + MySQL. It takes about half an hour.

 

In a project, the time limit is generally known and is determined by the project's own schedule. Therefore, we should try our best to achieve "clear task objectives, clear task content, and reasonable task execution Permissions" When disassembling tasks ". Only in this way can the executor of each task be ensured, and tasks can be quickly understood and executed quickly.

This is a product that our team is developing. It is the task management interface of the dotproject.

 

In actual management work, many of my friends may be as confused as I am.

The task is too large to be completed for half a day, or the "process" is out of control;

The task is too small, and it feels like a tractor project. Everyone is a bunch of tasks. Looking at the task list, the first thing is to scare people;

 

Recently, after calm and careful consideration, I came to the conclusion that the unreasonable task decomposition is ultimately caused by "only people.

In the past, I always followed these steps when splitting tasks:

(1) how many people are there?

(2) What can they do?

(3) start scheduling tasks .....

(4) If it cannot be arranged, first place it .....

 

If you look back, you will inevitably find problems. When breaking down tasks, we think too much about human factors, especially our own. Is the decomposed task still "reasonable?

After the last 1 ~ 2 years of project management. Task Decomposition cannot be "divided by people ".

 

As a project manager, we should keep our eyes open. When breaking down a task, you need to "divide the task by event ". Because you need to do something to break down the corresponding task. The following process should be followed when the task is decomposed:

(1) Current project requirements

(2) Identifying key task nodes

(3) sort out the subtasks required to complete these key task nodes

(4) form a complete task list. Use 1, 2, 3, 4, to list all tasks.

(5) team members who can complete these tasks through "Bidding" within the team;

(6) If the internal team members cannot meet their needs, more members from "world" to "Bidding" will participate.