evaluating software development team
Download as PPTX, PDF0 likes730 views
The document discusses strategies for evaluating the performance of software professionals and teams. It introduces the Strategy Based Evaluation Method (SEM) which aims to improve traditional annual or semi-annual reviews. SEM links performance directly to corporate goals, provides more positive feedback, and explicitly links evaluations to manager goals. It allows participation in developing measurable outcomes. SEM is said to reduce turnover, increase motivation and performance, and boost productivity for both engineers and management.
evaluating software development team
- 2. Examine -the evaluation of team members and teams as a whole a positive experience, benefiting the company, the project and the individual. Software project manager will be interact, communicate motivate and evaluate people
- 3. The Strategy Based Evaluation Method Research on how to improve evaluation of the performance of individual software professionals has resulted to the development of a review method called the strategy based evaluation method ( SEM) Developed - peters 2002
- 4. Software professionals has currently high turnover rates This problem due to the fact that the annual or semiannual review communicates to the software engineer is low. Improving the retention rates is the use of performance review. Some of the firm conduct these performance review on an annual basis or semiannually.
- 5. Performance review solve following issues; Incentives for continued and improve performance Improve communication- it helps achieve corporate goals Professional development Improved retention rate Improved productivity
- 6. Issues SEM Strong link to corporate goals √ Ease of learning and use √ Automated support tools available √ Proven track record and effectiveness √ Broad scope of applicability √ Used in broad range of corporate environment √
- 7. Ability of the corporation to set and achieve strategic goals Vertical support throughout the organization meaning that there is commitment to this approach from top to bottom. Budget for SEM is high
- 8. High level view of SEM process
- 10. Business perspective action financial Lower cost customer 1. Faster bug correction 2. Reduce bug count internal 1. Get it right the first time. 2. assign, track, and follow up consistently Learning and growth 1. Disciplined use of the Engineering Problem Report(EPR) system 2. Integration of EPR and ECP system 3. Reward based on quality of code
- 11. characteristic traditional SEM Scope of performance evaluation Local, task oriented Corporate, group, and individual Explicit linkage to strategy no yes +ve feedback in individual’s need for self worth and importance low high Explicit linkage to managers goals infrequently always Objective evaluation of achievements ” ” Participation of all parties in developing goals and measureable outcomes low high
- 12. Reduce turnover among software professionals Increased motivation and performance among software professionals Greater productivity both software engineer and management levels within the org.