Presentation on theme: "Wendan Consulting Webinar"— Presentation transcript:
1Wendan Consulting Webinar “Reduce the Risk of BPM Project Failure with a New Approach to Project Management”Wagile BPMS/BPMFacing business improvement: The Problem - nothing is easy, nothing is fast and results are not certain!
2Wendan Consulting Dan Morris Dan Morris, CBPP, CBA Managing Principal Wendan ConsultingDan has over 30 years of experience in business and IT operation transformation and management. He is currently serving as a Managing Principal for Wendan, Inc. Wendan is a BPMS methodology and consulting firm offering the ADDI (Architect, Design, Deploy, Improve) BPMS methodology. ADDI is the first vendor neutral BPMS methodology that follows a Wagile approach to provide consistency and promote project success.ExperienceNorth American Practice Director for Business Transformation at Ta TaUS Practice Director for BPM/SOA consulting at CapcoUS Practice Director for Business Transformation for Insurance, Healthcare and Life Sciences at Infosys TechnologyExecutive Consultant for IBMDan is the author of four books on Business Transformation and over 50 papers and articles. He is the author of the PEX column BPM Straight Up: Separating Fact from Fiction.Wendan Consulting
3Our focus is on the business side of change, not the IT side. AgendaOur focus is on the business side of change, not the IT side.Session will be presented in three sectionsWagile – what it is and where did it come from?Introducing Wagile – impact and useADDIQuestionsHelping you find your way through the business improvement maze!
4Concepts, Approaches and Methods Agile and Waterfall are approaches based on specific concepts and techniques that focus on different and conflicting fundamental ideasBoth approaches mean a lot of different things to different peopleThere is no single Agile method and no single Waterfall method – every company has their own variation that they declare as Agile or WaterfallAgile and BPM evolved together and leverage many of one another’s concepts – but their different perspectives caused serious differencesWaterfall/Agile was originally created in the tech world to overcome weaknessesIt has now been recreated, not adopted, in the business community as WagileThis business world recreation changes the concepts significantlyProject Management – management of a project is different from understanding what tasks need to be done to deliver the solution
5Waterfall Strengths Weaknesses Improves control Everyone agrees on the complete outcome early in the projectGoverns scope and improves estimationImproves the ability to measure status and understand exactly where you are and what still needs to be doneImproves everyone’s understanding of what they need to do and whenProvides rigorReduces the reliance on the project manager’s understanding of what needs to be done in the projectSeparates project management from project planning and executionWeaknessesCan be too rigid – little flexibility, depending on the project manager’s abilityPrescribe - Step by step in serial fashion through the projectEach stage or phase must be completed before the next one can beginRequirements must be right to start with – cannot easily changeIt is difficult to change the design – cannot easily go back to previous phasesIt is difficult to change the applications once they are builtWaterfall is rigid like American football – each play pushes forward with limited flexibility.
6AgileStrengthsFasterHigh design flexibility to accommodate changes – process is forgivingEasier to test because the increments or components are small and fairly simpleRequires significant ongoing customer involvement throughout the projectCustomers gain a strong sense of ownership because of their involvementEach sprint delivers a usable component part of the solutionAllows for specification changes - easier to change and evolve a solutionComponents are driven by business cases and are less complexWeaknessesNo clear understanding of the outcome or how it will change the businessMakes an assumption that the right things are being done in the business and they need to be automatedDoing the unnecessary work faster, cheaper, better doesn’t mean you are delivering improvement!With a less experienced project manager, the project can become an unending series of code sprint iterationsEasy for the project to come in over budget and take longer than expected – no real end at timesBecause there is no definitive outcome or plan, the product can be different than expected or desiredHarder to keep track of how all the components will fit together and control changeNot good at addressing complex work with a lot of interrelated activityAgile is flexible like Soccer – You run all over the field to get to the goal.
7What is a Wagile?Wagile is a balanced hybrid method that requires a deep partnership between business professionals and technology professionals to leverage the latest digital approaches and technologies as needed to deliver visible, time to market, dynamic and emerging business results
8Background: Wagile is a Proven Approach Wagile is a business driven approach to business changeWaterfall is a proven & careful approach that carries large and visible results, but is missing time to market results and requires perfect targetingAgile is a proven approach that delivers quick and emergent results that leverages a “Do it, try it and fix it” approach, but is hard to deliver consistent visibility and team coordinationCombining the best of both approaches with the visibility that BPM affords, leverages the advantages and minimizes the disadvantages of each family of methodsWagile is based on BPM concepts and supports traditional solution development and BPMS based application generation.
9Foundation for success Project foundation – the key to allowing successCritical to get this rightDefine the outcome – goals, standards, targets – operating requirementsAlignment to strategy – at some level in the business hierarchyFormal definition of success (different today) – who do you please?Project Management – providing controlPMI’s PMP certified project managers – still have a high failure rateDifference between project management and project methodologyDelivering project execution successCreation of a complete solution design (understanding what will change and how) for contextA business focused approach that combines the strengths of Waterfall and AgileA formal methodology – eliminate project manager differencesAbility to iterate and simulateBPM COE – consistent approach and governanceFormally measured results – prove success, remove it from opinionTo engage all affected (limit participation to direct sponsor and stakeholders)Appropriate tools to do the job
10Overcoming Agile Weaknesses How overcome in WagileNo clear understanding of the outcome or how it will change the businessRequires a complete design of both the old and new business operations that is first iterated and simulated to prove successWith a less experienced project manager, the project can become an unending series of code sprint iterationsFoundation and current state information discovery follow a waterfall approach. New design follows a melded Waterfall Agile approach to provide structure to design division into components for iteration/simulation flexibility and requirements ID and alignment. Comprehensive design guides the way components are combined to form the solution.Easy for the project to come in over budget and take longer than expected – no real end at timesIterations are controlled through simulation to deliver optimization quickly – as measured against formally agreed upon goals, standards, targets and requirements.Because the project doesn’t have a definitive outcome or plan, the product can be very different than what was initially expected or desiredThe foundation aligns goals among all who will be affected by the solution and defines success. The complete design defines outcomes for each component and iteration/simulation identifies when a target is obtained, limiting the number of iterations.Total cost is difficult to predict – just continue until money runs out and then you have what you haveBecause the design is controlled through the complete target outcome design and that is then divided into components that follow a controlled development approach cost can be controlled.Harder to keep track of how all the components will fit together and control change once the components are mergedThe complete design provides a guide for the reconstruction of the component parts. Change is controlled through the component evolution. Simplified if a BPMS is used as the tech platform.
11Overcoming Waterfall Weaknesses How overcome in WagileCan be too rigid – little flexibility, depending on the project manager’s abilityFormal serial steps guide project managers in what needs to be done and improves the quality of the deliverable. Flexibility in Wagile allows managers to go back and fix mistakes.Prescribe - Step by step in serial fashion through the projectMixes serial tasks with iteration and allows the flexibility to return to steps and improve what was done originallyEach stage or phase must be completed before the next one can beginAllows parallel work following the current state definition and analysis. Supports both iteration and change at any time.Requirements must be right to start with – cannot easily changeRequirements can evolve at any time as the team and business managers learn more about the operation and what is possible.It is difficult to change the design – cannot easily go back to previous phasesSupports iteration of components of the complete new design and allows change at any point in the construction or after at any time.It is difficult to change the applications once they are builtThis is best supported through the use of a BPMS. However, applications are tied to one or more components of the complete design and the impact of any modification is limited to affected components.
15Reduce Risk Iterate, simulate and improve/iterate within a solution framework DesignGenerateSimulateIterateSimulateIterateDeployBusiness RedesignBPMS ApplicationsGenerated Applications With “Stubs and Drivers”Redesign Until Solution Delivers KPIsWith IT ComponentsRun in Solution Lab and Change Until Operationally OptimalImplement and Move to Continuous ImprovementWith Wagile, the BPM project will have formal built in loops of iteration, simulation and iterationTechnology support outside of the BPMS generated applications is built and tested separately and then combined for the solution lab testingOnce the technical side is tested, the solution lab is used for live business operation testingIn this testing in a simulation environment, the solution goes through an iterative change process until it is accepted by the business users and others who may be affected
16The first question is always - Benefit Why is Wagile better than either of the approaches it is made from?Provides structure and a framework for the projectAligns the business solution with the way the technical part of the solution will be builtDelivers consistency of approach to all project teamsThe business design is the real problem – IT can build anything, but the real issue is determining what it needs to buildIT benefit suffers from the business side not providing sufficient clarity for what needs to be built and why it is neededIteration and simulation improves the probability of acceptance – all business and IT parts of the solution are tested in a live solution lab before it goes liveEnforces assessing business solution quality and usability before it goes liveBusiness managers have control over how their operation will run and be supportedQuantifies success and thus removes evaluation by opinion
17Why do we have difficulties reaching successful outcomes? Based on experience in rescue projects and through discussionsUse of IT methods that are not really business driven – instead focusing on ITFailure to set the project foundation properlyFailure to involve all affected groups and reach consensus on what will be delivered, how, why, where, whenInsufficient business manager participation in the projectFailure to define success and obtain consensus on how it will be measuredFailure to build a comprehensive baseline to measure improvement againstFailure to build a complete future state design that is proven to deliver goals through simulationFailure to properly analyze and design the data flow, transformation and interfacesFailure to properly define the increments and how they fit together before iteration is startedFailure to control iterationsFailure to properly test for tech success, then business user usability and then customer acceptanceFailure to properly consider continuous improvementUntrained project managers and staff – poor PMs and not experienced with BPMS or other supporting technologyMost issues are related to methodology
18Wagile, like all approaches must be controlled and used as the basis for governance Built by practitioners for practitioners – puts everyone on the same pageUniquely designed as a blending of Waterfall and Agile strengthsCreated new concepts needed to bridge the gaps in these methodsSuccess definition – collaboration and project foundation managementNew approach to requirements definitionFocus on analytics driven iterationUse of simulation to drive redesignMulti-perspective success determinationCustomer focused solution definitionUse of a model office environment for UI evaluation and iterationEvolutive ManagementToolboxBuild in Microsoft ProjectImbed links to your standards, policies, performance management requirements, legal compliance and reporting requirements and IT project management requirements and methodologiesImbedded notes for task groups execution275 page how to book aligned to the ADDI task groups
19Advantages of Wagile Reduces risk Provides control through formal governanceCreates a solid framework for the project that is based on collaboration and consensusDefines success and how it will be measuredManages expectations - defines the complete solution so the customer and the teams understand what they will be buildingSupports the definition of a baseline for comparison using current state simulationSupports iteration and simulation of the new design to ensure delivery of a solution that meets all needs/standards/requirementsSupports ongoing solution evolutionAllows the requirements to change and thus the solution to evolve in relation to cost control and benefit managementSupports the division of the solution into components for iterative developmentSupports the incremental and controlled delivery of components and guides how they will come together and join to form a complete solutionShows the value of each component – how each will contribute to the wholeSupports continuous improvement
20So How Can You Use Wagile? Adopt a Wagile Strategy for business transformation and improvementApply Wagile to both the business side and technical side of BPMS/BPM solution deliveryObtain a Wagile BPMS/BPM methodology, customize it to your company standards and link it to your IT application development approachFocus on the use of Wagile in business definition, analysis, design, performance design, application generation, outcome simulation, outcome iteration, performance management, outcome optimization “lab” testing, deployment and operational evolutionConsolidate BPMS/BPM expertise into a BPM COE and build the COE governance and support approach around the company’s Wagile BPMS/BPM methodology
21Questions Thank You Wendan Consulting For information on the ADDI Wagile methodology please contact Dan Morris at:Wendan Consulting
22Wagile is Controlled Iteration Complete new business operating design – to the business unit workflow levelControlled by Waterfall GovernanceAgile ApproachAgile ApproachDiagram from the ISTQB Exam Certification Website