Software Development Model

[Fresenius_Medical_Care]

Hi,

For a team it is always preferred to use Agile in order to have short sprints and collect customer feedback.

But what if we have a team which serve as resources for software development as well as software testing. 

Meaning development and test teams share a common pool resources.

In such a scenario which software development model should we use?

V-model? Agile? OR Spiral?

I know for sure it cannot be waterfall 🙂

[wiebe@CARYA]

XGH is used a lot 😑.

I'd say stick to what you 're (most) familiar with. Common sense goes a long way.

Or cherry pick from methods, to solve problems you run into.

I've never been able to adapt an entire method from scratch (GAMP, CMM, Agile, Scrum, Prince). Those methods might work (to some degree) if you join a team where everything is worked out, but I never saw any recourse on any of those methods that was both complete and comprehensive. YMMV.

[Martin_Henz]

A little bit off topic:

My feeling is, that I have seen hundreds of different "super" methods for software development. All of them are agile (and ugly) and the latest one has been named agile software development. Hmmm... every "new" idea could be reduced to its good name. Erything else is boring. Nothing special, none of them is perfect.

The best option since I stared with software development is to have very good software developers (or point them carefully into the right direction). The question is now and since ever: what is a very good software developer.

To came back to the topic: use what you want: every named method is as good as each other named method.

[wiebe@CARYA]

---

@Martin_Henz wrote:

To came back to the topic: use what you want: every named method is as good as each other named method.

---

Except XGH of course.

[JÞB]

---

@Fresenius_Medical_Care wrote:

Hi,

For a team it is always preferred to use Agile in order to have short sprints and collect customer feedback.

But what if we have a team which serve as resources for software development as well as software testing. 

Meaning development and test teams share a common pool resources.

In such a scenario which software development model should we use?

V-model? Agile? OR Spiral?

I know for sure it cannot be waterfall 🙂

---

If taken in the context of your latest posts involving the CLA-R exam I would have to say chose Spiral as the best answer. 

• The V model leverages design by intention where all requirements are known and traceable from inception 
• The Spiral model leverages design by investigation with an iterative process that allows new learning to feedback into design rapidly
• The Agile PROCESS allows a mixture of those two models that can be tailored by adjusting the sprint pace and or sprint Task objectives towards either end.

[wiebe@CARYA]

---

@JÞB wrote:

---

@Fresenius_Medical_Care wrote:

Hi,

For a team it is always preferred to use Agile in order to have short sprints and collect customer feedback.

But what if we have a team which serve as resources for software development as well as software testing. 

Meaning development and test teams share a common pool resources.

In such a scenario which software development model should we use?

V-model? Agile? OR Spiral?

I know for sure it cannot be waterfall 🙂

---

If taken in the context of your latest posts involving the CLA-R exam I would have to say chose Spiral as the best answer. 

---

If it's for an NI multiple choice exam, even CLAD, the answer is different.

You have to be either a complete novice, or absolutely master the material.

You have a higher change of passing the CLAD without any LabVIEW knowledge, just doing all the example exams (I know people that did this) or core 1, than you have with 1-3 year experience. 1-3 year experience will give you enough knowledge to know none of the answers is completely right or wrong, but (YMMV) not enough knowledge to know what the expected answer is...

So, to pass those exams, dumb down and learn what the expected answers are, or get so much experience to figure it out.