Transforming Business through next Gen Quality - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Transforming Business through next Gen Quality

Description:

The quality of services - be it development, support, ... tools, dial-in. Automation of batch jobs. Auto Alerts. Proactive capacity management. Proactive ... – PowerPoint PPT presentation

Number of Views:56
Avg rating:3.0/5.0
Slides: 17
Provided by: vap7
Category:

less

Transcript and Presenter's Notes

Title: Transforming Business through next Gen Quality


1
Transforming Business through next Gen Quality
  • Apparao V V

2
Customers expectations
  • HIGH PERFORMANCE
  • The quality of services - be it development,
    support, Infosec, physical security, BCP/DR
  • The cost of providing these services
  • The speed with which products and services are
    brought to market
  • Innovation in the development of new products and
    services
  • In short, customers are looking for More for
    less and Managing Risks well

3
Business Transformation - What kind of Quality is
required?
  • Quality processes have to be aligned to address
    the following in the changed scenario
  • Proactive Project Management as opposed to
    reactive Project management
  • Leading metrics in addition to lagging metrics
  • Risk management
  • Program Management
  • Infosec, Physical security, data security, BCP/DR
  • Non Functional Requirements
  • Incident Management
  • Seamless integration of services handshakes
  • Requirements to Design, Design to build, Build to
    SIT, SIT to UAT, Dev to Prod Supp Infra
  • Knowledge Management
  • Tool Management

4
Involvement of Prod. Supp team during SDLC
Requirements
Release Deployment
Design Architecture
Build
Testing SIT UAT
Consistency Detailing Use cases Reusability Supp
Model Functionality
Consistency Tools int. Reusability NFR
s Infosec Infra assmt Prob Mgmt
Coding Nam conv Objects Classes Detailing Use
cases Reusability
Test Packs Test Strategy Use cases Reusability Val
idation
Batch Jobs Release scripts Imp analysis Rollback
supp Dev to Supp Consistency
5
Production Support (1/1)
  • Standardization of Target Operating Model
  • Incident Managers/Management
  • De-skilling
  • Cross skilling
  • Linking up critical resources, skill index and
    training plan
  • SLA Management and Service Level Improvements
  • Governance
  • Development to Support handover
  • Reporting and communication
  • Root Cause Analysis assessment of Business
    Impact
  • Trend analysis

6
RTB (2/2)
  • Smart shift planning
  • Monitoring
  • tools, dial-in
  • Automation of batch jobs
  • Auto Alerts
  • Proactive capacity management
  • Proactive Performance Management
  • Estimation of the Support effort along with the
    development team
  • Maintenance of Known error Database (KeDB), Run
    books and System Documentation Knowledge
    Management

7
Requirements
  • Capturing requirements through BRD and URD (FSD)
  • Use Case based Functional Specifications
  • Explicit Non Functional Requirements (NFR)
    document
  • Tool based requirements capturing management
  • Requirements Analysis for missing, duplicate,
    nice to be etc requirements
  • Negotiation Prioritization
  • UI Prototype
  • Usage of Requirements Traceability Matrix (RTM)
    mandatory
  • Re-estimation

8
Architecture and Design
  • Architecture Realization Document
  • Addressing non functional security related
    requirements with Infra and Infosec
  • Assessing Technical feasibility earlier in the
    life cycle and then estimating in complex
    projects
  • Project Architecture Review committee
  • Assessing the consolidated views of stakeholders
    like Infra, security functional
  • Infosec requirements - Firewall design
  • Cloning/re-usability
  • Technology Frameworks (Struts, Spring, JSF etc)
  • Identification of re-usable components
  • COTS or freeware components usage
  • Support Model
  • Infrastructure assessment

9
Build
  • Coding Guidelines
  • Code check lists
  • Naming conventions
  • Objects/classes and constructs for scalability
  • Document Unit test cases in line with LLD and
    deployed objects
  • Code Review Tools (ePMD, FxCorp, BPA, Find Bugs,
    Jupitor etc)
  • Re-usability
  • Knowledge Management
  • Build Management (Ant, NAnt)
  • Build Automation (Cruise Control)

10
Testing
  • Test Strategy
  • Domain training to testers
  • Test Plan in line with Project Plan
  • Keeping Testing Team updated on UI, FS changes
  • Publishing test cases to business in early
    lifecycle
  • Linking the test cases to RTM (Test Traceability
    Matrix)
  • Test Data from Business Analysts/Business Users
  • Standard Test Case templates across projects
    (Test Director import compatibility)
  • Knowledge Management of test cases
  • Test Environment setup testing estimates based
    on historic data
  • Knowledge Management of test cases
  • Build re-use repository of test cases based on
    the impact analysis RTM

11
Project Management
  • Project Plan
  • Granular tasks (no task should be more than 2
    days)
  • Allocation of tasks daily
  • Schedule and effort tracking on a daily basis
  • Monitoring defect leakage daily by PL/PM s
  • Metrics based delivery
  • Human Pyramid 60/30 degrees
  • Weekly Check point reports
  • Publish rotation plan to all the stakeholders
  • Monday morning standup meetings
  • Leveraging RTB teams during SDLC phases
  • Push back wherever applicable
  • Effective Risk management
  • Managers meeting weekly
  • Defining KPI s at the beginning and reviewing
    quarterly

12
Release and Deployment
  • Roll back plans
  • Impact analysis
  • Business
  • Application availability
  • Change Approval Board CTB, RTB, Business,
    Testing, Deployment, Batch Jobs in-charge,
    Infrastructure team, Quality
  • Change Manager
  • FI reports

13
Governance Horizontals
  • Governance structure
  • Clear Organization Structure
  • R R to be defined and published to all
    stakeholders
  • Change Approval Board
  • Communication and Reporting
  • Escalation Mechanism and management
  • Sign off process
  • Competency Centers or CoE s
  • Design Architecture teams
  • Domain Competency Group

14
THANK YOU
15
Shift Rationalization
Original Planning
Revised
BACK
16
Process
  • Expectation setting with the customer at Project
    and Engagement level
  • Define interface between the customer and HCLs
    processes
  • Pragmatic Process Implementation Approach
  • Integration Implementation of processes with
    tools like PM Smart
  • Engagement specific Customization of PM Smart
    Process Template
  • Resource Management Utilization monitoring
    through PM Smart
  • Standard Estimation practices and model
  • Quantitative baseline of the performance
  • Agree on the parameters and the frequency of
    project/ engagement level reporting
  • Deployment Process, Support Handover process and
    System Documentation
Write a Comment
User Comments (0)
About PowerShow.com