{"id":428,"date":"2022-04-13T07:59:15","date_gmt":"2022-04-13T07:59:15","guid":{"rendered":"https:\/\/fluxtech.me\/blog\/?p=428"},"modified":"2022-04-13T07:59:17","modified_gmt":"2022-04-13T07:59:17","slug":"sdlc-agile-models","status":"publish","type":"post","link":"https:\/\/fluxtech.me\/blog\/sdlc-agile-models\/","title":{"rendered":"Software Development Models – Understanding What’s Right for Your Project Pt. 2"},"content":{"rendered":"\n

And we\u2019re back! In our previous article<\/a>, we focused on the difference between stricter and more flexible Software Development Life Cycle Models (SDLC). Specifically, we looked at the Waterfall and Agile models, both which Flux<\/a> has had success in applying to different projects.<\/p>\n\n\n\n

But wait, there\u2019s more! In fact, there are several types of agile models. In this piece, we\u2019ll be focusing on Agile Scrum, Lean, and Kanban. Understanding them will make you more informed when you begin your next negotiations with a software development team. So without further ado, let\u2019s get started…<\/p>\n\n\n\n

Agile Scrum<\/h2>\n\n\n\n

Agile Scrum (or Scrum for short) is one of the most used frameworks within the scope of agile. Compared with other agile models, Scrum stands out as one of the more structured ones. For example, the model entails daily meetings and a Scrum Master that oversees and reports on project progress. So if you are looking to be more engaged with your software development team throughout the process, this model is one you might consider.<\/p>\n\n\n\n

\"Scrum<\/figure><\/div>\n\n\n\n

Pros of Agile Scrum<\/strong><\/h3>\n\n\n\n

As is typical with agile, each sprint lasts roughly 2-4 weeks in Scrum. This gives you a great deal of flexibility to change requirements as you go. Scrum also uncomplicates the process of identifying and overcoming issues as they come up. Similarly, teams can prioritize key features and requirements. But most of all, arguably one of the greatest selling points for Scrum is that communication plays a vital role. In our experience, when communication is set as a priority, the result is that both DevOps and the client understand one another and therefore, expectations are properly met. With this model, you are always developing the product further based on feedback, which leads to higher quality.<\/p>\n\n\n\n

Cons of Agile Scrum<\/strong><\/h3>\n\n\n\n

One point folks typically don\u2019t like about Scrum is that several sprints can add a lot of time to the overall project development process. Like with other flexible models, it\u2019s tough to predict costs at the outset. So it stands to reason that only very experienced developers should work on a Scrum-based project. Daily meetings and reporting are great for communication, but it also can take up a lot of time.<\/p>\n\n\n\n

When to Use<\/strong><\/h3>\n\n\n\n

This model is definitely not suited for small projects with strict budgets. However, medium-sized projects can afford this kind of flexibility. Scrum is also recommended for those entrepreneurs of businesses that already have a foundational understanding of Scrum and also that have the time to be more hands-on. <\/p>\n\n\n\n

Lean<\/h2>\n\n\n\n

Lean is another agile framework with feedback and optimization at the heart of its methodology. The main goal is efficiency. Henc the term, Minimum Viable Product (MVP), which is often associated with Lean. MVPs allow developers to discuss and optimize the initial plan and then proceed to create a very simple version of the software. This will get the ball rolling. As always with agile models, user feedback and client input are key. <\/p>\n\n\n\n

Moreover, there are five core principles <\/strong>used when implementing Lean:<\/p>\n\n\n\n