Hi everyone! I’m a student currently working on a research activity for our Software Engineering class, and I’d really appreciate your insights. 😊

I’m looking to gather input from software developers, project managers, or engineers about the Software Development Life Cycle (SDLC) paradigms you’ve used in your past or current projects.

If you have a few minutes to spare, I’d love to hear your answers to these quick questions:

  1. What type of software did you develop? (e.g., mobile app, enterprise system, game, etc.)

  2. Which software development paradigm did your team follow? (eg. Prototyping Model, Spiral Model, Fourth Generation Techniques (4GT), Waterfall Model Agile Model, V-Shaped Model, Incremental Model, RAD (Rapid Application Development), Feature Driven Development (FDD), Big Bang Model, Scrum, etc)

  3. Why did you choose that particular paradigm? (e.g., client requirement, team familiarity, project scale, etc.)

Your input will be used for academic purposes only, and it would really help me complete this task with real-world insights. Thank you so much in advance!

  • Cheezyburger@programming.devOPEnglish
    1·
    6 days ago

    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!

    • Azzu@lemm.ee
      2·
      6 days ago

      Oh and as for reasoning why, another few points, all projects I’ve been in just kept being worked on and had constantly changing requirements. There was no real need to plan very much except maybe some rough estimations, that were allowed to be wrong.

      There were like some very rough aspects of scrum in professional development, but only in the sense that we’d talk about what we’d like to do in the next sprint, we didn’t do multiple plannings or estimations or cared about our velocity or did retrospectives often, and even the sprints were adjusted to last longer or shorter based on what we’re going to do, there were a couple of roles people should have missing, and idk what. In the end, the resulting system was just something in the direction of agile/kanban, work just came in, and was handled based on some prioritizing by someone.

      My personal projects could be really close to waterfall as well, I thought about a problem, made a rough plan on how to solve it, then just kept solving until I was done. Open source projects, no one organized anything, everyone just works on whatever they like.

      Basically, you’re the expert in software development paradigms, I’m just a developer that works on problems with code until solved, either given to me by someone or myself. The only ones who care about the paradigm are the business guys who wanna plan some shit.