| MSF for Agile Software Development | MSF for CMMI® Process Improvement |
| Concepts |
| Looks very similar between both releases at this time. |
| Cycles and Iterations |
| Aside from the acknowledgement of “Program” in the graphic for CMMI®, the two appear identical. |
| Governance |
| Summarized as: Are we doing the right thing? Can we do it within time and budget? Are we ready to integrate? Are we ready to deploy? Are we realizing the value? | Not much larger than the agile version, but definitely targeted at a more formal process. It brings the classic MSF phases and major milestones into view along with similar questions to the agile version. |
| Principles and Core Ideas |
| Summarized as: Partner with Customers Foster open communications Work toward a shared vision Quality is everyone's job every day Stay agile, adapt to change Make deployment a habit Flow of value | The same as Agile, including all of the Core Ideas listed on the left. Includes a little extra text ending with “The net result is a lightweight, agile, adaptive process for highly productive software engineering that provides a significant accelerator to achieving a CMMI® Level 3 assessment and lays the groundwork for achievement of Level 4 and 5 in future.” |
| Team Model |
| Both contain the same text laying out seven different advocacy groups: Program Management, Architecture, Product Management, Development, User Experience, Test and Release Operations. |
| Mindsets |
| Both seem to have the same mindsets, summarized as: Quality Is Defined By Customer, Pride of Workmanship, Team of Peers, Frequent Delivery, Willingness to Learn, Get Specific Early, Qualities of Service, and Citizenship. |
| Roles |
| Agile maps 6 roles to the different advocacy groups: Business Analyst, Project Manager, Architect, Developer, Tester and Release Manager. | Approximately eighteen roles are mapped to the seven advocacy groups. For example, the Product Management group contains the following roles: Business Analyst, Sponsor, SME, Auditor and Product Manager. |
| Work Item Types |
| Bug Quality of Service Requirement Scenario Risk Task | Task Change Request Risk Review Requirement Bug Issue |
| Views |
| The two seem to have identical content regarding views, Disciplines, Qualities of Service, and Cycles. The Agile process also has content on “Tracks” but it looks a lot like the MSF classic phases and the governance text provided in the CMMI® process. My guess is that the two are supposed to be nearly identical but the CMMI® release is a newer release. |
| CMMI |
| Not likely… | There is a new CMMI tab in this process guidance. It has a lot of documentation under it. The top level navigation includes: About CMMI, Process Management, Project Management, Engineering, Support, Generic Goal Level 2, Generic Goal Level 3 and All Process Areas. |
| Work Streams |
| Create Solution Architecture Capture Project Vision Create a Quality of Service Requirement Create a Scenario Build a Product Fix a Bug Implement a Development Task Guide Iteration Guide Project Plan an Iteration Release a Product Close a Bug Test a Quality of Service Requirement Test a Scenario | Analysis Create a Quality of Service Requirement Create Solution Architecture Establish Environments Build a Product Create a Scenario Create Product Requirements Manage Change Requests Fix a Bug Implement a Development Task Capture Product Vision Issue Management Plan an Iteration Plan Project Risk Management Baseline Configuration Management Establish Project Process Release a Product Close a Bug Test a Quality of Service Requirement Test a Scenario Verify a Functional Requirement Verify an Operational Requirement Develop Documentation |
| Activities |
| 68 activities, most (if not all) of which also appear in the CMMI® process guidance. | 157 activities defined including such classics as “Assess Alternatives (LAAAM)”, “Form Iteration Team(s)”, “IPMO Iteration Review” and “Populate Organization Process Asset Library”. |
| Work Products |
| 24 documented work products. Several of them are duplicated in the CMMI® process guidance. | 50 documented work products from “Application Connection Diagram” to “Web Test”. |
| Reports |
| Remaining Work Velocity Unplanned Work Quality Indicators Bug Rates Reactivations Bugs by Priority Actual Quality versus Planned Velocity | Remaining Work Velocity Unplanned Work Quality Indicators Bug Rates Reactivations Bugs by Priority Actual Quality versus Planned Velocity Open Issues and Blocked Work Items Trend Test History Customer Requirements Test History Product Requirements Test History Triage Inconsistencies Report Tasks Linked to Risks Status and Drill Down Test Failures |
| Queries |
| All Quality of Service Requirements
Active Bugs
All My Team Project Work Items
All Scenarios
All Work Items
My Work Items
Project Checklist
Resolved Bugs
All Tasks | Active Bugs All My Team Project Work Items All Tasks All Work Items (by Iteration) Summary and Drill Down Blocked Work Items (by Iteration) Summary and Drill Down Change Requests (by Iteration) Summary and Drill Down Corrective Actions (by Iteration) Summary and Drill Down Customer Requirements (by Iteration) Summary and Drill Down Development Tasks (by Iteration) Status and Drill Down Issue (by Iteration) Summary and Drill Down Mitigation Action Status My Work Items Product Requirements (by Iteration) Status and Drill Down Project Checklist Resolved Bugs Review (by Iteration) Summary and Drill Down Risks (by Iteration) Summary and Drill Down Tasks (by Iteration) Summary and Drill Down Test Tasks (by Iteration) Status and Drill Down |
| How To’s |
| “How To’s” appear to be identical in both documents. |
| Zip File size |
| 8 MB | 10MB |
| Download Link |
| http://www.microsoft.com/downloads/thankyou.aspx?familyId=9F3EA426-C2B2-4264-BA0F-35A021D85234&displayLang=en | http://www.microsoft.com/downloads/details.aspx?FamilyId=10B578F1-B7A4-459F-A783-04BC82CB2359&displaylang=en |