InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Beyond Agile - Cultural Patterns

Posted by Amr Elssamadisy on May 29, 2009

Sections
Process & Practices
Topics
Adopting Agile ,
Agile Techniques ,
Agile ,
Agile in the Enterprise
Tags
QCon ,
QCon London 2008

Willem van den Ende and Marc Evers introduce different cultural patterns you can find in software organizations, based on Gerald M. Weinberg's work, and tell how to recognize them, what behavior to expect, and how you can handle unexpected events and change. They show how different agile processes like Scrum, XP, and Lean Software Development fit in, while explaining some common agile failure modes.  The six cultures presented are:

  • Routine: Managers want people to stick to the plan and process.
  • Variable: Good relationships between customers and developers.  Typically small teams.  Performance and quality depends on the people involved moreso than other teams and is typically a hero culture.
  • Steering: Choose among routines by the results they produce, i.e. an empirical process.  Typical XP an Scrum teams are this culture.  A caveat, this is only true if you make XP or Scrum 'your own'.  XP 'by the book' reverts to a routine culture.
  • Oblivious: No seperation between the user and developer.  Highly adaptive and highly customer oriented.
  • Anticipating: The art of the long view. Constantly improving the process.  Lean Software Development falls in this area.
  • Congruent: Transferrable cultural practices.  Culture of ongoing reflection and improvement.

Watch this presentation to get an overview of typical cultures in software development organizations and their strengths and weaknesses.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.