Software Project Management

kaushalsai · 发表于 2019-04-04 17:35:10

The job pattern of an IT company engaged in software development can be seen split in two parts:[br][br]Software Creation[br][br][ul][li]Software Project Management[br][/li][/ul]A project is well-defined task, which is a collection of several operations done in order to achieve a goal (for example, software development and delivery). A Project can be characterized as:[br][br]Every project may has a unique and distinct goal.[br][br][ul][li]Project is not routine activity or day-to-day operations.[br][/li][/ul][ul][li]Project comes with a start time and end time.[br][/li][/ul][ul][li]Project ends when its goal is achieved hence it is a temporary phase in the lifetime of an organization.[br][/li][/ul][ul][li]Project needs adequate resources in terms of time, manpower, finance, material and knowledge-bank.[br][/li][/ul]Software Project[br][br]A Software Project is the complete procedure of software development from requirement gathering to testing and maintenance, carried out according to the execution methodologies, in a specified period of time to achieve intended software product.[br][br]Need of software project management[br][br]Software is said to be an intangible product. Software development is a kind of all new stream in world business and there’s very little experience in building software products. Most software products are tailor made to fit client’s requirements. The most important is that the underlying technology changes and advances so frequently and rapidly that experience of one product may not be applied to the other one. All such business and environmental constraints bring risk in software development hence it is essential to manage software projects efficiently.[br][br][br]

