Blog Xebia France

National Inquiry Agile Methods of FRENCH SUG

SCRUM User Group France, organ affiliated to SCRUM ALLIANCE, led, during two months, a national investigation, opened to all, through its site () to collect qualitative and quantitative data on adoption in France of the agile methods most used by those who decided to borrow the way of agility.

To download the results of this inquiry, follow following link.

Sponsor of conference XP Day France Xebia 2009

Xebia sponsors which will be held on May 25th and 26th, 2009.

You are in search of new ideas to make more efficient your software plans of development ?

You wish their borders in knowledge more on agile methods, their benefits, 
You set agile practices up within your plans and you want to confront your returns of experience with those of other practitioners 

Appointment on May 25th and 26th, 2009 for .

Read the continuation of this article

Distributed SCRUM: recipes to have teams of Offshore development hyper productive

SCRUM was conceived to attain a productiveness the upper from 5 to 10 times in that traditionally determined in industry and many co-located teams (c.a.d located physically in the same place) succeeded in reaching this target. The question which is asked in this article is to know if teams offshore and distributed are capable of attaining such performances in a lasting way.

Especially, the velocity of a local team can it be supported even augmented if it is distributed through several continents?

Xebia leads since mi 2006 of agile plans distributed between Europe and India. Having attained the stadium of the hyper productiveness in Europe, the Indian members of the team were re-installed in their country of origin. As part of this distribution, we noted that the velocity of the team even augmented. The use of the practices of engineering of XP (extreme Programming) within plans Scrum allowed to Xebia to retort in a lasting way a model of high quality distributed Offshore development identical to that of SirsiDynix [1].

Read the continuation of this article

What you perhaps missed in the first quarter 2008

Here is the list of tickets most read on this blog in January, February and March:

SCRUM or XP? SCRUM AND XP!

During the Agile Meetings, which we co-organised last December and which, am said by passing, met a fort and encouraging success - several persons asked me if, to start an agile plan, it was preferable to choose extreme Programming (XP) or SCRUM. Answer is simple: it is necessary to adopt two!
The complementarity of SCRUM and XP is universally recognised. SCRUM positions at the level of management and of organisation of plan where XP positions at the level of the activities of development. It is the reason for which these two approaches work so very together: they address different problems and complement each other mutually.

This article offers a presentation summary of SCRUM and of the way it (he? no, go, it is rather a girl) articulates with extreme Programming Bonne reading!

Read this article

The analysis of cover of code in Popular dance

He does not remain exaggerate the world any more to support that the writing of automated unit tests is a loss of time on a software plan the notion of technical debt becomes part of everyday life. This salutary realisation often collides however with two big categories of difficulties:

• Conservatism not to say foolishness about any project managers, who continue to see in the writing of tests an activity counterproductive, which will be of use as variable of adjustment for the slightest blow of firedamp
• The existent: when plan did not systematise the practice of the test from its origin and that the multiplication of late anomalies encourages it to reintroduce it. By where to begin ?

For the first point, solution is taken by a pedagogic effort, or, for hopeless cases, by an imposed restructuring or a sabbatical leave.
For second, is needed a little of common sense, and a little tools.

It is on the second aspect that intervene the tools of analysis of cover of code (or  encode coverage  in English). Afterwards, we will see that these tools do not allow to assess the unit tests of a qualitative point of view, but that they can bring on the other hand in common sense a precious support by answering following questions:

• What are in position the unit tests already ?
• Are tests on the wavelength of the code which they test ?
• Are critical functions of application covered by tests ?

Read this article

A new type of architect: the Agile Architect

They notice recently numerous debates on fact to know if an agile team needs an architect in its breast, and on the added value of this last on an agile plan while architecture evolves in every iteration.
The architects "Ivory tower" turn out to be little by little the weak link of agile plans. The responsibilities of the traditional architects are distributed ci and there within the agile teams, abolishing them in the passage of the tasks which were before allocated to them.
One new type is appearing and to go out of the lot as predicts it the theory of the evolution of Charles Darwin question of adaptation. The role of an Agile Architect should not provoke questions and every member of an agile team will confirm it to you: it is team members who bring one of the most great added values.

Then who is this Agile Architect? How to know if the architect of your team is an Agile Architect?

Read this article

Review of the papers Xebia

The review of the papers of actuality Popular dance / weekly J2EE offered by Xebia.

Actuality editors / SSII

• Microsoft and Yahoo!: what impacts for the ecosystem Popular dance?
• Source strengthening of stacks open Popular dance: Spring Source buys back Covalent
• MYSQL takes out a new engine of stocking
• Spring Security supports OpenID

Agility

• 10 ways of being planted in spite of SCRUM and XP

RIA

• Bookshop of components FLASH / FLEX by Yahoo!

The corner of technology

• Debate: Simple percentage Maven the right tool for builds?

Read the continuation of this article

A new type of architect: the Agile Architect

This ticket is a free translation of the article posted by our colleague Vikas Hazrati on the Agile site Newspaper.

They notice recently numerous debates on fact to know if an agile team needs an architect in its breast, and on the added value of this last on an agile plan while architecture evolves in every iteration.
The architects "Ivory tower" turn out to be little by little the weak link of agile plans. The responsibilities of the traditional architects are distributed ci and there within the agile teams, abolishing them in the passage of the tasks which were before allocated to them.
One new type is appearing and to go out of the lot as predicts it the theory of the evolution of Charles Darwin question of adaptation. The role of an Agile Architect should not provoke questions and every member of an agile team will confirm it to you: it is team members who bring one of the most great added values.

Then who is this Agile Architect? How to know if the architect of your team is an Agile Architect?

Read the continuation of this article

SCRUM or XP? SCRUM AND XP!

During the Agile Meetings, which we co-organised last December and which, am said by passing, met a fort and encouraging success - several persons asked me if, to start an agile plan, it was preferable to choose extreme Programming (XP) or SCRUM. Answer is simple: it is necessary to adopt two!

The complementarity of SCRUM and XP is universally recognised. SCRUM positions at the level of management and of organisation of plan where XP positions at the level of the activities of development. It is the reason for which these two approaches work so very together: they address different problems and complement each other mutually.

I offer you, in this article, a presentation summary of SCRUM and of the way it (he? no, go, it is rather a girl) articulates with extreme Programming Bonne reading!

Read the continuation of this article