AN ANALYSIS OF RAPID TECHNOLOGY TRANSFER SOLUTIONS ANDBEST PRACTICES FOR USE BY THE DEPARTMENT OF DEFENSE. Decision Support Systems - Acceptance of agile methodologies: A critical review and conceptual framework. Volume 46, Issue 4, March 2009, Pages 803–814 IT Decisions in Organizations Edited By James Y.L.
Changing the paradigm of software engineering. SCRUM_AND_CMMI_MAPPING-1. Best Practices for Agile/Lean Documentation. Ideally, an agile document is just barely good enough, or just barely sufficient, for the situation at hand.
Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall project risk and therefore strive to be as efficient as possible when it comes to documentation.
Agilists write documentation when that's the best way to achieve the relevant goals, but there often proves to be better ways to achieve those goals than writing static documentation. This article summarizes common "best practices" which agilists have adopted with respect to documentation. Best practices for increasing the agility of documentation: Agile Modeling: Effective Practices for XP and RUP. Overview Agile Modeling (AM) is a chaordic, practice-based methodology for effective modeling of software-based systems.
The AM methodology is a collection of practices – guided by principles and values – that are meant to be applied by software professionals on a day-to-day basis. AM is not a prescriptive process, in other words it does not define detailed procedures for how to create a given type of model, instead it provides advice for how to be effective as a modeler.