As a software manager of a project, in addition to undertaking some development tasks, it is also necessary to track and check the work of software developers. This article divides the software manager's work into daily, weekly, milestone, and event-driven tasks. What is listed in this article is not a complete set of work, it is only an important task for your reference.
1.
Daily Work2. Read the daily report of each group's work check, reply to and solve the problems in the daily report; 2. Track the completion of the Group's tasks; 2. Check the completed tasks based on the tasks marked as completed in the daily report; 2. Collect the code inspection form based on the completed coding task marked in the daily report.
2.
Work required per week2. Code pegging: a) spot check code (according to the specification and code checklist); 2. Track the bug Library: a) Check the bug library, inform the technical staff of similar bugs or frequently-occurring bugs in a timely manner; B) promptly distribute detected bugs and track the bug resolution. 2. Weekly Progress: a) hold weekly meetings (attended by the leader); B) Check the completion of tasks of the week; c) Roll out detailed work plans for the next week (or work with the leader ). 2. Organize weekly team activities
3.
Tasks to be completed for each milestone2. Refine the milestone Plan (together with the general team) based on the milestone objectives formulated by the Project Manager; 2. Assist the project manager in completing the milestone summary; 2. Participate in the Milestone Report; 2. Organize the milestone submission documents.
4.
Event-driven work2. Organizational Review: a) reviews the requirements and design of the review organizer; strictly implements the review process; B) supervises the timely entry of the review defect feedback form and Review Meeting Minutes to CVS; c) Defects of supervisory review are modified and resolved in the reviewed documents; d) Supervise the entry of modified documents into the baseline database or controlled database. 2. Build: a) release the build as planned; B) Check the release functions in the build report against the planned tasks; c) make timely decisions on technical problems arising during the build process, avoid build delays. 2. Change Management: a) Reviews and confirms requirements and design changes, and supervises the implementation of changes; B) tracks database design changes; c) check whether the change records are complete and timely input to CVS, whether the changed configuration items enter the baseline, and whether the configuration administrator publishes a notification after the baseline change and records the release records.
