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?
Agile Development: A Manager's Roadmap for Success
Case Study: IBM's Agile Transformation
Agility at scale, become as agile as you can be
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!
hao ka
This is an excellent diagnosis of the symptoms and problems encountered in an Enterprise Agile Adoption scenario, with a practical analysis of its prognosis, possible treatment plans and ideas for monitoring and maintaining the continuous improvements in it.
Thanks for sharing your experiences and ideas.
Kripanidhi
www.scrumtales.blogspot.com
www.binaryessentials.com
Mike's point about you shouldn't try to get a team to be self-organising by command and control is one of those insightful moments that everyone should pause and think about.
In the past during interviews, discussions etc. I've mentioned taking a light touch approach as discussed in Sanjiv Augustine's "Managing Agile Projects" book and so many people, including some who have been seasoned agile proponents, have mentally taken the opposite angle of "the team won't become self-organising unless I tell them how to be", and dismissed the light touch approach.
IMHO to get a team to move towards becoming self-organising needs continous encouragement, respect, shared knowledge between all team members, and most of all, knowing when (as a manager, coach, or mentor) your pre-conceived mental image of them being self-organising day to day should be retired as they've reached their own disciplined state of being self-organising and have moved from the norming to performing stage of team development.
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?
3 comments
Watch Thread Reply