
	Where results make sense

Topic: Agile Methods

Related Topics

RUP

Software development process

CMM

Methodology (software engineering)

Cleanroom

ISO 9000

Simulation game

Postage stamp

TBD Devastator

West Goshen Township, Pennsylvania

Climbing route

Daniel Barenboim

Japanese cuisine

Abbreviation

Kathleen Turner

In the News (Sun 15 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Agile software development - Encyclopedia.WorldSearch (Site not responding. Last check: 2007-11-07)
		These methods were developed with the understanding that software is difficult to control, and are intended to reduce the complexity, of software engineering.
		One way in which agile software development is generally distinguished from "heavier", more process-centric methodologies, for example the waterfall model, is by its emphasis on values and principles, rather than on processes.
		DSDM is considered the first established agile method throughout Europe and was formed by a decidedly more deliberate purpose and process.
	encyclopedia.worldsearch.com /agile_software_development.htm (2795 words)

	Agile Methods
		Agile Methods evolved in the mid 1990s as part of the reaction against high ceremony methods, like CMM, Prince and ISO 9000.
		In general, Agile Methods impose as little overhead as possible in the form of rationale, justification, documentation, reporting, meetings, and permission.
		Agile Testing - Set of links to a body of writing on Agile testing methods and their use.
	www.nebulasearch.com /encyclopedia/article/Agile_Methods.html (637 words)

	Agile Methods
		Agile approaches have emerged in the last 10 years along with new development, testing, source management, and version control tools which allow for solid development environments which in turn support the ability to generate high quality refactored releases of a system.
		Agile techniques emphasize stakeholder participation, ideally a representative of the client is on sight and participating in development on a daily basis.
		Agile methods differ from Cleanroom in that cleanroom is a much more scientific approach and is a much more heavywight methodology.
	pages.cpsc.ucalgary.ca /~davisk/613/Agile.html (1384 words)

	MF Bliki: agile
		Agile Universe did this on a wiki, which was alright - but I prefer the sound of Owen's approach.
		The upshot of all this is that agile methods fundamentally expect teams to decide what process to follow and furthermore expect teams to actively and regularly change their process.
		One of the common elements of agile methods is that they raise programming to a central role in software development - one much greater than the software engineering community usually does.
	martinfowler.com /bliki/agile.html (3104 words)

	The New Methodology
		Agile methods assert that no process will ever make up the the skill of the development team, so the role of a process is to support the development team in their work.
		The Agile Alliance is a non-profit organization that seeks to promote knowledge and discussion of all the agile methods.
		Craig Larman is a strong proponent of using the RUP in a agile manner.
	www.martinfowler.com /articles/newMethodology.html (9094 words)

	[No title] (Site not responding. Last check: 2007-11-07)
		Agile methods have been getting a lot of press lately.
		I'll give you a quick overview of the term "agile methods" and some pointers for more research (see the sidebar, "Core Concepts of Agile Methods").
		The underlying theme behind agile methods is the acceptance and facilitation of change.
	www.fawcette.com /resources/managingdev/methodologies/agile (364 words)

	STSC CrossTalk - Bridging Agile and Traditional Development Methods: A Project Management Perspective - May 2004 (Site not responding. Last check: 2007-11-07)
		The purpose of this article is not to compare agile and traditional methods, but to raise awareness of potential project management conflicts that can arise when a company employing an agile method collaborates with a company employing a traditional development methodology.
		One common misperception of agile methods is that the requirements are not controlled since they are allowed to change late in the game.
		Terms unique to the agile method such as coach, tracker, and metaphor [7] would be mapped to traditional terms such as project manager and architecture.
	www.stsc.hill.af.mil /crosstalk/2004/05/0405McMahon.html (3895 words)

	Kent Graziano On Agile Methods And Data Warehousing (Site not responding. Last check: 2007-11-07)
		Agile methods are a bit of a hot topic at the moment and I took a look at them, in the context of data warehousing, earlier last year in two articles.
		The idea of using agile techniques when building databases is not new, with Martin Taylor and Pramod Sadalage publishing "Agile Database Design" early in 2003 and a whole book, "Agile Database Techniques", written on the subject.
		Agile methods grew up because requirements change, and this we have to adapt during the course of the project.
	www.rittman.net /archives/001204.html (1531 words)

	Agile Methods. The bottom Line.
		Agile methods start out producing data like this from the very beginning of the project, and don't stop until the project is over.
		In an Agile project there is no Analysis phase that cannot be measured, there is no Elaboration phase that cannot be measured, there is no design phase that cannot be measured, there is no infrastructure development that cannot be measured.
		The bottom line for agile methods is that they provide the data that makes managing software projects possible.
	www.artima.com /weblogs/viewpost.jsp?thread=16880 (1000 words)

	Exploring Agile Methods for Web Design (Site not responding. Last check: 2007-11-07)
		Agile practices helped us know where we were the whole way through the project, but we had a side benefit I hadn't anticipated.
		Agile methodologies afford software professionals a firm, collective ground to stand on, and help separate top level management strategies from the granular reality of day-to-day software development.
		Agile methodologies which are refactored to fill the reqs of Web development processes will liberate the Web out of the hands paranoid ad execs and render it back to those passionate professionals who still believe the Web will deliver on its promise.
	agile_webdesign.blogspot.com (5423 words)

	Agile Development
		The Agile Manifesto offers a philosophy for Agile Development, and although philosophy is fine for underpinning practice I was more interested in what I should be doing.
		Each of the methods has a particular slant, which is largely a result of where it is invented, by whom, and for what type of project.
		The Agile methods agree that each timebox has a plan of its own that is created in a meeting at the start of the timebox.
	www.balagan.org.uk /work/agile_comparison.htm (3277 words)

	Search Tuna Report for Agile software development (Site not responding. Last check: 2007-11-07)
		Agile Software Development is the name given to a collection of lightweight software development methodologies, including Extreme Programming, Scrum, Crystal, Lean Software Development, Test Driven Development, Agile Project Management, Feature-Driven Development, and DSDM Joint Agile United 2005 Denver has been selected as the host for Agile United conference in 2005....
		Agile methods are flexible and interaction-focused, seeking to adapt...
		Agile is not a specific process, but rather an umbrella term for a group of methodologies and approaches that have a similar basis....
	www.searchtuna.com /ftlive2/1271.html (2325 words)

	STSC CrossTalk - Learning From Agile Software Development - Part Two - Nov 2002 (Site not responding. Last check: 2007-11-07)
		Being agile is a declaration of priorities, prioritizing for project maneuverability with respect to shifting requirements, shifting technology, and shifting understanding of the situation.
		Many of the differences between agile methodologies and cost- and plan-driven approaches are in deciding which issues are MFF or MFI issues, and what the best allocation of resource is for each.
		An agile team might decide that the project plan fundamentally cannot be resolved past a very simple approximation, and therefore a MFI strategy is a waste of money.
	www.stsc.hill.af.mil /crosstalk/2002/11/cockburn.html (3301 words)

	Guardian Unlimited Technology \| Technology \| Taken to extremes (Site not responding. Last check: 2007-11-07)
		The reaction against this has seen a rise in agile development methodologies, also known as lightweight methodologies, that enable complex projects to be delivered in a tight time-frame.
		XP is probably the best known agile methodology, and comes into its own in the rapid development cycles of today's fast moving, flexible businesses.
		However, agile methods tend towards common sense solutions to the problems of software development, and can best be described as a craft approach, rather than the overly intricate software engineering and project management methods at the heart of other popular development methodologies.
	www.guardian.co.uk /online/story/0,3605,1342328,00.html (898 words)

	Answering the "Where is the Proof That Agile Methods Work" Question
		SCRUM and DSDM are among the oldest agile methods, being defined in the mid-1990s.
		The Agile Alliance was loosely formed in the Spring of 2001.
		Agile Modeling (AM) was first defined in the Autumn of 2000 and was published in March of 2002 as a book.
	www.agilemodeling.com /essays/proof.htm (1378 words)

	Agile Software Development and Project Management Online Resource Center
		Agile program management is the "glue" between IT strategy and the delivery of business value.
		My current agile team is geographically distributed throughout the US with members on the east coast, multiple west coast locations, and in Arizona.
		However, I contend that if you cannot have a collocated team, then agile methods are still the best way to run a distributed team.
	www.cutter.com /project (382 words)

	Agile Development Conference 2004 (Site not responding. Last check: 2007-11-07)
		Agile enablement is the process of changing a traditional business to work in an agile way.
		A list of agile testing practices (or patterns, rules of the game, whatever is the best way to express them) would guide us and other agile testers in the way XP practices guide XP teams.
		This deficit is an excellent opportunity for the Agile community, with its emphasis on rapid delivery - which requires skilled testing - to assist those who are already committed to strengthening academic testing programs, and influence these programs to foster the testing knowledge and skills most valuable to Agile projects.
	www.agiledevelopmentconference.com /schedule/peertopeer.html (1689 words)

	Secrets of lightweight development success, Part 5: Agile development at conservative companies (Site not responding. Last check: 2007-11-07)
		Agile methods strip away unneeded process until you're left with just enough to get the job done.
		When you're trying to inject an agile process into a conservative company as a programmer or architect, it's best to stay away from dogma -- that is, keep the focus on principles rather than process.
		Agile process and conservative companies don't have to be like oil and water (or canoes and kayaks).
	www.ibm.com /developerworks/java/library/os-lightweight5/index.html (1918 words)

	Agile Modeling (AM) Home Page: Effective Practices for Modeling and Documentation
		Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems.
		Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner.
		As you see in Figure 1 AM is meant to be tailored into other, full-fledged methodologies such as XP or RUP, enabling you to develop a software process which truly meets your needs.
	www.agilemodeling.com (109 words)

	Software engineering (Site not responding. Last check: 2007-11-07)
		Successful projects where software engineering methods have been applied include Linux, the space shuttle software, and automatic teller machines.
		Aspect-oriented programming and agile methods are important emerging SE technologies and practices.
		Agile software development guides software development projects that evolve rapidly with changing expectations and competitive markets.
	www.brainyencyclopedia.com /encyclopedia/s/so/software_engineering.html (1472 words)

	Knowing and Doing: April 2005 Archives
		One of the beauties of the agile programming practices is their demonstration of programmers' willingness to be held accountable for their time and their efforts.
		Graham is not an "agile guy", and from my reading of him I'd guess he's a bit suspicious of all the hype around agile methods.
		After teaching Agile Software Development to university juniors and seniors last semester for the second time, and introducing test-driven design early in CS II this semester, I am coming to a deeper appreciation for how much agile methods require a change in deeply-rooted habits.
	www.cs.uni.edu /~wallingf/blog/archives/monthly/2005-04.html (7913 words)

	Agile Development Conference 2003: Free XP Book (Site not responding. Last check: 2007-11-07)
		ThoughtWorks is widely recognised as the a leader in Enterprise Agile: the practical application of Agile methods for large enterprises.
		Agile Development Conference was endorsed by the AgileAlliance and supported by Thoughtworks Australia.
		He writes the column, "An Introduction to Agile Methods", for ZDNet Australia, has contributed to "Extreme Programming Applied" by Ken Auer and Roy Miller, and "Pair Programming Illuminated" by Laurie Williams and Robert Kessler and is the founder of Melbourne-based Khatovar Technology.
	www.softed.co.nz /adc2003 (705 words)

	IA THINK: Digging Deeper Into Agile Methods
		One thing I stated I particularly liked about John Armitage's article in Interactions was how it uses the creation of a painting to illustrate three common approaches to software development: ad-hoc, agile methods, and so-called “heavy” methods.
		In this analogy, agile methods are depicted as a painting that is created by a series of small, very high fidelity squares.
		I agree with the image of the “rough cartoon first”--at least in the case of XP, the agile method with which I'm most familiar.
	www.iathink.com /2004/02/digging_deeper_.html (685 words)

	Agile methods and torpid programmers -- Some observations on troublesome terminology (Site not responding. Last check: 2007-11-07)
		Promoters of Extreme Programming (XP) and some other iterative and incremental approaches to software development have coined and tried to preempt the term "agile" to describe both their methodology and its practitioners.
		Willingness to investigate, learn, and try new methods, tools, and techniques, especially in the face of difficulty or obstacles in applying familiar ones.
		What I do is agile in every sense of the term, in some ways more so than what the extremists propose, and I'm not giving it up.
	www.idinews.com /agile.html (385 words)

	Agile methods for software development and project management (Site not responding. Last check: 2007-11-07)
		Agile does not reflect a single approach rather it represents a series of practices developed by different individuals and organisations.
		Agile approaches to software development can in turn be applied to all levels of business processes.
		One of the major criticisms of Agile methods is their ability to scale with a large organisation or across multiple organisations such as contractors.
	www.acs.org.au /act/events/2002_events/synop.html (829 words)

	Agile Alliance :: index_html
		The Agile Alliance is a non-profit organization that supports individuals and organizations who use agile approaches to develop software.
		Driven by the simple priorities articulated in the Manifesto for Agile Software Development, agile development approaches deliver value to organizations and end users faster and with higher quality.
		If you're wondering what agile software development is, start here.
	www.agilealliance.com (239 words)

	MF Bliki: IsAgileForAll
		I've often heard the claim that agile methods can only be used by the better developers and that average or below average developers should avoid agile methods.
		Self adaptation is required to change the process, many agile techniques focus on honing skill levels.
		I think this must mean that an effective agile team need to have some people who are of higher-ability.
	martinfowler.com /bliki/IsAgileForAll.html (406 words)

Try your search on: Qwika (all wikis)