M1 Task Plan - M0 Activity

Step 1: Assign tasks to team members

Scenario-Implementation Tasks. Each team member must be assigned a set of scenarios to implement for Milestone M1. 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 three 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).

Step 2: Plan code changes for each task

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 line item. For page-implementation subtasks, you may mention the route, controller, and view template in a single line 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

Your team’s 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.