Content deleted Content added
Praxidicae (talk | contribs) Reverted to revision 869439469 by ScottWAmbler (talk): Rst. (TW) |
Niceguyedc (talk | contribs) m v2.0 - Repaired 1 link to disambiguation page - (You can help) - Scrum |
||
Line 17:
# Iteration modeling. When a requirement/work item has not been sufficiently explored in detail via look-ahead modeling they 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]].
# Model storming. A short, often impromptu, agile modeling session. Model storming sessions are held to explore the details of a requirement or aspect of your design.
# Multiple models. Agile modelers should know how to create a range of model types (such as user stories, story maps, data models, [[Unified Modeling Language]] (UML) diagrams, and more) so as to apply the best model for the situation at hand.
| |||