Team fundation server-based task software production and management

Some time ago, when I was about to leave the company's spm r & D project, I summarized my loss in the project, although this project should be regarded as a failed project (R & D project or not) in my personal mind, some standards and management methods of the project can be used for reference, for example, Team fundation server-based task project management! To put it bluntly, let's first briefly describe what is SPM (Software Procedure manage), which is software process management. In the previous article, I mentioned software standardized production, if a company wants to standardize software production, in addition to capital chains and business lines, the most important thing is a platform that can support these production lines, A deeper level should include some macro and micro management of the production process of these projects.

Team fundation server: TFS (Team Foundation server) is a workflow collaboration engine that allows a team to use their custom processes, it also uses a centralized data warehouse collected in real time in the project history. Team Foundation server and other components in Visual Studio team system constitute the core part of the software development process. Our method is unique because the front-end design has good availability, and the latter-end design integrates the entire lifecycle. We focus mainly on availability and enter the software development cycle in a seamless manner for individuals and teams. Another aspect of customer interest is flexibility and review. The team Foundation server supports the Capability Maturity Model (cmme) report and audit functions of the Software Engineering Institute. With team Foundation server, organizations can automatically collect necessary information and generate Custom reports, which can help locate growth points in industrial management.

Task: work item. In TFS, we can see that TFs uses work items to differentiate different work items from some tasks in the software process, such as user scenarios, bugs, and tasks.

The above is a brief introduction. In this section, we officially discuss how to implement software production and management based on the tasks of the team fundation server. First, we adopt agile development for software production, divided by iteration. Then we divide the production personnel of the Software. We initially define it as a project manager, a Program Manager, a developer, and a tester. This person will receive some work tasks more or less when working in agile mode. Such as analyzing requirements, Writing user scenarios, designing, coding code, testing function points, and modifying bugs. All tasks are called tasks, which can be divided and changed. I can split a large task into smaller tasks. The splitting process is actually the details of the work task. I add some attributes to this task, such:

Title: person who defines a job

Employee score: quantize the value of work tasks

Assigned to: the person who receives the task

Region: attached Project

Status: status of the task

Priority, estimated start time, actual start time, and working hours.

With these attributes, we can make micro-adjustments to some KPI values of the project through some attributes, and make the project return to formal by adjusting these KPIs, in addition, we can collect statistics on these attributes to form a software production report.

The following is an example:

Assume that a project has a development team lead and a developer. In addition to basic development, the development team lead is responsible for the basic management of some projects:

1. We need to develop a notebook based on the above requirements.

2. After receiving the requirements, the development team lead will score the requirements and divide them into short periods of time (this time should be based on the company's situation and the customer's situation and definitions) complete the small task. and assign it to developers. Of course, all task attributes are in the initial state.

3. The developer receives the corresponding task, develops the task as required, and changes the task status immediately until the task is completed.

4. After the developer completes the task and closes the task, another task (the tester's work) will be generated ), the tester starts the test (if the test is complete, the status of the work item can be changed). If a bug occurs during the test, we connect these bugs to the task of the developer. Because we use work hours during bug modification, it is also a kind of work task.

5. After the project reaches a certain stage, we can calculate these attributes, such as the working hours, the total number of working hours we use, and the pre-working hours of the project.

6. The final report can be used not only for reporting, but also for management personnel to provide guidance on software production and management.

Of course, we can use the project server to complete these functions, but we know that the Project Server is mainly for management personnel to provide project personnel, resources, and Progress Management. In addition to basic management for management personnel, TFs also provides code management for software production for engineering personnel. In addition, if we develop some features on the periphery to form a large function set. In this way, the software scale can be used to generate machines. The management method proposed above is only based on this machine model.

Welcome to the discussion!