Daily Scrum?
Do we have to stand in the Coffee House now? (Daily Stand-up meetings can be part of Agile dev cycle)
 
(Sitting is the new smoking)

Mebee.

While I'm sure most scrum masters will say we're doing it wrong (although I have never met any developer or worked on a team that actually did scrum 100% by the book) we do incorporate a lot of scrum processes not only on SONAR but other parts of our operation as well. 
 
In a lot of ways, this change is a reflection of our internal processes. We're constantly working on SONAR but instead of working in the dark for months we'll just release features and fixes as they're available. 
 
And yes there is a SONAR daily - maybe I can convince Keith/Noel to live-stream it one morning 

Haha when Google gets their act together and make hangouts work properly, we can think about it. As it stands our sessions sometimes sound more like stutter edit mashups than meetings :)
 
But yes indeed this process allows us to be far more agile than we ever have been. Once a fix is approved, delivering it to users is as simple as Willy uploading the files and pulling a switch and Command center will deliver the new update to all customers. So it will allow us to be much more responsive without the overhead we had earlier for creating installers, release management, etc.
It also allows us to release feature updates on a more frequent release schedule rather than monolithic yearly releases which are very difficult to test and deliver.

Ooo I'd watch with my team during our meeting. Smiles

ooohhh.. As a software engineer myself, I hate agile.  Well, let me rephrase that. Once a base product is complete, then it's ok........ I guess.........  
 
To me agile is nothing more than giving the business free reign to constantly change requirements/feature creep, forcing developers to constantly go back and change, rewrite, code.  Tooo easy to create a spaghetti factory. 
 
If you don't have good scrum masters, it's a developers worst nightmare. In fact our agile methodologies were so pathetic, I got so frustrated and found a new job within my company as far away as I possibly could.  

redbarchetta
ooohhh.. As a software engineer myself, I hate agile.  Well, let me rephrase that. Once a base product is complete, then it's ok........ I guess.........  
 
To me agile is nothing more than giving the business free reign to constantly change requirements/feature creep, forcing developers to constantly go back and change, rewrite, code.  Tooo easy to create a spaghetti factory. 
 
If you don't have good scrum masters, it's a developers worst nightmare. In fact our agile methodologies were so pathetic, I got so frustrated and found a new job within my company as far away as I possibly could.  

We do agile. It works ok, you have to do the vertical slices bit and have the whole team do the feature, you also have make sure you include technical debt when scoring user stories. If you got spaghetti it's a 13 instead of an 8.

One of the problems we had as engineers is that the structure of the organization was such that the business called all the shots, wanted what they wanted and didn't want to listen to us.  None of them knew how to Agile worked, but they heard the buzzword and thought it was going to save the world so we MUST implement it.  Part of the team was in Oregon, some in California, some in Arizona and some all the way in India.  It was a mess. It's hard enough to have so many people scattered around in the first place, but then to add Agile on top of it when the scrum masters were newbies themselves was just a recipe for disaster.

redbarchetta
One of the problems we had as engineers is that the structure of the organization was such that the business called all the shots, wanted what they wanted and didn't want to listen to us.  None of them knew how to Agile worked, but they heard the buzzword and thought it was going to save the world so we MUST implement it.  Part of the team was in Oregon, some in California, some in Arizona and some all the way in India.  It was a mess. It's hard enough to have so many people scattered around in the first place, but then to add Agile on top of it when the scrum masters were newbies themselves was just a recipe for disaster.

Yeah, you have to have buy in from the C level down to the grunt coders and the team has to be empowered to push back. If it's just piling on as usual, it's not agile. If the grunt coder can't tell the C level guy "If you want that, you can't get this", it's not going to work.

Pigs and chickens pigs and chickens!

At work I'm a pig.

In my studio, just a regular chicken.