Project Plan- Risk and Quality Requirements Essay Example for Free

design Plan- Risk and eccentric Requirements EssayIT tramp Plan IT labor movements atomic number 18 complex in nature. A proper object gives non only maps the elements of the upchuck unless also discovers that the progress of cast is going in the desired direction. In separate terms, a switch plan reduces the fortune of chuck liveure or over runs and improves the quality of the pick up. Project plan is the initial step in kill the project trouble.Project management strives to meet the expectations of the project stakeh emeritusers in terms of cost, quality, pitch shot and operations. Project management is a crucial process that involves, spate, process, price, infrastructure and cost. Project management should balance the interests of various stakeholders of the project like Project police squad members, management of the working group, client parameters, industry practices and the budget restrictions. In IT industry, it becomes the responsibility of proje ct manager to look after the co-ordination of the in a higher place aspects. Project plan becomes an essential helping tool to the project management in directing the project requirements to the commonwealth and administration.The project plan aligns the activities with the project life cycle and gives visibility to contrastive phases of the project. IT allow for be like indicating the stakeholders of the project like client and project team to act upon the dissimilar activities of the project like, development, testing, roll extinct, instruction and carrying out. The project plan is developed in connection with Organizational plan, Risk plan, Cost plan, Test plan, Roll out plan, Quality plan, Maintenance plan etc.,So it is evident that Risk identification and Quality parameters act as forecasters for the project phase activities and does have a grand signifi croupce in the successful implementation.However project plan includes theThe Project Plan provides complete overvie w on how and when a projects objectives are to be achieved, by expressing different activities to resources to achieve targets at different milestonesThe major elements of the project plan are as followingDescription of the project or an over view of the project plan.Project specifications and requirements of the clientProject Initiation plan and requirements in terms of technology, budget and peopleProject dependencies- external, internalProject milestones like Analysis, design, development, testing, implementation and cookeryIdentification and specification of project assumptions like availability of resources, technical inputs, skills and competency requirements.Project plan with work break down structure through Gantt graph or bar chart and control points at different levels.Project level activity specifications for different stakeholders like client team,, analysis team, design team etc.,Project level resource specificationsProject budget and cost planProject tolerance, throug h put and capacity in terms of users and boundariesTechnology to be implemented with constrains and rationale for the usage.Network contingency plans and infrastructure layout plans to be required for the project work outRisk identification and risk tolerance specifications of he frameQuality framework under which the project is expected to executeRiskRisk can be termed as the possible loss or damage to a process. Risk identification is the estimation of possible potential dangers that can occur or hinder the progress of the project. Risk in IT project management is a major component to consider even before the project death penalty, as the un determine risks not only obstruct the progress but also may turn the entire project into loss. A risk will have a probability something above 0%. And there is an identified chance to happen, which opposite wise is not a risk. So a deliberate approach to identify and palliate the risks is highly appreciable from the project accomplishment from decades.According to Dr. Barry W. Boehm, (as cited in kjordan) the top 10 identified software risks are as followsPersonal Shortfalls in perception of risk and resourcesUnrealistic schedules and budgetsDeveloping the malign functions and propertiesDeveloping the wrong user interfaceGold-platingContinuing stream of requirements varysShortfalls in externally furnished componentsShortfalls in externally performed tasksReal- era performance shortfallsStraining computer-science capabilitiesSo, IT projects do have a risk management process that is expressed through the risk management plan. The risk management plan contains the four major areas to unwrap in the planRisk Identification The project manager or risk management personnel will identify the possible potential threats to the project management before well in advance. Eg Shortage of workforce due to the withdrawal of people from the team this can be from different reasons like, maternity leave, transfers to other projects or contract termination etc.,Risk Quantification The risk identified should be quantifiable, other wise which it is will not be of much useful. Eg What percentage of people are going to be placed on another major project or percentage of testers that may not be available on project A.Risk Response The consequences of risk should be specified, in the sense, sometimes the carcass may be less altered with certain types of risks. With this, the low answer of system indicates and attributes the risk as a less precession risk. And the risks that may cause major alterations to the process will be given high priority by the project plan to address them and mitigate them.Risk Monitoring and Control Risk monitoring and controlling involves the risk mitigation tools and practices for the easy execution of the project. Eg Training the new people to fill the gaps on attrition by the time they leave or to be transferred from the current project process.The common risk scenarios in IT projects are as followsSchedule RiskThis is the highly possible risks in IT projects, when projects over run with scheduled times or slip the grow schedules or the client priorities and queries are not answered Schedule risks alters the project phases and disturbs many dependencies. Other project dependencies like testing schedules, release schedules and infrastructure costing etc., can be altered and head in excessive costing and losses.Schedule risk can happened due to the following reasonsInappropriate or wrong project time estimationPoor tracking and monitoring of work break down plan with the resources.Over estimation of system functionality and through put. Eg When the existing system support only 50 resources to work, scheduling of 60 or 65 may proceeds in non availability of proper infrastructure.Wrong estimation of causa or skills. Eg the project with low skilled work force or low effort estimation may take much time compared with the scenario of see people on task.Failure to s pecify or identify complex functionalities or requirements that emerge and become stumbling blocks for the progress execution, takes longer time to resolve and them to elapse with the projected phases.Unexpected project scope expansions These can happen due to the poor business analysis and feasibility guidelines.Budget RiskAll the above schedule risks can ultimately result in increase in resource cost. In addition to this, the following at the initial project plan phase also result in budget risksWrong budget estimation When the cost of resources is going to be increased in future, adaptation of old compensation rates will ask for more funds to meet the project execution after some time.Cost overruns These will arise when the project activities are not aligning with the planned activitiesProject scope expansion Wrong specification of requirement may lead to extra budgets. Eg more or less IT projects fail to define the project scope very specifically in terms of design, developme nt, training (on site), installation, maintenance, and support. A project that fails to differentiate amid on site training support and training support through documentation like user guide and admin guide has to face a situation in which the company has to inhabit the traveling and expenses of training resource when on-site training is demanded in the last moment.Operational RisksOperational risks arises due to non specification of appropriate project methodology and non implementation of project processes like daily meetings (scrums), dialogue reports, Change requirement reports. Such risks will again result in over runs in in operation(p) schedules and results in high costs. Some causes of Operational risks are as followsFailure to address priority conflicts when tasks and conflicts are not nor prioritized, people sit on unnecessary or low priority tasks resulting the operational delays.Failure to resolve the responsibilities The non-defined roles and responsibilities wo rk on the similar operations or raise conflicts at some point of time in the operations.Insufficient resources A project with in sufficient resources may execute poor operational performance and may result in operational delay.No proper subject training When the project stakeholders are not given project training at consecutive levels, there will be no direction and clarity in the project operations.No resource planning If the resource allocation is not properly planned, conflict arises between the different activities of the systemNo communication in team poor communication is the major hindrance for smooth project execution. Excessive communication and less communication will also alter the project schedules. Non -defining the desired level and form of communication hampers the entropyrmation flow . eg Non-maintenance of Change request forms from the client may result in wastage of work on the old configuration of modules by the developers and may result in project over runs.T echnical risksTechnical risks are the or so unidentified risks with great damage and result in failure of functionality and performance. The causes of technical risks areContinuous changing requirements The initial technical specifications may require different technology platform to the technology that is appropriate for the recently added requirementsPoor suggestion of technology Lack of technical expertise of resources may result in compatibility problems. Some advanced features that may not be ready by the time of release, or that may not be compatible with the already developed functionalities will hamper the project execution.Product is complex to implement When the product development is too complex and there is a dearth of skill and expertise in the market, the project needs to suffer delay or failure.Difficult project modules integration When different modules are products are to be integrated, incompatibility problem arises between them that result in re work or failure.E xternal RisksThese are the external risks beyond the boundaries of project management. These are all uncertain and may result of the followingShortage of fund.Market Changes Transferred demandChanging customer product strategy and priorityGovernment rule changes.Quality Requirements of ProjectQuality refers to the delivery of projects and products that meet the expectations of all the stakeholders. A project that may meet all the specification of the client, but may over run the project schedule is not termed as a quality project, as it has resulted in extra cost to the management. So in order to bring down the risk, IT projects adopt different Quality models. For example software product design and development projects adopt quality models like CMMI, ISO, BSI, etc., he quality model frames a risk management plan and ensures the system to adhere to the planned project activities until the successful implementation. Usually the quality models identify some risk areas and constantly w ork on controlling the risk areas.The parameters that are commonly observed by different Quality models for IT systems are as follows Correctness, Reliability, Integrity, Usability, Efficiency, Maintainability, Testability, Interoperability, Flexibility, Reusability, Portability, Clarity, Modifiability, Documentation, Schedule, Validity, Functionality, Generality and Economy.The quality management department or manager will ensure the project that it is being executed properly as per the plan. All the stakeholders monitor the project activities according to the quality parameters and control the error or risk as per the risk mitigation guidelines.Project Quality Plan defines the expectation of the stakeholders in terms of project specifications, schedule time, technology inputs, dependencies etc., and also maps the process to ensure the system to balance.A Project Quality management supports the following through quality plans and system guidelines delimit organizational and project level quality objectives and parametersCustomer requirements and expectations in terms of functionality, deliveryAcceptance criteria of the IT product, which is a prioritized list of criteria for the customer to accept the final product.Roles and responsibilities of Quality management team.Functionality boundaries of the project quality systemReference to manufacturing practices or standards to be metThe quality-control and audit processes to be applied to project managementQuality-control and audit process parameters and requirementsChange management procedures in case of scope change in projectConfiguration management planValidation and verification controlsQuality control and Assurance plan and proceduresBy adopting quality monitoring proceduresDefining test lab procedures like- test documentation, testing resources, Test cases, scenarios, error logs and other testing documentationMetrics for quality analysisSystem guidelines for quality management proceduresMaintenance of conf iguration management and change control requirementsConclusionFor the Successful IT Project implementation, the project plan must address the risk issues and Quality requirements to mitigate the risk issues. Effective project planning, quality control, and monitoring will ensure the quality assurance of the project mitigating the identified risks.ReferencesElizabeth and Richard Larson, How to Create a Clear Project Plan, Retrieved February 2, 2008 from www.projectmanagement.ittoolbox.com/documents/industry-articles/how-to create-a-clear-project-plan-844 26k EPA Requirements for Quality Assurance Project Plans (EPA QA/R-5), Retrieved February 2, 2008 from http//www.epa.gov/QUALITY/qs-docs/r5-final.pdfkjordan, Introduction to Software Risk Risk Management, Retrieved February 2,2008 from http//baz.com/kjordan/swse625/intro.htmlHyatt L. Rosenberg, A Software Quality Model and Metrics for Identifying Project Risks and Assessing Software Quality, http//satc.gsfc.nasa.gov/support/ST C_APR96/qualtiy/stc_qual.htmlProject Management Planning, Retrieved February 2, 2008 from http//www.cio.ca.gov/itpolicy/pdf/PM3.2_Planning_Process_and_Plan.pdfProject Quality Plan , Retrieved February 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_project_quality_plan.aspProject plan, Retrieved February 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_project_plan_.aspQUALITY ASSURANCE PROJECT PLAN REQUIREMENTS, Retrieved February 2, 2008 from http//www.wipp.energy.gov/library/CRA/BaselineTool/Documents/Appendices/ WAP% 2010.PDFQuality Assurance Planning, Retrieved February 2, 2008 from http//www.chesapeakebay.net/info/qa_planning.cfmRisk management strategy, Retrieved February 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_risk_management_strateg y_.aspRisk management framework, Retrieved February 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_risk_management_framew ork_.as pRisk management strategy, Retrieved Februa ry 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_risk_management_strateg y_.aspRisk log (risk register) Retrieved February 2, 2008 from http//www.ogc.gov.uk/documentation_and_templates_risk_log_risk_register.aspTypes of Risks in Software Projects, Retrieved February 2, 2008 from http//www.softwaretestinghelp.com/types-of-risks-in-software-projects/