This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Opinion: Agile software development only works with a functioning feedback loop

I guess some will view this off-topic, but it is perfectly on-topic. I come from the Instinct Solar, but engagement there is low due to user numbers, and this topic applies to all Garmin watches, in my opinion.

Agile software development, in a very brief nutshell, means you program something for two weeks, put it out there, and react to the feedback. If done wrong, it basically leads to banana software, because you constantly let users work with beta versions.

This article summarises it well:

https://www.computerweekly.com/news/450418205/Agile-development-an-IT-fad-that-risks-iterative-failure

"Agile development an 'IT fad' that risks iterative failure - Agile promises continuous improvement through an iterative process, but without proper checks, project failure is commonplace"

That quote perfectly summarises Garmin for me. I look through months of old bug reports and complaints by users across so many forums, and often, nothing changes, because those responsible don't listen or falsely mark things as 'not a bug'.

I'd like to hear other people's opinion on this.

(Another good article on the subject is: https://stackoverflow.blog/2020/06/29/does-scrum-ruin-great-engineers-or-are-you-doing-it-wrong/ )

  • What makes you think garmin uses agile? There's other development methodologies 

  • Well, apart from the timed beta release cycle there is this strong 'correct after release' mentality (I just can see the team leaders giving out the tickets for the small issues you can easily fix to get as many 'done' as possible on the stats), and then of course there are job ads like these:

    "Previous experience with Agile/Scrum methodology and a PMI-PBA, CBAP, or scummaster certification is highly preferred!"

    ourability.jobs/.../

  • Personally, I am very happy that Garmin listens to its users and is constantly trying to fix bugs and add features. The Garmin watches are incredibly complicated devices, and it is not at all surprising that adding features and fixing bugs will give rise to other issues that could not have been foreseen. There are so many different use cases, and phones, and headphones, and accessories - I can't imagine a company being able to foresee every single one of them and design software that would be perfect out of the box. In fact, I can't think of a single company that has even come close to doing that.

    My hat is off to Garmin for consistently trying to make their products, and their users' experiences, better.

  • I couldn't agree less. Making things work as universally as possible is the one job that should define Garmin. Compared to other technical devices these days, or a dual or triple A computer game, these kind of watches are not that complicated. Much of the technical complexity has been solved elsewhere, as predominantly fixed hardware solutions are used for GPS, accelerometer, bluetooth, Wifi, memory, processor etc.

    Also, plowing through these forums, I by no means think that Garmin generally 'listens to its users'. And 'constantly trying to fix bugs' says a lot about the initial release state of a product.

  • Well, fortunately no one is forcing you to own a Garmin. Let us know which watch you end up going with that doesn't have any issues.

  • I'm not really into these new words, but isn't that called 'whataboutism'? Also, if there is a divide between what is promised, and what is delivered, and this only becomes obvious after some time (i.e. with battery life), what does the customer do then? Can't give it back, so... technical support?

  • Do you think that upvoting your own posts and downvoting any posts that express an opinion different from yours makes your arguments more compelling? (Hint: it doesn't).

    Enjoy your new non-Garmin watch.

  • I don't think agile software development is suited to consumer products like the Garmin ones. I doubt they even try to do that. Reality is that Garmin has no pressure to react super quick to change requests. They can take some time and that is fine. This is not a business line management software or something like that where quickness is desired and prioritized over other development attributes. Garmin work on a roadmap.

  • Apple Watch Series 4.. everything just works.