Software Project Management 2072

Answered by: Ashok Bhattarai

Software Configuration Management(SCM) is a process to systematically manage, organize, and control the changes in the documents, codes, and other entities during the Software Development Life Cycle. Tasks in SCM process:- a) Configuration Identification: Configuration identification is a method of determining the scope of the software system. With the help of this step, you can manage or control something even if you don't know what it is. It is a description that contains the CSCI type (Computer Software Configuration Item), a project identifier and version information. b) Baseline: A baseline is a formally accepted version of a software configuration item. It is designated and fixed at a specific time while conducting the SCM process. It can only be changed through formal change control procedures. c) Change Control: Change control is a procedural method which ensures quality and consistency when changes are made in the configuration object. In this step, the change request is submitted to software configuration manager. d) Configuration Status Accounting: Configuration status accounting tracks each release during the SCM process. This stage involves tracking what each version has and the changes that lead to this version. e) Configuration Audits and Reviews: Software Configuration audits verify that all the software product satisfies the baseline needs. It ensures that what is built is what is delivered. Roles of SPM are:- a) Configuration Manager: Configuration Manager is the head who is Responsible for identifying configuration items. CM ensures team follows the SCM process. He or She needs to approve or reject change requests b) Developer: The developer needs to change the code as per standard development activities or change requests. He is responsible for maintaining configuration of code. The developer should check the changes and resolves conflicts. c) Auditor: The auditor is responsible for SCM audits and reviews. Need to ensure the consistency and completeness of release. d) User: The end user should understand the key SCM terms to ensure he has the latest version of the software.

Answered by: Raj kumar sunar

A project management framework consists of the processes, tasks, and tools used to take a project from start to finish. It encompasses all the key components required for planning, managing, and governing projects. The project management framework can be broken into three parts: 1. Project life cycle This is the cycle a project goes through from beginning to end. It consists of five phases: Initiation: This is where you define what the project actually is. You can outline your objectives in a project charter and identify any potential risks. Planning: In this phase, you list all the project tasks in a detailed roadmap. Estimate how long each one will take, create deadlines, and add assignees. Execution: Put the plan into action. Teams commence work on project tasks and align their schedules to achieve key deliverables. Monitoring and controlling: Project managers oversee progress by tracking team performance, creating reports, and readjusting priorities if necessary. Closure: The final phase incorporates the results achieved when all project tasks are completed. A project manager will analyze these results and plan the next steps.

2. Project control cycle The control cycle is the process of monitoring and controlling the project. 3. Tools and templates Project plans, project management reports, and risk logs are common tools and templates for managing projects. Project framework examples There are many project management frameworks you can choose to use. Here are six of the most common ones: PRINCE2: This framework is highly structured with a heavy emphasis on upfront planning.

CCPM: Critical chain project management focuses primarily on resource allocation across the project.

Lean: A lean framework focuses on minimizing wasted effort and resources. Process improvement techniques are often incorporated into this framework.

XPM: Extreme project management was designed for complex projects that occur in fast-changing environments. Emphasis is on stakeholder management as plans and schedules are rapidly changing.

Scrum: This framework was also designed for industries undergoing rapid change. Using this framework, projects are often broken down and planned in 2-4 week sprints.

Waterfall: This framework is one of the traditional approaches to project management. Waterfall requires a project to be planned from beginning to end, with no phase of a project beginning until the previous one has ended.

How to choose a project management framework One single framework does not work for all projects, which is why so many of them have been created over the years. When deciding which framework is best for your project, consider the following: If your industry, technology, or product is fast-changing, an adaptable framework such as XPM or Scrum is recommended. If the project deliverable is not well defined and is intangible in nature (such as software), a sprint-based approach (such as Scrum) may work best. If the project is well defined and stable, planning it out in its entirety decreases risks. Therefore, PRINCE2 or Waterfall should work best. Frameworks may be chosen based on what your organization and stakeholders are familiar with. If your company has never completed an XPM project before, introducing one may be difficult. The priorities of your stakeholders will impact your framework. If waste is a critical concern, a lean framework may be chosen. Frameworks are designed to be flexible and adapt to a project’s needs. It may be that you will end up borrowing pieces of separate frameworks as the circumstances of your project change.

Answered by Anonymous

The product life cycle starts from the inception of the idea to the point when the product is retired. In the development stage, you will generate the idea to create the product and the product is created. In the introduction stage, you will start marketing the product and begin selling the product to customers. In the growth stage, the sales increase. In the maturity stage, the product is accepted widely and sales are at their peak Example: Let’s consider the product life cycle for a new motorcycle that your company may want to build and sell in the market. The first step of this product life cycle can be the idea generation. This may include a feasibility study, market research, and the business plan. When this phase is complete you can initiate a project to build this bike. Once the motorcycle is built, the project will be complete and the next phase of your product life cycle begins, which is marketing and selling motorcycles to customers. After selling you may need to provide after-sale support, and then the retirement phase occurs. The retirement phase may include selling motorcycles at a discounted price. Last is the retirement stage. At this level, you will try to sell out all of your inventory and move on to the next product. This stage happens due to technical advancement or because your product is not selling enough to support its production cost.

Anwered by Anonymous

Change Control is the process that a company uses to document, identify and authorize changes to an IT environment. It reduces the chances of unauthorized alterations, disruption and errors in the system. Whenever any new or different changes are requested for the system, especially by stakeholders, it is neither optional nor ignorable. It has to be implemented without affecting other components of the system. This is when the change control comes handy. It helps project teams to modify the scope of the project using specified controls and policies. Change Control is practiced whenever a project is not progressing as planned. It is mandatory that a formal document for change request is completed and reviewed in order to keep control of change requests. Steps:

• Change request identification: Identify the need for a change and describe it on the project change request form
• Change request assessment: If the change is not valid, it has to be deferred or rejected.Determine appropriate resources required to analyze the change request.Perform quick assessment of the potential impact and update the change request form.At this stage, rejected change request should stopped
• Change request analysis: For analysis assign the change request to an authorized member: Deferred change re-enter this analysis step.At this stage, rejected change request should stopped
• Change request approval: Identify change risk and complexity level before approval.Identify the impact level of the change before approval.Review impact of Change Request to authorized person for approval.At this stage, rejected change request should stopped
• Change request implementation: Update project procedure and management plans: Inform about the changes to the team.Monitor progress of change request.Record the completion of change request. Close change request
  

Answered by Anonymous

Verification and Validation is the process of investigating that a software system satisfies specifications and standards and it fulfills the required purpose. Verification: Verification is the process of checking that a software achieves its goal without any bugs. It is the process to ensure whether the product that is developed is right or not. It verifies whether the developed product fulfills the requirements that we have. Verification is Static Testing. Activities involved in verification: 1. Inspections 2. Reviews 3. Walkthroughs 4. Desk-checking Validation: Validation is the process of checking whether the software product is up to the mark or in other words product has high level requirements. It is the process of checking the validation of product i.e. it checks what we are developing is the right product. it is validation of actual and expected product. Validation is the Dynamic Testing. Activities involved in validation: 1. Black box testing 2. White box testing 3. Unit testing 4. Integration testing