Agile and Specialist


Do you agree that the agile team may not possess all the specialized skills and technical knowledge required for the project?

You may argue that the team should be so constituted that team members among themselves have skills and knowledge  required – but is that always feasible?

What about UX experts, Functional Specialists, Architects, Technical Specialists …

Can they always become a full time member of the team?

Do you require them for the full duration of the project?

Do they walk in and out of the team?

What happens to the team dynamics?

Do they take responsibility of delivering story points?

Do they act as a user?

Do they only coach the team?

The Tao of Software Architect

While on this topic of role of specialist in agile project, I was reminded of the 2001 article by Philippe Kruchten. If you consider yourself an architect or if you want to become one then you must read it. Here are few lines from it!

The architect doesn’t talk, she acts. When this is done, the team says, “Amazing: we did it, all by ourselves!”

Let your workings remain a mystery. Just show people the results.

She steps out of the way and lets the design speak for itself.

More Reading

Comments
3 Responses to “Agile and Specialist”
  1. Alok says:

    Do you agree that the agile team may not possess all the specialized skills and technical knowledge required for the project?
    # Yes, I came across a situation where we were trying to implement Single-Sign-On (SSO) in a project with a reporting application. It was a difficult user story and we had to take help from external teams to get it done.

    You may argue that the team should be so constituted that team members among themselves have skills and knowledge required – but is that always feasible?
    # Not always feasible, but since agile believes in cross-functional expertise it can be possible that a developer may be very good at testing or vice versa.

    What about UX experts, Functional Specialists, Architects, Technical Specialists …Can they always become a full time member of the team?
    # Yes, why not? Since we do short releases.

    Do you require them for the full duration of the project?
    # Must not always be the case

    Do they walk in and out of the team?
    # Yeah, especially UX and Architects

    What happens to the team dynamics?
    # Not much of a difference

    Do they take responsibility of delivering story points?
    # Absolutely, they own their tasks

    Do they act as a user?
    # Yes

    Do they only coach the team?
    # Yeah, but they have to do that by pair-programming and so on. They can’t be in a team just for coaching; they have to own the tasks.

  2. Gene Hughson says:

    It is naive to assert that specialists are unnecessary or harmful, even. Additionally, depending on the organization, it may be that specialties must be shared between teams for financial reasons. I’ve seen some who claim to be “Agile”, but who take some very rigid, dogmatic approaches to what is agile and what is not.

Trackbacks
Check out what others are saying...
  1. […] Agile and Role of Specialist Share this:LinkedInTwitterFacebookStumbleUponPinterestEmailLike this:LikeBe the first to like this. […]



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: