InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

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: Kent Beck: Trends in Agile Development

Posted by Abel Avram on Jan 19, 2009

Sections
Process & Practices,
Architecture & Design,
Enterprise Architecture
Topics
Adopting Agile ,
Business ,
Agile
Tags
Trends ,
QCon London 2008 ,
XP ,
Patterns

In this presentation, Kent Beck, the father of eXtreme Programming, shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.

Watch: Kent Beck: Trends in Agile Development (56 min)

Kent starts his presentation with today’s business trends:

  • Accountability
  • Responsibility
  • Transparency
  • Relationships

He continues with current development trends:

  • Effective software
  • Reliable software
  • When promised
  • Reasonable price

Agile currently knows a growth in adoption, according to Kent, being embraced both by small and large companies, established industries and start-ups, government and private companies. The reason Agile has this influx of adopters is its synergy with business trends: Agile responds to business demands, accountability, responsibility, transparency, with practices which meet these demands. Agile development has techniques to estimate the man-hours needed to complete a project, it supports a solid relationship with customers by listening and responding to them, and it produces more reliable software. 

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

1 comment

Watch Thread Reply

nothing beats programming at night.. by Richard Kucera Posted

  1. Back to top

    nothing beats programming at night..

    by Richard Kucera

    well, not exactly nothing. Programming at night beats not getting it done due to spillover during the day. Everyone is asleep at home and at work.

    Another trend: Work At Home. What this is really for older programmers is "Work And Home", that is, Maximum Spillover.

    That means More Programming At Night, yay!

    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.