Capco Point of ViewSDLC Transformation – The Rise of Risk Methods<br />October 2010<br />
Introduction<br />Some Useful Definitions<br />Methodology<br />PMLC or EPM<br />RUP<br />SDLC<br />Agile<br />Iterative Solution Delivery Lifecycle<br />Other<br />Infrastructure Solution Delivery Lifecycle<br />From a methodology perspective, a PMLC remains relatively stable over time but accommodates multiple SDLC lifecycles (i.e. project types) within the Execution Phase.<br />
Our Point of View <br />SDLC Transformation Imperatives<br />Both Technology and Business drivers are compelling companies to re-examine their SDLCs and other methods.<br />Balancing Relevance with Flexibility – Dynamic with quality<br />TechnologyImperative<br />Technology Drivers<br />Business Drivers<br />Efficiency<br />Risk Management<br /><ul><li>Economy has driven companies to reduce staff levels.
Governance, Risk and Compliance complexity is on he rise.
New legislation introducing additional mandates.
Market demands for flawless transparency.</li></ul>Relevance<br />Flexibility<br /><ul><li>Methodologies have historically lagged behind current practice and the gap is widening because the adoption of new technologies and techniques is accelerating (e.g. mobile / Smartphone, cloud)
Technology teams increasingly require the ability to chose methods based on the needs of the task at hand and emerging techniques are gaining traction (e.g. Agile).</li></ul>Balancing Risk and Efficiency – How to “Right-Size The Rigor” required?<br />BusinessImperative<br />
Our Point of ViewSDLC Transformation Requirements<br />The Technology and Business imperatives give rise to specific requirements for SDLC. Capco believes these requirements fall into five key AREAS.<br />Balance Relevance with Flexibility<br />TechnologyImperative<br />Balance Risk and Efficiency<br />BusinessImperative<br /><ul><li>Adopt risk-based governance rules to focus on value-add activities informed by compliance needs
Reduce overall delivery cost by minimizing process “overhead”
Empower teams with the ability to tailor & filter SDLC based on a Project Profile (risk, complexity, etc.)
Align methods & tools with how technology teams actually perform effective work
Support on-going management and continuous improvement of methodologies</li></ul>So what would a solution designed to address these AREAS look like?<br />
Capco has helped multiple clients address the requirement AREAS using our DMAsm approach:<br />Selected MinimalBase Path<br />Empower teams<br />Our Point of ViewDynamic Methodology Adaptation (DMAsm)<br />Adopt risk-based rules<br />Reduce “overhead”<br />Align Methods<br />Team<br />Governance<br />Control Point<br />ExceptionWaiver<br />Fact-Based Project Profile<br />Project-Specific Path<br />Process, Activity, and Artifact recommendations – based on risk, rules and modified decisioning facts.<br />Risk-based Rules<br />In-Flight & Post-Project Adjustments<br />Risk scoring of “optional” elements<br />Support continuous improvement<br /> On the next page we illustrate how we helped one of our clients visualize their DMAsm...<br />
Our Point of ViewDynamic Methodology Adaptation (DMAsm)<br />Here’s an example of how one client is evolving toward a more Dynamic SDLC<br />They will have “arrived” after decomposing their methods into re-usable work packages that can shared and re-assembled depending upon the project’s profile.<br />A first step is to optimize what they already have.<br />Starting with a rather large set of static SDLCs.<br /> Where to begin? The answer lies in where you are today relative to where you want to be...<br />
Our Point of View <br />Dynamic Methodology Adaptation (DMAsm) – Domain Framework<br />The DMAsm Domain Framework can be helpful to prioritize SDLC Transformation tasks.<br />Qualitative Measures<br /><ul><li>All Domains will progress along a continuum of qualitative and quantitative measures.</li></ul>Interoperable<br />Flexible<br />Completeness<br />Quantitative Metrics<br />Domains<br />Guiding Principles<br />KPI<br />Vision<br />Strategic<br />Project Mgmt Lifecycle<br /><ul><li>Capco groups SDLC Transformation work into 10 domains, grouped as Strategic, Foundational or Operational
Companies typically have various levels of maturity across these groups</li></ul>Demand Mgmt<br />Must Do<br />Foundational<br />SDLC<br />Should Do<br />Release Mgmt<br />Centerof<br />Excellence<br />Product<br />Management<br />Tools<br />Operational<br />Note: Prioritizations indicated <br />are for example purposes only.<br />Inhibitor<br />
Our Point of View <br />Dynamic Methodology Adaptation (DMAsm) – Domain Framework<br />Content summary and implementation considerations for each of the 10 Domains. <br />Let’s look at the SDLC domain in more detail...<br />
Our Point of View <br />DMAsm SDLC Domain – Evaluation Framework<br />An SDLC Methodologyhas a complex structure that must be viewed from multiple dimensions. Capco has developed the framework below to represent the three aspects of:<br />Key Process Areas – Sequences of tasks performed by roles over time<br />1<br />Activities & Deliverables – Process Components and Work Objects produced<br />2<br />Methodology Components – Detailed characteristics of Processes, Activities, Deliverables and other methodology elements.<br />3<br />Post-Project Analysis & Feedback into Knowledge Base<br />Construct and Evaluate (Coding, Integrating, Testing, Debugging) <br />Quality<br />1<br />Key Process Areas<br />Analysis and Design (Conceptual, Logical, Physical, Final) <br />Process Definition<br /><ul><li>WBS
Samples</li></ul>MethodologyComponents<br />3<br />Methodology Repository<br />Many companies have some or all of these elements but they are seldom found in one place because...<br />
Our Point of View <br />DMAsm SDLC Domain – Tools<br />Providing a complete SDLC requires a unique repository!<br />Purpose<br /><ul><li>Analyze, design and build SDLC process descriptions
Identify and provide all necessary guidelines, document templates, examples, checklists, etc.
Provide tailoring guidelines</li></ul>Key Capabilities Required<br /><ul><li>Setup of rules for process modeling in order to achieve uniformity and consistency (process “metamodel”).
Integration of all types of process assets useful for process institutionalization.
Graphical representation of processes for visualization and analysis purposes.
Configuration management for all SDLC process assets and versioning.</li></ul>Want an example?<br /><ul><li>See the Eclipse Process Framework at:http://www.eclipse.org/epf/</li></li></ul><li>SDLC Transformation<br />Is It Worth The Effort?<br />This published research and Capco’s recent experience with multiple clients says “Yes!”<br />But you need not take our word for it. Every company is different. That’s why Capco recommends...<br />
SDLC Transformation Assessment Approach<br />Capco’s assessment approach starts with broad discovery and converges to a specific improvement action plan based upon a series of findings as compared to leading practices.<br />Improvements and remedies are identified as a series of Findings and Recommendations<br />These are then sequenced into a relevant set of Initiatives and a high-level Business Case<br />A Transformation Roadmap is tailored to your culture and organization based upon our experience<br />
SDLC Transformation Assessment Areas and Dimensions<br />The current state maturity assessment is accomplished through review of existing artifacts, in-flight activities, future plans and stakeholder interviews -- then compared against 12 Dimensions grouped into 4 areas. This assessment provides an understanding of the landscape and operating environment in order to provide a baseline from which to identify and prioritize improvement opportunities. <br />Capability Maturity Stage<br />Capco works with you to add or remove Areas and Dimensions as appropriate for your environment<br />