Project management MS Project in software development

The article discusses the issues of creating software using the MS Project tool. The main methods of using application  tasks  with  MS  Project  are  shown.  The technology of the life cycle  of the  software project is described: definition of the project implementation time, product evaluation, observation of the implementation and monitoring, establishment of links. The specificity of the content of the execution of the software product is singled out, in which the main tasks are indicated: the time spent on the project, the specialists needed for the project, the estimated costs. The author considers the issues of software for the implementation of the project plan, as well as the fulfillment of the methods of technical assignments. Conclusions are drawn about the use of a large number of complex problems, which makes it difficult to prepare a quick assessment of the problem. 

At creation of software for control of projects I want to share the manual of use MS Project. As during a few years worked with projects, as a result methodical instructions on use MS Project are developed. It is the set of the proposals and simple methods for the decision of applied tasks by the project leader with the aid of MS Project. If the user acquires by one version, then in subsequent will work without problems. Given work is considered to 2014 versions. The type of the program is shown on the Figure 1.

Figure 1. The program of MS Project interface

Let's will remember the first version. For knowing it is not difficult, and for beginning it is necessary to remember. Moreover creation of the project of software is creation a few products [1].

During life cycle possibly performance of chief's various tasks. In the beginning of the project it is necessary answer two questions:

1. Time to execution of the project;
2. The evaluation of the

The chief's main obligation it preparation of the project by specified time and it will influence her price. Unexpected circumstances can take on the time of performance of the project. Sometimes possibly and the time reduction of performance of the project. The project leader should supervise, as contingencies are possible. There is the sole exit for performance of given task it thorough planning, performance and errors correction in time, constant supervision of the problem. As a rule chief заканчвает work after total check of the project. First of all it is necessary to find out on how much project left for performance schedule. Not seeing to external complexities MS Project is very simple in performance. For it is necessary to use task, resource, schedule and their communication.  Actually, it is database and user's interface for processing.  They are task duration, volume directed resources and their various properties. If given properties will little, then you can добовить your work.   Task is possibly to connect among themselves by раличными connection. Resource has various properties, one of the main it availability in time and use of them in time-table. Ресур can be directed to task, on the basis of these data in MS Project possibly performance various kinds of filtration, grouping, samples.

Besides it, with the aid of a few algorithms with calculation of availability of resources time is calculated begginning and the end of task and communication between them. Work of the program is executed exactly so. At creation of software control of project it is executed in a few phase. At the end of each phase we should receive communication , therefore we should count total time of the project, and each phase separately. The sole resource requirement is people, as to result of work will correct not include unfamiliar people. During work of the plan it is necessary to answer three questions and to terms of reference:

1. Time is spent to project;
2. What (how much) specialities are needed for project;
3. Approximate working project

To do this, in MS Project we are preparing a project implementation plan. In the course of the assignment, you must implement them on a mandatory basis. In the method of performing the technical tasks of the job for a week, if the period was delayed, then it is worth considering the retail connection base. The estimation technique I like the most simple: a simple problem – 2 days, medium difficulty –1 week, difficult task 2 weeks. Also should not be too many difficult tasks, this approach allows significantly faster in the preparation of the evaluation plan. Of course, on the one hand, the estimate is not accurate, but if you look on the other hand, the question arises which one is more accurate.

When performing certain tasks there are several executors. This is wrong, each task must have one performer. Implementation of the plan is performed in several stages:

1. Preparation of job list;
2. Setting dependencies between tasks;
3. The appointment of the assignee;
4. The obtained result of the balancing

The most important thing in the methodology is equalization. The purpose of this process is to prepare a plan, which is distributed equally among the performers. At the initial preparation of the plan, as a rule, unattractiveness is not fully chosen [2]. So let's start classifying them. In the course of manual classification of performers to divide by the direction and stages. For this, we group tasks by performers, because we need to see the location of the tasks. For convenience, it is recommended to sort tasks by the beginnings time. Theoretically, the loading graph is used to estimate the loading of the user. For managers, these schedules are evaluated at a very high level. Then the classification is carried out. For all project participants, minimize the time required for execution each stage. To do this, we perform the following actions:

1. Replacement of the task executor;
2. Transferring the task to another

Due to the lack of prompt receipt of the result by the task stages, it is possible to extend the deadline, but not transfer to another stage. Also, if in the loading of the performer the work of the stages is wrong, the performer should not be replaced. Thus, the tasks can be taken from the following steps. Unfortunately, after each change, the entire resource loading will have to be performed manually. Despite the difficulties, this process usually sets a finite time. Now let's look at another project, and will check the correct location of the links between the tasks, the correspondence of the specialty and the qualifications of the performers. The latter type is a risk report [3].

Possible task and risk level, as well as the expected duration, depending on the methods of determination. It is necessary to avoid such a threat, because the result of the work is evaluated. Therefore, I think that it is necessary to carefully review the tasks at each stage of implementation. Speaking about all  this, the project implementation plan is being taken. We can apply this plan in the following order.

1. Determination of the duration of the project and its stages;
2. Estimate of project

Monitoring the implementation of the project plan, included in the work during the main, used to evaluate the project, can be used for monitoring. From the project manager requires compulsory completion of the following actions:

1. Distribution of tasks to performers;
2. Set the project tasks;
3. Correct significant deviations of the 

The results of performing tasks by executors can be performed in different ways. Performances can be divided into short iterations. Since the values and methods depend on the direct loading of the TFS, it is possible to use the TFS iteration and MS Project. It is important to constantly update the initial plan. To determine complex areas, it is possible to use different groupings by performers and components. I do not advise for functional communication or for categorizing tasks in the MS Project to use a set of tasks. But to manage the structure of the job, I suggest using the user field. In the Project MS there is a set of fields that you can use at your discretion. The user can divide tasks into categories, for example, according to the type  of work: familiarization, execution, protection. The execution of the work is shown in Figure 2 [4].

Figure 2. Completing of the work 

In MS Project, based on the properties of the job, you can set the drawing rule for the chart. When fields are used in the MS Project, the user can receive various forms in the result of filtering, sorting and grouping tasks. As a result of the work, we get the project plan. Usually the original database is stored as the base one. And so, project management is the acquisition of project goals as a result of planning, organizing and managing resources and tasks. As a result, in the MS program the Project is considered in the possibility of project management and their implementation at a high level. The program is easy to work with. Using MS Project for project management, gives the user the opportunity to make the best decision and finish the job very quickly.

References

1. Bogdanov, V (2007). Upravlenie proektami v Microsoft Project 2007 [Managing projects in Microsoft Project 2007]. Saint Petersburg: Piter [in Russian].
2. Grekul, V.I., Denshchenko, G.N. & Korovkina, N.L. (2005). Proektirovanie informatsionnykh sistem [Design of information systems]. Saint Petersburg: Intuit [in Russian].
3. Rudakov, A.V. (2006). Tekhnolohiia razrabotki prohrammnykh produktov [Technology of software development]. Saint Petersburg: Akademiia [in Russian].
4. Alan Shallouei, Dzheims R. Trott  (2002).  Shablony  proektirovaniia  [The  design  patterns].  Saint  Petersburg:  Viliams [in Russian].