{"id":794,"date":"2017-09-10T03:49:22","date_gmt":"2017-09-10T03:49:22","guid":{"rendered":"http:\/\/sh056.global.temp.domains\/~riturajb\/technicalfundas\/?p=794"},"modified":"2019-04-06T01:14:25","modified_gmt":"2019-04-06T01:14:25","slug":"scrum-vs-waterfall-which-development-cycle-is-best-for-your-project","status":"publish","type":"post","link":"https:\/\/technicalfundas.com\/scrum-vs-waterfall-which-development-cycle-is-best-for-your-project\/","title":{"rendered":"SCRUM vs. Waterfall: Which Development Cycle is Best For Your Project?"},"content":{"rendered":"

\"Scrum<\/p>\n

With the invention of new software methodologies it becomes more challenging for companies to choose the  best methodology that best suits their project needs. For example in Web App or Mobile App Development it becomes essential to choose a a methodology that best suit the project at hand.<\/h3>\n

Waterfall Model<\/h3>\n

This is a classic life cycle model which is a linear sequential model. In the waterfall model each phase should be completed in entirety before the next phase.<\/h3>\n

This model is useful for small sized projects and having very accurate requirements.  Each phase needs to be completed to move to the next phase. The testing process is only carried out after completion of  the implementation.  The main point is that  this  model gives successful outcomes only if the requirements are certain, product defination is stable, and known technology is used.<\/h3>\n

The main advantages of the Waterfall Model are as follows:<\/h3>\n
    \n
  1. \n

    The model is simple & easy to use.<\/h3>\n<\/li>\n
  2. \n

    Due to the rigidity of the  model each phase has precise deliverables and review process.<\/h3>\n<\/li>\n
  3. \n

    Each phase is processed and completed one at a time.<\/h3>\n<\/li>\n
  4. \n

    This model works well for small projects where requirements are understood well.<\/h3>\n<\/li>\n<\/ol>\n

    The main disadvantage of  Waterfall Model are as follows<\/h3>\n
      \n
    1. \n

      Scope adjustment during the life cycle can end a project.<\/h3>\n<\/li>\n
    2. \n

      Working Software is only produced in the later phases of the life cycle.<\/h3>\n<\/li>\n
    3. \n

      Not a good model for large and complex projects.<\/h3>\n<\/li>\n
    4. \n

      Not a good model for long & ongoing  projects.<\/h3>\n<\/li>\n
    5. \n

      If the requirments are at a higher risk of changing than it is not a good model.<\/h3>\n<\/li>\n<\/ol>\n

      Scrum<\/h3>\n

      Scrum is a agile framework for effective team collaboration on relatively complex projects.  Some of the key element of scrum are<\/h3>\n
        \n
      1. \n

        Scrum is lightweight.<\/h3>\n<\/li>\n
      2. \n

        It is simple to understand.<\/h3>\n<\/li>\n
      3. \n

        It is difficult to master.<\/h3>\n<\/li>\n<\/ol>\n

        Scrum employs a heuristic approach as opposed to a programmed algorithmic approach used in the Waterfall Model. This helps to effectively solve complex problems which is not possible in the Waterfall Model.<\/h3>\n

        The Key Roles of a Scrum are as follows:<\/h3>\n
          \n
        1. \n

          Product Owner : The product owner decides what needs to be in the product and is responsible for how the product has to be.<\/h3>\n<\/li>\n
        2. \n

          Scrum Master: The scrum master will monitor the performance of the scrum within the sprint. (Sprint is a period that the team decided to deliver their part. The sprint period is normally 2-4 weeks).<\/h3>\n<\/li>\n
        3. \n

          Scrum Team : The resources are grouped as scrum teams which comprises of BA’s, developers, testers. Each team will be of size of 7-8 members.<\/h3>\n<\/li>\n<\/ol>\n

          So what are the meetings associated with Scrum ?<\/h3>\n

          1. Sprint Planning Meeting : In this meeting the team decides what they will deliver in the sprint.<\/h3>\n

          2. Daily Scrum Meeting : In the daily scrum meeting three questions are asked a) What did you do today? b) What will you do tomorrow ? c) Is there any impediments that is slowing or stopping you ?<\/h3>\n

          3. Sprint Review Meeting : This happens at the end of the sprint where team will demo the completed part to the product owner.<\/h3>\n

          4.  Sprint Retrospective Meeting: This happens at the end of the sprint where team will answer three questions a) What went well in the sprint ? b) What went bad in the sprint ? c ) Which areas can be improved in the next sprint ?<\/h3>\n

          The Key Advantages of Scrum<\/h3>\n
            \n
          1. \n

            Greater ability to incorporate changes as they occur : This is one of the major advantages of scrum. Any change that comes in the middle of the project can be implemented easily. Rather than waiting for a phase to complete, in scrum a change can be taken up in a sprint and completed .<\/h3>\n<\/li>\n
          2. \n

            Quicker release of usable product: As the team do not have the obligation to wait for the end of the implementation to release a software. The running software can be released from time to time. This helps getting good customer feedback opposed to doing in a sequential manner.<\/h3>\n<\/li>\n
          3. \n

            Increase Project Visibility: This process helps the team to get more visibility. Therefore, any impediment to the project can be found out early in the project and fixed immediately<\/h3>\n<\/li>\n
          4. \n

            More chance and greater responsibility for each team memeber:  Since team meetings are held in short durations team members have greater chances to prove. If anything needs to be improved it can be easily taken care of in the next sprint.<\/h3>\n<\/li>\n
          5. \n

            Low Cost Model : The overhead cost of using this methodology is less. Therefore,  using this model substantial cost savings can be made.<\/h3>\n<\/li>\n<\/ol>\n

            The Key Disadvantages of Scrum<\/h3>\n

            1. Scrum leads to Scope Creep as there is no definite end date.<\/h3>\n

            2. The main challenge in scrum is effective team management. If  the team members are not cooperative it becomes an impediment. If a team member leaves in the middle of the project it becomes very hard to implement scrum.<\/h3>\n

            3. Daily meetings can be frustrating at times.<\/h3>\n

            4.  Quality is hard to implement until the testing  is not done properly.<\/h3>\n

            5. Also, the project can be only completed in time only if the team members are experienced.<\/h3>\n

            Conclusion<\/h3>\n

            Thus,  it can be seen that both Waterfall model and Scrum can be used in the project development life cycle. The Waterfall model becomes expensive for big sized projects. However, for small sized projects where requirements are known Waterfall model can be used.<\/h3>\n

            Scrum Model can be used for both small & big sized projects. However, Scrum Model is most suitable in large & complex projects where change in requirements are fast. Scrum model needs a dynamic approach which may become challenging at times.<\/h3>\n

            <\/h3>\n

            <\/h3>\n","protected":false},"excerpt":{"rendered":"

            With the invention of new software methodologies it becomes more challenging for companies to choose the  best methodology that best suits their project needs. For example in Web App or Mobile App Development it becomes essential to choose a a methodology that best suit the project at hand. Waterfall Model This is a classic life … <\/p>\n

            Continue reading “SCRUM vs. Waterfall: Which Development Cycle is Best For Your Project?”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[14],"tags":[53,54,60],"yst_prominent_words":[212,213,203,189,197,199,191,211,195,186,205,1109,185,209,190,214,201,193,207,183],"class_list":["post-794","post","type-post","status-publish","format-standard","hentry","category-software","tag-scrum","tag-sdlc","tag-waterfall-model"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/posts\/794","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/comments?post=794"}],"version-history":[{"count":3,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/posts\/794\/revisions"}],"predecessor-version":[{"id":3350,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/posts\/794\/revisions\/3350"}],"wp:attachment":[{"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/media?parent=794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/categories?post=794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/tags?post=794"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/technicalfundas.com\/wp-json\/wp\/v2\/yst_prominent_words?post=794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}