fbpx
Wikipedia

Agile unified process

Agile unified process (AUP) is a simplified version of the 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 (AM), agile change management, and database refactoring to improve productivity.

In 2011 the AUP accounted for one percent of all the agile methodologies used.[2] In 2012 the AUP was superseded by disciplined agile delivery (DAD). Since then work has ceased on evolving AUP.

Discipline Edit

Unlike the RUP, the AUP has only seven disciplines[citation needed]:

  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.
  2. Implementation. Transform model(s) into executable code and perform a basic level of testing, in particular unit testing.
  3. Test. Perform an objective evaluation to ensure quality. This includes finding defects, verifying that the system works as designed, and validating that the requirements are met.
  4. Deployment. Plan for the delivery of the system and to execute the plan to make the system available to end users.
  5. Configuration management. Manage access to project artifacts. This includes not only tracking artifact versions over time but also controlling and managing changes to them.
  6. 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.
  7. 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.

Philosophies Edit

The Agile UP is based on the following philosophies [3]

  1. Your staff know 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.
  2. Simplicity. Everything is described concisely using a handful of pages, not thousands of them.
  3. Agility. The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance.
  4. Focus on high-value activities. The focus is on the activities which actually count, not every possible thing that could happen to you on a project.
  5. Tool independence. You can use any toolset that you want with the Agile UP. The recommendation is that you use the tools which are best suited for the job, which are often simple tools.
  6. You'll want to tailor the AUP to meet your own needs.

Releases Edit

The agile unified process distinguishes between two types of iterations. A development release iteration results in a deployment to the quality-assurance and/or demo area. A production release iteration results in a deployment to the production area. This is a significant refinement to the rational unified process.

 

See also Edit

References Edit

  1. ^ Waters, John K (28 February 2008). "Agile lands role in games and business software". The Register. Retrieved 2009-08-03.
  2. ^ . Archived from the original on 2015-07-17. Retrieved 2014-06-26.
  3. ^ Ambler, Scott. . Ambysoft. Archived from the original on 8 August 2019. Retrieved 21 December 2015.

External links Edit

  • AmbySoft Agile Unified Process page 2019-08-08 at the Wayback Machine
  • Scott Amber's Dr Dobbs article "Where Did All the Positions Go?"

agile, unified, process, this, article, needs, additional, citations, verification, please, help, improve, this, article, adding, citations, reliable, sources, unsourced, material, challenged, removed, find, sources, news, newspapers, books, scholar, jstor, au. This article needs additional citations for verification Please help improve this article by adding citations to reliable sources Unsourced material may be challenged and removed Find sources Agile unified process news newspapers books scholar JSTOR August 2009 Learn how and when to remove this template message Agile unified process AUP is a simplified version of the 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 AM agile change management and database refactoring to improve productivity In 2011 the AUP accounted for one percent of all the agile methodologies used 2 In 2012 the AUP was superseded by disciplined agile delivery DAD Since then work has ceased on evolving AUP Contents 1 Discipline 2 Philosophies 3 Releases 4 See also 5 References 6 External linksDiscipline EditUnlike the RUP the AUP has only seven disciplines citation needed 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 Test Perform an objective evaluation to ensure quality This includes finding defects verifying that the system works as designed and validating that the requirements are met 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 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 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 Philosophies EditThe Agile UP is based on the following philosophies 3 Your staff know 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 Simplicity Everything is described concisely using a handful of pages not thousands of them Agility The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance Focus on high value activities The focus is on the activities which actually count not every possible thing that could happen to you on a project Tool independence You can use any toolset that you want with the Agile UP The recommendation is that you use the tools which are best suited for the job which are often simple tools You ll want to tailor the AUP to meet your own needs Releases EditThe agile unified process distinguishes between two types of iterations A development release iteration results in a deployment to the quality assurance and or demo area A production release iteration results in a deployment to the production area This is a significant refinement to the rational unified process See also EditEnterprise unified process Unified processReferences Edit Waters John K 28 February 2008 Agile lands role in games and business software The Register Retrieved 2009 08 03 State of Agile Development Survey Results 2011 VersionOne Archived from the original on 2015 07 17 Retrieved 2014 06 26 Ambler Scott The Agile Unified Process AUP Ambysoft Archived from the original on 8 August 2019 Retrieved 21 December 2015 External links EditAmbySoft Agile Unified Process page Archived 2019 08 08 at the Wayback Machine Scott Amber s Dr Dobbs article Where Did All the Positions Go Retrieved from https en wikipedia org w index php title Agile unified process amp oldid 1168899021, wikipedia, wiki, book, books, library,

article

, read, download, free, free download, mp3, video, mp4, 3gp, jpg, jpeg, gif, png, picture, music, song, movie, book, game, games.