Beauty Is in the Eye of the Beholder
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
18 agile and lean practices for effective software development governance
A Guide to Branching and Merging Patterns
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
The whole "take what we think is important, but don't go all the way" paradigm is omnipresent in the field, and is one of the major cause of project failures.
Often, when new methodologies or technologies are introduced, there has been great in depth analysis of the potential pitfalls, and documentation on how to avoid them (often as part of the core methodology or tool or whatever). These are often ignored by teams as "not for us", "doesn't fit in our company", "people would never accept it", etc etc.
So then all of the severe flaws of the methodology, tool, technology, API, whatever which were thought about in the planning stage, are left wide open, and the people blame the methodology. Its -always- like that.
Francois's experience mirrors my own. In the past 4 years, I've only seen Scrum implemented correctly twice. I suspect 90% of those companies using Scrum do so in name only.
I've been scanning around agile material. Most are very large projects. My company have turned out projects with 3-4 team members max, working for some times less than 2 months.
Recently I've tested out a team where the team PM, was more "Agile Coach" role and the team consisted of a BA plus two developers. The result turned out good. No way of comparison, since from the start of the company we were into Agile.
The challenge presented to executives and leaders in organizations is to recognize the fundamental organizational design issues that sustained Agile adoption requires. At the end of the presentation we work with the audience on an exercise to define what is "done" for an enterprise Agile adoption. Insightful discussion and ideas are presented, including from Steve Greene and members of the Salesforce R&D team.
Innovel is a leading Scrum, Agile, and Lean training and consulting firm. Industry and academic contribution are core parts of our business. In addition to this presentation, Robin Dymond presented a new training simulation that has been made available at no charge to companies and consultants training businesses to use Agile methods.
Regards,
Robin Dymond, CST
Managing Partner, Innovel
Assistant Producer Learning and Education Stage Agile 2008
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
4 comments
Watch Thread Reply