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:
-
What type of software did you develop? (e.g., mobile app, enterprise system, game, etc.)
-
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)
-
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!
Damn finally someone got into the management position and made positive changes instead of just drinking the company cool aid and becoming a part of the problem. I was very frustrated at my last job where they would pretend to half heartedly follow some Scrum / Kanban process and pretend we are doing proper project design, and task estimation when everyone was just checked out and you as a developer are just expected to figure things out on your own and if there’s any delays in the project because the stakeholders changed requirements or other external factors they won’t adjust the time line and blame the dev for the delays if those deadlines aren’t met. All this focus on the “process”, the meetings the pointless RTO, but not one person was interested in getting shit done. No wonder the company had to resort to layoffs. Hopefully at my next job I’ll find a team that’s better managed.