Revision as of 22:11, 9 November 2019 edit MrOllie (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 255,806 edits Added {{Notability}}, {{COI}} and {{Third-party}} tags (within {{multiple issues}}) tag to article (TW) ← Previous edit		Revision as of 22:12, 9 November 2019 edit undo MrOllie (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 255,806 edits →History: rm section of pure self promotion Next edit →
Line 27: # Prioritized requirements. Requirements should be worked on in priority order. # Requirements envisioning. The team performs light-weight, high-level modeling that is JBGE at the beginning of a software project to explore the stakeholder requirements. ~~==History==~~ The development of agile modeling was led by [[Scott Ambler]] starting in the autumn of 2000. It initially was called extreme modeling (XM) but at the suggestion of [[Robert Cecil Martin]] was renamed to AM in the spring of 2001. The book ''Agile Modeling'' <ref>[http://www.ambysoft.com/books/agileModeling.html Agile Modeling: Effective Practices for Extreme Programming and Unified Process]</ref> was published in 2002 by John Wiley Press. He also has a promotional web site.<ref>http://www.AgileModeling.com/ The Agile Modeling Home Page</ref> ==Limitations==

Agile modeling: Difference between revisions