Programming

19457 readers

199 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

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 [email protected]

founded 2 years ago

MODERATORS

[email protected]

What SDLC Paradigm Did You Use in Your Project? (programming.dev)

submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 1 week ago (1 children)

I've spent the last 25 years writing enterprise applications. 10 or so years ago the sdlc became "Dark Scrum" where all the trappings of scrum, expectations of waterfall and non of the prep work of waterfall. It's an interesting system where management can demand anything and then blame the devs for any and all problems that occur because "we didn't follow the process". Recently I've been given a larger management role and kind threw the entire process out of the window. Baby, bathwater, all of it. And just went with a basic kanban style. We try to do one thing at a time and a lot of my time is spent keeping a backlog that is estimated and prioritized. We have a standup type of call on Monday and Thursday for no more than 5 minutes. (we're a 100% remote team now, so no office)

[–] [email protected] 4 points 1 week ago

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.