Posted by Erwin van der Koogh just before lunchtime: April 30th, 2010
I was triggered recently by a status update from someone that mentioned that we will have to get ‘this’ right the first time around in the future.
This particular case was about a test, very late in the project cycle, where lots of things needed to get together perfectly to make it work. Any delays would not only delay the current project, but all other projects that rely on the shared resources being used. This huge cost if things go wrong is why it is so imperative that we do get it right the first time around.
The problem is that this involves tens of people across multiple companies and departments, who have written thousands of lines of code.
Now I do not know what they are going to do to make things right in the future, but if we go by past experience most people will want to enforce even stricter entrance criteria.
There are a couple of problems with this approach:
(more…)
Posted by Geert Bossuyt just before lunchtime: April 29th, 2010
A Scrum team from London was trying
To deliver the app without dying
Sustainable pace
no more rat race
The feedback augmented the buy-in.
Posted by Sander Hautvast mid-morning: April 28th, 2010
What is ‘middleware’? French professor Sacha Krakowiak defines middleware
as [a] software layer [which role] is to make application development easier,
by providing common programming abstractions,
by masking the heterogeneity and the distribution of the underlying hardware and operating systems,
and by hiding low-level programming details
This makes sense, considering the fact that writing an http server nowadays or a servlet-container is not considered sane anymore, given the multitude of commercial and open source products that have already proven themselves. Over the years a range of products and standards has emerged that to a growing extent hide the low-level intricacies and provide the application programmer with easy yet powerful abstractions. They range from webservers, databases and application servers to EBS´s and BPM platforms. They form the IT landscape that enable modern business. And it´s their heterogeneity and distribution that is at the heart of the emerging problems that we will address in a top-10 style series of blogs in the coming weeks.
(more…)
Posted by Gero Vermaas in the early morning: April 28th, 2010
This is the second of a series of blog posts discussing Lean Architecture principles. Each post will discuss one principle and applying these principles will result in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The first principle that we discuss applies to the architect role and is called “Always Involved“. The architect role is not limited to one project phase or even one project, a good architect takes a much broader perspective. The Lean Architect constantly communicates with all stakeholders (from business till operations), plays an active role in running projects, and ensures that lessons learned in projects are known and where applicable used in other projects.
Posted by Jan Vermeir around lunchtime: April 27th, 2010
Knowledge of the past allows us to predict the future, at least, for certain areas of human enterprise. I’m convinced that software development is one such area. The theme of this blog is ‘to measure = to know and to know = to predict’, so by the transitivity of equals we can state ‘to measure = to predict’.
But what should we measure? I suggest you at least measure the following and will try to explain why below: trends in burn down, trends in bugs, trends in test coverage and trends in complexity.
Posted by Jan Vermeir in the early morning: April 27th, 2010
Development teams or even development organizations, are not always the well balanced, smooth operations we’d like them to be. In our software quality audit practice we have had the privilege to investigate many different types of organizations and found many different ways quality and productivity can suffer from a problem known as the Prima Donna Syndrome: a single individual exercises a disproportionate influence on the team causing problems like stagnation and unnecessary complexity.
(more…)
Posted by Gerard Janssen terribly early in the morning: April 23rd, 2010
In our work with clients we often have discussions about the function of architecture and the role of architects. These discussion are largely due to fact that architecture does not visibly contribute to organizational goals and is perceived as a nuisance for projects. Many discussions originate from a lack of understanding of the role and place of architects in the organization. We have defined three goals of the architecture function in IT organizations: The Three C’s of Architecture. These are: Connection, Cohesion and Changeability. Taking these as the prime principles of architecture provides focus on what to do and how to position architecture in the organization.
(more…)
Posted by Andrew Phillips around lunchtime: April 22nd, 2010
While recently fiddling with some more runtime generic type extraction for Deployit, I was caught out by some unexpected behaviour by the reflection API. A check of the Javadocs quickly revealed that I had once again been too hasty in relying on “common sense”. Still, the case seems sufficiently unintuitive to merit discussion. (more…)
Posted by Geert Bossuyt in the early morning: April 21st, 2010
The Agile Alliance wants to translate the Agile Manifest into different languages. The Dutch translation will be coordinated by me.
I really want this to be a community effort of the Dutch speaking community. Therefor the blog to guide this translation effort is in Dutch and on a community blogsite (AgileHolland).
If you want to add your contribution to this translation please follow this link for the translation of the Manifesto,
and follow this link for the translation of the Agile Principles.
Because the translation started from this blogpost, there are already some comments on this post. I’ll see with the people who posted the comment how we will transfer these comments to the new post.
Posted by Wilfred Springer mid-afternoon: April 20th, 2010
If there is anything that made Java popular during the last decade, then it must be the community. This may sound like a paradox at first: popularity does sort of imply the existence of a community. But it’s really not just the existence or even the size of the community. It’s the vibe that counts.
(more…)
Categories
- Java (311)
- Agile (181)
- General (136)
- Scrum (67)
- Architecture (64)
- Testing (59)
- Performance (46)
- Middleware (55)
- Deployment (37)
- Xebia Labs (38)
- SOA (31)
- Podcast (31)
- Project Management (28)
- Tools (25)
- Uncategorized (20)
- lean architecture (20)
- Quality Assurance (17)
- Articles (13)
- Virtualization (19)