Timeline, cost and quality. Thus one can easily understand that project management is very much required for software project in order to facilitate, evaluate, accept user requirements, changes in project scope by properly assessing its impact on project budget, project timeline as well as project quality.
Once it is accepted that software project delivery is a not a simple or risk-free affair and it requires a proper process; then there is need of experienced and skilled professional who can articulate this process for the project and translate team effort, stakeholder communication and other aspects into project delivery. We are talking about IT project manager or software project manager. Software project manager is responsible for planning of project, project execution, monitoring and closure.
Project manager prepares software development plan, testing plan, identifies and assigns required resources, track progress, manages project communication among team members as well as other stakeholders. If enterprise businesses or critical public utility software applications are to be delivered, software project management is all the more important.
Like typical project management, IT project management involves number of activities to plan, track, monitor and deliver project. Software project management also involves certain activities about software development and maintenance. Introduction, nature and identification of risk, risk analysis, evaluation of risk to the schedule using Z-values. Identifying resource requirements, resource allocation, resource smoothening and resource balancing. Introduction, collecting data, visualizing progress, cost monitoring, earned value analysis, project control.
CM keeps check on any changes done in software. Change control is function of configuration management, which ensures that all changes made to software system are consistent and made as per organizational rules and regulations. Identification - A change request arrives from either internal or external source. When change request is identified formally, it is properly documented. Validation - Validity of the change request is checked and its handling procedure is confirmed.
Analysis - The impact of change request is analyzed in terms of schedule, cost and required efforts. Overall impact of the prospective change on system is analyzed.
Control - If the prospective change either impacts too many entities in the system or it is unavoidable, it is mandatory to take approval of high authorities before change is incorporated into the system. It is decided if the change is worth incorporation or not. If it is not, change request is refused formally.
Execution - If the previous phase determines to execute the change request, this phase take appropriate actions to execute the change, does a thorough revision if necessary. Close request - The change is verified for correct implementation and merging with the rest of the system. This newly incorporated change in the software is documented properly and the request is formally is closed. The risk and uncertainty rises multifold with respect to the size of the project, even when the project is developed according to set methodologies.
Gantt charts was devised by Henry Gantt It represents project schedule with respect to time periods. It is a horizontal bar chart with bars representing activities and time scheduled for the project activities. It is capable of graphically representing main events of project in both parallel and consecutive way.
Events, which occur one after another, show dependency of the later event over the previous one. Events are shown as numbered nodes. They are connected by labeled arrows depicting sequence of tasks in the project. This is a graphical tool that contains bar or chart representing number of resources usually skilled staff required over time for a project event or phase.
Resource Histogram is an effective tool for staff planning and coordination. This tools is useful in recognizing interdependent tasks in the project. It also helps to find out the shortest path or critical path to complete the project successfully. Like PERT diagram, each event is allotted a specific time frame.
Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New.
0コメント