Jump to content


Agile Methodology

  • Please log in to reply
5 replies to this topic

#1 daveamour


    Active Member

  • Members
  • PipPip
  • 11 posts
  • Location:Staffs, UK
  • Interests:Computers, Squash, Chess

Posted 20 October 2008 - 11:00 PM

The process discussed in the book is clearly agile in nature.

Does anyone know which particular agile methodology it is though?

#2 MikeyJudd


    Active Member

  • Members
  • PipPipPip
  • 63 posts
  • Location:Cortland, NY

Posted 03 December 2008 - 05:56 AM

daveamour, there are actually more than one methodology being used in this book. However, there is a BIG focus on SCRUM. I would start looking at that.

#3 Dan_Pilone


    Active Member

  • O'Reilly Author
  • PipPip
  • 10 posts

Posted 03 February 2009 - 06:03 PM


Yes, MikeyJudd is right. We deliberately didn't pick an agile process, but tried to pull best practices from ones we've seen work in the real world. However, it is very Scrum-like. One of the key things we've seen on projects is that you really do need to tailor the process you use to the project and your team. Some teams/projects work really well with code reviews for example, other projects just don't get as much benefit. Some teams (or customers) need detailed designs to make progress, other teams do well with whiteboarding UML-ish models and going from there. Don't be afraid to tweak your process for an iteration, just make sure you measure whether or not it helped at the end of the iteration (sprint).

So, if you're looking for a specific process to get more detail on, I'd recommend looking at Scrum, but don't be afraid to borrow and try out ideas from other processes - don't get hung up on "we don't do that in process X" or something like that. Hope that helps -- Dan

Dan Pilone

#4 Matt John

Matt John

    New Member

  • Members
  • Pip
  • 1 posts

Posted 16 February 2010 - 11:01 PM

Agile Methods are not a panacea. We address this in the note “Don’t Let Short-Term Agile Create Long-Term Pain”. Simply stated, Agile methodologies can “get you there faster but constrict you later” by creating more costly overheads. And therefore they should not be used on all projects.

And I encourage proactive things which can expedite solutions as described in my post on “Master Data Management Enables BPM and SOA” as well as implementing the role of the Application/Solution Architect to create reusable software and data services, patterns and templates across application solutions to improve quality, productivity and consistency.

But I’d also like to address two positive things about Agile methods:

1)Agile methods are iterative and intended to build more agile solutions – so overheads ought to be more easily addressed in later iterations and

2)The business can derive value from the delivery of early iterations.

So, while the total cost of development and maintenance of a set of solutions and iterations built using Agile methods might be high, this can be offset by producing greater financial and competitive advantages to the business sooner.

Also, I would like to point out there are advantages to using Agile methods for doing business process improvement – beyond those benefits which IT may see using Agile methods for developers.

But to substantiate your point, organizations need to look at each application or service solution and determine if Agile methods are appropriate or not based on sound business principles.

#5 Jessica Robort

Jessica Robort

    Active Member

  • Members
  • PipPip
  • 19 posts

Posted 25 September 2013 - 02:04 AM

What is agile? Agile is one of the big buzzwords of the IT development industry. But exactly what is agile development? Put simply, agile development is a different way of managing IT development teams and projects. The use of the word agile in this context derives from the agile manifesto. A small group of people got together in 2001 to discuss their feelings that the traditional approach to managing software development projects was failing far too often, and there had to be a better way. They came up with the agile manifesto, which describes 4 important values that are as relevant today as they were then. It says, “we value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

The various agile methodologies share much of the same philosophy, as well as many of the same characteristics and practices. But from an implementation standpoint, each has its own recipe of practices, terminology, and tactics. Here we have summarized a few of the main methodology contenders:

Lean and Kanban Software Development
Extreme Programming (XP)
Dynamic Systems Development Method (DSDM)
Feature-Driven Development (FDD)

#6 edwardepps


    New Member

  • Members
  • Pip
  • 1 posts
  • Gender:Male
  • Location:New York
  • Interests:Web development, PHP

Posted 21 March 2014 - 03:40 AM

Speaking about agile, scrum and other development methodologies. Here some good articles on Agile and on Scrum. And also, here's a good infographic about software development stages and methodologies in general.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users