3 ms·
>suspicious that Washington's culture could really accept a lot of the Agile and Lean notions that are commonplace in the high-tech world. given my experience
by trhway 12y ago
>suspicious that Washington's culture could really accept a lot of the Agile and Lean notions that are commonplace in the high-tech world.
given my experience with thorough, to the letter, under supervision of no-expenses-spared-top-notch experts implementation of Agile/Lean/Scrum - 2 years non-stop across pretty much the whole company, only very-super-important-critical-projects got exception - the government would love it - a lot of planing, reporting, meetings and other crap boggling down everything with actual product development slowing down to the crawl as a result.
Btw, the original healthcare.gov - the one that failed and required that emergency super-team fixing - was developed using Scrum, and as result it had all the characteristics of a Scrum project, chief among them - bad, to the point of straight failure, integration between components.
- bkeroack 12y agoI agree and share your cynical view of Agile/Scrum, at least how it's often used in top-down organizations. In my experience there are two factors required for a successful project: a) Developer autonomy sufficient to modify core design/implementation if necessary--and developers experienced and talented enough to recognize when this is necessary. b) Developer ownership of the project. By that I mean minimal power difference between "stakeholders"/"business owners" and the developers actually building the product. You don't want developers to feel like consultants working on someone else's project because they won't care when bad decisions are made and they will naturally do the least amount of work possible to satisfy each Scrum ticket.
- wpietri 12y agoI share your suspicion of large-company Agile: by and large I think it's at best Mini-Waterfall, and at worst it's the same old bullshit with some new jargon on top. However, the large amount of bathwater doesn't mean there isn't a baby there. And the places I see doing best at making the necessary culture shift are the ones with a sense of mission. So I have hope. And honestly, even if this merely means a transition away from pure Waterfall to Mini-Waterfall, I think that will be a step forward. In the commercial world, the rise of the Internet has made 3-year release cycles untenable for most software; people now just scoff. So if we can merely get governments to emulate business in the shift from titanic failures to medium-sized failures, as a citizen I think that's a win. But still, from what I've seen, I'm hoping for more here.
- trhway 12y ago>However, the large amount of bathwater doesn't mean there isn't a baby there. Applying generic systems analysis (where it doesn't matter whether it is protein building, network protocol flow or software engineering process) one can easily see that Scrum is a highly synchronous low-latency process (that is the "baby" that management loves) which comes at the cost of dramatically decreased bandwidth. In addition, changing a team's process inside, Scrum indirectly completely changes how the team interacts with up- and downstream teams/components - in particular on practice eliminating any chance for early integration and for any iterations of the integrations. That became obvious to me during the first day at the first Scrum course, especially after i tried to ask those questions to the teaching Scrum expert from the consulting company and received blank face with some blabbing in response. Some time later, different company with different consultants - that first hand 2 year experience i described in the previous post - the Scrum drawbacks on practice happened to be even worse than i thought they may in theory. We actually have great time right now at our BigCo. as after the Scrum fiasco, and quietly dropping the Scrum company-wide as the result, the management still seems to be kind of "in shock", and they haven't brought up any new fad in the process improvement so far, so we're just doing typical old-fashioned per-feature waterfall, and it just works as usual - which is huge achievement compare to Scrum :)
- wpietri 12y agoI can't really answer for Scrum, especially as taught by consulting companies. I think of Scrum as a set of too-basic but reasonably good ideas that quickly ended up mostly as a certification scam. I wrote more about that a number of places, including here: http://agilefocus.com/2011/02/21/agiles-second-chasm-and-how-we-fell-in/ http://agilefocus.com/2011/02/21/agiles-second-chasm-and-how... I think that's especially true for dramatic company-wide, top-down Agile adoptions, which I have never heard of working. I think people doing that cannot possibly understand Agile philosophy, which promotes local control and continuous improvement of top-down control and giant leaps. My positive experience is mostly with smaller shops, but I've definitely seen many places where companies have grown up releasing early and often and have no problem working in what I'd consider good Agile style. Wealthfront, Etsy, and Spotify are all explicitly and openly like that. But I think there are plenty of other places that aren't explicitly Agile but ended up that way as a natural evolution. For example, when I visited YouTube to study their process, there were a great number of developers, designers, and product managers all working in relatively independent small teams. They'd release at least weekly but sometimes more often. There was no overarching plan; each team had particular goals to pursue, and coordinated with other teams as needed. They never used Agile jargon and didn't think of themselves as Agile, but I think they were acting in ways that exactly matched the spirit.