Software Project Management - Part 1

[no dialogue]. Good evening one and all. It's a pleasure for me to introduce all my team members. My team members are Chendra, Mallikarju, Vijay, and it's me. Before starting my presentation I would like you guys to ask a small question about what is a software? Well, a software is an instruction of programs or computer which performs certain tasks and coming to the presentation, our presentation is on software project management. This is an agenda which we are going to take today. That's the introduction part which I am going to handle. Project planning, management spectrum, and measurement and metrics will be taken care of my friends. Projects scheduling and conclusion [unclear audio] which I thought would be benefit for the class and the last one is queries. The first starting word is a software project management. It is a sub-discipline of project management which deals with the software project for monitoring planning and controlling. Well, the main object of software project management is defining the requirements that are needed by a software. And next coming into the management spectrum is managament spectrum focuses mainly on four Ps, that is people, product, project and process. And software project management is an activity or an umbrella activity in software engineering. And it begins when the project is initialized and lasts until the development of the computer software. Next, coming into the management spectrums like people, product, process and project, which would be coming in a later part of the presentation. And coming to what is project planning? Project planning is identifying the scope of the project, estimating the work involved, creating a project schedule. It's like effective planning plays a major role for the development of a software. And this is the first component of software project management. Defining and documenting the assumptions, goals, and estimating the cost schedule of the project, is the first step of the planning process. Next coming into the estimation, estimates are made depending upon the beginning of the project and it would be regularly updated as a project proceeds. The estimations should be made in the best and worst case of any scenario. So that it should be bounded by the outcome. And, not only that, next comes a project management and control. The main objective of this is to monitor the project and keep track of all the things which are going on in the project like updating things whether there are any changes in the project. For example, if there is any unfortunate reason for happening that there is any change in the plan then the project manager needs to take care of all this things. And it is his responsibilty to solve the issue. And if there is any problem then the project manager would schedule meetings with all its team members. And next coming is the main object of this project control is on--if there are any deviations occuring in the plan, then those deviations should be detected earlier so that the organization could keep up very easily and effectively. And inspite of all these things, most of the project control techniques are based on splitting the goals into sub-goals and those sub-goals are splitted further down into small sub-tasks. Then this kind of breaking of this goals into sub-goals and sub-task is also called as breaking structure. And next coming into management spectrum is mainly focuses on four P's: people, product, process, project. People are the most important part in any software industry or developing any software. People is the main focus because if you bring people together, or arrange people into team, then you can be successful. We have a main software engineering institute which has proposed people management capability material model. If this model or level is used in every organization, then that organization would be successful and there will not be any issues or errors if you use this kind of technology or model. In the later part we'll take advantage. Hi friends. Team leaders. Team leaders are the one who has the qualities of the leader and it should encourage the technical people and should capable offer selecting the existing process and he should be capable of taking it to the final process. And next is a software team that is, we have three parts in that: democratic decentralized, controlled decentralized, and controlled centralized. In the democratic decentralized, there is no team leader for that and there will be a task coordinator who will coordinate all the tasks in that. And later on, he acts as a leader but he's not a leader. And he's [unclear audio] for the short durations. And after sometime he'll be replaced by the other one. And next is control decentralized. In the control decentralized there will be two leaders. One is primary leader and the other is a secondary leader. The primary leader, he takes care of all the main tasks and the secondary leader takes care of the sub-tasks. And go to the back slide. And third one is the control centralized. In that, there will be one leader who he'll be taking care of all the main things, main parts of the project. And next is the product. In this product, prior to the beginning of the project, you should examine what other problems when they get during the process of doing the project and they should know how to solve the problems in that and they should be able to solve the problems when the product is in progress. And they should know the scope of the project should be determined. And next is the scope. There are three things in this, the scope of product is different by answering to the following questions one is what is context? What are the things that should be considered? And what are the constraints imposed on the product regarding the context. And next is information objectives. In this we should know what are the inputs that had to be given to the functions? And we should determine the output with that. And next coming the functions and performance. We should know that prior to giving the input, we should determine the output so that we can do the exact input of that. And problem decompositon. It itself says that decomposing a problem, that is elaborating the problem in that...it is the intitial step of the software requirement and analysis. And the problem is it's decomposed into two parts. One is the functionality that must be delivered and the other one is the process that is used to deliver it. So in this day the problem is not completely decomposed. So we use the next process of that. Go to the next slide. Next is the process. In this process, the basic idea of this process is to create-- we should know the basic plan for developing a software prior to designing a software project. In this, there are various software process in this are one of the linear sequential model, the prototyping model, the rapid application development model, the incremental model, the spiral model, the formal methods model and the concurrent development model.