AH
So this is a technicality and I can do my model just fine, but I was hoping for a quick clarification.
In ARIS 10 - there is a Work Breakdown Structure model. The objects are:
Function, Task, Program, Requirement, Project
But for a WBS to be "correct" I would need an object that represents a deliverable (a noun). Not an action.
I don't seem to see that type of object in the model. Of course I can get by with Function -> Task to the same effect. But in my (limited) research this seems like the wrong type of objects for a "true" WBS.
Thoughts?
Adam Hulse
Hi Adam,
The WBS primarily is concerned with the hierarchy of tasks. You add all the details on the tasks in Task allocation diagrams you assign to each task. The WBS model would be overloaded with information. So hot candidates for deliverables are all symbols representing Information Carriers, such as "Document". I could imagine you would take into consideration the object type "Product/Service" for deliverables, however they are not available in the standard method configuration of Task allocation diagram. I would assume that Information carrier is more adequate, because "Product/Service" describes a typification of standardized artifacts produced regularly (in many instances of a business process), while the artifacts you produce in a project are produced once and only once. The deliverable has got some media shape. You would use the actual deliverable (file) name there.
Another consideration: You might have someone being responsible for the entire WBS (or some project WBS) and many owners of the tasks. The task allocation diagram gives the owners of the tasks the opportunity to define their deliverables and other things they want to model in the context of each task.
"The WBS primarily is concerned with the hierarchy of tasks"
See - that's what I thought. And the WBS ARIS model seems to support that.
But when I was doing research about WBS, I kept seeing that its not focused on tasks, but deliverables. Tasks (verb+ noun) is used for a Task Allocation diagram or a Schedule model (example: Microsoft Project).
Note: Information Carrier is not available for the WBS model.
I will probably use the Task Allocation Model, but from this conversation, I'm guessing that the WBS model is incomplete for ARIS 10.
Thanks
Adam
Hi Adam,
you have two options.
- Use a task allocation diagram for each task (or project, program) to add the details such as documents, information carriers etc.
- Extend the ARIS method of the WBS model type with the details from the TAD that you want to see in the WBS.
Benefit of TAD:
You can delegate the responsibility for maintaining the details to the task owners, project managers etc. by giving them ownership of all TADs where they are responsible for the task/project/program.
Regards, M. Zschuckelt
