Talk:Agile unified process

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.

Science

	Science portal This article is within the scope of WikiProject Science, a collaborative effort to improve the coverage of Science on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ScienceWikipedia:WikiProject ScienceTemplate:WikiProject Sciencescience articles
???	This article has not yet received a rating on the project's importance scale.

Agile Software Development vs. Agile Unified process[edit]

What is the relation between Agile software development and Agile Unified Process ?!!!

Style[edit]

I would like to know what is the difference between AUP and RUP? Avoid using 2nd-person: "you", "your". Icky style.

From further down in the article....

Agile Unified Process (AUP) is a simplified version of the IBM Rational Unified Process (RUP) developed by Scott Ambler.[1] It describes a simple, easy to understand approach to developing business application software using agile techniques and concepts yet still remaining true to the RUP. The AUP applies agile techniques including test driven development (TDD), Agile Modeling, agile change management, and database refactoring to improve productivity.

Unlike the RUP, the AUP has only seven disciplines: 1. Model. Understand the business of the organization, the problem domain being addressed by the project, and identify a viable solution to address the problem domain. Implementation. Transform model(s) into executable code and perform a basic level of testing, in particular unit testing. 2. Test. Perform an objective evaluation to ensure quality. This includes finding defects, validating that the system works as designed, and verifying that the requirements are met. 3. Deployment. Plan for the delivery of the system and to execute the plan to make the system available to end users. Configuration Management. Manage access to project artifacts. This includes not only tracking artifact versions over time but also controlling and managing changes to them. 4. Project Management. Direct the activities that take place within the project. This includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people and systems outside the scope of the project to be sure that it is delivered on time and within budget. 5. Environment. Support the rest of the effort by ensuring that the proper process, guidance (standards and guidelines), and tools (hardware, software, etc.) are available for the team as needed. — Preceding unsigned comment added by Goldsrm13 (talk • contribs) 19:14, 5 January 2012 (UTC)[reply]

There is bad missmatch in discipline and philosophy.. this is far from agile manifesto...[edit]

I don't see how these two things fit to same page / process:

Disciplines: 6. Project Management. Direct the activities that takes place within the project. This includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people and systems outside the scope of the project to be sure that it is delivered on time and within budget.

and

Philosophy: 1. Your staff knows what they're doing. People are not going to read detailed process documentation, but they will want some high-level guidance and/or training from time to time. The AUP product provides links to many of the details, if you are interested, but doesn't force them upon you. —Preceding unsigned comment added by 83.150.125.125 (talk) 09:56, 20 August 2010 (UTC)[reply]