Question 4 (Marks: 10)
You are required to use Project Management Software such as Microsoft Project or any suitable
application software such as TeamGantt for this task.
LU1 and LU5 articles and readings will further help you complete this question.
Q.4.1 With reference to the project selected above and completed, build an Agile
project task list
The project you build should demonstrate the following:
a. Set up tasks for project initiation and releases (2 marks).
b. Create and manage the product backlog (2 marks).
c. Assigning features to a print (2 marks).
d. Assigning resources to features (2 marks).
(8)
Q.4.2 Using the same project above, generate a burndown report. (2)
To complete this question, you will need to use a project management software that supports Agile methodologies such as Microsoft Project or TeamGantt. Follow the instructions below to build an Agile project task list and generate a burndown report:
Q.4.1 Agile Project Task List:
a. Set up tasks for project initiation and releases:
- Create a task for project initiation activities such as gathering requirements, identifying stakeholders, and defining project scope.
- Create separate tasks for each release, specifying the release objectives and deliverables.
b. Create and manage the product backlog:
- Create a task for backlog management activities such as prioritizing user stories, estimating effort, and refining the backlog.
- Break down user stories into smaller tasks and assign them to the appropriate backlog items.
c. Assigning features to a sprint:
- Create a task for sprint planning and create subtasks for each feature or user story selected for the sprint.
- Assign the relevant features or user stories to each sprint.
d. Assigning resources to features:
- Create a task for resource allocation and assign resources to each feature or user story based on their skills and availability.
- Track resource utilization and adjust assignments as needed.
Q.4.2 Burndown Report:
- Generate a burndown report in the project management software, selecting the appropriate timeframe (e.g., daily, weekly, or sprint-based).
- The burndown report should display the remaining work (in hours or story points) on the y-axis and the time (e.g., days or sprints) on the x-axis.
- The report should show the planned work progress line (ideal burndown) and the actual work progress line.
- Compare the actual work progress against the planned progress to identify any deviations or delays.
Make sure to input the required information and tasks into the project management software accurately to effectively demonstrate the Agile project management process.
Q.4.1 With reference to the project selected above and completed, build an Agile project task list:
a. Set up tasks for project initiation and releases:
- Conduct project kickoff meeting (Task 1)
- Define project scope and objectives (Task 2)
- Create project charter (Task 3)
- Identify project stakeholders (Task 4)
- Develop project timeline and milestones (Task 5)
- Define project budget and resource requirements (Task 6)
- Obtain management approval for project initiation (Task 7)
- Release 1 planning (Task 8)
- Release 2 planning (Task 9)
- Release 3 planning (Task 10)
b. Create and manage the product backlog:
- Collect user requirements (Task 11)
- Prioritize requirements (Task 12)
- Create user stories (Task 13)
- Estimate user stories' effort points (Task 14)
- Review and validate user stories with stakeholders (Task 15)
- Assign user stories to appropriate releases (Task 16)
- Refine user stories based on feedback (Task 17)
- Continuously manage and update the product backlog (Task 18)
c. Assigning features to a sprint:
- Conduct sprint planning meeting (Task 19)
- Select and prioritize user stories for the sprint backlog (Task 20)
- Estimate effort points for the selected user stories (Task 21)
- Assign user stories to development team members (Task 22)
- Define sprint goals and objectives (Task 23)
- Determine sprint duration (Task 24)
- Begin sprint development (Task 25)
d. Assigning resources to features:
- Identify required resources for each feature (Task 26)
- Allocate resources based on availability and skillset (Task 27)
- Monitor and track resource allocation (Task 28)
- Resolve resource conflicts and bottlenecks (Task 29)
- Continuously optimize resource allocation throughout the project (Task 30)
Q.4.2 Using the same project above, generate a burndown report:
A burndown report tracks the completion of work over time in an Agile project. The report compares the planned work (backlog) with the actual work completed and visualizes the progress.
To generate a burndown report for the project, follow these steps:
1. Open the Agile project management software (e.g., Microsoft Project or TeamGantt).
2. Navigate to the project task list or backlog section.
3. Identify the total work remaining for each sprint or iteration.
4. Plot the remaining work on a graph against the time duration of the project.
5. Start plotting the actual work completed each day or week against the planned work.
6. Update the burndown report regularly, reflecting the progress made and any changes in the project scope or timeline.
7. Analyze the burndown report to identify trends, potential delays, or areas requiring more resources or attention.
8. Use the burndown report to communicate progress to stakeholders and make necessary adjustments to the project plan.
The burndown report provides a visual representation of the project's progress and helps the project team and stakeholders understand the remaining work and potential risks in meeting the project objectives.