This document discusses using Central Composite Design (CCD), a statistical optimization technique, to set goals for reducing tickets and costs in a Run the Business (RTB) project for a retail banking customer. CCD was used to analyze historical data and determine that 50% ticket reduction and $0.5 million cost savings were achievable goals for 2013. The Causal Analysis and Resolution process area of the CMMI framework was then used to prioritize and address root causes in order to achieve the ticket reduction goal.
This document describes a statistical model created by Tata Consultancy Services to predict customer satisfaction levels. The model was built using data from 3000 customer projects where satisfaction decreased. It identifies factors that influence satisfaction positively or negatively. The model enables project managers to proactively monitor key factors, assess potential satisfaction impacts, and take action to improve outcomes. It has been implemented digitally and is helping the organization significantly improve customer satisfaction levels across many projects.
The document describes a skill-based predictive model for talent forecasting developed by Piyush Jain and Vinay Prabhu of Infosys. It outlines the shortcomings of traditional talent forecasting models, which focus on overall headcount needs rather than skill utilization. The authors propose a model incorporating a talent skill repository and input/derived parameters for each skill. This allows for more accurate forecasting of skill needs and utilization over time, helping optimize talent acquisition costs and utilization levels.
The document discusses using an agile approach called Hybrid ASAP methodology for SAP implementations to overcome the limitations of the traditional waterfall approach. Hybrid ASAP combines aspects of ASAP methodology and agile methods like Scrum. It involves dividing the project team into smaller groups to work in parallel sprints. An initial product backlog is created using SAP accelerators and baseline builds. Then a lean business blueprint is made along with a release plan. Multiple sprints are conducted with dynamic updates to the product backlog at each sprint completion to deliver incremental working software. This allows for faster deployment, reduced risks and improved customer satisfaction over the traditional waterfall approach.
This document provides an overview of developing a stakeholder management system for large infrastructure projects. It discusses identifying stakeholders, analyzing them to determine their power/interests, and assessing their current engagement levels. The document then outlines developing stakeholder management plans with engagement strategies. These strategies aim to keep supporters engaged, neutralize sceptics, decrease negative impacts, and raise interest of disinterested stakeholders over the project life. The overall goal is an effective system to ensure stakeholder support and participation for project success.
This document discusses how process excellence can be achieved through the Agile methodology and Time and Material (T&M) estimation model. It explains that Agile allows for flexible development through short sprints and T&M allows clients to participate in and monitor development while controlling costs. Combining Agile and T&M allows clients to provide feedback and request changes iteratively, while developers track time spent to bill clients accurately.
This document discusses implementing a "process way of life" culture within an organization. It involves three key steps:
1) Enabling people through fun and interactive training to increase process awareness. This helps ensure the right data enters systems.
2) Implementing common metrics and a single project management tool so internal and customer reporting is streamlined. This provides immediate feedback.
3) Recognizing and rewarding "process champions" and best practices to motivate adherence to processes and spread positive messages.
Benefits included more predictable project management, improved metrics, and effort/metrics being reported without reminders. The approach helped establish a consistent process culture.
The document discusses how project managers can leverage recent advances in psychology to better manage human aspects of projects. It provides a framework for applying concepts from evidence-based psychology, positive psychology, and organizational psychology across the project lifecycle. The framework identifies common project management challenges and shows how psychological solutions like focusing on process over results, breaking work into small tasks, and praising effort over talent can address issues around negotiation, team motivation, and performance. The document advocates using a scientific, evidence-based approach to incorporate psychology into project management.
This document discusses applying innovative models and theories to project management. It describes four main innovative concepts: TRIZ, morphological analysis, system concept-knowledge theory, and the method of focal objects. TRIZ involves analyzing patents to identify common inventive principles to solve problems and eliminate conflicts. Morphological analysis works backwards from outcomes to components rather than vice versa. The document argues that using these innovative models in project modeling software could provide more solution options to meet client objectives compared to current practices.
This document describes a statistical model created by Tata Consultancy Services to predict customer satisfaction levels. The model was built using data from 3000 customer projects where satisfaction decreased. It identifies factors that influence satisfaction positively or negatively. The model enables project managers to proactively monitor key factors, assess potential satisfaction impacts, and take action to improve outcomes. It has been implemented digitally and is helping the organization significantly improve customer satisfaction levels across many projects.
The document describes a skill-based predictive model for talent forecasting developed by Piyush Jain and Vinay Prabhu of Infosys. It outlines the shortcomings of traditional talent forecasting models, which focus on overall headcount needs rather than skill utilization. The authors propose a model incorporating a talent skill repository and input/derived parameters for each skill. This allows for more accurate forecasting of skill needs and utilization over time, helping optimize talent acquisition costs and utilization levels.
The document discusses using an agile approach called Hybrid ASAP methodology for SAP implementations to overcome the limitations of the traditional waterfall approach. Hybrid ASAP combines aspects of ASAP methodology and agile methods like Scrum. It involves dividing the project team into smaller groups to work in parallel sprints. An initial product backlog is created using SAP accelerators and baseline builds. Then a lean business blueprint is made along with a release plan. Multiple sprints are conducted with dynamic updates to the product backlog at each sprint completion to deliver incremental working software. This allows for faster deployment, reduced risks and improved customer satisfaction over the traditional waterfall approach.
This document provides an overview of developing a stakeholder management system for large infrastructure projects. It discusses identifying stakeholders, analyzing them to determine their power/interests, and assessing their current engagement levels. The document then outlines developing stakeholder management plans with engagement strategies. These strategies aim to keep supporters engaged, neutralize sceptics, decrease negative impacts, and raise interest of disinterested stakeholders over the project life. The overall goal is an effective system to ensure stakeholder support and participation for project success.
This document discusses how process excellence can be achieved through the Agile methodology and Time and Material (T&M) estimation model. It explains that Agile allows for flexible development through short sprints and T&M allows clients to participate in and monitor development while controlling costs. Combining Agile and T&M allows clients to provide feedback and request changes iteratively, while developers track time spent to bill clients accurately.
This document discusses implementing a "process way of life" culture within an organization. It involves three key steps:
1) Enabling people through fun and interactive training to increase process awareness. This helps ensure the right data enters systems.
2) Implementing common metrics and a single project management tool so internal and customer reporting is streamlined. This provides immediate feedback.
3) Recognizing and rewarding "process champions" and best practices to motivate adherence to processes and spread positive messages.
Benefits included more predictable project management, improved metrics, and effort/metrics being reported without reminders. The approach helped establish a consistent process culture.
The document discusses how project managers can leverage recent advances in psychology to better manage human aspects of projects. It provides a framework for applying concepts from evidence-based psychology, positive psychology, and organizational psychology across the project lifecycle. The framework identifies common project management challenges and shows how psychological solutions like focusing on process over results, breaking work into small tasks, and praising effort over talent can address issues around negotiation, team motivation, and performance. The document advocates using a scientific, evidence-based approach to incorporate psychology into project management.
This document discusses applying innovative models and theories to project management. It describes four main innovative concepts: TRIZ, morphological analysis, system concept-knowledge theory, and the method of focal objects. TRIZ involves analyzing patents to identify common inventive principles to solve problems and eliminate conflicts. Morphological analysis works backwards from outcomes to components rather than vice versa. The document argues that using these innovative models in project modeling software could provide more solution options to meet client objectives compared to current practices.
This document describes a Deployment Excellence Framework (DEF) to effectively adopt high maturity processes. The framework includes 3 interlinked cycles: 1) Identification Cycle to target initial units and stakeholders, 2) Initial Deployment Cycle focusing on awareness and success indicators, and 3) Sustenance Cycle increasing adoption scope and self-reliance. It also includes a feedback adapter for course correction. The case study illustrates using DEF to standardize an organization's project estimation processes and templates by deploying new estimation models and tools over 6 quarters.
Presentation by sathish nataraj sundararajanPMI_IREP_TP
This document discusses process excellence for new age project management. It describes tools like Advanced Product Quality Planning (APQP), target cost matching, target cost approach curve, point of no return (PONR), ABC analysis, and characteristic management that can be used to enhance the planning, steering, and reporting of projects. These tools help structure project management by aiding in planning, tracking project timelines and costs against targets, prioritizing parts, and ensuring all requirements are met. Using such tools in a standardized way across a company brings transparency and helps complete projects on time and on budget.
The document discusses how fusing aspects of traditional waterfall project management and agile methodologies can improve the chances of project success, especially for large upgrade or migration projects. It provides examples of different "fusion approaches", such as using waterfall delivery within agile iterations or applying agile execution techniques within a waterfall framework. The success of a fusion approach depends on variables like organizational culture, risk appetite, and governance structures. When applied appropriately, a fusion model can help complete projects on time and budget while minimizing risks.
This document describes the Scaled Agile Framework (SAFe) which is a framework for implementing agile development practices at the enterprise level. It discusses how SAFe addresses the limitations of traditional waterfall development and scales agile to meet the needs of large projects. SAFe incorporates key lean principles and consists of three levels - Team, Program, and Portfolio. At each level it defines roles and practices for planning, prioritizing work, and delivering value in short iterations. The goal of SAFe is to synchronize collaboration across many agile teams to continuously and predictably deliver working software.
The document discusses causes of delay in the erection of power transformers in India. It identifies 18 causes of delay which are categorized into 5 groups: internal, external, planning, contractor/vendor, and transportation/packaging. Common delays include material damage during transit, poor storage areas, rework activities, and lack of resources. Addressing three key delays - material damage, rework, and security issues - could save around 40% of delay time and 200,000 INR per site. Proper planning and adherence to quality processes are recommended to avoid delays and their impacts on costs, customer satisfaction, and safety.
The document discusses building a sustainable customer advocacy program. It recommends starting with identifying requirements, forming a program team, and creating a responsibility matrix. The process then focuses on delivering a tailored program to drive new customer acquisitions by shortlisting strong advocates and creating an advocacy messaging framework and outreach program. The final step is creating a tracker to monitor process efficiency and effectiveness against key performance indicators. Implementing this approach can significantly increase customer loyalty and give a competitive advantage.
This document discusses Project Management as a Service (PMAAS), an innovative approach to managing project management phases and processes through a cloud of project management consultants working on an agile platform. Under PMAAS, individual project management phases and processes are managed independently by cloud-based consultants. Each phase acts as an agile sprint, with information from one phase feeding into the next. This gives project managers visibility while keeping project intricacies abstracted. The concept originated from challenges organizations face developing in-house project management capabilities. PMAAS provides a cost-effective cloud-based solution for managing projects.
The document discusses how an innovation program at Tata Consultancy Services adopted Agile project management methodology to address issues they were facing. Some key problems prior to adopting Agile included frequent changes to delivery targets, spending too much time on requirements and design upfront, lack of transparency, and escalated issues. By introducing Agile with support from senior management, establishing user stories and sprints, and increasing transparency, the program benefited from improved planning, early feedback, on-time delivery, and quality.
This document discusses mantras for innovative project management and creating a happy workforce for software/IT project managers. It analyzes common aspirations of young Indian IT professionals, such as work-life balance, new learning opportunities, and challenging roles. The document proposes that project managers can increase worker happiness and productivity by helping fulfill these aspirations. It presents frameworks for understanding individual aspirations, including an aspiration pyramid with work-life balance at the bottom and career growth aspirations like new learning and challenging roles at the top. The document also provides examples of project-level enablers a manager could implement to help team members achieve their aspirations.
This document discusses approaches to implementing agile project management processes for distributed teams across multiple locations. It describes two case studies where distributed agile was successfully used. In the first case study, agile allowed for more frequent releases, reduced defects, and leveraged global talent. Best practices like daily stand-ups, estimation games, and tools like JIRA were used. The second case study involved a larger team across more locations developing mobile apps. Specialized teams and automated processes in tools allowed complex work to be completed successfully using distributed agile. Both cases saw benefits like improved velocity, faster turnaround, and time to market.
This document discusses conducting a sensitivity analysis on a proposed investment to install power savers on street lights along a road project to reduce energy costs. It analyzed two alternatives: installing power savers on the existing sodium vapor lamps, or replacing them entirely with LED lights. Field tests showed power savers could reduce energy usage by 25%. A financial model evaluated funding options and found debt financing in phases for one package and full debt financing for the other package yielded the highest returns. Sensitivity analysis showed the investment was not highly sensitive to cost increases up to 50% but could become unprofitable if the remaining concession period was reduced by over 28%. The proposal was concluded to improve profits but was not implemented due to time and cost constraints.
This document outlines 10 commandments or principles for project success based on the concepts of mind, body, and soul. It begins with an introduction to the topic and definitions of key terms. It then describes 3 cardinal rules for project teams based on mind, body, and soul. The rest of the document outlines each of the 10 commandments for project success and discusses challenges in implementing them. For each commandment, it provides solutions categorized as knowledge/mind, action/body, and soul. The commandments focus on areas like scope management, cost estimation, team development, risk management, use of quality tools, and project monitoring and control.
The document describes Concept Prototyping on PMAAS Suite (CPOPS), an approach for managing entrepreneurial projects. CPOPS leverages a Project Management as a Service (PMAAS) framework to prototype concepts and manage project phases in a cost-effective way with minimal risk. Each phase follows an agile methodology and waterfall model to clarify requirements and release components incrementally. CPOPS allows tasks to be prioritized flexibly in the cloud. The approach aims to help entrepreneurs focus on their business while cloud consultants efficiently manage project work.
The document discusses implementing an agile methodology on a project at Atos India while maintaining CMMI compliance. It describes challenges with a fresh, distributed team and how the company customized agile practices like adding two scrum masters, documentation standards, and mandatory pair programming. Metrics showed improved quality, reduced rework and schedule variance after adopting this blended agile-CMMI approach. A survey found the team benefited from better communication, collaboration and early problem identification. The customized process was added to Atos' global standards to provide benefits of both agile and CMMI frameworks.
This document discusses how project management needs to evolve to address changing trends in the business environment. Traditional methods of stakeholder management, communication, and human resources management need to transform into deeper client engagement, articulating client value, and talent management. Project delivery also needs to incorporate more consulting approaches. Additionally, innovation, consulting skills, and social technologies can help augment traditional project management. These changes will help organizations better engage customers, deliver higher value, and ensure project success in today's dynamic marketplace.
Day 1 1620 - 1705 - pearl 1 - deep kamal singhPMI2011
This document outlines a strategic approach for telecom companies to make accurate decisions after an unplanned service outage. It discusses:
1) The need to plan for uncertainty and have a crisis management team to handle outages.
2) The importance of identifying all services, their revenue potential, and stakeholders to understand the full business impact of an outage.
3) Creating a "Service Impact Matrix" during planning that documents each service's subscribers, revenue, and costs if disrupted, to facilitate rapid decision making during a crisis.
4) Steps for handling an outage including consolidating affected services, outage details, and calculating total estimated revenue loss to determine the best option of delaying, proceeding or reverting to
This document discusses best practices for improving efficiency in distributed agile teams. It addresses common challenges such as limited time zone overlap, availability of stakeholders, and cultural differences. Some strategies proposed include daily video meetings to improve communication, assigning pseudo product owners at off-site locations to provide quick clarifications, and involving off-site teams in sprint planning and reviews to increase engagement. Recording important meetings allows off-site teams to review discussions later. Practices like these aim to enhance collaboration and trust between distributed scrum teams.
This document describes the Evolve methodology for implementing CRM solutions. The methodology aims to adapt best practices to diverse IT organizations. It outlines key principles such as iterative development, requirements management, and quality verification. The methodology consists of inception, evolution, and retrospection phases. During inception, the project is scoped and designed. The evolution phase involves iterative analysis, design, construction, and deployment. Retrospection provides project closure. The Evolve Plan documents how the project process will be tuned based on client participation, delivery iterations, and artifact requirements.
This document discusses a framework for motivating quality experts to become quality innovators. It outlines several challenges, including getting a dedicated team of innovators from a non-billable resource team, and motivating innovation that is non-technical and provides internal benefits rather than external customer value. The proposed framework includes appointing innovation champions and teams, creating a sense of competitiveness, tracking progress regularly with senior management support, rewarding and supporting creativity, utilizing employee diversity, and creating a positive work environment. The benefits discussed are improved business and quality management processes, as well as lessons learned and critical success factors.
The document summarizes a business case for a new connected digital picture frame product called DigiPix. It outlines the opportunity, market potential, product concept, development plan, and go-to-market strategy. Key points include strong growth in the digital photo frame market, customer interest in DigiPix's connectivity features, a first-mover advantage over competitors, and financial projections showing potential for $30M in revenue by year 4 with an initial $5M investment and positive NPV. The summary recommends moving forward with a $50K investment to further validate the market opportunity.
This document outlines best practices for project managers to build sustainable enterprises, including leveraging proven quality methodologies like Six Sigma and Lean to improve processes and reduce costs. It emphasizes effective knowledge management, collaborative innovation with customers, and cultivating an "innovation as a habit" mindset in project teams. Adopting these practices can help optimize processes, increase productivity, deliver more value to customers, improve customer satisfaction and loyalty, and ensure long-term business growth and sustainability.
This document provides an overview of a project report on sales prediction using machine learning models. It describes using linear regression and logistic regression to analyze time series sales data and predict future sales and sales of specific products. It outlines collecting sales data, preprocessing the data to address issues, training a model on the data, and using the model for forecasting. The document discusses using these techniques on a dataset from a company to predict sales for upcoming time periods.
This document describes a Deployment Excellence Framework (DEF) to effectively adopt high maturity processes. The framework includes 3 interlinked cycles: 1) Identification Cycle to target initial units and stakeholders, 2) Initial Deployment Cycle focusing on awareness and success indicators, and 3) Sustenance Cycle increasing adoption scope and self-reliance. It also includes a feedback adapter for course correction. The case study illustrates using DEF to standardize an organization's project estimation processes and templates by deploying new estimation models and tools over 6 quarters.
Presentation by sathish nataraj sundararajanPMI_IREP_TP
This document discusses process excellence for new age project management. It describes tools like Advanced Product Quality Planning (APQP), target cost matching, target cost approach curve, point of no return (PONR), ABC analysis, and characteristic management that can be used to enhance the planning, steering, and reporting of projects. These tools help structure project management by aiding in planning, tracking project timelines and costs against targets, prioritizing parts, and ensuring all requirements are met. Using such tools in a standardized way across a company brings transparency and helps complete projects on time and on budget.
The document discusses how fusing aspects of traditional waterfall project management and agile methodologies can improve the chances of project success, especially for large upgrade or migration projects. It provides examples of different "fusion approaches", such as using waterfall delivery within agile iterations or applying agile execution techniques within a waterfall framework. The success of a fusion approach depends on variables like organizational culture, risk appetite, and governance structures. When applied appropriately, a fusion model can help complete projects on time and budget while minimizing risks.
This document describes the Scaled Agile Framework (SAFe) which is a framework for implementing agile development practices at the enterprise level. It discusses how SAFe addresses the limitations of traditional waterfall development and scales agile to meet the needs of large projects. SAFe incorporates key lean principles and consists of three levels - Team, Program, and Portfolio. At each level it defines roles and practices for planning, prioritizing work, and delivering value in short iterations. The goal of SAFe is to synchronize collaboration across many agile teams to continuously and predictably deliver working software.
The document discusses causes of delay in the erection of power transformers in India. It identifies 18 causes of delay which are categorized into 5 groups: internal, external, planning, contractor/vendor, and transportation/packaging. Common delays include material damage during transit, poor storage areas, rework activities, and lack of resources. Addressing three key delays - material damage, rework, and security issues - could save around 40% of delay time and 200,000 INR per site. Proper planning and adherence to quality processes are recommended to avoid delays and their impacts on costs, customer satisfaction, and safety.
The document discusses building a sustainable customer advocacy program. It recommends starting with identifying requirements, forming a program team, and creating a responsibility matrix. The process then focuses on delivering a tailored program to drive new customer acquisitions by shortlisting strong advocates and creating an advocacy messaging framework and outreach program. The final step is creating a tracker to monitor process efficiency and effectiveness against key performance indicators. Implementing this approach can significantly increase customer loyalty and give a competitive advantage.
This document discusses Project Management as a Service (PMAAS), an innovative approach to managing project management phases and processes through a cloud of project management consultants working on an agile platform. Under PMAAS, individual project management phases and processes are managed independently by cloud-based consultants. Each phase acts as an agile sprint, with information from one phase feeding into the next. This gives project managers visibility while keeping project intricacies abstracted. The concept originated from challenges organizations face developing in-house project management capabilities. PMAAS provides a cost-effective cloud-based solution for managing projects.
The document discusses how an innovation program at Tata Consultancy Services adopted Agile project management methodology to address issues they were facing. Some key problems prior to adopting Agile included frequent changes to delivery targets, spending too much time on requirements and design upfront, lack of transparency, and escalated issues. By introducing Agile with support from senior management, establishing user stories and sprints, and increasing transparency, the program benefited from improved planning, early feedback, on-time delivery, and quality.
This document discusses mantras for innovative project management and creating a happy workforce for software/IT project managers. It analyzes common aspirations of young Indian IT professionals, such as work-life balance, new learning opportunities, and challenging roles. The document proposes that project managers can increase worker happiness and productivity by helping fulfill these aspirations. It presents frameworks for understanding individual aspirations, including an aspiration pyramid with work-life balance at the bottom and career growth aspirations like new learning and challenging roles at the top. The document also provides examples of project-level enablers a manager could implement to help team members achieve their aspirations.
This document discusses approaches to implementing agile project management processes for distributed teams across multiple locations. It describes two case studies where distributed agile was successfully used. In the first case study, agile allowed for more frequent releases, reduced defects, and leveraged global talent. Best practices like daily stand-ups, estimation games, and tools like JIRA were used. The second case study involved a larger team across more locations developing mobile apps. Specialized teams and automated processes in tools allowed complex work to be completed successfully using distributed agile. Both cases saw benefits like improved velocity, faster turnaround, and time to market.
This document discusses conducting a sensitivity analysis on a proposed investment to install power savers on street lights along a road project to reduce energy costs. It analyzed two alternatives: installing power savers on the existing sodium vapor lamps, or replacing them entirely with LED lights. Field tests showed power savers could reduce energy usage by 25%. A financial model evaluated funding options and found debt financing in phases for one package and full debt financing for the other package yielded the highest returns. Sensitivity analysis showed the investment was not highly sensitive to cost increases up to 50% but could become unprofitable if the remaining concession period was reduced by over 28%. The proposal was concluded to improve profits but was not implemented due to time and cost constraints.
This document outlines 10 commandments or principles for project success based on the concepts of mind, body, and soul. It begins with an introduction to the topic and definitions of key terms. It then describes 3 cardinal rules for project teams based on mind, body, and soul. The rest of the document outlines each of the 10 commandments for project success and discusses challenges in implementing them. For each commandment, it provides solutions categorized as knowledge/mind, action/body, and soul. The commandments focus on areas like scope management, cost estimation, team development, risk management, use of quality tools, and project monitoring and control.
The document describes Concept Prototyping on PMAAS Suite (CPOPS), an approach for managing entrepreneurial projects. CPOPS leverages a Project Management as a Service (PMAAS) framework to prototype concepts and manage project phases in a cost-effective way with minimal risk. Each phase follows an agile methodology and waterfall model to clarify requirements and release components incrementally. CPOPS allows tasks to be prioritized flexibly in the cloud. The approach aims to help entrepreneurs focus on their business while cloud consultants efficiently manage project work.
The document discusses implementing an agile methodology on a project at Atos India while maintaining CMMI compliance. It describes challenges with a fresh, distributed team and how the company customized agile practices like adding two scrum masters, documentation standards, and mandatory pair programming. Metrics showed improved quality, reduced rework and schedule variance after adopting this blended agile-CMMI approach. A survey found the team benefited from better communication, collaboration and early problem identification. The customized process was added to Atos' global standards to provide benefits of both agile and CMMI frameworks.
This document discusses how project management needs to evolve to address changing trends in the business environment. Traditional methods of stakeholder management, communication, and human resources management need to transform into deeper client engagement, articulating client value, and talent management. Project delivery also needs to incorporate more consulting approaches. Additionally, innovation, consulting skills, and social technologies can help augment traditional project management. These changes will help organizations better engage customers, deliver higher value, and ensure project success in today's dynamic marketplace.
Day 1 1620 - 1705 - pearl 1 - deep kamal singhPMI2011
This document outlines a strategic approach for telecom companies to make accurate decisions after an unplanned service outage. It discusses:
1) The need to plan for uncertainty and have a crisis management team to handle outages.
2) The importance of identifying all services, their revenue potential, and stakeholders to understand the full business impact of an outage.
3) Creating a "Service Impact Matrix" during planning that documents each service's subscribers, revenue, and costs if disrupted, to facilitate rapid decision making during a crisis.
4) Steps for handling an outage including consolidating affected services, outage details, and calculating total estimated revenue loss to determine the best option of delaying, proceeding or reverting to
This document discusses best practices for improving efficiency in distributed agile teams. It addresses common challenges such as limited time zone overlap, availability of stakeholders, and cultural differences. Some strategies proposed include daily video meetings to improve communication, assigning pseudo product owners at off-site locations to provide quick clarifications, and involving off-site teams in sprint planning and reviews to increase engagement. Recording important meetings allows off-site teams to review discussions later. Practices like these aim to enhance collaboration and trust between distributed scrum teams.
This document describes the Evolve methodology for implementing CRM solutions. The methodology aims to adapt best practices to diverse IT organizations. It outlines key principles such as iterative development, requirements management, and quality verification. The methodology consists of inception, evolution, and retrospection phases. During inception, the project is scoped and designed. The evolution phase involves iterative analysis, design, construction, and deployment. Retrospection provides project closure. The Evolve Plan documents how the project process will be tuned based on client participation, delivery iterations, and artifact requirements.
This document discusses a framework for motivating quality experts to become quality innovators. It outlines several challenges, including getting a dedicated team of innovators from a non-billable resource team, and motivating innovation that is non-technical and provides internal benefits rather than external customer value. The proposed framework includes appointing innovation champions and teams, creating a sense of competitiveness, tracking progress regularly with senior management support, rewarding and supporting creativity, utilizing employee diversity, and creating a positive work environment. The benefits discussed are improved business and quality management processes, as well as lessons learned and critical success factors.
The document summarizes a business case for a new connected digital picture frame product called DigiPix. It outlines the opportunity, market potential, product concept, development plan, and go-to-market strategy. Key points include strong growth in the digital photo frame market, customer interest in DigiPix's connectivity features, a first-mover advantage over competitors, and financial projections showing potential for $30M in revenue by year 4 with an initial $5M investment and positive NPV. The summary recommends moving forward with a $50K investment to further validate the market opportunity.
This document outlines best practices for project managers to build sustainable enterprises, including leveraging proven quality methodologies like Six Sigma and Lean to improve processes and reduce costs. It emphasizes effective knowledge management, collaborative innovation with customers, and cultivating an "innovation as a habit" mindset in project teams. Adopting these practices can help optimize processes, increase productivity, deliver more value to customers, improve customer satisfaction and loyalty, and ensure long-term business growth and sustainability.
This document provides an overview of a project report on sales prediction using machine learning models. It describes using linear regression and logistic regression to analyze time series sales data and predict future sales and sales of specific products. It outlines collecting sales data, preprocessing the data to address issues, training a model on the data, and using the model for forecasting. The document discusses using these techniques on a dataset from a company to predict sales for upcoming time periods.
This document discusses how improving printed circuit board (PCB) design processes can provide strategic advantages for companies such as faster time to market, lower product costs, and product differentiation. It finds that the top pressures driving companies to improve PCB design are the need to quickly launch new products, market demands for lower cost and higher quality products, and reduced development budgets. The best-in-class companies are defined as those achieving 88% on-time product launches, 13% decreased development time, 86% meeting cost targets, 11% lower product costs, and 88% meeting quality targets. These companies leverage design for manufacturability tools, formal component cost management processes, and optimize resources across projects. The document recommends companies adopt these best
This document discusses business process reengineering (BPR). It begins by explaining that core business processes can become complex and inefficient over time, adding unnecessary costs. BPR aims to radically redesign these processes to optimize costs and enhance profits. The document then provides a brief history of BPR, outlines some common BPR methodologies, and describes the key phases of the McKinsey BPR methodology in particular - including defining the scope, redesigning the process, and piloting the new design. Information technology is discussed as playing a key enabling role in BPR initiatives.
Customer relationship management (CRM) is an important element in all forms of industry. This process involves ensuring that the customers of a business are satisfied with the product or services that they are paying for. Since most businesses collect and store large volumes of data about their customers; it is easy for the data analysts to use that data and perform predictive analysis. One aspect of this includes customer retention and customer churn. Customer churn is defined as the concept of understanding whether or not a customer of the company will stop using the product or service in future. In this paper a supervised machine learning algorithm has been implemented using Python to perform customer churn analysis on a given data-set of Telco, a mobile telecommunication company. This is achieved by building a decision tree model based on historical data provided by the company on the platform of Kaggle. This report also investigates the utility of extreme gradient boosting (XGBoost) library in the gradient boosting framework (XGB) of Python for its portable and flexible functionality which can be used to solve many data science related problems highly efficiently. The implementation result shows the accuracy is comparatively improved in XGBoost than other learning models.
This resume summarizes Chandrashekhar Potula's experience in performance engineering of large IT systems over 8.5 years. He has worked on technologies like IBM Mainframe, databases like DB2, Oracle, and SQL Server 2005. Recent work includes reducing MIPS/MSU for a UK insurer and performance modeling. He lists technical skills, methods experience, and achievements including awards and certifications. The resume provides details on several roles with customers in industries like insurance, banking, and retail.
1. The report provides a benchmark analysis of Cape Rock Ltd's business technology solutions compared to a chosen benchmark group.
2. It assesses the maturity and functionality of Cape Rock Ltd's applications, infrastructure, and IT services in key solution areas.
3. The report also outlines top development trends, popular solutions and providers, and satisfaction ratings within the benchmark group to help Cape Rock Ltd evaluate opportunities to improve support for their business needs.
Data Severance Using Machine Learning for Marketing StrategiesIRJET Journal
This document discusses using machine learning techniques for data segmentation and analysis to improve marketing strategies. It proposes two clustering models: one for customer segmentation and one for product segmentation. For customer segmentation, it uses RFM (Recency, Frequency, Monetary) analysis and k-means clustering on a dataset of 642,234 customers. For product segmentation, it uses ABC analysis with Pareto charts on a dataset of 20,870 products. The goal is to segment the customer and product data into meaningful groups to gain insights for marketing strategies. Key algorithms discussed include RFM analysis, k-means clustering, ABC analysis, Pareto charts, and the elbow method.
This document summarizes a capstone project for a small electric motor component manufacturer called The Company Inc. The project aimed to help the company address revenue and profit margin lags by identifying niche markets to create strategic differentiation, specifically in the oil & gas industry.
The approach involved three stages: 1) a technology analysis to identify core capabilities and opportunities in electric motor technology for oil & gas, 2) a strategic analysis of The Company's environment and the oil & gas value chain to identify opportunities, and 3) brainstorming, prioritizing, and assessing strategic opportunities.
The recommendation was for The Company to become a system integrator for "SMART" electric motor components in oil & gas, including a control monitoring
(Brian dost central office) rasco, brian u. - pmdp mmc 27-capstone project id...CHED
This project aims to improve the productivity and efficiency of the Financial and Management Service (FMS) of the Department of Science and Technology Central Office (DOST-CO) through process simulation and streamlining. The project will review and simulate FMS processes to identify areas for improvement. It will consider the goals of the organization, customers, and employees. Process models and options will be generated to more efficiently allocate resources and regularize employee schedules. This is expected to lead to improved financial conditions, shorter work hours, better workplace safety, and strengthened teamwork. The project will use Define, Measure, Analyze, Implement, Control methodology and lean process techniques. It will be implemented by a cross-functional team over 3 months to support
1) Adopting green IT practices like consolidating servers and optimizing data centers can significantly reduce costs and carbon emissions while improving reliability and performance. One company achieved savings of £1.9 billion over 5 years and reduced carbon emissions by 29,897 tons annually.
2) As financial institutions, your ability to influence clients' IT transformations towards sustainability is important both financially and environmentally. Partnering with experts in green IT can replicate these benefits through proven methods.
3) A short assessment of your current IT delivery against industry standards can identify opportunities to cut costs up to 50% through standardized, efficient services while reducing risks.
CUSTOMER SEGMENTATION IN SHOPPING MALL USING CLUSTERING IN MACHINE LEARNINGIRJET Journal
This document discusses using clustering algorithms in machine learning to segment customers in a shopping mall. It aims to identify groups of customers with similar characteristics like gender, age, spending habits to more effectively market to each group. Specifically, it uses k-means clustering to segment customers and visualize differences in gender and age. It then examines their annual income and proposes that segmentation focuses on improving customer spending scores. The proposed system uses machine learning approaches like k-means clustering which is more accurate and efficient than traditional manual methods for analyzing customer data and finding insights to identify customer segments.
This document discusses requirements analysis and prioritization for a new home sector order processing system for the Clean Brite Company (CBC). It begins by providing background on CBC and issues with a previous failed IT project. A requirements workshop was then held with various CBC departments to gather requirements. 18 initial requirements were listed, but some were deemed "non-appropriate high level requirements" as they were not functional or specific enough. The document identifies 11 "high level requirements" that are critical for the new system. It concludes by explaining MoSCoW prioritization for categorizing requirements as "Must have", "Should have", "Could have", or "Won't have".
IJRET : International Journal of Research in Engineering and Technology is an international peer reviewed, online journal published by eSAT Publishing House for the enhancement of research in various disciplines of Engineering and Technology. The aim and scope of the journal is to provide an academic medium and an important reference for the advancement and dissemination of research results that support high-level learning, teaching and research in the fields of Engineering and Technology. We bring together Scientists, Academician, Field Engineers, Scholars and Students of related fields of Engineering and Technology
A Practical Approach for Power Utilities Seeking to Create Sustaining Busines...Cognizant
For power utilities, analytics are a key to enhanced operational performance and competitive standing. We offer a roadmap for determining and prioritizing relevant analytics, assessing analytics maturity, and implementing an effective analytics process encompassing smart meters, phasor measurement units and other useful sources.
How to select the best business continuity strategy and solution?PECB
This webinar covers underlying principles for the selection of a Business Continuity solution and the tiers of Business Continuity. Within these segments we will analyze different tiers and strategies, from Rebuilt and restoration strategy to mirror site. Also, a list of BCM strategy considerations related to business trends and emerging technologies will be provided.
Main points covered:
• The underlying principles for the selection of a Business Continuity solution and the tiers of Business Continuity
• Analyze different tiers and strategies
• BCM strategy considerations related to business trends
Presenter:
The webinar was presented by Silvana Tomic Rotim. She has 20 years of rich work experience in the development and delivery of business and ICT consulting services for public and private sector. She has more than 15 years of experience in leading, coordinating and managing of different consulting project teams in more than 50 consulting projects
Link of the recorded webinar published on YouTube: https://youtu.be/F79enht3IEY
Project and Portfolio Management in a Federated Governance ModelUMT
This document describes an approach for managing project portfolios across multiple business units using proportional and binary optimization. It discusses how corporate and business unit CIOs can use these techniques to prioritize projects, optimize spending, and align investments with corporate strategies. Binary optimization allows business units to select optimal project portfolios, while proportional optimization gives corporate CIOs a way to adjust program funding levels without eliminating them entirely. The methodology provides a framework for effective portfolio management in complex, federated organizations.
10 Key Action to Reduce IT Infrastructure and Operation Cost StuctureIcomm Technologies
With NetApp, we have realized major cost savings in terms of our storage and server infrastructure. This has allowed us to catch up with other colleges and universities that compete with us by freeing up budget to invest
in classroom technologies.”
Similar to Presentation by vignesh swamidurai (20)
The document describes IBM's Actuate program for project launches. Actuate aims to ensure projects are started right by facilitating key startup activities within 45 days. These activities are grouped under 10 focus areas like project scope, risk assessment, governance, and tools setup. IBM has seen benefits of Actuate like reduced surprises, improved risk assessment, and faster startup phase completion. Over time, Actuate coverage has increased while duration to complete activities has decreased, showing improved efficiency. Lessons learned include addressing delays in input documents and stakeholder availability.
This document discusses how businesses can create shared value for both society and business through their operations and strategies. It provides four approaches for shared value creation: 1) Solve societal problems and create new business opportunities; 2) Align existing products to benefit society; 3) Improve internal operations; and 4) Choose a social cause to support that aligns with the business. Creating shared value can provide competitive advantages for businesses through new markets, cost savings, and increased loyalty while also generating employment, participation opportunities, and improved standards of living for communities.
The document discusses different approaches an IT services company can take to incubate emerging technologies and build capabilities around them. It describes three main approaches: the "deep dive first" approach where R&D explores a technology in-depth before bringing it to delivery units; the "hand in hand" approach where R&D and delivery units collaborate early in the process; and crowdsourcing challenges to the organization. It provides examples of how these approaches have worked or not worked for technologies like cloud computing, enterprise mobility, location intelligence and IoT. The document advocates that a collaborative approach involving both R&D and delivery units early on tends to be most effective for technology adoption.
The document discusses ways an offshore team improved engagement and ownership of a software project. The team increased communication, implemented regular status reporting, and delegated resources onsite. These changes built trust with partners and improved predictability. As a result, the offshore team took on more work, delivered additional features ahead of schedule, and received very positive feedback and requests for more offshoring from partners. However, challenges around testing automation, buffer management, and continuous learning remain.
Social media, mobile devices, analytics and cloud computing (SMAC) have combined to create a technology ecosystem that supports project management. SMAC allows project managers to access information anytime from anywhere, collaborate more effectively with teams, and gain insights from analytics. While SMAC has benefits, successful adoption depends on factors like an organization's business model and culture. Project managers must redefine processes and best practices to leverage SMAC's value.
This document discusses stakeholder management strategies for the successful implementation of India's Right to Education Act. It argues that stakeholder engagement and community mobilization are key, as seen in the success of India's polio eradication campaign. Specifically, establishing effective school management committees and increasing parental involvement can help address ongoing challenges like low learning outcomes and the enrollment of economically disadvantaged children. Proper monitoring of schools is also needed to ensure compliance with the act in practice, not just on paper. With coordinated efforts among all stakeholders, including government, schools, communities and volunteers, the goals of universal elementary education can be achieved.
This document discusses the qualities of an entrepreneurial project manager. It argues that entrepreneurial project managers see beyond the typical constraints of time, cost and scope, and understand how projects fit within an organization's strategic goals and culture. They are able to motivate teams by communicating the bigger picture and building strong relationships. Entrepreneurial managers also anticipate challenges and adapt to changing priorities. While they face barriers like lack of growth opportunities, organizations benefit from supporting entrepreneurial managers through training, mentoring and providing challenging assignments to help them grow with the company.
This document discusses approaches to implementing agile project management processes for distributed teams across multiple locations. It describes two case studies where distributed agile was successfully used. In the first case study, agile allowed for more frequent releases, reduced defects, and leveraged global talent. Best practices like daily stand-ups, estimation games, and tools like JIRA were used. The second case study involved a larger team across more locations developing mobile apps. Skill-based team structures and automated processes helped ensure success. Both cases saw benefits like improved velocity, faster turnaround, and time to market.
The document discusses using social networks in project management. It describes how social networks can provide benefits like increased business value, better stakeholder engagement, and improved collaboration for virtual teams. The document outlines how social networks can be applied to various project management areas such as scope definition, communications, collaboration, and risk management. It also provides examples of how tools like Twitter can facilitate project communications and information sharing through features like tweets, hashtags, and lists. Finally, the document discusses considerations for implementing social networks in projects, including training teams and defining rules for privacy and content management.
1. Mantra for Process Excellence
Vignesh Swamidurai
Assistant Consultant
TATA Consultancy Services
2. Taming RTB using
Central Composite
Design for Process
Improvement
PMI National Conference – Mantra for Process Excellence
3. Table of Contents
1. THE BUSINESS CHALLENGE ................................................................................................4
2. CENTRAL COMPOSITE DESIGN ...........................................................................................5
3. INITIATION ...............................................................................................................................6
4. APPLYING CCD TO TICKET OPTIMIZATION ........................................................................7
5. APPLYING CCD TO COST OPTIMISATION ..........................................................................9
6. SETTING UP THE GOALS FOR 2013 .................................................................................. 10
7. THE PATH TO OPTIMISATION ............................................................................................. 11
7.1 The Ticket Optimization Exercise ................................................................................... 11
7.1.1 Ticket Reduction using Causal Analysis and Resolution Process Area ........................... 11
7.1.2 The Results –Ticket Optimization................................................................................. 12
7.2 The Cost Optimization Exercise ..................................................................................... 13
7.2.1 Cost Optimization using Organizational Performance Management Process Area ........... 13
7.2.2 The Results ................................................................................................................ 14
8. CONCLUSION ........................................................................................................................ 15
9. ACKNOWLEDGEMENTS....................................................................................................... 15
10. REFERENCES.................................................................................................................... 15
4. Taming RTB using Central Composite Design
ABSTRACT
The application of Central Composite Design (CCD) in Software estimation is an innovative approach to
determine the Optimum goals for a project. This combination of Statistical estimation and highly matured
process deployment can result in substantial benefits and reduction in operating cost for an Organization
and can be applied to any RTB project across any industry. CCD is a statistical methodology of identifying
the independent variables or factors that affect a product or process, and then studies thei r effects on a
dependent variable or response in order to find the optimum setting of factors. In this paper, the Authors
have evaluated the usage of CCD for Software Optimization Estimation to determine the optimum goals
for a project. As a case study for this analysis, the Authors have chosen an RTB project for a Retail
Banking Customer. The different project parameters required for optimal performance have been
assessed and these parameters have been applied to CCD model to arrive at optimized goals. The two
primary focus areas were Ticket Optimization and Cost Optimization. The optimum goals for the project
have been derived through research of historical data and applying them through the CCD model which is
explained in the paper. The following goals were set for the project for 2013 as an outcome of CCD and
these determined goals were achieved successfully by the project team.
• 50% reduction in the number of Production Failures / Resolution Days
• 0.5 Million USD total cost of application savings / Soft Dollar savings
Keywords: Process Improvement, Cost Savings, Ticket Management, Central Composite Design, CMMI,
Pareto, RTB
1. THE BUSINESS CHALLENGE
Businesses in the Industry vary daily due to market dynamics in the global economy. Organizations are
striving hard to cope up with the ever-growing business needs, in addition to facing challenges such as
slim operating margins, rapidly changing technologies, decreasing time to market and strong competition
with counterparts. Coping up with these increased dynamism, uncertainty and complexities are a huge
challenge faced by the organizations of the current era.
Organizations are looking for every possible opportunity to reduce expenses, conserve resources and
increase their stock prices. An ideal scenario expects the Run theBusiness (RTB) cost to remain constant
and at a minimum, thereby allowing organizations to concentrate more on Change the Business(CTB)
projects.
5. However in the current scenario, due to the market dynamics, the cost incurred by RTB is increasing
exponentially. Therefore the CTB cost has to be compromised, to keep the business running. This causes
a huge pressure to reduce the day-to-day operating cost to grow more efficiently. The ideal scenario and
current scenario sample is depicted in Fig.1 and Fig.2.
Figure 1: RTB Vs CTB - Ideal Scenario** Figure 2: RTB vs CTB–Current Scenario**
** - Graphs plotted with mocked data to show the distribution, does not include actual spread
To reduce the RTB cost, there is a need for a verified Optimization technique and a proven Management
methodology to achieve good results. This paper discusses about the modernistic approach of using a
well-established Statistical Optimization model – Central Composite Design (CCD) for Software Process
Optimization. The paper also describes the use of Management Art to achieve the set of determined
goals using the Scientific Optimization model in an RTB Project.
This innovative combination of statistical study and management principles has facilitated in reducing the
operating cost of RTB, thereby helping to invest more in CTB, which in turn benefits the organization to
stay competitive and Customer-focused.
2. CENTRAL COMPOSITE DESIGN
Central Composite Design (CCD) is an established design approach for Optimization, which is
predominantly used in Metallurgical and Pharmaceutical industries. It is a technique that revolves around
the study of the influence of different variables, based on the outcome of a process. It involves identifying
the independent variables or factors that affect a product or process, and then studies their effects on a
dependent variable or response. CCD can also be treated as an enabler, to find optimum setting of
factors.
6. The implementation of CCD involves identifying the following three key factors:
1) A Factorial Design in parameters, each having two different coding levels.
2) A set of Centre Point for each parameter whose values is a median of levels identified in the
Factorial design
3) A set of Axial Points, which considers values that are below and above the median of Factorial
Design Points.
To use CCD, a controlled environment is required. A Production environment is an ideal fit for such a
controlled environment, because the Production environment is a setting where the reliable software and
robust hardware configuration are available for commercial daily operations of applications. Hence, it
becomes easier to vary the required set of parameters and realize the results. In addition, RTB projects
have historical data and can be easily tapped to be used for CCD analysis.
In a conventional CCD, a set of controlled experiments is performed with identified factors. However, in
this case, some re-computation was performed with the historical data, to arrive at the results of a
process. For this purpose, Data Mining was performed for each category of Optimization and the factors
were determined. Using the factors determined, the Quadratic expression of CCD is used to obtain the
Optimum goal point.
3. INITIATION
CIOs find it challenging to mandate the reduction of the RTB cost, as much as possible and invest the
savings benefit into strategic CTB projects. Increased complexities with RTB cannot be managed easily
using legacy management principles and skills. As a result, the Authors of this paper have chosen the
approach of CCD, which is a proven statistical model for Optimization.
For CCD analysis, the Authors chose an RTB project for a Retail Banking Customer. To start with, the
focus areas have to be set for the project. The basic requisite for an RTB project is the stability of
applications and reduction of tickets. Based on the applications’ performance in the past, complexity of
applications and the nature of work, the following two primary focus areas were determined:
Ticket Optimization
Cost Optimization
The following are the limitations of the current setting in the project:
Cost budget is limited
Number of FTE is constrained
7. The two Optimization areas were considered for investigation with CCD technique to obtain optimum
levels that can be set as a goal for the year 2013.
4. APPLYING CCD TO TICKET OPTIMIZATION
Being an RTB project, the priority of the project primarily lies on ticket reduction. Tickets are created,
whenever there are any Production failures (known as Abends or Abnormal End in Mainframe).
Historical data from 2012 was collected for tickets that occurred during 2012, and they were scrutinized
for factors contributing to them. There are three primary factors that affect the numbers of tickets (from
the year 2012):
Number of Production failures(Abends) in a month
Recovery time for each Production failure1
Resolution time for each Production failure2
These factors were fed to the CCD technique, to get an optimum value of tickets that could be fixed with
current base resources in the year 2013. Number of resources available to provide break -fix installs and
baseline hours were almost the same for 2012 and 2013 and hence this factor was a constant. The
Authors used a standard CCD with five center points and alpha value of 1. The corresponding factor
properties were updated within the CCD model and each independent variable had three levels assigned
to it (– 1, 0 and +1), based on a predetermined range of tickets or time and categories.
Table 1: CCD Variable – Coded Level Matrix
Independent variables
Coded levels
-1 0 1
Top 5 categories 80 100 120
Time/abend (mins) 35 50 65
Time/resolution (days) 80 100 120
The study was carried out, according to the CCD, and the experimental points were used, based on data
points from 2012. The regression coefficients for the second order polynomial equations and results for
the linear, quadratic and interaction term are presented in Table 2.
1 – Recovery time of a ticket is the time taken to restore service after an incident has occurred. This may be a temporary solution
or work-around to restore the Service
2- Resolution time of a ticket time taken to permanently fix the ticket, so that reoccurrence will not happen again.
8. Table 2: Variation of Parameters for Optimum Point
S.NO
Top 5
categories
Time/abend
(mins)
Time/resolution
(days)
No of tickets
that can be
resolved
1 80 38 88 51.11
2 83 45 80 53.3
3 120 56 93 50.09
4 105 35 99 52.2
5 119 55 119 48.33
6 114 60 120 52.11
7 103 65 111 49.6
8 109 37 86 48
9 94 44 94 38.88
10 117 35 90 49.3
11 96 39 86 49.09
12 112 49 90 49.7
GRAND
TOTAL 1252
1156 591.71
The second order polynomial formula for CCD was used, to arrive at the number of tickets that can be
resolved.
y = β0 + β1x1 + β2 x2 + β12x1x2 + β11x12 + β22x2
2
The contour and quadratic formula result indicates that the maximum benefit occurs when an average
(591.71/1252) tickets can be reduced. As the average is 47.26, 50% ticket reduction is considered, as a
result from the Optimization. The predicted maximum achievable result will be 50% ticket reduction in
2013, out of the total tickets from 2012.
9. 5. APPLYING CCD TO COST OPTIMISATION
The major factor for the increasing RTB spend is the total cost of applications. By effectively managing
this cost, a good savings can be achieved, which can be turned into a profit for the organization.
The four major factors that impact the Cost Optimization are as follows:
Number of Production failures(Abends) in a month
Recovery time for each Production failure
Resolution time for each Production failure
Effort per cost saving task
These factors were introduced to the CCD technique to obtain an optimum Cost savings that can be
obtained in the year 2013, with current resources being the same during 2012 and 2013. The
corresponding factor properties were updated within the CCD model and each independent variable had
3 levels assigned which were – 1, 0 and +1 based on a predetermined range and categories.
Table 3: CCD Variable – Coded Level Matrix
Independent variables Coded levels
-1 0 1
Number of Production Failures in
a month 80 100 120
Recovery Time per failure (hours) 35 50 65
Resolution Time per failure (days) 80 100 120
Effort per cost saving task 100 200 300
The study was carried out according to the central composite design and the experimental points were
used from project reports for 2012.The regression coefficients for the second order polynomial equations
and results for the linear, quadratic and interaction term are presented in below table.
10. Table 4: Variation of Parameters for Optimum Point
S. No
# of Prod
Failures /
month
Recovery
time / failure
(mins)
Resolution
Time / failure
(days)
Effort per
cost
saving
task
(hours)
Cost Savings (in
MM USD)
1 80 38 88 256 0.8
2 83 45 80 210.03 0.63
3 120 56 93 190 0.45
4 105 35 99 188 0.41
5 119 55 119 189.11 0.37
6 114 60 120 188.78 0.309
7 103 65 111 280 0.965
8 109 37 86 210 0.699
9 94 44 94 194 0.501
10 117 35 90 193.67 0.58
11 96 39 86 189 0.49
12 112 49 90 190.9 0.51
Grand
Total
6.714
Applying the second order polynomial equation to this data, the Cost Savings in MM USD was obtained:
y = β0 + β1x1 + β2 x2 + β12x1x2 + β11x12 + β22x2
2
The contour and quadratic formula result that the maximum Cost Savings obtained by the team could be
near 6.714 MM /12 = 0.56 MM. The determined achievable Savings Goal would be in this case as 0.5
Million USD in 2013.
6. SETTING UP THE GOALS FOR 2013
Based on the results from CCD Approach and after internal brainstorming within the teams, the following
goals were set for 2013:
50% reduction in number of tickets from Year 2012
0.5 Million USD Total Cost of Application Savings / Hard Dollar Savings
11. 7. THE PATH TO OPTIMISATION
After the goals were identified, the next step was to identify a good management approach to achieve
them. Based on constraints on the problem, various structured frameworks are available for solving
business problems and effective process execution. The Authors of the paper have chosen the well-established
and accepted model for implementation of goals – CMMi framework. TCS being at CMMI
Level 5, both the goals were targeted to be implemented with CMMI Level 5 areas for Support and
Process Management.
7.1 The Ticket Optimization Exercise
For the Ticket Optimization exercise, the authors chose the Causal Analysis and Resolution (CAR)
Process area of CMMI Level 5 model. As per this process area, the root causes of historical tickets from
2012 wereanalyzed systematically using Pareto Chart. Once the Causal Analysis for the occurrence of
the tickets was determined, they were systematically addressed to prevent their reoccurrence.
7.1.1 Ticket Reduction using Causal Analysis and Resolution Process Area
Based on the CCD Model described in previous sections, the goal for 2013 was set as 50% Reduction in
the number of tickets from previous year. The Ticket Reduction Exercise was done in 2 phases as per the
Specific goals outlined in CMMI Level 5 CAR Process area as below:
Phase I : Measure and Perform Causal Analysis
In this phase, the historical data of 2012 tickets were analyzed and causal analysis was done for each of
them. After this, similar causes were grouped together and Pareto principle was used to prioritize the
deployment actions.
Figure 3: The Pareto Analysis for Root Cause for 2012 Tickets
12. 7.1.2 The Results –Ticket Optimization
Once the prioritized causes were identified, the next step was to implement the action proposals to avoid
the occurrence. For this, the second specific goal statement of CMMI Level 5 CAR Process area was
followed:
Phase II :Prioritize and Deploy action proposals
For causal analysis and resolution tracking, a new tracking approach, Ticket Tracking Sheet, was
introduced to keep a track of all tickets and causal analysis for each ticket. On analyzing the tickets, it
was seen that Top 3 causes attribute to 80% of the tickets. By fixing the Top 3 Causes, more than 50%
reduction of tickets could be achieved.
Proactive approach was followed to mitigate all the top 3 root causes. Automated tools were introduced to
track frequently occurring problems. Supplementary automated monitoring systems were introduced to all
critical interfaces to avoid data issues and thereby reduce mass incidents. False alert Optimization was
done to make sure that tickets are created only when there is really an issue in the Applications. This also
reduced the manual intervention on delays and false notifications. Bottom line of this exercise was "Every
ticket should have a follow up or action item" thereby to nail down the root cause at the first occurrence of
an issue. Meticulous reviews were conducted when a change was installed in Production from the
Development team, to reduce the issues arising due to Integrated Releases.
Figure 4: Ticket Reduction – Actual Vs Target
Due to quicker Root Cause Analysis, number of tickets reduced leading to quicker resolution for the
tickets and thereby leading to tasks getting completed at a faster pace. All of this contributed to more time
available for working on Value Additions. This leads to a Cyclic Effect, due to which the applications were
optimized to the maximum.
13. Figure 6: The CYCLIC Effect
7.2 The Cost Optimization Exercise
7.2.1 Cost Optimization using Organizational Performance Management Process Area
The purpose of Organization Performance Management (OPM) Process Area of CMMI Level 5 is to
manage the organization’s performance and meet the business objectives in a proactive manner. This
process area follows a very well defined sequence of procedural steps that can be used to realize a goal
to improve the Organization’s performance. The specific goals of this process area and how they were
realized is given below:
Phase I : Identify the Scope and areas for Process Improvement
In this phase, the scope of the problem is defined and the SME’s from the teams defined which
applications have opportunities to start with for Cost Optimization.
Phase II : Review and Validation of Selected improvements
In this phase, the current state of the problem is reviewed, all the relevant information is studied and to
identify if there are any bottle-necks for implementation. During this phase, the Proposals are submitted to
the Performance Management team and reviewed with them to identify the cost saving opportunity. The
estimated savings for the task is identified in this stage.
Some of the opportunities identified and proposed to the Performance Management team are as follows:
Deletion of unused datasets in Production regions
Purging of Obsolete data in tables
14. Replace Full updates with Delta Updates in Tables
Usage of new Utilities and newer version of software to reduce the cost
Program changes which will bring about Cost savings
Cost-Benefit analysis is done based on the benefits yielded by the improvement against the effort spent
on deployment. After this, the improvement is taken forward to the next phase.
Phase III : Verify, Execute and Evaluate the benefits
In this phase, the identified opportunities are prioritized and a draft roadmap is outlined. The required
changes to enable and sustain the improvements are done in this phase. The implementations of
identified opportunities are done and the actual cost savings are calculated and submitted to the
Customer for feedback. The feedback is collected and the cost savings are approved by the Customer.
7.2.2 The Results
As a result of the steps outlined by the Organization Performance Management Process Area of CMMI
Level 5, teams worked on different Process Improvement tasks in the year 2013. These tasks have
yielded good results and yielded substantial savings to the Customer.
Figure 8: The Cost Savings Achieved in 2013
15. 8. CONCLUSION
Thus the CCD Optimization Technique is a good fit for Software Optimization Estimation also. This
technique can be used for any RTB project which has historic data. Using the CCD, realistic goals can be
determined. Skillful planning and meticulous approach to the determined goals can result in substantial
benefits and can reduce the Operational cost. This will balance the RTB and CTB cost and the
Organization can spend more in Strategic CTB projects.
9. ACKNOWLEDGEMENTS
We would like to sincerely thank Kannan Balamurugan (Delivery Head) for providing valuable inputs
about Central Composite Design and for reviewing the paper and providing constructive feedback which
helped us to keep progressing. Our thanks to Sivashankar Hariharan (Delivery Manager), for providing
his inputs on Management techniques in Process Improvement and also initiating the idea for the paper.
We would also like to thank Rejo Reghunadh(Senior Business Analyst) for his contribution towards the
project data analytics.
10. REFERENCES
[1] Myers, Raymond H. Response Surface Methodology. Boston: Allyn and Bacon, Inc., 1971
[2] Koch, Richard – The 80/20 Principle – The Secret to Success by achieving more with less, 1998
[3] N.S. Sreenivasan, V.Narayana – Continual Improvement Process, 2005
[4] Carnegie Mellon Software Engineering Institute, “The CMMI Version 1.2 Overview presentation 2007.
http://www.sei.cmu.edu/library/assets/cmmi-overview071.pdf
[5] CMMI for Development, “CMMI-DEV V1.3,” Technical Report, Software Engineering Institute,
Pittsburgh, 2010.