Generally speaking, Agile development works together with relatively few, very briefly defined specifications in the form of user stories. Agile’s requirements usually are in the form of user stories, which by definition are very brief and comparatively few in the number in keeping with Agile’s focus on just the work to be done in the near term. User story acceptance QA tests also tend to be restricted to the small user story, which is closest in scope or objective to integration software tests. Agile tends not to devote much attention to software develop. Instead Agile usually limits its attention to the individual small pieces of code implementing particular features, often without necessarily addressing the designhow those features fit together with each other and with other components. Consequently, typical agile software development often lacks system QA and testing. Not surprisingly, such lack of develop can cause agile development upstream difficulties when the