Having a More Concise RAM #122
Closed
MucahitErdoganUnlu
started this conversation in
Ideas
Replies: 1 comment
-
After this discussion, the lecturer also pointed this out. Therefore, everybody agrees now |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Responsibility Assignment Matrix shows the responsibilities of the team members for certain tasks. For example, creating the project plan is a responsibility. This can be done in one row. For its subtasks, you can point your efforts in your issues and personal efforts page individually.
These two rows can be written in one row.
| Construct project plan | 🟨 | ⬜ | ⬜| ⬜| ⬜ | 🟨 | 🟩 | 🟨| ⬜ | ⬜ |
| Document the project plan | 🟨 | ⬜ | 🟩| ⬜| ⬜ | 🟨 | ⬜ | 🟨| ⬜ | ⬜ |
Another example: Mücahit, Emre, and Yunus are assigned to document the requirements. They divided this task into three subtasks: User requirements, system requirements, and non-functional requirements. They point to these subtasks on their personal efforts page but they have only one row for this task:
| Define requirements for the project | ⬜ | 🟩 | 🟨 | 🟩 | 🟩 | ⬜ | 🟨 | ⬜ | ⬜ | 🟨 |
Further, RAM should be used to indicate the division of labor. If everybody is required to perform a certain task, it shouldn't be on the RAM.
Suggestion: We can make use of RAM while we assign tasks during group meetings.
By following these guidelines, I believe we will have a more clear and concise RAM.
What do you guys think?
| 🟨 Contributor | Contributes to the task |
| 🟩 Reviewer | Reviews and gives feedback to the contributors |
Beta Was this translation helpful? Give feedback.
All reactions