BT

InfoQ Homepage Presentations Tamara Sulaiman on Tips And Techniques For Implementing An Agile Program Across Distributed Teams

Tamara Sulaiman on Tips And Techniques For Implementing An Agile Program Across Distributed Teams

Bookmarks

Bio

Tamara Sulaiman is Managing Consultant at Applied Scrum where she is focused on coaching teams and organizations transitioning to Agile software development. Tamara brings over 20 years of experience in management across a spectrum of industries including: information technology, construction, international development and education to her consulting expertise.

About the conference

Agile 2009 is an exciting international industry conference that presents the latest techniques, technologies, attitudes and first-hand experience, from both a management and development perspective, for successful Agile software development.

Recorded at:

Jan 21, 2010

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Very interesting but ... how is this related to agile?

    by Udayan Banerjee /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Just replace the word agile with any other change that you want accomplished ... and the presentation will be equally impressive.

    Agile requires specific questions to be answered ... setandbma.wordpress.com/2008/12/01/off-shoring-...

  • All in all I agree, but some points to discuss...

    by Henrik Berglund /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi,

    I think the approach outlined in the video is what most agile coaches seems to propose, and I mostly agree. Thanks for putting this together Tamara.

    I found some things to that probably do not agree:

    - The whole thing with creating the name and the logo for the change. I think a lot of smart people is advocating NOT to name change initiatives. I can think of several reasons: 1) To prevent resistance from people tired of named change programs. 2) To prevent resistance in general, if it does not have a name it is harder to whack it. 3) It is not supposed to be a program that ends some time, it is supposed to be a new culture of learning, problem solving, inspect adapt.

    - Creating Best Practices. 1) I think Taichi Ohno said that once you define the best way to do anything it is all over. You will kill future innovation. 2) I am a strong believer that teams need to contribute to a process to feel that they own it. By dong this it will be sustainable change. It will also ensure that the teams keepsdeveloping the process. Best Practices is dangerous stuff...

    Best Regards


    Henrik

    www.cedur.se/index_us.html

  • Just another "Agile" consultant.

    by Christopher Churchill /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Just another one of the million Agile consultants in the market.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.