1 / 41

Right-Sizing the SW Development Process Altaf Khan

Right-Sizing the SW Development Process Altaf Khan. software development process. ?. Good process and continually improving process are admirable goals. They are also very natural goals: Good technical workers will focus on them whether your tell’em to or not !. software process standards ?.

yannis
Download Presentation

Right-Sizing the SW Development Process Altaf Khan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Right-Sizingthe SW Development ProcessAltaf 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 wrongstandards are good

  14. standardize the interface

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

  16. achtung!

  17. CMM issuesCMM 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 Esolve process problems one at a time

  25. how do I identify problems?

  26. measureyour process!

  27. measurementshelp in the identification of problems! measurementshelp 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 fewmeaningful,butsimple-to-implementmeasures

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

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

  32. Defects Upper limit Actualdefects Lower limit Test cases

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

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

  35. the measureshould beas simple as possible,but meaningful

  36. the (perpetual) process improvement cycle

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

  38. 3 main messages

  39. Essential ProcessesProject planning & trackingRequirements managementConfiguration managementDefects tracking

  40. motivatethe team about the benefits before implementing the processinvolve the team in the design of the process

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

More Related