Pastoral Care comments will remain an integral component of the End of Semester Reports as an ongoing reflection of the individual progress of all students. Students and families will continue to be provided with extensive, ongoing, and up to date feedback on formative and all summative work throughout the semester, which we believe to be a more effective indicator of student success and development. No longer including final subject comments in the end-of-semester reporting cycle will allow the Reporting process to be streamlined and ensure that there is more flexibility in the classroom to best support student outcomes. The role out of the implementation of Daymap means that we are now ready to complete the next phase, which will include the conclusion end-of-semester subject comments on Reports for Middle and Senior School students.

The detailed comments completed by staff for each assessment component and provided to families via Daymap means that continuous assessment has become a more effective way of understanding the ongoing progress of students. And remember, Timm Esque’s book, “No Surprises Project Management” describes the process in detail.Since 2019, the implementation of the Unity College Daymap Learning Management System has been occurring to reorganise and modernise the methods of communication between staff, students, and parents, and we have provided up to date and relevant marking and feedback of all assessment across the College. How do we track progress? This is material for a future blog. At all times, sub-teams should talk and negotiate dates and details of the deliverables. Regular meetings to review progress as well as changes need to take place, although not everyone needs to be involved. This is a first cut of the map or plan and further meetings will be necessary to refine the map. These issues get captured in a pink sticky (you can use any color that’s different from other colors used) and discussed.Īt the end of the day, a map similar to the one illustrated in the picture is available and should be entered into an electronic form to share. Once every team has presented, the group as a whole walks through the map, identifying issues such as missing deliverables, conflicting dates, etc. At the same time, if possible, they provide a commit date for those deliverables that have been requested of them. Each team then presents in a similar way as the customer. Next each time breaks to review their deliverables, adjust the ones they had created before hand and create new ones as needed. Questions are answered and then the customer posts the sticky in the correct time bucket. The customer speaks about each deliverable, who they think needs to provide it, and when they (the customer) needs it. It is critical that in this later case these expectations have been validated with the customer before the map day. If a customer team is unavailable, someone needs to represent what the customer expects. The customer team starts by presenting what they need from the other teams. The third column lists a “needed by” date(s). The second one, in one or more rows, lists the “customer(s)” of the deliverable. The first one is for the “owner” of the deliverable and the date the team is committing to delivering it.

At the top, the deliverable number and name is entered. The most common timeframe is months.Įach team uses a 3M Post-It like “sticky” to enter information about their deliverables. Depending on the length of the project, the date columns can be weeks, months, or quarters. The PM or facilitator, if one is available, posts large sheets of paper around the room, with swim lanes for each sub-team and vertical columns for dates. This map development is where the term “map day” comes from. Once this is accomplished, then a “map” of the deliverables is developed at the same meeting (many times going for multiple days) or at a follow-on meeting. At the beginning, it is a way for all team members to get to know each other and to get agreement on what the deliverable is. The objectives of a map day can vary depending on where a project is. So, what happens during map day? Yesterday I gave a quick overview of the process but now it is time to provide more details.

To this daymap