1. Right-Sizing the SW Development Process Altaf Khan

2. software development process ?

3. Good process and continually improving process are admirable goals

4. They are also very natural goals: Good technical workers will focus on them whether your tell’em to or not !

5. software process standards ?

6. the trouble with CMM...

7. the trouble with model-based process improvement...

8. how do we know if the model is correct ? (because the author says so!)

9. how do we know if the model is applicable to all sorts of projects and organizations ? (because the author says so!)

10. they give no guarantees

11. false sense of security

12. creativity stifling atmosphere

13. don’t get me wrong standards are good

14. standardize the interface

15. What is the alternative to model-based process improvement ?

16. achtung!

17. ! CMM issues CMM philosophy

18. Are there any fruitful alternatives to model- based process improvement ?

19. here is one alternative...

20. Define the (business) objective of the process improvement effort

21. example: I wanna finish my projects on time, within budget, and with known quality

22. WARNING! One should not expect too great a benefit for the current project, but should look for longer- term improvements

23. Process Improvement Recipe Define “your” current SW development lifecycle Identify the main bottleneck Look for a remedy for removing the bottleneck Remove that bottleneck Identify the next one; find remedy; remove … …

24. K E Y M E S S A G E solve process problems one at a time

25. how do I identify problems ?

26. measure your process !

27. measurements help in the identification of problems ! measurements help in determining the effectiveness of remedies !

28. Anything that you need to quantify can be measured in some way that is superior to not measuring at all ! Tom Gilb

29. A few meaningful, but simple -to-implement measures

30. Time 1 2 3 4 5 6 7 8 9 Sorted Milestones Actual progress Planned Milestone 8 was planned to be achieved on the 91st day Milestone 8 was was actually achieved on the 100th day

31. Defects Time Total reported defects Defects yet to be fixed Defects fixed to date

32. Defects Test cases Upper limit Lower limit Actual defects

33. Defect Ripple 1 2 3 4 5 6 7 8 9 Defect Fixed 4 - 3 - 2 - 1 - 0 - Three new defects appeared as a consequence of fixing defect 5

34. Not - A - Defect Time 4 - 3 - 2 - 1 - 0 -

35. measure meaningful the measure should be as simple as possible, but meaningful

36. the (perpetual) process improvement cycle

37. Identify problem Keep measuring Find remedy Pilot remedy Propagate Learn from pilot Identify problem Keep measuring Find remedy Pilot remedy Propagate Learn from pilot

38. 3 main messages

39. Essential Processes Project planning & tracking Requirements management Configuration management Defects tracking

40. motivate the team about the benefits before implementing the process involve the team in the design of the process

41. Don’t make more than a single change during the lifecycles of individual projects otherwise you’ll impede the progress of the project significantly