Each software engineering action (Communication, Planning, Modeling, etc) can be represented by a task set, or series of tasks to do to complete the action.
Depending upon the size of the project, and the needs of the project, the number of task could vary.
When doing initial communication, a small project with a single stakeholder might be conducted via an informal meeting in an office.
A medium project might need several stakeholders with several meetings both individually and collectively until a process is ready to be rolled out.
Large projects might need a series of meetings, interviews with individual stakeholders, meetings for revisions, defining time lines, etc.
With each action, this will be true, and it makes the “engineering” part difficult as there is no such formal definition for what is small, medium, or large, nor for the specific tasks.
Company culture and the type of tasks being done may play a big part in the correct way to handle things, which is why it is important to go over projects at the end to determine what should continue, and what should be changed to make them work more effectively.
Identifying a Task Set was originally found on Access 2 Learn
