1.
A Comparative Study: Rational Unified Process , Agile with Microsoft Solution Framework Submitted By: Shailesh Bohra MBA-SDM(2007-09) 07030244022 Symbiosis Centre For IT

2.
Background of RUP <ul><li>The RUP is &quot;use-case driven, architecture-centric, and incremental and iterative&quot;. Each iteration is part of four overall 'phases': Inception, Elaboration, Construction, and Transition. Iterations occur in each phase. Activities in iterations are focused on one of the four activities: gathering requirements, analyzing, designing, implementing, and testing. </li></ul><ul><li>RUP comes with six engineering disciplines & three supporting discipline. </li></ul>

3.
Continued : <ul><li>Six Engineering Discipline: </li></ul><ul><ul><li>Business modeling discipline </li></ul></ul><ul><ul><li>Requirements discipline </li></ul></ul><ul><ul><li>Analysis and design discipline </li></ul></ul><ul><ul><li>Implementation discipline </li></ul></ul><ul><ul><li>Test discipline </li></ul></ul><ul><ul><li>Deployment discipline </li></ul></ul><ul><li>Three Supporting Discipline: </li></ul><ul><ul><li>Configuration & Change Management Discipline. </li></ul></ul><ul><ul><li>Project Management </li></ul></ul><ul><ul><li>Environment Discipline </li></ul></ul>

4.
Background of Agile <ul><li>Agile methodologies generally promote a project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. </li></ul><ul><li>The Agile Manifesto, widely regarded as the canonical definition of agile development and accompanying agile principles. The Agile Manifesto states: </li></ul><ul><ul><li>Individuals and interactions over processes and tools </li></ul></ul><ul><ul><li>Working software over comprehensive documentation </li></ul></ul><ul><ul><li>Customer collaboration over contract negotiation </li></ul></ul><ul><ul><li>Responding to change over following a plan </li></ul></ul>

5.
Continued: <ul><li>Some of the principles behind the Agile Manifesto are: </li></ul><ul><li>Customer satisfaction by rapid, continuous delivery of useful software </li></ul><ul><li>Working software is delivered frequently (weeks rather than months) </li></ul><ul><li>Working software is the principal measure of progress </li></ul><ul><li>Even late changes in requirements are welcomed </li></ul><ul><li>Close, daily cooperation between business people and developers </li></ul><ul><li>Face-to-face conversation is the best form of communication (Co-location) </li></ul><ul><li>Projects are built around motivated individuals, who should be trusted </li></ul><ul><li>Continuous attention to technical excellence and good design </li></ul><ul><li>Simplicity </li></ul><ul><li>Self-organizing teams </li></ul><ul><li>Regular adaptation to changing circumstances </li></ul>

6.
Background of Microsoft Solution Framework <ul><li>Microsoft Solutions Framework (MSF) is a set of principles, models, disciplines, concepts, and guidelines for successfully delivering information technology solutions from Microsoft. MSF is not limited to developing applications only, it is also applicable to other IT projects like deployment, networking or infrastructure projects. MSF does not force the developer to use a specific methodology (Waterfall, Agile) but lets them decide what methodology to use. </li></ul><ul><li>The MSF 4.0 released in 2005 included two derivative methodologies which are: </li></ul><ul><ul><li>Microsoft Solutions Framework for Agile Software Development (MSF4ASD) </li></ul></ul><ul><ul><li>Microsoft Solutions Framework for Capability Maturity Model Integration Process Improvement (MSF4CMMI) </li></ul></ul>

7.
MSF Tracks <ul><li>Envision </li></ul><ul><li>Plan </li></ul><ul><li>Build </li></ul><ul><li>Stabilize </li></ul><ul><li>Deploy </li></ul><ul><li>Continuous </li></ul>

8.
What is RUP & Agile ? <ul><li>RUP is a configurable software development process that is based on many years of experience in using object technology to develop mission critical software in a variety of industries. </li></ul><ul><li>Agile methodology defines a system of methods designed to minimize the cost of change, especially in a context where important facts emerge late in a project, or where we are obliged to adapt to important uncontrolled factors. </li></ul>

