{"id":9300,"date":"2025-03-30T01:02:03","date_gmt":"2025-03-30T01:02:03","guid":{"rendered":"https:\/\/murshedul.com\/?p=9300"},"modified":"2025-12-27T01:34:32","modified_gmt":"2025-12-26T16:34:32","slug":"how-to-choose-a-perfect-sdlc-waterfall-agile-kanban-and-scrum","status":"publish","type":"post","link":"https:\/\/murshed.jp\/?p=9300&lang=en","title":{"rendered":"How to choose a perfect SDLC (Waterfall, Agile, Kanban and Scrum)"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What is the waterfall?<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The\u00a0waterfall model\u00a0divides each project into different phases and moves through the phases in sequential order. No phase can begin until the phase before it is completed.<\/span><\/p>

The specific phases of the waterfall process typically look similar to this:<\/span><\/p>

        1. The Requirements<\/strong> phase, sometimes split into an additional analysis phase<\/span><\/li>
        2. The System design<\/strong> phase<\/span><\/li>
        3. Implementation<\/strong> phase, also known as the development phase or coding phase\u2014depending on the type of project<\/span><\/li>
        4. Testing<\/strong> phase<\/span><\/li>
        5. The Deployment<\/strong> phase, also known as the operations phase<\/span><\/li>
        6. The Maintenance<\/strong> phase<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
          \n\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t

          How the waterfall works<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          \"\"The phases of the projects look like they\u2019re cascading from one\u00a0phase\u00a0to the next.<\/span><\/p>

          Implementing this project management methodology requires a lot of up-front planning and preparation.<\/span><\/p>

          And the major part of this methodology is creating an airtight project plan so your team clearly understands the project requirements and restraints before they get started on the work.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

          \n\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t
          \n\t
          \n\t\t\t\t\t\n\t\t\t<\/i>\t\t\t<\/span>\n\t\t\n\t\t
          \n\t\t\t\n\t\t\t
          \n\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t

          This project methodology is great for\u00a0time management\u00a0and progress tracking, though it\u2019s less flexible than other models.<\/p>\n\t\t\t\t\n\t\t\t\t

          \n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
          \n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Pros of waterfall<\/span><\/h4>

          Waterfall project management is more effective for cross-functional projects. Some of the biggest advantages of the waterfall methodology are that you can\u2026<\/span><\/p>

              1. Plan projects ahead of time to prevent scope creep.<\/span><\/li>
              2. Track progress easily between different phases of the project.<\/span><\/li>
              3. Work on multiple projects without being completely dedicated to one initiative.<\/span><\/li>
              4. Manage dependencies with ease.<\/span><\/li>
              5. Maintenance is more easy.\u00a0<\/li><\/ol><\/li><\/ol><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t

                Cons of waterfall<\/span><\/h4>

                However, the waterfall methodology also comes with a few disadvantages that are important to note (according to the real project life cycle experiences):<\/span><\/p>

                    1. Can lead to increased project risk due to lack of flexibility.<\/span><\/li>
                    2. Can lead to loss of information if different people work on the project during different phases and don\u2019t document clearly.<\/span><\/li>
                    3. Can lead to unexpected bugs when QAs happen late.<\/span><\/li>
                    4. Can cause decreased customer satisfaction without their involvement.<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                      \n\t\t\t\t\t
                      \n\t\t\t\t
                      \n\t\t\t\t
                      \n\t\t\t\t\t

                      What is Agile?<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                      \n\t\t\t\t\t
                      \n\t\t\t\t
                      \n\t\t\t\t
                      \n\t\t\t\t\t\t\t\t\t

                      Agile project management\u00a0is an iterative methodology where work is completed in short sprints. By prioritizing a flexible approach and continuous delivery, the Agile method is more flexible when it comes to unexpected project changes\u2014however, it can suffer from\u00a0scope creep\u00a0as a result.<\/span><\/p>

                      How Agile works<\/span><\/h3>

                      Agile project management includes iterative backlog management, sprints, reflection, iteration, and more sprints. Each Agile sprint typically lasts two to four weeks.<\/span><\/p>

                      \"\"<\/p>

                      Each sprint goes through the following phases:<\/span><\/p>

                          1. First, the product owner organizes the product backlog. The product backlog is a list of every task that may be worked on during the sprint. This information is usually stored in a project management tool.<\/span><\/li>
                          2. Before the sprint, the entire project team participates in sprint planning to identify the best tasks to work on during the two-week period.<\/span><\/li>
                          3. During the sprint, Agile teams meet frequently to discuss blockers and action items. <\/span><\/li>
                          4. Once the sprint is over, team members get together to run a sprint retrospective and identify what went well and what could have been better. <\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                            \n\t\t\t\t
                            \n\t\t\t\t
                            \n\t\t\t\t\t\t\t\t\t

                            Pros of Agile<\/span><\/h4>\nThe Agile methodology is popular for a reason\u2014here are some of the biggest advantages for Agile teams. They\u2026<\/span>\n
                              \n \t
                            • \n
                                \n \t
                              • \n
                                  \n \t
                                • Adapt quickly to unexpected changes<\/span><\/li>\n \t
                                • Focus on customer satisfaction<\/span><\/li>\n \t
                                • Experience high intrinsic motivation by emphasizing teamwork and team member involvement<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
                                  \n\t\t\t\t
                                  \n\t\t\t\t\t\t\t\t\t

                                  Cons of Agile<\/span><\/h4>\nWith all of that flexibility come a few disadvantages Agile teams have to face:<\/span>\n
                                    \n \t
                                  • \n
                                      \n \t
                                    • \n
                                        \n \t
                                      • Can increase scope creep and\u00a0project budget\u00a0unexpectedly<\/span><\/li>\n \t
                                      • Can be difficult to engage with customers if they don\u2019t have the time or bandwidth<\/span><\/li>\n \t
                                      • Focusing exclusively on the Agile sprint process doesn\u2019t allow team members to work on other initiatives<\/span><\/li>\n \t
                                      • Can be difficult for\u00a0virtual teams\u00a0to thrive in Agile environments<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                        \n\t\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t\t

                                        What is Kanban?<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                        \n\t\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t\t\t\t\t\t

                                        Kanban is a subsect of the Agile methodology and functions within the broader Agile mentality. The Agile philosophy is all about adaptive planning, early delivery, and continuous improvement\u2014all of which Kanban can support.<\/span><\/p>

                                        When speaking of Kanban in project management, most commonly refer to Kanban boards. A Kanban board represents stages of work with columns that hold the individual tasks for each stage\u2014but more on that in a li’l bit.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                                        \n\t\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t\t

                                        How Kanban works<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                        \n\t\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t
                                        \n\t\t\t\t\t\t\t\t\t\"\"Benefits of Kanban boards<\/strong><\/span>\n
                                          \n \t
                                        1. \n
                                            \n \t
                                          1. \n
                                              \n \t
                                            1. Tasks or deliverables<\/strong><\/span><\/li>\n \t
                                            2. Task assignee<\/strong><\/span><\/li>\n \t
                                            3. Due dates<\/strong><\/span><\/li>\n \t
                                            4. Task details<\/strong><\/span><\/li>\n \t
                                            5. Context<\/strong><\/span><\/li>\n \t
                                            6. Relevant files<\/strong><\/span><\/li>\n \t
                                            7. Relevant tags, <\/strong>like priority <\/strong>or task type<\/strong><\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

                                              The modern Kanban framework is an online, visual method to manage work.\u00a0Typically these stages are \u2018to do\u2019<\/strong>, \u2018in progress\u2019 and \u2018done\u2019<\/strong>.<\/span><\/p>\n

                                              Kanban boards are one of the most popular forms of visual project management. They\u2019re most effective for providing easy, at-a-glance insight into a project.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t

                                              What is Scrum?<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t\t\t\t\t

                                              Scrum is an Agile Project Management Framework that helps team structure and manage their work through a set of values, principles, particles, guidelines and roles to help a team focus on continuous improvement and iteration.<\/span><\/p>

                                              It\u2019s much less flexible than Kanban but a great way for Agile teams to collaborate and get high-impact work done.<\/span><\/p>

                                              How Scrum works<\/span><\/h3>

                                              \"\"<\/p>

                                              While Scrum, like Agile, was originally created for software development teams, industries like product, engineering, and others now run Scrum to execute their work faster and more effectively.<\/span><\/p>

                                              To run a Scrum, teams typically assign a\u00a0Scrum master, who is in charge of running the three distinct Scrum phases and keeping everyone on track. The Scrum master can be your team lead, project manager, product owner, or the person most interested in running Scrum.<\/span><\/p>

                                              The Scrum master is responsible for implementing the three traditional Scrum phases:<\/span><\/p>

                                              Phase 1:\u00a0Sprint planning.<\/strong><\/span> A Scrum sprint is usually two weeks long, though teams can run faster or shorter sprints. During the sprint planning phase, the Scrum master and team take a look at the team\u2019s\u00a0product backlog\u00a0and select work to accomplish during the sprint.<\/span><\/p>

                                              Phase 2:\u00a0Daily Scrum standups.<\/strong><\/span> Over the course of the Scrum teams traditionally meet for 15 minutes every day to check in on progress and make sure the amount of assigned work is appropriate.<\/span><\/p>

                                              Phase 3:\u00a0Sprint retrospective. <\/strong><\/span>When the Scrum is over, the Scrum master hosts a sprint retrospective meeting to evaluate what work was done, route any unfinished work back into the backlog, and prepare for the next sprint.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t
                                              \n\t
                                              \n\t\t\t\t\t\n\t\t\t<\/i>\t\t\t<\/span>\n\t\t\n\t\t
                                              \n\t\t\t\n\t\t\t
                                              \n\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t

                                              The goal of Scrum isn\u2019t to build something in two weeks, ship it, and never see it again. Rather, Scrum embraces a mindset of \u201ccontinuous improvement,\u201d where teams take small steps towards bigger goals. By breaking work into smaller chunks and working on those chunks, Scrum helps teams better prioritize and ship work more efficiently.<\/p>\n\t\t\t\t\n\t\t\t\t

                                              \n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t\t\t
                                              \n\t\t\t
                                              <\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t
                                              \n\t
                                              \n\t\t
                                              <\/div>\n\t\t\t\n\t\t<\/path><\/svg>\t<\/span>\n\t\t\t
                                              <\/div>\n\t<\/div>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t\t\t
                                              \n\t\t\t
                                              <\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t

                                              How to choose the right project methodology<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                              \n\t\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t
                                              \n\t\t\t\t\t\t\t\t\t

                                              When to use the Waterfall methodology<\/strong><\/span><\/p>

                                              Use the waterfall methodology if\u2026<\/span><\/p>

                                                  1. You\u2019re working on a sequential project and no phase can begin unless the other is complete.<\/span><\/li>
                                                  2. You want to tightly control scope creep.<\/span><\/li>
                                                  3. You value clear, effective planning.<\/span><\/li>
                                                  4. You want to understand the entire development lifecycle before beginning the project.<\/span><\/li>
                                                  5. You value functionality over quick delivery.<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>

                                                    When to use the Agile methodology<\/strong><\/span><\/p>

                                                    Try the Agile approach when\u2026<\/span><\/p>

                                                        1. You want to use a more iterative process.<\/span><\/li>
                                                        2. You want to deliver results quickly\u2014even if that means improving them later on.<\/span><\/li>
                                                        3. Your team moves quickly.<\/span><\/li>
                                                        4. Your team values adaptability over predictability.<\/span><\/li>
                                                        5. Your customers want to be active stakeholders.<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>

                                                          When to use the Kanban methodology<\/strong><\/span><\/p>

                                                          A good way to decide if Kanban is right if…<\/span><\/p>

                                                              1. Your team needs a visual project management system.<\/span><\/li>
                                                              2. You want an at-a-glance way to understand where a project stands.<\/span><\/li>
                                                              3. You\u2019re not on an engineering, product, or software development team.<\/span><\/li>
                                                              4. You run ongoing processes and projects.<\/span><\/li>
                                                              5. Most of your work isn\u2019t produced in short periods of time.<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>

                                                                When to use the Scrum\u00a0methodology<\/strong><\/span><\/p>

                                                                Though not every team thrives on Scrum, yet might benefit from Scrum if…<\/span><\/p>

                                                                    1. You\u2019re on an engineering, product, software development, or Agile-based team.<\/span><\/li>
                                                                    2. You think your team could benefit from a slightly more rigid structure.<\/span><\/li>
                                                                    3. You have a large backlog of work to get through.<\/span><\/li>
                                                                    4. Your team is motivated by quick deadlines and deliverables.<\/span><\/li>
                                                                    5. Someone on your team is committed to being the Scrum master.<\/span><\/li><\/ol><\/li><\/ol><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                                                      \n\t\t\t\t\t
                                                                      \n\t\t\t\t
                                                                      \n\t\t\t\t
                                                                      \n\t\t\t\t\t

                                                                      How to combine Scrum and Kanban<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                                                      \n\t\t\t\t\t
                                                                      \n\t\t\t\t
                                                                      \n\t\t\t\t
                                                                      \n\t\t\t\t\t\t\t\t\t

                                                                      \"\"In order to host effective daily standup meetings, stellar sprint planning, and retrospectives, need a strong way to visualize work through stages and track all of the work in progress. Kanban boards can help to tackle sprint backlog and organize the flow of work during a sprint, so every Scrum cycle is a success.<\/span><\/p>

                                                                      Teams that run Scrum on Kanban boards frequently create a new board for every Scrum sprint. The reason for this is twofold:<\/span><\/p>

                                                                      1. Teams that create new boards for every sprint can start with a clean slate. <\/strong>This makes it easier for the Scrum master and Scrum team to visualize the new work they have to do for each sprint.<\/span><\/li>
                                                                      2. Scrum masters use past Scrum boards to track what work was accomplished during each Scrum cycle.<\/strong> Since a big reason teams implement Scrum is process improvement and efficiency, it can be helpful to look back and see what you\u2019ve accomplished.<\/span><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                                                                        \n\t\t\t\t\t
                                                                        \n\t\t\t\t
                                                                        \n\t\t\t\t
                                                                        \n\t\t\t\t\t\t\t\t\t

                                                                        Thank You<\/strong><\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

                                                                        \n\t\t\t\t
                                                                        \n\t\t\t\t\t\n\n