CSC/ECE 517 Fall 2016 E1676 Role-based reviewing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
== Purpose == | |||
In the current version of Expertiza, members among a team can evaluate each other’s contribution and give appropriate scores based on the same questionnaire. However, in the lifetime the software development, members in a team often take on different roles whose works content are vastly differentiated. Like in an agile development environment, such as Scrum, there are typically seven roles group members can take: software engineer, architect, programmer, analyst, QA expert, tester and UI designers. Job description and evaluation entailed are vastly varied among these roles, thus a generic assessment rubric cannot hold reasonably. | |||
== Task Description== | == Task Description== | ||
===Rationale of using Scrum & Role based reviewing === | ===Rationale of using Scrum & Role based reviewing === | ||
Revision as of 01:31, 9 November 2016
Purpose
In the current version of Expertiza, members among a team can evaluate each other’s contribution and give appropriate scores based on the same questionnaire. However, in the lifetime the software development, members in a team often take on different roles whose works content are vastly differentiated. Like in an agile development environment, such as Scrum, there are typically seven roles group members can take: software engineer, architect, programmer, analyst, QA expert, tester and UI designers. Job description and evaluation entailed are vastly varied among these roles, thus a generic assessment rubric cannot hold reasonably.
Task Description
Rationale of using Scrum & Role based reviewing
Design
Database Design
Updates
Below are the key files modified: