Comparison Of Rup & Agile Method (Xp) For Projects

19,564 views
19,044 views

Published on

This slides I prepared for making my first screencast on the topic : Comparison of RUP & Agile method (XP) for Projects.

Published in: Education
2 Comments
13 Likes
Statistics
Notes
No Downloads
Views
Total views
19,564
On SlideShare
0
From Embeds
0
Number of Embeds
148
Actions
Shares
0
Downloads
818
Comments
2
Likes
13
Embeds 0
No embeds

No notes for slide
  • Topic is: Comparison of RUP & Agile method (XP) for Projects(for small & Medium Projects)
  • Comparison Of Rup & Agile Method (Xp) For Projects

    1. 1. Prepared by: Mahesh Panchal MBA-Software Development &Management Symbiosis(SCIT) : 07-09
    2. 2. <ul><li>Overview of RUP </li></ul><ul><li>Overview of XP </li></ul><ul><li>Comparative study </li></ul><ul><li>conclusion </li></ul>
    3. 3. <ul><li>RUP is a popular off-the-shelf process based on the idea of highly iterative development </li></ul><ul><ul><li>One thing that makes RUP unique is that it is a product in addition to a process. </li></ul></ul><ul><li>RUP includes a disciplined approach to requirements management that is based on the idea of managing changes. </li></ul><ul><ul><li>RUP incorporates software design using the Unified Modeling Language (UML), a visual modeling system for graphically representing the use cases, class model, object interactions, and components of the software. </li></ul></ul><ul><li>One core element of RUP is the continuous assessment of the quality of the system. </li></ul>
    4. 4. <ul><li>XP consists of a set of rules and practices that govern all areas of software development: planning, designing, coding, and testing. </li></ul><ul><ul><li>The goal of XP is to lower the cost of change. To meet this goal, many XP practices are highly iterative. </li></ul></ul><ul><ul><li>XP is a disciplined and well-defined process. </li></ul></ul><ul><ul><li>By making the stakeholders part of the project team, XP addresses the problem of the hands-off customer. </li></ul></ul>
    5. 5. <ul><li>Characteristics </li></ul><ul><li>Evolutionary development </li></ul><ul><li>Collection of 12 „Best Practices“ </li></ul><ul><li>Focus on working code that implements customer needs (rather than documents) </li></ul><ul><li>Testing is a crucial element of the process </li></ul><ul><li>Focus on flexibility and efficiency of the process </li></ul><ul><li>Designed for </li></ul><ul><li>small teams (<10) </li></ul>Write tests Planning Test Pair Programming + Refactoring Integration Min. daily Every 2-3 weeks Release
    6. 6. Document driven Elaborate workflow definitions Many different roles Many checkpoints High management overhead Highly bureaucratic Focus on working code rather than documentation Focus on direct communication (between developers and between developers and the customer) Low management overhead Heavyweight e.g., V-Process Customizable Framework e.g., Rational Unified Process (RUP) Agile (Lightweight) e.g., eXtreme Programming (XP)
    7. 11. <ul><li>RUP </li></ul><ul><ul><li>highly formal and structured </li></ul></ul><ul><ul><li>providing out-of-the-box roadmaps for a number of project types </li></ul></ul><ul><ul><li>does not say anything about how to actually run a project </li></ul></ul><ul><li>XP </li></ul><ul><ul><li>devoted to everyday life and low-level management of the development team </li></ul></ul><ul><ul><li>does not insist on documentation </li></ul></ul><ul><ul><li>does not provide project templates </li></ul></ul><ul><ul><li>people oriented methodology, relying on human intelligence </li></ul></ul>
    8. 12. <ul><li>XP is suitable, if both of the following conditions are true: </li></ul><ul><ul><li>You have a small team (2-12) </li></ul></ul><ul><ul><li>Requirements are vague (users don’t know yet what they want) </li></ul></ul><ul><li>RUP is suitable if one of the previous conditions are false. </li></ul><ul><li>When using XP with large teams, the general (unspoken) idea that everyone needs to know everyone else's code details, becomes hard to defend, especially when requirements/specifications are clear. </li></ul>
    9. 13. <ul><li>Thank you for patient listening. </li></ul>[email_address]

    ×