9.
What is MSF? <ul><li>Microsoft Solutions Framework (MSF) is a set of software engineering processes, principles, and proven practices that enable developers to achieve success in the software development life cycle (SDLC). MSF provides an adaptable guidance, based upon experiences and best practices from inside and outside of Microsoft, to increase the chance of successful deliverance of information technology solution to the customer by working fast, decreasing the number of people on the project team, averting risk, while enabling high quality results. </li></ul><ul><li>MSF 4.0 provides a higher-level framework of guidance and principles which can be mapped to a variety of prescriptive process templates. It is structured in both descriptive and prescriptive methodologies. The descriptive component is called the MSF 4.0 metamodel, which is a theoretical description of the SDLC best practices for creating SDLC methodologies. </li></ul>

10.
MSF 4.0 Structure

11.
MSF TEAM MODEL

12.
MSF for Agile Software Development methodology <ul><li>Scenario & Context driven to determine how to operate the project. </li></ul><ul><li>It is composed of tracks, advocacy groups and cycles. </li></ul><ul><li>The non-functional and functional requirements of the system are expressed in scenarios and quality of service requirements (QSR). </li></ul><ul><li>The tracks represent the process in time, the advocacy groups represent the process in work activities. The cycles describe the frequency with which activities, within the tracks and advocacy groups, are performed or work products produced and updated to turn the project cycle </li></ul>

13.
RUP Practitioners <ul><li>RUP Practitioners are: </li></ul><ul><ul><li>document-centric </li></ul></ul><ul><ul><li>perfectionists (with perfect artifacts) </li></ul></ul><ul><ul><li>Cautious ( Can’t afford even a single mistake) </li></ul></ul><ul><ul><li>independent (with well defined interfaces) </li></ul></ul>

14.
Agile Practitioners <ul><li>Agile Practitioners are: </li></ul><ul><ul><li>Customer focused </li></ul></ul><ul><ul><li>Real (No guesses) </li></ul></ul><ul><ul><li>Intuitive ( Rely on experience) </li></ul></ul><ul><ul><li>Communicators </li></ul></ul>

15.
Iterative <ul><li>Although UP is iterative, it follows the general phases of inception, elaboration, construction, and transition in a more or less linear fashion. As the development proceeds less time is spent on requirements and analysis, and more time is spent on construction, testing, and transition. </li></ul><ul><li>Agile processes on the other hand, spend time on each activity in each iteration. During each iteration (usually 2-4 weeks) a little of all steps (requirements, analysis, design, development, test, etc.) are undertaken. The goal is to have stable software which could be shipped at the end of each iteration. </li></ul>

16.
Flexibility V/S Team Size <ul><li>Rational Unified Process (RUP) are quire comprehensive, and were designed to be modified to suit the project being developed. This adds another layer of complexity to the development effort, as the process has first to be modified before being implemented. While this allows for the flexibility to use UP on any project, it requires teams to have access to UP experts to ensure that the process is being defined and used properly. </li></ul><ul><li>Agile on the other hand tends to be used for small to medium sized projects involving teams up to 10 closely knit developers. Once teams become bigger than this, agile methodologies begin to fail, as they don’t scale to large teams, or teams spread across geographies. </li></ul>

17.
RUP Best Practices <ul><li>Develop software iteratively. </li></ul><ul><li>Manage requirements. </li></ul><ul><li>Use component-based architectures. </li></ul><ul><li>Visually model software. </li></ul><ul><li>Continuously verify software quality. </li></ul><ul><li>Control changes to software . </li></ul>

18.
MSF Foundation Principle <ul><li>Foster open communications </li></ul><ul><li>Work toward a shared vision </li></ul><ul><li>Quality is everyone's job every day </li></ul><ul><li>Stay agile, adapt to change </li></ul><ul><li>Make deployment a habit </li></ul><ul><li>Flow of value </li></ul><ul><li>Partner with customers </li></ul>

19.
References: <ul><li>http://ccollins.wordpress.com/2008/06/11/unified-process-vs-agile-processes/ </li></ul><ul><li>http://en.wikipedia.org/wiki/Agile_software_development </li></ul><ul><li>http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process </li></ul><ul><li>https://www.samrantech.com/methodologies-comparison-between-agile-and-rup-2.html </li></ul><ul><li>http://www.esnips.com/doc/7bbb8479-94df-4d5a-8a61-c432707050c1/Traa,-J.W.A.---RUP-vs.-MSF---A-Comparative-Study.pdf ( A nice book.. Must go through i t ) </li></ul><ul><li>http://en.wikipedia.org/wiki/Microsoft_Solutions_Framework </li></ul>

20.
THE END <ul><ul><ul><ul><ul><li>THANK YOU ! </li></ul></ul></ul></ul></ul>