this post was submitted on 06 Apr 2025
14 points (88.9% liked)
Programming
19447 readers
116 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hi guys thank you so much for participating in my survey! I understand that some of you may not be familiar with the specific SDLC models used in your past projects. To help clarify, here is a list of common SDLC models that may have been used in your projects:
Prototyping Model: Quickly builds a basic version (prototype) of the software, gets feedback from users, and improves it through several iterations. It's helpful when requirements are unclear.
Spiral Model: Combines planning, risk analysis, and iterative development, revisiting each stage multiple times. It’s great for complex projects where risk management is key.
Fourth Generation Techniques (4GT): Uses tools that automatically generate code, speeding up development but still requiring testing and design. It's useful for small projects or prototypes.
Waterfall Model: A sequential process where each step (e.g., design, coding, testing) is completed before moving to the next. It works well for projects with clear, unchanging requirements.
Agile Model: Uses short development cycles (sprints) to create small, working parts of the software and allows frequent feedback from users. It’s flexible and works well when requirements change.
Scrum Model: A type of Agile, Scrum breaks the project into small, manageable tasks and focuses on completing them in short, time-boxed periods called sprints. Teams hold daily meetings to discuss progress and adjust plans. It’s great for projects where the team needs flexibility and constant communication.
V-Shaped Model: Like Waterfall but with a focus on testing. Each development phase is followed by a corresponding testing phase to ensure quality.
Incremental Model: Breaks the system into smaller parts (increments) that are developed and tested one by one, delivering functional parts early. It allows flexibility in adding features later.
RAD (Rapid Application Development): Focuses on quickly building prototypes and gathering user feedback to refine the system. It’s fast and flexible, making it great for projects with changing needs.
Feature Driven Development (FDD): Develops software based on client-valued features, with each feature being developed in small cycles. It’s effective for medium-sized projects.
Big Bang Model: Starts development with little planning and no defined steps, often used for smaller projects with minimal requirements. Changes are made as needed, but it’s unpredictable.
Where would "having two weekly meetups with everyone and talk about what is done and to do" fit?