Agile is not a methodology, it's a family of product development approaches. While it is possible to apply MBSE methods within an Agile approach, this requires modification of the definition of a user story to better align with UML use cases, and traceability from MBSE artifacts to backlog items and class implementations (e.g. the code). At present, there is a lack of integration between MBSE and Agile process tools to achieve this effectively. This needs to be addressed. Moreover, the fixed-length Agile sprints (typically 2 weeks) do not align well with the variable complexity of the goal-oriented use cases that most directly define value from user's perspective. In general, Agile is better suited to lower-complexity systems with largely independent features. There are a myriad of other iterative and incremental process models that can be tailored to suit the specific needs of a given program.
Agile is not a methodology, it's a family of product development approaches. While it is possible to apply MBSE methods within an Agile approach, this requires modification of the definition of a user story to better align with UML use cases, and traceability from MBSE artifacts to backlog items and class implementations (e.g. the code). At present, there is a lack of integration between MBSE and Agile process tools to achieve this effectively. This needs to be addressed. Moreover, the fixed-length Agile sprints (typically 2 weeks) do not align well with the variable complexity of the goal-oriented use cases that most directly define value from user's perspective. In general, Agile is better suited to lower-complexity systems with largely independent features. There are a myriad of other iterative and incremental process models that can be tailored to suit the specific needs of a given program.
well stated.
Good presentation. Can we get an update if the models have been able to replace the CDRLs as stated at 32:58?
Outstanding content!!
Interesting. Thank you
nice work