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 Amr Elssamadisy on May 25, 2011
Mattias Skarin, co-author of InfoQ's popular mini-book on Kanban and Scrum, shares a set of kanban boards that can be used to visually manage anything from system administration, to development teams with multiple clients, to sales. Below are four interesting examples of how kanban boards can be used to visually manage several different scenarios. (Mattias shares twelve different kanban boards on his blog site.)
For those who are not already adept at reading kanban boards, it helps to view the most simple of them, a kanban board for Scrum. As the notes on the left indicate, you have the context - answering the question "who can use this board?", and pros and cons, which in this case would be to flatten out your burndown chart.
The next example answers the question "what if I have multiple clients?" In this example we can see that a team will end up having one value stream no matter how many clients they are working with.
Another interesting application for a kanban board would be for system administrators who have a completely different set of requirements than a typical development team:
And finally, there is the kanban board for sales which can be a great visual tool for organizations with a lean culture.
Remember, eight more kanban boards can be found on Mattias' blog.
If you are new to lean and kanban, these may give you some ideas. If you are more experienced, have you found similar uses for kanban? Have you found other configurations that you have found useful? Please share your experiences with the community.
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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.
No comments
Watch Thread Reply