Middleware Management pitfalls 8. Application immaturity
Posted by Sander Hautvast mid-morning: August 20th, 2010
This is number 8, the third article in a top10 of middleware management pitfalls. The previous article dealt with infrastructure. This time I´ll discuss the application itself.
There has been much cool stuff lately about devops and devs and ops working together in one team, like at sky.com. The uncool reality for a lot of companies is that dev and ops are separated in different departments and don´t communicate well. Immature applications, at least from a middleware perspective, are what you get.
Lean Architecture Principles: Wrap up!
Posted by Sander van den Berg in the early evening: August 11th, 2010
Over the last 4 month's we have written a series of blogposts describing 11 principles of Lean Architecture. This post will be the last of the series, the wrap up post.
Lean Architecture Principle #11: Freedom where possible, standardize where needed
Posted by Denis Koelewijn in the early evening: August 10th, 2010
This is the eleventh and last post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The eleventh principle we discuss is called "Freedom where possible, standardize where needed". (more...)
Lean Architecture Principle #10: Architecture emerging from Projects
Posted by Gero Vermaas in the early afternoon: July 28th, 2010
This is the tenth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The tenth principle we discuss is called "Architecture emerging from Projects". (more...)
Lean Architecture Principle #9: Comprehensible over comprehensiveness
Posted by Sander van den Berg in the early evening: July 21st, 2010
This is the ninth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The ninth principle we
discuss is "Comprehensible over Comprehensiveness".
Lean Architecture Principle #8: Focus on the Value Stream
Posted by Denis Koelewijn in the early morning: July 15th, 2010
This is the eight post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The eight principle we discuss is called "Focus on the value stream". (more...)
Lean Architecture Principle #7: Architecture Initiated by Business Goals
Posted by Gero Vermaas in the early evening: June 21st, 2010
This is the seventh post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The seventh principle we discuss is called "Architecture Initiated by Business Goals". (more...)
Lean Architecture Principle #6: Iterative Architecture Development
Posted by Sander van den Berg around lunchtime: June 11th, 2010
This is the sixth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The sixth principle we discuss applies to the process of architecting and is called “Iterative Architecture Development”.
Lean Architecture Principle #5: Just in time, just enough
Posted by Denis Koelewijn at around evening time: June 2nd, 2010
This is the fifth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The fifth principle is called "Just in time, just enough". The essence of this principle is that only architectural work is done that is necessary and possible at that very moment.
(more...)
Lean Architecture Principle #4: All Hands on Deck early on
Posted by Gero Vermaas in the early morning: May 27th, 2010
This is the forth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The forth principle is call "All hands on deck early on" (initially coined by James O. Coplien). The essence of this principle is that all stakeholders of a project are involved at the start of the project.
Categories
- Java (292)
- Agile (136)
- General (98)
- Architecture (49)
- Scrum (46)
- Testing (45)
- Performance (42)
- Podcast (31)
- Middleware (34)
- Deployment (22)
- SOA (25)
- Project Management (23)
- Xebia Labs (23)
- Quality Assurance (16)
- lean architecture (15)
- Tools (12)
- Virtualization (10)
- Articles (9)
- Security (7)