Agile versus CMMI - process template selection and integration with microsoft team foundation server
Proceedings of the 46th Annual Southeast Regional Conference on XX
Climbing the ladder: CMMI level 3
EDOC'09 Proceedings of the 13th IEEE international conference on Enterprise Distributed Object Computing
Measuring and comparing the adoption of software process practices in the software product industry
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Reconciling software development models: A quasi-systematic review
Journal of Systems and Software
A scrum-based approach to CMMI maturity level 2 in web development environments
Proceedings of the 14th International Conference on Information Integration and Web-based Applications & Services
Hi-index | 0.00 |
Agile practitioners pride themselves on highly productive, responsive, low ceremony, lightweight, tacit knowledge processes with little waste, adaptive planning and frequent iterative delivery of value. It is often assumed that CMMI compliant processes need to be heavyweight, bureaucratic, slow moving, high ceremony and plan driven. Agile developers often skeptically perceive formal process improvement initiatives as management generated inefficiency that gets in the way of productivity. At Microsoft, we've adopted the teachings of W. Edwards Deming and stretched our MSF for Agile Software Development method to fit the requirements for CMMI Level 3. The resultant MSF for CMMI Process Improvement is a highly iterative, adaptive planning method, light on documentation, and heavily automated through tooling. It enables management and organization of software engineering through use of agile metrics such as velocity and cumulative flow but with an added dimension of an understanding of variation - adapted from Deming's teachings. This is the story of how mixing Deming with Agile produced a lightweight CMMI solution for .Net developers everywhere.