CMMI | CMMI Compatibility | CMMI and Agile
This information has moved to www.cmmiinstitute.com. As part of its mission to transition mature technology to the software community, the SEI has transferred CMMI-related products and activities to the CMMI Institute, a 100%-controlled subsidiary of Carnegie Innovations, Carnegie Mellon University’s technology commercialization enterprise. The CMMI Institute will conduct CMMI training and certification, sponsor conferences and classes, and provide information about CMMI process improvement models and appraisals. The SEI will continue to pioneer and advance new research in the field of software process management.
People Capability Maturity Model
The People Capability Maturity Model (short names:People CMM, PCMM,P-CMM) is a maturity framework that focuses on continuously improving the management and development of the human assets of an organization. It describes an evolutionary improvement path from ad hoc, inconsistently performed practices, to a mature, disciplined, and continuously improving development of the knowledge, skills, and motivation of the workforce that enhances strategic business performance. The People Capability Maturity Model (People CMMI) is a framework that helps organizations successfully address their critical people issues. Characterize the maturity of their workforce practicesSet priorities for immediate actionIntegrate workforce development with process improvementBecome an employer of choice Description[edit] The People CMM has been published in book form in numerous editions around the world.[2] Structure[edit] People Capability Maturity Model See also[edit] References[edit] External links[edit]
Agile and CMMI: Better Together
Organizations follow many paths in their pursuit of excellence, applying various principles, methods, and techniques along the way. It stands to reason, then, that an organization interested in adopting agile practices might also be interested in PMI’s OPM3, ISO or Capability Maturity Model® Integration (CMMI) as a means to achieve that excellence. While I have seen some organizations that are trying to implement agile and a PMI model at the same time, none are doing it successfully. Last year, in fact, I observed two very large companies that had simultaneous internal initiatives to utilize agile and CMMI. Many believe that agile and CMMI are polar opposites and sub-optimize each other’s efforts. CMMI Refresher Capability Maturity Model® Integration (CMMI)1 is a process improvement approach that provides organizations with the essential elements of effective processes. To the new generation of agile practitioners, CMMI may seem bloated, dull and unimaginative. Agile Sweet Spot 1. 2. 3.
Organization Performance CMM
Scrum (development)
Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.
untitled
Scrum's Product Backlog - Agile Requirements Management
The Product Backlog: What should we make? One of the first things assembled when we embark on a new project is a list of things to do. Everyone loves a list! Projects often start as a to-do list, jotted down on a piece of paper. For small pieces of work, this may be all you need. In this article, I’ll describe techniques for collecting requests relating to your product and helpful practices for managing that list of requests. Before you start Do you know what you are doing? Delivery teams are created to help a business realize a part of its vision. But why? In order for the delivery team to complete a piece of work, many small decisions have to be made to solve the problems encountered along the way. Fortunately, Scrum provides an incredibly effective way to manage the requests of our enthusiastic collaborators when building a software product – the product backlog. What is a Product Backlog? The product backlog is used to: capture requests for modifying a product. Product Backlog Items Notes
untitled
Story Points: Why are they better than hours?
Traditional Estimation Funnel Microsoft Story Point accuracy Story points give more accurate estimates, they drastically reduce planning time, they more accurately predict release dates, and they help teams improve performance. Hours give worse estimates, introduce large amounts of waste into the system, handicap the Product Owner's release planning, and confuse the team about what process improvements really worked. Interesting new research has become available. Scrum + Engineering Practices: Experiences of Three Microsoft TeamsLaurie Williams, Gabe Brown, Adam Meltzer, Nachiappan NagappanIEEE Best Industry Paper award winnerMany people who have managed projects with hours have a hard time understanding why story points are better. First, let's look at the latest data on project failures. In fact the latest Forrester Group research shows that:Common Project Management Metrics Doom IT Departments to Failure The stability of a user story is critical for planning.
untitled
