Agile modeling: Difference between revisions

Revision as of 08:38, 21 May 2020

Revision as of 12:20, 23 June 2020

Line 28:

# 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.

===Limitations===

There is significant dependence on personal communication and customer collaboration. Agile modeling disciplines can be difficult to apply {{Citation needed|date=October 2016}}:

There is a significant dependence on personal communication and customer collaboration. This limitation is similar to that faced in trying to apply principles of Agile in a distributed setting through [[Distributed Agile Software Development|Distributed Agile Software Development]]. Agile modeling disciplines can be difficult to apply <ref>{{cite web |website=classicinformatics.com

|url=https://www.classicinformatics.com/blog/getting-started-with-distributed-agile-development

|title=Getting started with Distributed Agile Development}}</ref>:

* On large teams (say 30 or more) without adequate tooling support

* Where team members are unable to share and collaborate on models (which would make [[agile software development]] in general difficult)

Line 48 ⟶ 45:

* [http://www.AgileModeling.com/ The Agile Modeling Home Page]

* [http://www.agileModeling.com/essays/amdd.htm Agile Model Driven Development (AMDD)]

* [https://www.classicinformatics.com/blog/getting-started-with-distributed-agile-development/ Getting started with Distributed Agile Development]

[[Category:Agile software development]]