[br]The image above shows triple constraints for software projects. It is an essential part of software organization to deliver quality product, keeping the cost within client’s budget constrain and deliver the project as per scheduled. There are several factors, both internal and external, which may impact this triple constrain triangle. Any of three factor can severely impact the other two.[br][br]Therefore, software project management is essential to incorporate user requirements along with budget and time constraints.[br][br]Software Project Manager[br][br]A software project manager is a person who undertakes the responsibility of executing the software project. Software project manager is thoroughly aware of all the phases of SDLC that the software would go through. Project manager may never directly involve in producing the end product but he controls and manages the activities involved in production.[br][br]A project manager closely monitors the development process, prepares and executes various plans, arranges necessary and adequate resources, maintains communication among all team members in order to address issues of cost, budget, resources, time, quality and customer satisfaction.[br][br]Let us see few responsibilities that a project manager shoulders -[br][br]Managing People[br][br]Act as project leader[br][br][ul][li]Liaison with stakeholders[br][/li][/ul][ul][li]Managing human resources[br][/li][/ul][ul][li]Setting up reporting hierarchy etc.[br][/li][/ul]Managing Project[br][br]Defining and setting up project scope[br][br][ul][li]Managing project management activities[br][/li][/ul][ul][li]Monitoring progress and performance[br][/li][/ul][ul][li]Risk analysis at every phase[br][/li][/ul][ul][li]Take necessary step to avoid or come out of problems[br][/li][/ul][ul][li]Act as project spokesperson[br][/li][/ul]Software Management Activities[br][br]Software project management comprises of a number of activities, which contains planning of project, deciding scope of software product, estimation of cost in various terms, scheduling of tasks and events, and resource management. Project management activities may include:[br][br]Project Planning[br][br][ul][li]Scope Management[br][/li][/ul][ul][li]Project Estimation[br][/li][/ul]Project Planning[br][br]Software project planning is task, which is performed before the production of software actually starts. It is there for the software production but involves no concrete activity that has any direction connection with software production; rather it is a set of multiple processes, which facilitates software production. Project planning may include the following:[br][br]Scope Management[br][br]It defines the scope of project; this includes all the activities, process need to be done in order to make a deliverable software product. Scope management is essential because it creates boundaries of the project by clearly defining what would be done in the project and what would not be done. This makes project to contain limited and quantifiable tasks, which can easily be documented and in turn avoids cost and time overrun.[br][br]During Project Scope management, it is necessary to -[br][br]Define the scope[br][br][ul][li]Decide its verification and control[br][/li][/ul][ul][li]Divide the project into various smaller parts for ease of management.[br][/li][/ul][ul][li]Verify the scope[br][/li][/ul][ul][li]Control the scope by incorporating changes to the scope[br][/li][/ul]Project Estimation[br][br]For an effective management accurate estimation of various measures is a must. With correct estimation managers can manage and control the project more efficiently and effectively.[br][br]Project estimation may involve the following:[br][br]Software size estimation[br][br]Software size may be estimated either in terms of KLOC (Kilo Line of Code) or by calculating number of function points in the software. Lines of code depend upon coding practices and Function points vary according to the user or software requirement.[br][br][ul][li]Effort estimation[br][br]The managers estimate efforts in terms of personnel requirement and man-hour required to produce the software. For effort estimation software size should be known. This can either be derived by managers’ experience, organization’s historical data or software size can be converted into efforts by using some standard formulae.[br][/li][/ul][ul][li]Time estimation[br][br]Once size and efforts are estimated, the time required to produce the software can be estimated. Efforts required is segregated into sub categories as per the requirement specifications and interdependency of various components of software. Software tasks are divided into smaller tasks, activities or events by Work Breakthrough Structure (WBS). The tasks are scheduled on day-to-day basis or in calendar months.[br][br]The sum of time required to complete all tasks in hours or days is the total time invested to complete the project.[br][/li][/ul][ul][li]Cost estimation[br][br]This might be considered as the most difficult of all because it depends on more elements than any of the previous ones. For estimating project cost, it is required to consider -[br][/li][/ul][ul][li]Size of software[br][/li][/ul][ul][li]Software quality[br][/li][/ul][ul][li]Hardware[br][/li][/ul][ul][li]Additional software or tools, licenses etc.[br][/li][/ul][ul][li]Skilled personnel with task-specific skills[br][/li][/ul][ul][li]Travel involved[br][/li][/ul][ul][li]Communication[br][/li][/ul][ul][li]Training and support[br][/li][/ul]Project Estimation Techniques[br][br]We discussed various parameters involving project estimation such as size, effort, time and cost.[br][br]Project manager can estimate the listed factors using two broadly recognized techniques –[br][br]Decomposition Technique[br][br]This technique assumes the software as a product of various compositions.[br][br]There are two main models -[br][br]Line of Code Estimation is done on behalf of number of line of codes in the software product.[br][br][ul][li]Function Points Estimation is done on behalf of number of function points in the software product.[br][/li][/ul]Empirical Estimation Technique[br][br]This technique uses empirically derived formulae to make estimation.These formulae are based on LOC or FPs.[br][br]Putnam Model[br][br]This model is made by Lawrence H. Putnam, which is based on Norden’s frequency distribution (Rayleigh curve). Putnam model maps time and efforts required with software size.[br][br][ul][li]COCOMO[br][br]COCOMO stands for COnstructive COst MOdel, developed by Barry W. Boehm. It divides the software product into three categories of software: organic, semi-detached and embedded.[br][/li][/ul]Project Scheduling[br][br]Project Scheduling in a project refers to roadmap of all activities to be done with specified order and within time slot allotted to each activity. Project managers tend to define various tasks, and project milestones and them arrange them keeping various factors in mind. They look for tasks lie in critical path in the schedule, which are necessary to complete in specific manner (because of task interdependency) and strictly within the time allocated. Arrangement of tasks which lies out of critical path are less likely to impact over all schedule of the project.[br][br]For scheduling a project, it is necessary to -[br][br]Break down the project tasks into smaller, manageable form[br][br][ul][li]Find out various tasks and correlate them[br][/li][/ul][ul][li]Estimate time frame required for each task[br][/li][/ul][ul][li]Divide time into work-units[br][/li][/ul][ul][li]Assign adequate number of work-units for each task[br][/li][/ul][ul][li]Calculate total time required for the project from start to finish[br][/li][/ul]