Recommended
More Related Content
What's hot
Viewers also liked
Viewers also liked (13)
Similar to Derak project plan overview
Similar to Derak project plan overview (20)
Recently uploaded
Recently uploaded (20)
Derak project plan overview
- 1. Consumer Electronics Team – Session 5 Checkpoint B Daniel Anderson – dananderson17@gmail.com Raphael Brykman – raphaelbrykman2015@u.northwestern.edu Eric Gero – gero.eric@gmail.com Ketan Lakhani – ketan.lakhani@gmail.com Aaron Matthews – aaronmatthews2018@u.northwestern.edu Northwestern University Author Note Predict 480, Sec 55
- 2. File “DERAK Sprint – 1.xlsm” is an example of the project plan that will be used during the project. The project plan will allow the team to view and track the progress of tasks for each sprint, and is based on an Agile methodology and integrates the concepts of CRISP-DM. To prepare for the project, the team has met with the stakeholders and completed the Iteration 0 tasks of identifying and estimating stories. For this project, each sprint will be 14 calendar days, with weekends and holidays excluded from the available hours. Therefore, the team of 5 will have 400 hours available for each sprint. The “Sprint” tab lists all tasks assigned to the sprint. On this tab, tasks may be assigned to individuals and their progress tracked. The “Story Backlog” tab includes all stories that have been defined to-date. Currently, that includes Iteration 0 tasks, Iteration 1 tasks, and a portion of Iteration 2 tasks. This tab serves as the master log of all tasks. The “Analysis” tab contains burndown charts for the sprint. It also provides a breakdown of
- 3. hours worked versus hours remaining for each task. The “Capacity” and “Team Roster” tabs are used to list team members and define their capacity for the iteration. While the current spreadsheet works well for a sprint, it does not provide a complete view for the project from start to finish. To address this issue, several changes are being made. On the “Sprint” tab, a sprint column will be added. This will allow all tasks to be listed and tracked on the “Sprint” tab. A particular sprint may be viewed by applying a filter on that column. Currently, the project plan only allows one developer to work on a task at a time. To assign more than one developer to a task, the task must be listed multiple times, which inflates the hours required for the sprint and makes tracking the hours for that task difficult. A viable solution for this issue is being discussed. Since the “Analysis” tab only tracks progress for the current sprint, a new tab will be added to track progress for the entire project. The project level tab will be similar to the “Analysis” tab.