Agile modeling: Difference between revisions

Revision as of 10:13, 26 October 2020

Revision as of 20:27, 9 December 2020

Line 20:

# Architecture envisioning. The team performs light-weight, high-level modeling that is just barely good enough (JBGE) at the beginning of a software project so as to explore the architecture strategy that the team believes will work.

# Inclusive tools. Prefer modelling tools, such as whiteboards and paper, that are easy to work with (they're inclusive).

# Iteration modeling. When a requirement/work item has not been sufficiently explored in detail via look-ahead modeling theythe team may choose to do that exploration during their iteration/sprint planning session. The need to do this is generally seen as a symptom that the team is not doing sufficient look-ahead modeling.

# Just barely good enough (JBGE). All artifact, including models and documents, should be just sufficient for the task at hand. JBGE is contextual in nature, in the case of the model it is determined by a combination of the complexity of whatever the model describes and the skills of the audience for that model.

# Look-ahead modeling. An agile team will look down their backlog one or more iterations/sprints ahead to ensure that a requirement/work item is ready to be worked on. Also called "backlog grooming" or "backlog refinement" in [[Scrum (software development)|Scrum]].