Has Sonar gone Agile

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)

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

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.

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.

Unfortunately agile has become like a religion for some people and they think its the solution to all problems.
Without understanding the good parts of waterfall and top down design process, agile can become an excuse for the wild west style of development and easily lead to chaos.

The great Noel B!
and easily lead to chaos.

Isn't Captain Chaos the alter-ego of Butters in South Park? :-)
 

Noel Borthwick [Cakewalk]
Unfortunately agile has become like a religion for some people and they think its the solution to all problems.
Without understanding the good parts of waterfall and top down design process, agile can become an excuse for the wild west style of development and easily lead to chaos.

Yes, exactly.  

SuperG
Me too
It just a short term methodology for a short term business plan.

Never thought about it that way but yes.

Pigs and the chickens... Yum...

Noel Borthwick [Cakewalk]

bitflipper
I guess I've been agile since I started my business in 1993, because I am a development team of one. My meetings are conducted standing, because most of them take place in the shower.

Isn't that waterfall rather than agile? :P

FTW

We did agile in the 80s. It just wasn't called that then. In fact there was no name for it. We were coders working as fast (and as long) as we could to bring our first product to market.
 
 

TomHelvey

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.

THe buy-in is important...however, mutiny does work. I have been in situations like the one you describe...the team was universal in refusing to 'build ballistically' and we 'had the power', so we delivered an excellent core that had the original structure and features agreed to before embarking on feeture creep (sp intended). 
 
Agreed that it works MUCH better in a scenario of a solid base architecture that is robust, and fortunately for us, this is the situation for SONAR. X3e is sooooo good, however, that I may just ride along for a while before jumping on the bandwagon. I would like to see a little more clarity on timeout for <upgrade> costs as <opt out> duration increases. Right now it looks like I could do PRO (from X3) for $99 a year?? Does that go up to $299 if I wait a year???

scrum just sounds dirty