If you find this site useful, you should try my 55-page eBook here

Why General Agile Is Not Enough - Why Scrum Wins

by Kelly Waters

Email This Post Print This Post Save As PDF
Why Scrum Agile Development WinsI found this article on Agile Journal really interesting:

Why 'General Agile' Isn't Enough - Why Scrum Wins in the Enterprise.

I have to say, I agree with Katie's points entirely...

We have implemented Scrum in a large web development group that is now about 120 people.

The simplicity of Scrum. The high visibility. The collaborative approach. The frequent delivery of product. All in all, Scrum really did transform the relationship between IT and the business units. And transformed our ability to deliver.

Kelly.

P.S. Click one of the icons below to join the growing community of people keeping up with this blog by RSS or by email...
keep up by rss feedkeep up by email

  • Digg
  • del.icio.us
  • StumbleUpon
  • Yahoo! Buzz
  • Technorati
  • Facebook
  • TwitThis
  • MySpace
  • LinkedIn
  • Live
  • Google
  • Reddit
  • Sphinn
  • Propeller
  • Slashdot
  • Netvibes

3 comments:

  1. Sebastian said...

    Hello Kelly,

    I read your blog (like others) continuously and I find it very helpful. But there are a few answers I never found.

    You wrote that you implemented scrum for a product with 120 people working on. How do you synchronize the teams?

    We have a product with round about 25 developers working on. We formed three teams with different main-goals but the product development mainly is concentrated on two teams that have a planning session together but separated review/retrospective sessions. Out of this approach arise some synchronization issues. I'd be interested in some information concerning your approach.

    Thanks in advance

  2. Brandon said...

    I would also be interested in more specifics. My experience has been that you need a highly customized implementation of Scrum in order for it to be effective.

  3. Kelly Waters said...

    Hi Brandon

    I was interested in your comment. In what ways would you say Scrum needs to be customised in order to be effective in larger organisations?

    Personally I see a lightweight project management wrapper around Scrum for large projects. And I see some or all of eXtreme Programming to improve engineering practices.

    I also see value in the more traditional PMO function providing a view of the overall programme of projects, and an Enterprise Architecture function sitting technically across the whole lot.

    So I do believe an organisation benefits a lot from augmenting Scrum with XP and some project management practices - without which it possibly wouldn't succeeed. But I don't see Scrum practices heavily customised as such.

    Kelly.

10 Key Principles of Agile Development

How To Implement Scrum in 10 Easy Steps

User Stories - Agile Requirements

Agile Project Management

10 Key Principles of Agile

How To Implement Scrum

Most Read

Agile Leadership

Agile Requirements - User Stories

Agile Estimating

Agile Testing

Agile Project Management

Lean Software Development

Agile Teams