
	Where results make sense

Topic: Agile methods, when to use

Related Topics

Extreme Programming

Methodology (software engineering)

	Agile software development - Wikipedia, the free encyclopedia
		Initially, agile methods were called "lightweight methods." In 2001, prominent members of the community met at Snowbird and adopted the name "agile methods." Later, some of these people formed The Agile Alliance[2], a non-profit organization that promotes agile development.
		Agile methods are sometimes characterized as being at the opposite end of the spectrum from "plan-driven" or "disciplined" methodologies.
		Agile methods differ from iterative methods in that their time period is measured in weeks rather than months and work is performed in a highly collaborative manner.
	en.wikipedia.org /wiki/Agile_programming (3719 words)

	The New Methodology
		Agile methods assert that no process will ever make up the skill of the development team, so the role of a process is to support the development team in their work.
		Agile methods seek to take advantage of this, encouraging business people to learn about their needs as the system gets built, and to build the system in such a way that changes can be incorporated quickly.
		Agile methods are still too young to see enough action to get a sense of where the boundaries are.
	www.martinfowler.com /articles/newMethodology.html (8929 words)

	Agile Requirements
		Agile methods are all built around a key assumption — we continue to learn about a system and it’s operating environment during the project.
		Agile methods iteratively evolve both requirements and the system under development by planning the development in short cycles (weeks rather than months).
		Other agile methods do not explicitly use stories but also emphasis that requirements descriptions need to be short and loose, the bare-minimum needed to plan development.
	www.methodsandtools.com /archive/agilereq2.php (1189 words)

	InfoQ: Agile Alliance Survey: Are We There Yet?
		Agile, and the recognition of the need for methods that respond to market changes and deliver faster, is showing up in places where no one expected it, like on mission critical projects (NASA and military applications) and other government-regulated processes (e.g., the V-Model XT in Germany).
		Agile methods are no longer considered the approach of last resort in a crisis, but more often turned to as the first choice for rapid, responsive, accurate development.
		Agile is scaling along a number of dimensions: geographic distribution and global development, number of collaborations with suppliers, combined hardware/software projects including and beyond embedded software, team size, project size, mission criticality, and involvement with legacy systems.
	www.infoq.com /articles/agile-alliance-survey-2006 (5890 words)

	Requirements Engineering in Agile Processes
		Agile Methods methods requires interaction with the user during development, but in CSE the analysts are the only ones involved during development.
		Agile methods don't allow for too much planning because the idea is to get the software done as quick and as economiclly as possible, while QFD takes time to evaluate the market, the competitors, and the customer's needs.
		Agile methods provide instructions for the entire software life cycle, while JAD is used mostly in the requirements elicitation and analysis.
	pages.cpsc.ucalgary.ca /~jadalow/seng613/agile_summary.html (1231 words)

	Dr. Dobb's \| Scaling Agile Methods \| September 4, 2002
		Agile methods have introduced new practices, such as pair programming, while discarding some old ones.
		Using XP methods, project teams were more enthusiastic and eager.
		Traditional methods assume fairly static requirements and impose high cost burdens because of the high volume of processes and people needed to complete a task.
	www.ddj.com /dept/architect/184411706 (1428 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)

	Mistaeks I Hav Made: Agile Development Archives
		Like many that use pair programming, the teams I work on often use pair stairs to track who pairs with whom and to ensure that each member has paired with all others.
		Agile methods try to use meaningful identifiers as much as possible to reduce comment noise and to ensure that human readable text is always kept up to date.
		Perhaps a narrative database would be a useful tool for collecting user stories at the start of an agile project before pulling out or synthesising "archetypal" stories to act as system requirements.
	nat.truemesh.com /archives/cat_agile_development.html (1590 words)

	First eWorkshop on Agile Methods
		The type of personnel needed for Agile projects and their role in the success of the agile development was another topic discussed during the meeting.
		Despite the perception that agile methods are obviously beneficial, some participants (Philip Johnson and Alistair Cockburn) felt that there is a need for proper validation (especially for late adopters) and suggested possible studies.
		It would be great to say that we followed an agile methodology group and document that it achieved a highly dependable real-time system (or whatever it is that objectors argue against agile ever being able to reach.
	fc-md.umd.edu /projects/Agile/Summary/SummaryPF.htm (4614 words)

	Agile Methods Incompatible with Human Psychology? at Technoetic
		Other agile methods, like XP, tend to focus more on development practices but even XP is doomed if it’s attempted in a highly dysfunctional organization.
		Agile methods definitely do not say that forward motion in a cloud of confusion is all that matters.
		Because iterative development methods were used with each part of the system independently designed without a broad view of the full requirements.”The phrase “independently designed” sounds like a euphemism for designed with ineffective communication between the developers.
	blog.technoetic.com /2006/09/11/agile-method-criticism (934 words)

	Agile Development Methodologies For DBAs (Site not responding. Last check: 2007-11-03)
		Ever since an old colleague of mine mentioned that his Oracle development team were using Scrum, an agile development methodology, to run and plan their projects, I've been looking out for an opportunity to use agile methods in my line of work.
		Of course, the added complication when working on consulting engagements is that whilst agile methods may suit the customer well (in that requirements are driven out iterativelty, and development goes on as long as value is being delivered) the client also almost always wants a fixed price, and a fixed delivery date.
		Certaintly, the situation described in the article (where a DBA is on call anyway, and the question is more about how best to spend their time) is probably better suited to agile methods than when you're on a fixed-price, fixed-duration project for a client.
	www.dba-oracle.com /oracle_tips_rittman_agile_develop_method.htm (429 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 (1027 words)

	Application Development Trends - An agile approach to rocket science
		Unlike heavy or process-centric methodologies, agile methods focus on smaller units of work and tight team development as a way of coping with the inherent unruliness of software.
		Agile methods, such as the popular eXtreme Programming, emphasize principles over process, increase developer-customer interactions, and reduce the length of development and feedback cycles.
		The judges cited the team for its use of agile methods in a large, complex project; its 'open-minded' approach to development; and its ability to put new development-customer relations in place.
	www.adtmag.com /article.asp?id=10093 (758 words)

	Agile Journal - Articles
		The numbers are growing: over 1100 people attended the Agile 2006 conference in Minneapolis; over 15,000 people participate in Yahoo groups on topics including general Agile development, XP, Scrum, and Agile management (although many belong to more than one group); 700 Agile developers responded to the VersionOne study with their perspectives; and so on.
		Agile development continues to gain traction in enterprise IT organizations, but myths and misconceptions slow the pace of acceptance and preclude the use of Agile methods in situations where they could otherwise add significant value.
		Part of the issue is the simplicity of its philosophy as stated in the Agile Manifesto, which leaves plenty of room for (mis)interpretation and leads to myths such as Agile is anti-documentation.
	www.agilejournal.com /content/blogsection/4/76 (1449 words)

	STSC CrossTalk - Extending Agile Methods:A Distributed Project and Organizational Improvement Perspective - May 2005 (Site not responding. Last check: 2007-11-03)
		Agile architecture is similar to User Stories in that it represents a commitment to talking to solve detailed architecture issues collaboratively with the agile teams during each iteration.
		If an agile team finds itself working 80-hour weeks, this is a sign that they may not be accurately measuring their velocity, or they are not controlling their work tasks, or they are not communicating effectively the real status up the chain.
		Agile is not about customers living without all requirements; it is about breaking through to the grassroots level, making real status visible and acted upon sooner, which ultimately provides greater value to the customer.
	www.stsc.hill.af.mil /crosstalk/2005/05/0505mcmahon.html (3817 words)

	White paper on agile programming management and development
		Agile Management and Development Method is one of a growing number of alternatives to traditional, process-centric software management methods with a focus on people, results, minimal methods and maximum collaboration.
		Common examples are “use case modelling sessions”, “class modelling sessions”, or “data modelling sessions.” The root cause of this problem is typically “one artefact developers” such as people specialized in data modelling or user interface modelling – with Agile Method generalists should be leading the effort.
		Agile development methods are very pragmatic in understanding the fact that requirements in a business environment changes constantly.
	www.projectperfect.com.au /info_agile_programming.php (2983 words)

	Using Agile Processes and Modeling To Build Enterprise Applications
		On the technical (design) side of agile development, we can use an informal, high-level architecture to give us a sense of the enterprise application being built, enough to move forward with the first couple of iterations.
		I would recommend using these merely as guidelines because when process, models, or documentation become your goal, you are losing sight of what really matters, the customer you are building the application for.
		The idea behind Agile Draw is to use the simplest tools possible and keep the notation to a bare minimum (for example, there are only three core shapes: circles, boxes, and lines).
	dev2dev.bea.com /pub/a/2006/05/agile-modeling.html?page=last (880 words)

	Merging Agile with Use Case best practices
		Agile development processes are proving themselves to be effective.
		The answer is to combine the iterative nature of agility with incremental development of use cases.
		He is certified by both Cockburn and Associates to teach “Writing Effective Use Cases” and Advanced Development Methods as a Scrum Master.
	www.geocities.com /chicago_spin/meet0410.html (428 words)

	Object Technology Jeff Sutherland: Pump Up Your Stock Options With Agile Methods!
		This is because hard evidence of the economic benefits of using agile methods for developing Internet products isn’t the only reason executives and managers may benefit from this study.
		Firms may simply benefit from exploiting the use of agile methods in marketing activities, business development proposals, and in their advertising.
		In other words, merely saying a firm is committed to the use of agile methods may result in more business partnerships, more sales leads, and more contracts for Internet products and services, regardless of the actual commitment to the use of agile methods.
	jeffsutherland.com /2005/08/pump-up-your-stock-options-with-agile.html (532 words)

	XP Agile Universe - The premier conference on Agile software development processes.Setting the Agile Context (Site not responding. Last check: 2007-11-03)
		The use of agile software methods requires a proper context.
		In this talk, Watts Humphrey discusses the environmental characteristics required for complex creative work, how the working situation is typically established, and what the software professional can do to influence the context of his or her work.
		Humphrey discusses the factors that determine the ability of professionals to set the contexts for their own work and how this relates to the use of agile methods.
	www.xpuniverse.com /2002/schedule/whagilecontext (162 words)

	Service-oriented agility: use agile methods for successful SOA development, part 1: basics of SOA an (Site not responding. Last check: 2007-11-03)
		The elemental services, used by the service choreography layer and also by user interface applications, are implemented by service applications.
		Agile software development started to take off during the late 90s when Kent Beck promoted "Extreme Programming" with a set of values, principles and practices for planning, coding, designing and testing software.
		In February 2001, the Agile Manifesto was defined, valuing individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
	www.developers.net /external/1050?pager=4856 (737 words)

	Kevin Aguanno - Ever-Changing Requirements? Use Agile Methods to Reduce Project Risk
		Use Agile Methods to Reduce Project Risk." Here is what some of our delegate had to say about his session:
		Managing Agile Projects - The business benefits behind agile development methods and the insider secrets of how to manage such projects from those who developed the methods.
		Agile Project Management Using Scrum - Background on the Scrum methodology and how it can be applied on development projects to reduce risk, improve quality, and improve stakeholder satisfaction.
	www.mmpubs.com /aguanno/topic6.html (521 words)

	Agile Sussex (Site not responding. Last check: 2007-11-03)
		Our mission is to encourage Agile methods in software development in Sussex, helping development teams be more productive, bring valuable software to customers faster, be responsive to change, and cultivate a good working environment.
		Encourage the use of agile methods in practice.
		Agile Sussex is a specialist group of BCS Sussex, the local branch of the British Computer Society.
	c2.com /cgi/wiki?AgileSussex (133 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)

	Agile Methodologies Programming Computers
		An Agile New Year's Resolution for All of UsDr.
		it is not clear yet whether agile methodologies -- or even the concept of agile software development in general -- is going to succeed in the long term.
		Getting Agile with MS VSTS for Database ProfessionalsInfoQ.com, Canada - Dec 13, 2006Practices and tooling for database testing and refactoring were poor or non-existent in the early years of Agile methodologies.
	www.iaswww.com /ODP/Computers/Programming/Methodologies/Agile (708 words)

Try your search on: Qwika (all wikis)