Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Vikas Hazrati on Jan 18, 2011
Jim Collins, in his famous book “Good to Great” talks about his teams five year research where they determined what it takes to change a good company into a great one. Can Agile help in the creation of great companies?
Jean Tabaka suggested a list of 10 characteristics of a truly Agile organization which potentially would help an organization make the leap. Jean suggested the following characteristics in order of increasing importance
Likewise, Mike Beedle emphasized on the following characteristics of a truly Agile organization,
Mike Cottmeyer suggested a list of patterns that he has observed across organizations, which are essential for success of Agile. According to Mike,
There are some patterns I see over and over that are fundamental to a successful agile adoption, or a large scale enterprise agile transformation. Here are the ones I think are most important and why.
As one would observe, most of the characteristics place a lot of importance on empowerment, communication and collaboration. The key is to promote an environment of trust, learning and deliver business value with a sustainable pace.
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
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!
I really like these. Just wondering what's unique to "agile" here, though. Seems this could be entitled "Characteristics of an Effective Organization."
I also tend to agree that it is not about agile, but about work principles in general
I agree. All good things. It just seems as time passes, lists like these pop up and include less and less that is distinctly Agile and more that is basic organizational excellence, change management, etc. Not that all of this isn't important, especially in large organizations that seek to adopt an Agile approach. But I sometimes wonder if folks are beginning to find the Agile context for all of this a harder "sell" and are falling back on traditional expression of such things because organizations are more familiar with and comfortable hearing them expressed this way. I just hope the Agile content finds its way into what the organizations end up doing as that is the unique aspect of trying to do all these otherwise good things.
Great post Vikas. This is a great resource for IM professionals. We have a community (www.openmethodology.org) and have bookmarked this post for our users. Look forward to reading your work in the future.
What about the level 5 leaders? And what about that they are "fanatically driven, infected with and incurable need to produce sustained results"?
Most agile posts come from the direction of creating a "cosy" environment for developers and not from the direction of an "incurable need to produce sustainable results".
I really try to understand :) I am not certain if my interpretation is right. But I would currently suggest that agile is a tool in the toolbox of a level 5 leader that he can use in the right circumstances.
In addition I don't think that the mechanics of agile, like described above, count! It is all about mental state of people in the sense of Christopher Avery:
www.christopheravery.com/pdf/citj0604avery.pdf
If you get the mental state of people right and if they come from the direction of and "incurable need to produce sustainable results" then I think agile (in the best sense of the word) will emerge automatically.
How do you see that?
this sounds like the Holy Gospel, Mark 9,35.
For years I have heard that religion is one thing and one thing is the "hard reality in". Instead I'm increasingly convinced that there is wisdom: that's all.
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
6 comments
Watch Thread Reply