Hang it on the wall, everyone is busy, the project is starting to look good, it’s okay at the beginning

Within a few days, I discovered that the plan seemed to have nothing to do with the actual work.

Last week’s work results and next week’s work plan

Filling it out hastily on weekends will not serve the purpose of tracking personal work progress.

Some work needs to be reworked, and some people have adjusted their plans and failed to complete the work according to schedule.

The plan hanging on the wall became a "plan" and its main function seemed to be to decorate the office.

How exactly do you get everyone to work according to plan?

How to know the progress of each person's work?

Compare the key points of task delegation: deliverables, responsible persons and time points are all included

Why does there seem to be no connection between the pending plans and everyone’s work?

The plan on the wall is too granular. I know every week, but I still arrange it myself every day.

During the running-in period, inexperienced employees may have to rework or repeat work.

First, the plan is not broken down into subdivisions, and there is a lack of a bridge between the plan and personal work.

Second, although training has been provided, the levels vary. Even with templates and guides, some work results are not up to standard due to lack of experience, and rework affects the execution of the plan.

Each group uses a whiteboard to further break down the group's weekly plan and implement it into human and daily life

The whiteboard can be modified in time, which is equivalent to a combat map, allowing everyone to know the combat mission.

Check the whiteboard every day and make adjustments at any time if there are any abnormalities.

On Friday, we will organize the weekly work report based on the whiteboard records. It will not take more than 10 minutes to fill in.

Weekly reports are used for tracking and analysis, forming a system of daily filling, weekly reporting, and monthly analysis.

Provide examples of high-quality work results for training, and see common mistakes on the whiteboard

The notes on the whiteboard are like a checklist. Check yourself before submitting.

Decompose work tasks into "key steps" according to workflow

Each key step is a person's work task and is the smallest management unit

The task breakdown only needs to be formulated on a rolling basis 1-2 weeks in advance.

Let the team members carry out the decomposition process on their own, and the team leader only provides guidance and confirmation.

Personal work tasks only have two statuses: "completed" and "uncompleted"

Here’s a breakdown of the key steps in requirements analysis

1) Prepare environment and data

2) Difference analysis

3) Determine the solution

4) Organize analysis reports

5) Review and confirm

start/end time

Deliverables and Completion Standards

Who is responsible for this matter and who to contact if you encounter problems?

Work responsibilities are written on the whiteboard so that each other knows who is doing what

Each group holds a "morning meeting" every day to review yesterday's progress and arrange the day's work

A weekly meeting is held every Friday afternoon, with all members of the project team participating

Similar to the daily stand-up meeting in Agile, it lasts 15 minutes and focuses on inspection and confirmation without discussion.

Step 1: Check status

Step 2: Adjust the plan

Step Three: Solve the Problem

Review and adjust project plans, requiring some discussion

Concerns

Relevant issues will only be briefly recorded in weekly meetings, and then special meetings will be arranged for discussion.

Preparation before meeting

meeting process

Overtime, resource allocation between groups and asking outside experienced people to help newbies

Share experiences and lessons learned horizontally and promote them to the entire project team to improve efficiency

Only by establishing acceptance criteria can we determine how to complete the task.

In order to implement it, it needs to be refined into each person’s work tasks.

Personal work plans can be managed through whiteboards to reflect the situation in real time

The core of software development is people, and fully mobilizing the initiative of "people" is the most important