3.3.4 Project performance/monitoring
Last updated
Last updated
Various methods are available to track project progress and assess the performance of individuals or groups during project execution. In Agile software development, techniques like Kanban boards are employed for daily task monitoring within sprints. These techniques are also utilized in schools, as explained in the preceding section. Additionally, performance assessment methods such as the burn-down chart and its counterpart, the burn-up chart, are employed in software development. When using the eduScrum methodology in schools, a run-up chart is commonly utilized for similar purposes.
Project monitoring
Monitoring is an essential and recurring task that involves systematically gathering information from a project. It serves several important purposes, including documenting results, processes, and experiences, which can be used to guide decision-making and learning processes. Monitoring allows you to check the progress of your project against your plans and intentions, providing data that can be used for various purposes:
In Agile project management, project monitoring is an ongoing and iterative process aimed at tracking project progress and making necessary adjustments. Its goal is to ensure the project stays on course and meets stakeholder requirements. This process involves monitoring progress against the project plan, identifying and addressing issues or risks, and taking corrective actions when needed. Agile project management uses various tools for monitoring, such as feedback loops, Gantt charts, work breakdown structures, issue logs, and sprint reviews.
In some Agile learning centers, students are required to engage in daily blogging as part of their learning experience. This information is collected systematically and used for reflective purposes rather than for performance measurement. These centers emphasize self-directed learning and individual learning pathways, with no comparisons made between students. In contrast, at Freinet schools in Belgium, monitoring may not occur daily, and information is collected at specific times with deadlines for presenting work. Monitoring in Freinet schools includes activities like regular project presentations, group governance meetings, and written text assignments, which may involve performance assessments like exams or other types of evaluations.
The board below shows how eduScrum monitors project-based learning. You can find such a board in its web-based form implemented in Miro:
We encourage you to search for web-based Agile resources to support the Agile structures you want to build in your classroom, or for your own learning or the learning pathways of your students.
Project performance
Agile project management has introduced a transformative approach to how teams plan and execute projects. It emphasizes flexibility, adaptability, and a strong commitment to delivering value. To ensure the success of Agile projects, it's essential to utilize effective tools and techniques, such as the BurnUp chart , the BurnDown chart and the RunUp chart.
BurnDown and BurnUp charts serve as invaluable tools for tracking and managing progress in various academic projects and initiatives. These graphical representations allow educators and students to visualize the journey towards project completion.
A BurnDown chart illustrates the remaining work over time, helping to ensure goals are met within set timeframes.
Conversely, a BurnUp chart displays both completed work and additional requirements, offering a comprehensive view of project status and aiding in transparent communication and early issue detection. These tools are essential for effectively managing educational projects and fostering collaboration among stakeholders.
In the context of BurnUp chart, RunUp chart serves as a valuable tool for monitoring work planning progress. This chart features a graphical representation, with the number of available lessons displayed along the horizontal axis and the quantity of work completed along the vertical axis.
To estimate the overall volume of work, the team engages in a collaborative exercise known as "planning poker." In this process, each task is thoroughly discussed, and a specific number of points is assigned to each task, reflecting its scope and complexity. After tallying the points allocated to all tasks, the total workload becomes clear.
Subsequently, the team proceeds to create the RunUp Chart. This chart showcases the total points achieved on the Y-axis, while the X-axis represents the available lessons, meetings, weeks, and similar time increments. A line is drawn, extending to the end of the designated sprint, signifying the completion of all work.
By dividing the total points by the available lessons, the team gains insight into their work rate, referred to as "Velocity." This calculation offers a clear indication of the amount of work that needs to be accomplished in each lesson to ensure timely completion.
During the initial phase of each lesson, typically within the context of a stand-up meeting, tasks are declared as "Done." This update is promptly reflected on the RunUp Chart. This real-time visualization allows both the team and the teacher to gauge whether the project's progress aligns with the intended course, ensuring transparency and facilitating effective project management.
