How many PCB prototypes does your company allow in hardware design?

[tooki]

A huge problem with agile is that managers often say they’re using agile, when in fact they’re just allowing completely undisciplined development and calling it agile, without doing any of the actual methods used in real Agile-with-a-capital-A development.

So rather than reaping the benefits of Agile, you just gain undisciplined development and unpredictable, ill-prepared product releases.

And yeah, there are areas where Agile should not even be attempted, IMHO, never mind fake agile.

[Just_another_Dave]

A huge problem with agile is that managers often say they’re using agile, when in fact they’re just allowing completely undisciplined development and calling it agile, without doing any of the actual methods used in real Agile-with-a-capital-A development.

So rather than reaping the benefits of Agile, you just gain undisciplined development and unpredictable, ill-prepared product releases.

And yeah, there are areas where Agile should not even be attempted, IMHO, never mind fake agile.

I hate when they use “agile” to justify constant specification changes. Suddenly you need to rush because a manager has decided that a feature that wasn’t considered before is incredibly important, just to forget about it next week due to a new feature that they want

[tooki]

Exactly. Or, if the boss also happens to be the lead developer, then chooses to pull an all-nighter implementing it, and rolls it into the next day’s production update without telling anyone, like us testers… 😂

“Fun” ensues as customers report serious bugs that literally 5 minutes of informal testing would have caught…