Team System and Microsoft Solutions Framework
Team collaboration toolsProcess authoringProcess GuidanceMSF-Agile & MSF-CMMISoftware FactoriesFuture developments
Cycles for Application Development
Cycles describe the frequency with which activities are performed or work products produced and updated
Cycles are about the execution of the project and its tasks
MSF-Agile vs. MSF-CMMI
MSF for CMMI Process Improvement
Approvals
Change Requests
Formal Reviews
Process Improvement Activities
Requirements Analysis
MSF for Agile Software Development
Iteration Planning
Shadow Architecture
Functional/Exploratory Testing
Test Driven Development
Context-Driven Test
When to use each methodology
• Choose MSF for CMMI Process Improvement over MSF for Agile Software Development, if – Your project has a longer life cycle and requires
a record of decisions made– Your organization is undertaking a broad quality
assurance and process improvement initiative – Your team needs the assistance of explicit
process guidance rather than relying on tacit knowledge and experience
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
Kent Beck James Grenning Robert C. Martin
Mike Beedle Jim Highsmith Steve Mellor
Arie van Bennekum Andrew Hunt Ken Schwaber
Alistair Cockburn Ron Jeffries Jeff Sutherland
Ward Cunningham Jon Kern Dave Thomas
Martin Fowler Brian Marick
© 2001, the above authors
this declaration may be freely copied in any form,
but only in its entirety through this notice.
http://www.agilemanifesto.org
Team System and Microsoft Solutions Framework
Team collaboration toolsProcess authoringProcess GuidanceMSF-Agile & MSF-CMMISoftware FactoriesFuture developments
Software Factory
• All the kit you need for working within a particular development context– E.g. telecoms, financial; web services, databases
Initial solution and project structure and content
Domain Specific Languages
For example:
Miscellaneous tools
Recipes (= context-specific tools in VS)
Add ServiceRun on server
Add ServiceRun on server
Team Software Factory
• All the kit you need for working within a particular development context– Including process support
Miscellaneous tools
Initial solution and project structure and content
Domain Specific Languages
Recipes (= context-specific tools in VS)
Add ServiceRun on server
Add ServiceRun on server
Team Foundation Server
Miscellaneous tools
Initial solution and project structure and content
Domain Specific Languages
Recipes (= context-specific tools in VS)
Add ServiceRun on server
Add ServiceRun on server
Process Templatefor this domain
Process Components
Current – big blocks:
Future – composable components:
MSF-Agile MSF-CMMI SCRUM
Agile Bug
tracking
Issue Tracking
XP Tasks
ChangeRequesttracking
Select EUP
XP Tasks
Agile Bug
tracking
Strict Checkin
rules
Burndown reportsIssue
Tracking
Process Development Model
• Process users author the Process Template as experience is gained
ProcessTemplate
Guidance in all forms
Pass to next projectsReuse it ourselves
Create with experience
Guru helps generalize
Stiffening
• Process gets less malleable as time goes on
Guidance in all forms
Pass to next projectsReuse it ourselvesCreate with experience
Review,triage
Project 1 Project 2 Project n…
Mature factory
• Well-developed process can be passed around
Process template
Coaching
From development
Software Factory = packaged tools for a purpose
• Published factories may come with process support included
• Or use combinations of publised factories
• You can author factories– Including authoring guidance while in use
Top Related