M1 Task Plans and Outcomes

• Instructions
• Grading Rubric

Instructions

Prior to the start of the Milestone M1 development iteration, the team must work together to create for each team member a set of task plans. The task plans specify the coding work that each team member is expected to complete during the M1 iteration and must be documented in the team’s backlog document.

Scenario-Implementation Tasks. The M1 task plan for each team member must comprise a set of user scenarios from the team’s backlog to implement by the end of the M1 iteration. To successfully implement a scenario, all the features required to enact the scenario in the app must be fully completed. It is assumed that error-handling will also be completed although not explicitly depicted in the scenario.

• 10-Hour Minimum per Team Member. Each team member must plan scenario-implementation tasks that total at least 10 hours of work for Milestone M1.
• 3-Scenario Minimum per Team Member. Each team member must be assigned at least 3 scenarios to implement.
• No Shared Task Assignments. Do not assign a scenario-implementation task to more than one team member. Although team members are encouraged to collaborate, the responsibility for completing a particular task must lie with one and only one team member. Teammates who assist on a task can be credited in the pull request.
• Other Work Assumed. It is assumed that each team member will have additional work beyond just their scenario-implementation tasks to perform for M1 (e.g., demo-video creation, code reviewing).

List of Planned Code Changes. For each scenario-implementation task assigned to each team member, the team member must document a list of the anticipated code changes required to complete the task:

• Code Artifacts to Include. Include all anticipated changes (create, modify, or remove) regarding the following types of code artifacts.
  • Model classes
  • Model class associations
  • Routes
  • Controllers
  • View templates
• Page Items. For page-implementation subtasks, you may list the route, controller, and view template as a single list item.
• Other Code Artifacts. It is expected that other code artifacts beyond those listed above may need to included in the list of planned code changes.
• Iterate between Task Assignment and Code Change Planning. Planning the list of code changes may change the team’s assessment of how long a task will take. It is expected that, in creating the task plans, there may be some back and forth between updating the assignments and filling out the planned code changes.
• Plan together to prevent redundancy. The same artifact changes should not be listed in multiple task plans. The team must work together to decide who will make the change, so that the other tasks can assume the change was already made.

Task-Plan Formatting. In your team’s backlog document, the task plans must be specified and formatted as follows:

• Milestone: Be sure to indicate the milestone for which the task is planned.
• Assigned to: The name of the team member who is responsible for completing the task.
• Planned Code Changes: The list of anticipated code changes required to complete the task.

To clarify what is expected, here is an example backlog with user stories, scenarios, and task plans.

Grading Rubric

Grade Requirements. Minimum requirements to earn each grade:

• Pass:
  • 75% of provided task plan content is clear and followed instructions.
  • For each team member, there are tasks assigned that amount to at least 75% of the quantity of work expected.
  • 75% of expected task outcomes are reported and followed reporting instructions.
• Fail:
  • Fails to meet requirements for Pass.