Agile Modelling, Diciplined Agile Delivery, Roles in the Modeling Process
"Agility" is an often used Buzz Word. Whether in connection with agile development, agile companies or agile modeling. The slogan expresses that organizations are able to respond quickly to changing conditions. Agile approaches - Scrum, XP, SAFe - do not favor role definitions. However, the skills and knowledge in the model development process are so diverse today (process modeling and analysis, decision modeling and analysis, risk assessments, etc.). It is not possible to master all skills equally well. But we still expect employees to keep track of everything and have a holistic understanding. Scott Ambler speaks of "Generalizing Specialists." in this context
"Disciplined Agile Delivery" defines various roles in the team (Mark Lines, Scott Ambler: Introduction to Disciplined Agile Delivery) (a hybrid framework that incorporates various agile approaches) defines different roles. The framework differentiates between "Primary Roles" (necessary in every project) and "Secondary Roles" (depending on the project). See "Roles on DAD Teams".
DAD focuses on software development first. Modeling is an important part of the lifecycle. I have adopted the roles a bit to the realities in (agile) modeling projects. For the definition of roles, I see different possibilities. To structure according to content and delegate tasks and responsibilities to sub-roles of the model owner (e.g., model owner brewer, model owner logistics, ...). Another possibility is to distinguish between the used presentation means used (e.g., model owner process models, model owner decision models, model owner risk models, ...). The separation can be done according to the area of tasks (model owner ISO certification, model owner GDPR, ..).
Based on the role definitions in DAD, I suggest the following roles in a modeling project team:
|Responsible for the models and the structure in our project
Can delegate sub-responsibilities
(e.g. Model Owner Logistic, Model Owner ISO-Certification)
|Defines the Business Architecture
Defines Content and notations used
Defines the relationships between the Architecture Elements
|Business Process Analyst
Responsible for the description of the business process models
|Decision Analyst (Specialist)
Secondary role (if decision management is needed)
|Responsible for the description of operational decision models
Determines the notations to be used (DMN, TDM) and additional descriptions (OMI, others)
Defines the decision patterns for reuse in the enterprise
|Domain Expert/SME||Provides information about business processes and decisions.
Checks the quality of implementation in formal models.
|Model Tester / Validator
|Checks the model quality|
|Tool Specialist||Teaches the knowledge necessary for the tool used.
Provides the implementation of the style guide and modeling guideline and the architect owner's definitions in the tool
Following additional explanations:
The role of "Architecture Owner" is copied from DAD. The presentation of different perspectives, abstractions and views requires a business architecture.
I newly defined the role of "Tool Specialist". Today's tools require knowledge and skills to adapt to our needs.
I look forward to feedback for this post.
Disliplined Agile Delivery
Model-Based Business Engineering