Thanks for sharing your experience! It sounds like the approach you’ve followed is quite flexible and adapted to each project’s needs. It definitely seems more like a mix of Agile and a bit of improvisation based on what the project manager or client prioritizes. I appreciate your insight!

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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. V-Shaped Model: Like Waterfall but with a focus on testing. Each development phase is followed by a corresponding testing phase to ensure quality.

8. 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.

9. 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.

10. 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.

11. 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.