Speaker 1: Jai Hind, my name is Mukhleet Goyal and I am Assistant Professor in Department of MCA. Today I am here to present a lecture from the subject software project management and the topic of my presentation is project management and planning. So the content of my slides is what is management, what is project, requirement for project management, characteristics and objectives of project, project knowledge areas and step by approach of software planning. First of all, what is management? Management is defined as achieving goals in a way that makes the best use of all resources and it includes around 8 activities which starts from planning. Basically what is planning? Planning is the function where we decide what is to be done, what we want to done. So before starting anything we do a planning for that event or any event or developing any project. Second is organizing, in organizing in which we bring together a physical, financial and other development related people to achieve a organizational goal. So in organization we make arrangements. Third is staffing. Staffing means we have to select the right people for the job so that all our functions can be executed properly. Fourth is directing in which we give the instruction and supervise. The directing can be achieved through a role which can be defined by we can say it like project manager, team leader. Next is controlling in which we control the standards, we abide by the standards, monitoring we have to check on the progress, innovating when we have to give some solutions or we can update our software or our project according to the customer needs. And last is representing in which we liaising with the clients and developers and other stakeholders so that they can come with us and they join hands with us for developing any project or manage anything. Next what is a project? Basically project is an effort in which we create a unique product or service which includes cost, schedule and outcome. Project is planned set of interrelated tasks to be executed over a fixed period of time within certain cost and other limitations. So in project management what will we do? We do what we by doing all these activities we manage, we learn how to manage a project. So what is project management is a discipline in which we do a planning, organizing, motivating, scheduling our resources to achieve a specific goals and guide a product or a project from start to finish. Why we need project management? Basically we need project management for the better control of financial, physical and human resources. We can improve our customer relations. We develop anything in a shorter times, lower our cost, increase our quality and reliability, improve our productivity and achieve a better internal coordination between the employees. Next what are the characteristics of project? Basically what are types of the project? First are the non-routine project, second is planned project, planned project are those project which we do for achieving any specific goal, aiming at the specific target. For example, we are developing any project to identify the health beings of the people of Gwajarwad. So the people of Gwajarwad is a specific target, work carried out for a customer, the example of work carried out for a customer is like the government of India given the portal of income tax to the Infosys. So for Infosys the government of India is customer and they have to work for the, they have to develop that IT portal, income tax portal for government of India involving several specialists. What is this specialist? Specialist means that the person is doing some special work like for design, for developing any web project, the interface or we can say the landing page is developed by some web creator, not a developer which do a code. Basically that work is done by a graphic designer. The characteristics, one of the characteristics is made up of several different phases. This is constrained by time and resources and the last characteristic, the some projects might be large and complex. Now next is what are the objectives of web? So for defining the objectives of web we have a very good or we can say a very smart word which is, which is, which is smart. This word, each alphabet in this word itself explain all the objectives of the project. S, S means might be simple, in some terms we can say that our project should be simple and easily understandable to a client and along with simple it should be specific. Each project or each module should do some specific work. M is for manageable. What we can say manageable or it should also be a measurable. Then comes A, A means attainable. What does this attainable means? Attainable means the project which we are doing or product which we are developing or designing it should be attainable. It should not be a hypothetical we thought something and we start working on that but it should not be a really attainable. R is for realistic and relevant and T which is a very major constraint for any project development is time constraint, is time constraint. So each project should be developed within a specific time frame. S, now I will define S is specific or simple, M is manageable and measurable means that it should satisfaction of the objective can be judged, achievable or attainable means that within the power of the individual group or concerned to meet the target means which group of people we decide for achieving any project they should attain the goals of that project. Then R is for relevant or realistic the objective must be realistic to define the true purpose of the project and last is time constraint which is defined that all the objective should be achieved within a time frame. After this objective there are 9 project management knowledge areas. These knowledge areas are defined into 2 categories or we can say might be in 3 categories in which one is core, core knowledge area, second is facilitating core area and last is, last core area is, is integration, integration of these 2 types of core areas. So the core key areas have, there are 4 core key areas, there are 4 facilitating key areas and integration itself is a one core area. So the core areas which is the, knowledge areas which are the core knowledge areas are scope, time, cost and quality. Four facilitating key areas are human resource, communication, risk and procurement management and the last is project integration management. So what is the scope? What is the scope of the project or who comes under these 4 core knowledge areas? Who will define the scope of the project? Scope of the project can be defined by the organization which is developing that project or by the client, by the client who, who comes for that project. Time, time is the duration which is taken to develop that project, cost is the money involved and quality is the another parameter which define, which is very important for development of any project. If the project is not of the good quality then the chances of its failure are more. So the 4 facilitating knowledge areas are like human resource, communication, risk and procurement management. What is human resource? Human resource in short form we say is HR, means who deals with the behavioral concepts of the employees. Communication is related with somewhat with the marketing or our representation. Risk is the, what is the risk in the risk management in or risk handling while developing any project and procurement management, procurement management is deal with the raw materials and the one knowledge area which is integration management is well defined through this image that is the, what are the, what stakeholders or a client needs. It is only needs and expectations, it only have needs and expectations and what we do by using some tools and techniques we develop a project with 4 these core functions, 4 these facilitating functions and these 4 core functions and 4 facilitating functions are integrated through project integration management using by, using some tools and techniques. And after the, after these projects are developed we define the enterprise success. If we, if we design or develop a successful project obviously our enterprise is going to success. So what helps in our successful project? In successful project there are 10 criteria's, one is executive support means employees, user involvement, experienced project manager, clear business objectives, we should be clear what we want to achieve with this project, minimize scope, standard software infrastructure. We have some basic requirements to develop any project, we have to define one methodology like the project for web we needs, might be we use Javascript, we use NodeJS, we use AngularJS, reliable estimates and some other criteria's which we create for small, small milestones that if we do our planning, what we have done in our design, what, how, when we have to done for our, when we are completed our coding work. So we should create some small, small milestones, we should do proper planning and take a proper ownership. Now there is one for doing that plan we have some step wise activities and these step wise activities are defined in this flowchart type structure, there are around 11 activities which starts from the select project and the planning ends with the lower level planning after which we do a review. So what we have to do, first we define, first what we do we select a project, after selection of the project we identify its objective and its infrastructure, for developing any project why we are developing it and next what infrastructure we need for develop this project. For example, if we, I have my own company, for example I have my own company and I have two clients, one needs a web project or another needs a device based project. So the infrastructure for web project is different and the infrastructure for IOT based project is different, might be the technologies of both the projects are different. So for after selecting a project what we have to do, we have to identify the objectives and then we have to identify the project infrastructure, then after defining or identifying all these both things we analyze the characteristics of the project. After analyzing the characteristics we identify the product and activities, after identify the product and activities we do estimate, for each activity we do a, we identify the risk, means after doing this activity what are the risk factors which are involved. We allocate resources, we publicize plan, we execute plan and we do a planning for reviewing our products and activities. So let us define these step wise planning one by one, first is established project scope and objectives. So in this how do we know that we get success, first we have to define who will take the project authority, means we have to report to whom, if we are employees. Modify all stakeholders in the project and their interest, modify objectives in the light of stakeholder analysis and establish method of communication with all the parties. Means we have to communicate through online mode, we have to communicate through offline mode or we do a meeting weekly, monthly, we have to establish all those modes and methods for communication. Second is establishment of infrastructure, we establish link between the project and any strategic plan and identify the standards and procedures. After that we identify project team organization, means we have to fit whom and where. Third is analysis of project characteristics in which we distinguish the project as either objective or product based, like I told Kimmy's objective of either objective or product based means in which we develop any device and in objective based like web project or android project. Second analyze other project characteristics in which we have to define the unique things of that project and what is different about this project. Then identify high level project list and take into account the requirement and concerning implementation in which we define the general life cycle approach. Fourth, identify product and activities in which we do a testing, what we have to produce and how we have to produce and what we have to develop. Means we have to develop an analysis report, any change request, any cautionary design if we do any survey. In product design we have to define, describe the product, means product identity what it is, how, what, on what it is based on, what are its composition and what are its format, what standard is follow and what quality criteria it has to be, it has to met. In testing plan what we do, we do a cautionary design, we analyze the report and if there is any change request then we do that. Then produce ideal activity network in which we identify the activities needed to create each product in the product description. Then it might be possible to identify specific instances and we have to, also we have in some cases we have to left some for the later phases of the product, for the project. Then we have to add the checklist if needed in the step 4, we have to put a checklist after completing how much module or how much work we have to analyze our work. So that to analyzing that work or at any certain point of time we have call it as a checklist. Now come at the step 5 in which we estimate efforts for each activity, we carry out bottom up estimates in which we distinguish carefully between the effort and the time and revise plan to create controllable activities, break up the very long activities into series of the smaller activities and bundle up very short activities to create a checklist. In step 6 we identify activity risk, activity risk means identify and quantify risk for activity if any damage if occurs then we have to define and we have to measure it in the times or money like many projects are put on the hold because of the corona time in 2020. So that is the risk which is been come and we have to identify our loss of time or the loss of any of money if any occurs. Then we have to plan risk reduction, how we have to, how I have to minimize that risk then adjust overall plan and estimates. Then in step 7 we allocate resources, identify and allocate resources to activities, revise plan and estimate to take into account resource constraint. What we do? We develop an a grand chart and define our work in terms of months, testing, subjects, test, analyze results or any draft changes if we do. Then we review and publicize our plan and step 9 and 10 we execute and create a lower level plans. So this step wise approach is only for planning activity not for the software whole development activity. These steps are involved only in which how do we plan for starting any project, how do we start our software project management. That is all from my side. Thank you very much.