I (as an architect/developer) and my business users love agile. For me, it's all about identifying requirement changes ASAP to minimize rework. Would you rather a requirement change before you work on it or after? The user thinks they know what they want but it's so abstract as a bunch of thoughts in their mind that they can't possibly identify every detail. But put a tangible product in front of them and a lot of what they want changes. It's inevitable.
So for me, I want the user to see the work ASAP so we can proactively identify these changes before we've wasted a bunch of time doing the wrong stuff. Our users totally bought in so it's like having one day iterations instead of the two weeks that we had before. I suppose YMMV with the user and technical team.
but you know what's real fun? that the guy who is supposed to handle the roadblock isn't even at the meeting. at the daily meeting you're supposed to find out then who the fuck might be the guy who's responsibility it would be to get that other team in some other ivory tower to remove the roadblock.
Which is why somebody else is supposed to step up and assume their responsibility temporarily. It's the exact same thing that would happen in any other methodology.
1. Do you work in a silo exclusively? I can't believe that others' work doesn't affect yours and your work doesn't affect others.
2. Nothing in Agile says you can only raise an issue during the scrum. That's either a silly trumped up example or your co-workers are imbeciles.
We're not talking about the same types of attacks though. I think it's safe to assume all major governments conduct military and diplomatic espionage. However, the US complaint is that the Chinese military is conducting industrial espionage and gives the stolen secrets to their own industry.
Indeed but they have the "build it and they will come" delusion of selling tens of millions of tablets. If desktop Metro really sucks that bad then the PR uproar will force Microsoft to make it optional for keyboard and mouse.