宝马中国需求变更管理文档模板.ppt

PM Qualification.Change Request.ITPMSheer Driving PleasureBMW GroupChinaMay 2010Trainer:Karl Klein(Darev)Co-Trainer:Jack LiuDate:2010.05.31Change RequestsITPMChange RequestK.KleinDatePage 2ITPMChange Request.Agenda.Agenda 1.Targets2.Definitions3.Process/Tasks 4.Toolkit5.Exercise6.Summary of key aspects7.Attachment-Examples8.ITPMChange RequestK.KleinDatePage 3ITPMChange Request.Targets.The participants of the lessons have learned the following aspects:The definition of a change request is clearThe change request process is understoodWho has to be involvedWho is responsible for whatThe benefit of the change request procedure is knownITPMChange RequestK.KleinDatePage 4ITPMChange Request.Definitions.Change RequestsITPMChange RequestK.KleinDatePage 5ITPMChange Request.Definition.Target of the management of Change Requests:Management of the effects from changes on already accepted deliverables in order to Include the additional requests structuredAnalyze the effects(effects on deliverables,costs,benefit,consequences)Build a basis for“good”decisions on requested changesChange Requests do not only occur in projects,but also in already existing applications(CCB=Change Control Board)If an additional requirement occurs for a accepted(reviewed)deliverable which will most probable have an impact on the effort and timelines we talk about a change request.ITPMChange RequestK.KleinDatePage 6ITPMNormal ChangeNormal Change(Release(Release management)management)DefinitionConstructTest/ReviewAcceptance/DistributionApplication Application developmentdevelopment(Project Model)(Project Model)Business PropsalBusiness PropsalSystem ProposalSystem ProposalSystem DesignSystem DesignConstruct&TestConstruct&TestInstall,Commission Install,Commission&Deploy&DeployStandard ChangeStandard Change(SLA)(SLA)DefineConstructTest/ReviewAcceptance/Distribution(With/withoutCode changes)Emergency ChangeEmergency Change(Hot-fix)Define SolutionConstructTest/ReviewAcceptance/DistributionNormal ChangeNormal ChangeProject BriefProject BriefChange Change RequestsRequestsPriorizationPriorizationConfirmationIncidentIncidentChange Change RequestsRequestsEmergency Emergency Change Change RequestRequestUserStandard Standard Change Req.Change Req.Service Service RequestRequestIn case of an emergencyIn case of an emergencyIn case of In case of maintenance maintenance requestsrequestsIn case In case of CRsof CRsSLASLAApplication Application developmentdevelopmentAnalyzeAnalyzeChange Request.Changes Request types.AnalyzeAnalyzeAnalyzeAnalyzeITPMChange RequestK.KleinDatePage 7ITPMChange Request.Process/Tasks.Change RequestsITPMChange RequestK.KleinDatePage 8ITPMChange Request.CR within CRM Project(example).ITPMChange RequestK.KleinDatePage 9ITPMChange Request.Process Overview.ITPMChange RequestK.KleinDatePage 10ITPMChange Request.Process Overview.ITPMChange RequestK.KleinDatePage 11ITPMChange Request.CR Process within a project.Changes can only occur on a reviewed/accepted deliverables!TimeAccepted Business Proposal(frozen)System Proposal in ProgressChange RequestForm filled in by business including:CR descriptionBenefitConsequences(IT/Business related),Verify CR together with project Team and consolidate CRsRequester presents to Escalation Board the CR Escalation Board decides on EACH CR YesCommunication to Project Team(incl.Supplier)NoCommunication to Project Team(incl.Supplier)ITPMChange RequestK.KleinDatePage 12ITPMChange Request.Before a decision can take place.Every change request must be documented:Objective of change requestShort description of the background of the problemAlternative solutions for the problem Per solution(one slide):Short descriptionCostsBenefitTimelines/Due datesResourcesRisks Consequences of the change for the project and the targetsRecommendationConsequences,if Escalation board/Steering Committee does not decidePossible Consequences for next releaseResponsible:Person who raises the changeHint:The change request MUST be documented in order to get a decision!No written request=No change!Person who raises the change must present it to the Escalation Board/Steering Committee to get a decision(together with the PM).ITPMChange RequestK.KleinDatePage 13ITPMChange Request.Tip costs for changes within Project.CostsProject Phase(Project initiation Close down report)The later the request for a change occurs,the higher the costs get!ITPMChange RequestK.KleinDatePage 14ITPMChange Request.Toolkit.Change RequestsITPMChange RequestK.KleinDatePage 15ITPMChange Request.Which tools and templates are available?CR Tracking List:CR Samples:ITPMChange RequestK.KleinDatePage 16ITPMChange Request.Exercises.Change RequestsITPMChange RequestK.KleinDatePage 17ITPMChange Request.Exercises.Exercise 1:Identify the existing change(not in progress)and define a CR Tracking Form for your project if no Tracking Form is in place.If a Tracking Form is in place discuss with the Project Manager the potential improvements.Present the Tracking Form to the trainers.Time:30 minutesExercise 2:Review the existing CR Form in your project with the attached example and identify the potential improvements;show them to the Project Manager.Fill out a CR Form for an existing CR and present them to the trainers.Time:60 minutesITPMChange RequestK.KleinDatePage 18ITPMChange Request.Summary of key aspects.Change RequestsITPMChange RequestK.KleinDatePage 19ITPMChange Request.Summary of the key aspects.Define and agree in the beginning of a project on:How to handle CR?CR FormCR Tracking listUse existing CR Forms and CR Tracking listsUse Escalation Board for getting agreements on each CR very quick CR must be presented to Escalation Board by the Requester“ITPMChange RequestK.KleinDatePage 20ITPMChange Request.Attachments-examples.Change RequestsCRM IT RestructuringDirk Meissner Page 2101.11.2007CRM IT Restructuring.Project Procedures Change Requests.Description of Requirements and Test CasesResponsible:Key Users1234Description of SolutionResponsible:Partner/ITDescription of Technical Design and Effort EstimationResponsible:Partner/ITDevelopment of CRsResponsible:Partner/ITAcceptance of Requirement Description and Solution Description by Project Manager and Key Users Acceptance of Technical Design,Effort Estimation and Development Order by Business,IT and Project ManagerAll change requests will be handled in the following way: