Software process maturity+ framework

Uploaded on


More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Software Process Maturity+ Framework – Agile , Development & Maintenance Vishnu Varthanan Moorthy 06 July 2014 Copyright No:0031613
  • 2. Contents  Description  What Constitutes Process Maturity  Process Maturity+ Framework  Process Maturity+ Rating  Process Maturity+ Reports
  • 3. Description Software Industry has technically advanced a lot and new methods and techniques dominates the industry by every new day. In this changing world the heavy weight processes and models/standards are more of rituals than contributing factors. The industry needs lighter, faster to deliver processes with high quality. Software Process Maturity+ is a framework designed with the understanding of the current technology advancements and lighter processes in mind. This framework consists of Processes for Development, maintenance and Agile development lifecycles. It also consists of Practices relevant to these areas under each processes. This framework offers maturity levels that are natural in a organizations’ growth. Every start up organization would expected to naturally adopt processes in a manner, in which its described in this framework. Apart from that the “+” symbol indicates, that first time Non functional aspects of processes and business alignment Study is added as part of a framework in a detailed manner with sufficient insights. Though there are models which has similar concept of Business alignment study, but they don’t have them at lesser maturity levels.
  • 4. Benefits  Organization’s can benefit a lot by developing processes given as per this framework  Agile Projects can have streamlined processes for better delivery  Maintenance projects will get greater benefits, as the key services areas are addressed in the model and Processes are kept minimal.  The model brings the best of development with relevant project controls which can help small and medium organizations to benefit  The model also caters advanced process maturity practices, which gives prediction and improvement abilities  Quality teams can benefit by understanding how good their processes are meeting user end needs through Non functional requirements.  The management of an organization will get good benefit by aligning their objective with processes, irrespective of any level of maturity.  Benchmarking tool for Process Maturity
  • 5. What Constitutes to Process Maturity? Measurement Framework Process Architectur e Relevant Processes Aligned to Business Requirements Consistency Improvements Degree to which the Processes are Standardized/Optimized Degree to which they are met Business Goals Results Process vs Business Goals Alignment Process Non- Functional Characteristics
  • 6. Process Maturity+ Levels Point of Contact Processes Base Delivery Processes Process Standardization Process Optimization •Client or supplier driven • Individuals performance oriented • Project Delivery Process • Systematic Process • Team performance • Standardized Delivery • Controlled Customization • Organizational Unit performance • Optimized Delivery • Statistical Process Control • Business PerformanceClass A Class B Class C Class D Business Goals vs Process Alignment Process Non- Functional Characteristics•Readability •Complexity •Accessibility •Traceability •Support
  • 7. Process Maturity+ Framework
  • 8. Process Groups and Practices Grade Processes Practices Class D 4 23 Class C 8 55 Class B 12 81 Class A 14 97 Grade Processes Practices Class D 4 23 Class C 9 62 Class B 14 93 Class A 16 109 Development Maintenance Grade Processes Practices Class D 3 23 Class C 5 40 Class B 8 69 Class A 10 85 Agile
  • 9. Processes and Detailed Practices sheet with Example Artefacts
  • 10. Business Goals Alignment Study Quality Unit cost of Support Demand & Capacity Planning Utilization Defect Detection and Removal Mean Time to Resolve Velocity of Production First Pass Yield Cost of Poor Quality Cost of Rework Forecast Accuracy Unused output Capacity Used Capacity Available Project Target ? MTTR 16 hrs for P4 with SD 3hrs Project Target ? Cost of Poor Quality <12% of total Effort in 90% projects Project Target ? Forecast Accuracy is > 80% in 100% of projects Analysis Develop Fix Review Testing Estimation Inflow Monitoring Change Managemen t Control Analysis elapsed Time within 3 hrs Design Review Effectiveness is more than 70% Design Review efficiency is 2 defects/hr Estimation of complexity/size 90% accurate Inflow is within 80% of the Weekly/monthly Pattern Incidents raised because of change &release <25% •Knowledge data base •Competency Level •Details of Incident •Complexity •Etc •Improved KDB •Incident Mgmt Tool with better description field •Resourcing by Complexity •Review Method • Reviewer Skill • Tools used • Standards/ Checklist •Review Tool & macros • Workflow Tools •Static Code Analyzer •Type of Work •Estimation Method •Skill •Guidelines •Benchmarkin g data •Estimation Management Tool •Slim or other international Estimation utility • Prediction/ •simulation Tools Goals KPA Project Goals Process Steps Interim Targets Controlla ble I know what we have to achieve this year! What is my Project target? Which Process & step is critical? What are my intermediate / Process targets What influencing factors , I can control ? & Improvements I can make? Business Alignment workshops Influencers Initiatives/ improvements Manager Senior Management
  • 11. Non functional Aspects (Ease of Use) Ease of Use Readability Complexity AccessibilityTraceability Support
  • 12. Evaluation Roadmap Using Process Maturity+ Scoping Initiation Planning Define Study Mapping Workshop/ Clarification Assess Maturity Grading Observations Discussions Report Improvements Training Sustenance Improve Week 1 Week 2 / 3/ 4 Week 5 Week 6 - TBD
  • 13. Evaluation Method – Rating Scales Type Level of Rating Description Practice Checks High Practice is addressed/detailed in a process/procedure/work manual/tool and Relevant Templates/Tools/Checklists/output format is available Medium Practice is Partially addressed/detailed in a process/procedure/work manual/tool and Templates/Tools/Checklists/output format is partially addressing Low Practice is not addressed/detailed in a process/procedure/work manual/tool and Templates/Tools/Checklists/output format is not addressed Non Functional - Readability High /Medium/low High - Activity contains tasks lesser than 7, Pages of a process & Procedure is less than 12, Tasks are lesser than 20 words Medium - Activity contains tasks 7 to 11, Pages of a process & Procedure is between 12 to 20 , Tasks are between 20 to 40 words in most places Low - Activity contains tasks greater than 11 , Pages of a process & Procedure is between greater than 20 , Tasks are greater than 40 words Non Functional - Complexity High /Medium/low High - Less than 5 process Interactions, dependency of associated components like template/guideline/etc are less than 10 Medium- Less than 8 process Interactions, dependency of associated components like template/guideline/etc are less than 15 Low - More than 8 process Interactions, dependency of associated components like template/guideline/etc are more than 20 Non functional - Accessibility High /Medium/low High – Online & Offline access, Quick Search & advance search enabled, Virtual Connectivity/Secured access Medium- Online access and offline Search enabled Low- Online database and without search Non Functional - Traceability High /Medium/low High- Traceable to Requirement & Architecture, Navigation through lifecycle and role Medium - Navigation through lifecycle or role and traceable to needs/goals Low – Navigation is only based Category Non Functional - Support High /Medium/low High – Well defined support using Email/Chat/Feedback/On call Medium – Support using on Call/Email/feedback Low – Support using offline modes alone (feedback, mail)
  • 14. Sample Reports of Evaluation Class C Class BClass D Class A Overall Process Maturity – 2.4 out of 4 Ease of Use Development Maintenance Agile Class D Class C Class B Class A 0 0.5 1 1.5 2 2.5 3 3.5 4 Maturity Profile
  • 15. Process Group Compliance – Sample Maintenance Development Agile Class D Class C Class B Class A High Compliance Medium Compliance Low Compliance Not Applicable
  • 16. Sample – architecture Study Class Process Architecture Components Current Set Status Class A * Tool Alignment with Process No * Cost Benefit Analysis / Evaluation of Process Improvements P Class B * Interaction & Inter-relationship of Process No * Standards Yes * Policies Yes * RACI Yes * Process Training Material P * Tailoring Norms Yes * Standardized Process P * Standard Lifecycles Yes * Process Repositories Ex: Estimation, Risk, KEDB No * Tools standardization No Class C * ETVX based Process Yes * Input & Output defined Yes * Templates Yes * Guidelines Yes * Overview Training Material Yes Class D * Process Flow No * Templates -Client Interaction Points Yes * Roles and Responsibilities No
  • 17. Contact Us: Thanks to,  Banibratha Chowdhury  Velayutham karthikeyan For further details( Detailed Practices vs example Artefacts) and/or sample report, contact us :