Intention: We are open to how you want to create and maintain your RAF, wiki, trello, github issues, another tool as long as you adhere to the spirit of the intention for doing the RAF. Your TA needs to have access (be a user) on whatever form you use for grading purposes and there needs to be an ability for the teaching staff to view the history of progress (screen shots are fine). The intentions:
For the team: this will be the place where you will actively and dynamically manage the project, who is doing what, what is accomplished, what is left to do, etc. The should be your go-to place for project management, it should actually be helpful for your team and not only :) a burden to maintain.
For the teaching staff: this is where we can go and see how your team is progressing, make an assessment of your progress, and obtain a picture of whether everyone on the team is pulling their own weight for the success of the team.
Assignment:
Create a Wiki (or other) page for each RAF (1 RAF per weekly iteration).
Complete the following three sections
Progress Report - What did you complete in the previous week? At a minimum, each team member should contribute something EVERY week!
Work accomplished - Tasks completed, very specific (e.g. Unit tested OfficeVisit.java)
Major findings - Document issues or problems encountered when completing task
Who - Person(s) who completed task
Estimated hours to complete - Copied from previous week's RAF. For the first RAF this column is blank.
Actual hour to complete - Actual time to complete. Compare with the estimated hours to complete for insight into your estimation effectiveness.
Planning Next Iteration - What will you accomplish in the next week? At a minimum, each team member should plan to contribute something every week!
Work item for next week - Tasks that the team will accomplish in the next week
Criticality - Importance of task to the project and the class as a whole. If the task is very important to the project's success, assign it a criticality of "high."
Who - Person(s) who is(are) responsible for the task.
Estimated hours to complete - For planning purposes, each task should be analyzed to identify how long it will take to complete.
Risk Identification and Mitigation - One of the most important factors for successful project management is implementation of risk management. A significant contribution of risk management to project management is the technique of tracking the top-10 risk item tracking. It is very likely for one or more new risks to be identified every week. This section helps in identifying new risks, and tracking risks identified in the prior weeks.
Risks can originate from any project related areas, including personnel shortfalls; schedule issues; requirements mismatch or requirements creep; user interface mismatch; software quality; team skills; unfamiliar technology issues; etc. This section has five columns.
Risk description: This column should describe the risk. It should be very specific in nature. Some of the examples of describing risk items are: unrealistic schedules; developing wrong user interface; continuing stream of requirements changes; incompatibility amongst team members; etc. Each risk should be assessed for its criticality to the project’s success. Based on the assessment, each risk should be given a priority value ranging from 1 to 10, 1 being highest priority and 10 being lowest priority.
Risk priority [current week]: This column should state the priority of the risk for the current week.
Risk priority [last week]. This column should state the priority assigned to the same risk last week. This would allow the team to analyze if the risk has been mitigated.
Number of weeks on the list
Risk resolution progress: Risk resolution involves executing the risk management plan, which include identifying objectives, assigning responsibilities, and performing activities to satisfy project milestones. This column should state clearly how each risk is planned for resolution. The resolution should include the goals identified, how the tasks were assigned to team members, and the activities that are planned for to overcome the risk.
CSC326: Weekly Progress Report & Risk Assessment
Date:
Project Name:
Progress Report
Planning for Next Iteration
Risk Assessment
Is there a need for faculty intervention to address team or individual problems?
If yes, please clarify.
Risk List