New Director of research and development old m, talk more smoothly, get along with not too difficult _ daily notes

Good early want to open bo, but lazy Ah, dragged a year later, finally took the first step, to encourage themselves.

The new director of old M, has been in touch with a few days, do a set of, technical origins persuasive, give me a group of rookie a lot of guidance, firmly believe that the team really need a manager-mentor role.

Old m organization full communication, to promote planning Gantt chart and design constraints and tools to facilitate the team communication unified language, I have some small confusion, and then old m to communicate a bit.

Question one: The Gantt Chart does not affect the team's spontaneity, it may be 3 days of things estimated 5 days to complete, to keep their own buffer. If there is a deadline project, then we have to reverse the evaluation, another too long plan needs to adjust and compress time. Gantt Chart WBS to fine-grained, child task granularity can not exceed 3 days, so that we do not have too much buffer space. From the management point of view, need to track and feedback, timely adjustment plan. Question two: The company originally is pushes agile, does not emphasize the meticulous plan, another set of Jira system is manages the project task, and the Gantt Chart has the conflict. Agile for the Internet company's rapid iterations, I do enterprise-class products allow the rules to work as planned. In the immature team, should pay more attention to the plan, otherwise many things are drifting up, can not be implemented and tracked. Process and constraints (access conditions), help the team to develop good work habits. Conclusion: For the time being, we are only locally optimized (the overall process is not moving), emphasizing planning (teams and projects) and documentation (product, design, test documentation). Gantt Chart only for the team leader to make plans to improve the ability to manage their own teams. The team leader will then enter the WBS task into the Jira, because Jira is the management and collaboration system, we still cannot abandon. Project personnel Plan and deploy Kanban, and post tasks to Kanban. The group leader organizes the daily station meeting, everyone speaks what I did yesterday, what to do today, I have what difficulties and obstacles and so on.

Question three: The question of data collection and measurement, previously done agile also made a Gantt chart, the collision of the two modes has become more and more blurred, what is the goal of measurement.

The purpose of metrics is to perceive the causes of nature through data representation and to analyze classifications to provide a reference for the next iteration improvement. The team is the first to do the basic data collection, in due time to do data analysis and measurement, and old m will teach us some methods. Metrics can have plans (Gantt Chart vs. Actual) and goal metrics (measured in product quantities). Conclusion: The problem is classified and sorted into Jira system, which is collected for data analysis. Delayed start------> reason is the following 1.2.3.4 ... Design delay------> reason is the following 1.2.3.4 ... Development latency------> reason is the following 1.2.3.4 ... Test latency------> reason is the following 1.2.3.4 ... Delivery delay------> reason is the following 1.2.3.4 ... equipment, resources not in place development skills not enough design skills insufficient test skills not completed on hand task not in time to start the next task scheduling conflict external dependencies Other pending conclusions: The following two important points of planning and tracking Summary and feedback