Sie sind auf Seite 1von 5

Pareto Analysis 1) Individual team Performance For employee lay off Pareto analysis is being used in software organization.

Low performer list can be achieved by plotting the list of team member in descending order over a span of sprint or release. This helps in formulating balance score card. Low performers can be identified and replaced as per time. Number of hours per line of codes will determine the efficiency of team member performance. If a developer is writing less code in whole sprint and affecting the performance of whole team, through Pareto chart that can be identified. 2) Product Failure reasons Software business is based on products of services. When a product is launched and it fails in market. To analyze the failure of the product Pareto analysis is used. All the failure reasons/causes are listed in descending order All reasons are given the magnitude as per surveys conducted or product complaint received. Research is made to sort out the actual cause of failure. Most of the cases a very low priority issue like environment or user behavior make the reason of product failure. Reason identified in the Pareto Analysis is kept in consideration while developing other products. It is made part of requirement gathering from onward projects. 3) User Reductions Software business is mostly based on number of users. More the number of users more profit you can earn. To analyze reduction in number of users of products Pareto analysis is being used in software industry. All the reasons identified are plotted in descending order. Magnitude is given to all the reason as per data collected from sources. Organization works on minor causes which are reducing the number of users Most of the time research on competitors focus is not done. Which is major cause of failures. User attraction plan is added in future plan in form of early marketing or by launching beta versions to get user response on products. Helps in capturing maximum customer market. 4) Performance Issues Good quality of Software depends upon performance of workers. If the performance of workers is good, the quality of product will have much more satisfaction level. To figure out the major reason of low performance software organization uses Pareto Analysis. Performance issues involve work environment, pay ranges, tools and many other things. Less focus is given to work environment in software organization as lead persons came from diverse domains where environmental factor is not reflecting on performance. If overall performance is low, Pareto analysis is used to figure out the major cause.

All the identified issues are listed in descending order. Most of the time, work environment is the cause of low performance which is always ignored. This helps in increasing the performance of employees.

5) Project Improvement identification after assessment Software organizations evolve very rapidly with passage of time. Pareto analysis helps in identification of improvement areas. If there are issues occurring in any process area, all the issues are identified along with the improvement areas related to that process area Minor issues are addressed which are mostly ignored, in most of cases customer involvement is ignored which is reason of major failures. Helps in future planning for process improvement Histogram 1) Mean time to failure Mean time to failure is calculated as it is part of contract or provided to customer when product is sold to them. Reasons of failures can be identified Number of failure over a period of time can be identified. Recovery time can be identified over a period of time. Helps in future planning for the product. 2) Product support cases for specific products Product support cases for specific products can be identified over a period of time. Number of increased product support cases over a period of time can be identified over period of time. Reason of increased number of support cases can be identified. Issues can be addressed as early as possible while looking at the increasing trend. Helps in future planning. 3) Employee turnover Employee turn-over over a period of time can be observed, why employees are leaving jobs. Employee turnover trend over period of time can be observed. Reasons of turnover can be identified Work upon the reasons can be done and employee retention rate can be increased. Future policy can be made for employee as per the results achieved from histogram. 4) Performance Employee or team performance can be measured over a period of time. As organization is working in sprints, team velocity matters a lot to higher management. Team/employee work velocity can be calculated over a period of time

Velocity can help in identifying performance over a period of time. Can help in identification of reasons of good and bad performance. Helps in identification of blocking issues, which are reducing team performance in a specific time period. Helps in future planning for other projects. 5) Issue logging Number of issues logged over a period of time can be identified, which will be helpful in identifying the root cause Number of issues logged over a period of time. In the start of sprint numbers of issues logged are more and as product get mature, number of issues lower down. If number of increasing in end, then project manager has to take serious actions after identifying the root cause of the raise in logged issues. Helps in identification of issues logged after release of product. Helps in planning of future projects Check Sheet 1) Team Performance 2) Number of bugs logged per day 3) Number of hits per day 4) Threshold exceed measures 5) Number of failures 6) Charter 7) Bugs classification

Scatter diagram 1) Team performance Team performance over a period of time can be measured. As organization is using different SDLC depending on project nature. Team velocity can be measured over time Team velocity can be measured on number of story points completed in a sprint. Number of product support cases resolved in a sprint. If team is deviating from normal trend, the occurrence can be identified and actions can be taken against that. Can helps in future planning

2) Comparison between lines of codes and number of bugs Number of lines of codes can be compared to number of bugs logged over a period of time. If lines of codes are less and numbers of bugs are more, it clearly shows that there is some issue with coding/programmer. This helps in determining maturity of development and testing process. Helps in taking corrective action at early stage rather than at completion. Helps in code quality improvement. 3) Comparison between number of sales and user hits As the number of sale increases, performance of product gets affected. As numbers of users get increased, number of hits also increases. Performance factor or response time of the product will be of great concern to the organization. If numbers of hits are rising much more after sales are increased, organization needs to take actions to meet current usage needs. Helps in future planning of product and marketing 4) Comparison of product support cases per release Numbers of product support cases are logged after releases. How many product support cases are logged over a release cycle? Number of product support cases logged during a release can be monitored. If number a product support cases increases dramatically, it shows poor work quality or any other major issue. Issue can be identified, and serious actions can be taken at an early stage. Helps in future planning to reduce post release issues. 5) Bug comparison after release Comparison of number of bugs logged before and after release can help in determining how well teams are working. If numbers of bugs logged are less than the number of bugs after release it clearly shows the deficiencies in testing work, or incomplete requirement gathering. This is a reactive approach. Used to determine the performance of teams. It is not mostly used, as it has huge risk of product failure, most of the time proactive approaches are used to determine the right path of product. Cause and effect diagram 1) Employee turn over Cause and effect diagram helps in determining reasons of employee turnover. If employee turnover is increasing, cause and effect diagram can be used to determine the root cause of the problem. In most of the cases good package offered from competitors make the reason. In some cases management decisions increases the turnover. It helps in future planning and strategy determining

2) Bug increase ratio 3) Performance reduction 4) Sales reduction 5) Product failure

Das könnte Ihnen auch gefallen