7 a] What is software project management explain project management lifecycle.
Software project management is a discipline that involves planning, organizing, and managing resources to bring about the successful completion of specific software project goals and objectives. It encompasses various activities and methodologies to ensure that software projects are completed on time, within budget, and meet the required quality standards. Key aspects of software project management include:
- planning : – Deciding what is to be done.
- Organizing – making arrangements
- Staffing – Selecting the right people for the job etc.
- Directing – Giving instruction.
- Monitoring – checking on progress
- Controlling – taking action to remedy hold-ups.
- Innovating – Coming up with new solution.
- Representing – liaising with clients , user, developer, supplier and other stakeholders.
Project Management Life Cycle.
Project Initiation
The software project management life cycle begins with the project initiation phase, which typically starts with project concept development. During this phase, various aspects of the project, such as scope, constraints, cost, and benefits, are thoroughly examined. A feasibility study is conducted to determine whether the project is financially and technically viable. This is applicable to both in-house product development and outsourced projects. Based on the feasibility study, a business case is developed. Once top management approves the business case, a project manager is appointed, the project charter is created, and the project team is formed. This sets the stage for the project planning phase.
During project initiation, it’s crucial for the project champions to understand the key characteristics of the project thoroughly. Barry Boehm summarized essential questions that need to be asked to comprehend these characteristics, known as the W5HH Principle. The questions are:
- Why is the software being built?
- What will be done?
- When will it be done?
- Who is responsible for a function?
- Where are they organizationally located?
- How will the job be done technically and managerially?
- How much of each resource is needed?
Project Bidding
After the business case convinces top management, the project charter is developed. Some projects require a formal bidding process to select a suitable vendor based on cost-performance criteria. If the project involves automating activities, the organization may choose to develop it in-house or solicit bids from various software vendors. Bidding techniques include:
- Request for Quotation (RFQ): An organization advertises an RFQ if it has a clear understanding of the project and possible solutions. The RFQ includes a statement of work (SOW) defining the scope. Vendors submit quotations, and the organization selects a vendor based on price and competency. In government, this is often termed a Request for Tender (RFT), where bidders must deposit a tender fee.
- Request for Proposal (RFP): Used when the organization understands the problem but not the solution. Vendors submit proposals with solutions and costs. The organization may ask vendors to explain or demonstrate solutions. The RFP process helps understand available solutions, leading to a detailed SOW for RFQ or RFT.
- Request for Information (RFI): An organization may publish an RFI to assess vendor competencies and shortlist potential bidders. While RFI responses are seldom the sole basis for selection, they aid in conjunction with RFP and RFQ responses for vendor selection.
Project Planning Phase:
During this phase, the project manager creates several key documents, including:
- Project Plan: This document outlines the project’s tasks, schedule, resource allocation, and timeframes.
- Resource Plan: This document lists the resources (manpower and equipment) required for the project.
- Financial Plan: This document details the project’s budget for manpower, equipment, and other costs.
- Quality Plan: This document includes quality targets and control plans.
- Risk Plan: This document identifies potential risks, prioritizes them, and outlines a plan for mitigating those risks.
Project Execution Phase:
In this phase, project tasks are executed according to the project plan. The project manager monitors and controls the project to ensure it stays on track. Corrective actions are taken if necessary. The project plan may need to be revised to accommodate changes or risks that arise during execution. Quality is ensured through proper processes, and deliverables are produced and accepted by the customer.
Project Closure :
Project Closure involves completing the release of all the required deliverables to the customer along a with the necessary documentation . subsequently all the project resource are released and supply agreement with the vendors are terminated and all the pending payment are completed. Finally , a postimplementation review is undertaken to analyze the project performance and to list the lessons learnt for use in future project.