What Types Software Development Life Cycle Models Responsible for Better Results?

[sunilmkt]

There are different types of software development life cycle models that are used in project development. Each & every software development models follow different processes or methodologies that are selected for the development of the project depend on the project’s aims and goals. There are many software development life cycle models that have been developed in order to achieve different required objectives such as –
Iterative Model
V Model
Spiral Model
Water Fall Model
RAD model
Agile model
Incremental model
Every software development models comes with advantages as well as disadvantage. So my main concern is which software development models provides better project development environment with bettor ROI.

 

[Jaydip]

It depends! and there is no definite answer.We use Agile scrum and it works well but if the teams are not aligned with the product backlog it can become a nightmare.We are also experimenting with Kanban(not a model but a scheduler instead). I have not heard good things about RAD though.

 

[DaveSimmons]

It depends! and there is no definite answer.

The needs of a Mars Rover control program are different from a kitten videos website, or a bank website, or a game, or a shrink-wrap application.

Factors include the team size, company culture, budget, how soon the software is needed, how bug-free it really needs to be, and so on.

 

[Train]

Build and Deliver project? Or "ongoing" project like a SaaS application? Or something in between?

I currently run a SaaS application, we are in perpetual build & maintain mode, there is rarely a deadline for anything. We have one giant codebase that is constantly evolving and improving. For our needs, Kanban works very well.

Aside from that, development models mean nothing without good people. A better than average PM helps too, an average or worse PM, IMHO, has a negative effect and the team would likely function better without one.

 

[IHateMyJob2004]

I forget who it was ...... I think one of hte top Google employees that has written books.

Know all the models for development and for each project, take hte pieces from each that make the most sense.

For example, waterfall might not make sense for a 5 year project due to a customer not knowing what they want. But over 5 years, agile would be a PITA with 6 week cycles. You might do a blend that uses 6 month cycles with more attention to requirments up front in each cycle.

Blindly or diligently choosing one methodology is bnot wise granted strict agile or waterfall might make sense in some cases.

 

[ringtail]

TRL (Technology Readiness Level)

Happy reading!