Blog 4: Our Farewell

What?

Over the last few weeks we have been working hard to finalize the last details of our project. We have been in contact with our community partner and over the last week we had the opportunity to do a school visit to watch the program in action. We did the school visit over two days to allow the majority of our group to attend and observe. On each day the visit was done at different schools.

 

November 15 2017: Visit at Florence Nightingale School

We are asked to arrive in the cafeteria of the elementary early in the morning at 8:30 AM. Upon arrival, we met with the primary breakfast producer Nancy, who is in charge of general food preparation of the school. There were no volunteers aside from Nancy to help run the breakfast program. On most mornings, there are a few breakfast options serving a total of 40 to 50 children. The two breakfast options on that day were either cheese toast or a choice between cereal or oatmeal for children that do not prefer cheese. Both options are accompanied by seasonal fruits such as sliced oranges or apples. Usually, there are no leftover foods however occasionally, foods that are leftover are packaged for snacks on the bus. Each morning, Nancy begins preparing at 8:00 AM and usually finish food preparation at 8:30 AM. It takes the children around twenty minutes to complete breakfast and school starts at 9:00 PM. According to Nancy, the sources of food come from a food distribution center partly sponsored by the Breakfast Club of Canada and the children were given the option to choose which breakfast they wanted earlier in the month. Something that is different from expected was the lack of volunteers involved with the program at this location and also the fact Nancy created most of the recipes herself. Overall, we had a great visit and felt very warming watching children eating breakfast.

 

November 16 2017: Visit at Queen Alexandra School

We visited Queen Alexandra School the day after visiting Florence Nightingale School. We met with Ryan and Jessica at 8:30am. They led us to the dining room in the basement where we visited the kitchen and the cafeteria. The staff prepared a Cheese Hash Brown Wrap that morning with milk and fruits that they served every single morning like bananas and blueberries. The operators who cook the breakfast are staff working in the school. The staff told us that there are usually 35 – 50 students per day, which would be considered a high attendance rate. For breakfast they serve hot meals every day and the foods are normally easy to go since some older kids prefer “to-go” rather than sitting in cafeteria. They prepare food with a strict control, so there is usually no left over. The ingredients they use are purchased online, and certain companies will order for them.

Ryan and Jessica told us that a high proportion of kids in this school are facing poverty. Therefore, there are many other food programs in Queen Alexandra for helping alleviate food insecurity. For example, a program called “Backpack Buddies” that gives kids bags of pasta sauce for free during Christmas and school breaks. There is another one called “Firefighter” that provides snakes to school every year. Ryan also said that only a small portion in total 90 elementary schools in Vancouver have breakfast programs, so there is still a lot we could do for helping kids who are food insecure.

So What?

From this learning, we considered the fact that older school aged children prefer “on the go” meals. In our recipe book we include a large “on the go” section that includes meals for these students who prefer not to sit down in the school cafeteria. We also took into consideration the proportion of students participating in the program and expanded our serving sizes within the recipes to ensure no food is going to waste. We also took into consideration the fact that most of the volunteers in the program are staff at the school. From this learning we adjusted our recipes to include simple directions and recipes with fewer ingredients so that the staff could successfully recreate the recipes.

Moreover, we found that the standard breakfast recipe repeats after 7 day in Florence Nightingale School (see pic). The children may be bored with eating the same kind of breakfast every week. Therefore, we adjusted our recipes to include different styles of breakfast and tried to avoid repetition. Also, we double check each other’s work and make sure every user of our recipe can fully understand the directions. By making these changes, we hope our recipe will be helpful and useful for both children and kitchen stuffs in the school.

Now What?

From this learning, we are going to do the last editing for our recipes including proofreading and editing the layout. No matter what kind of difficulty we met, or the potential drawback there was, we were still happy that we could contribute to this project, and it was a pleasure to be given the opportunity to collaborate with the Breakfast Club of Canada.

Moving forward, we hope more and more people can pay attention to the problem of children food insecurity, because children’s health is vital to the nation’s present and its future. Through providing them healthy and nutritious breakfast, it will help children to keep up with the demands of growth and development. Since children’s healthy growth is of the most vital indicators of health that want to see; we hope all parts of society can dedicate to this project, like donating money or volunteering in the organizations. Though our joint efforts, the end of children’s food insecurity should not be far away. In the future, when afforded the opportunity, we hope to use our professional knowledge and experience to mitigate food insecurity in further place.

 

Some final words:

It is time to say goodbye. We thank you for all of your time on reading the posts we have blogged so far. Even though it is end of this project, it is not end of our academic career. We will continue to study in seeking better solutions to contribute to solving food insecurity one day. We appreciate the chance to work with our community partner, Breakfast Club of Canada. We have truly cherished the experience and the friendship we gain from this project.

Blog Post 3: Our Graceful Dismount

Strategies For A Graceful Dismount

As you all know from our previous post, we had a crazy couple of weeks trying to figure out the recipe book and setting up a time to meet with our community partners, Robin and Ryan. We have been continuing to develop our recipe book and keep in contact with our partners as our journey slowly comes to an end. There is still a lot to be done before we reach our final destination and as things are finally coming into place our weekly objectives are changing. Below we outline what our previous objectives had been and some additional ones that have been added as the weeks go on.

Week 8: October 22-28

Previous Objective:

  • Learn how to display collected data in a clear and effective way

Additional Objectives:

  • Continue to add to our recipe draft and send draft to our community partner

Achievements:

We have made good progress with finalizing which recipes will be in the cookbook. On October 23 we had sent out our first draft of our recipes to our community partner. Within a couple days we received feedback on how we should display the recipes. This helped fulfill our objective of learning how to display collected data in a clear and effective way.

 

Week 9: October 29-November 4

Previous Objective:

  • Understand what is required to complete a strong, well done, final project

Additional Objectives:

  • Continue to edit the recipes using the feedback received from our community partner

Achievements:

So far this week we have managed to fully understand what is expected in our recipe draft from discussion with our community partner. We used the feedback we received to edit the draft and on November 1, we sent another copy over to Robin, Ryan, and Angel for more feedback. We are continuing to refer back to our initial goals to keep them in mind as we edit. Over the next couple of weeks we hope to hear more feedback from our community partner as our project slowly comes together!

 

Project Progress Due Dates
Send rough draft of recipes to our community partner October 23
Edit recipes and resend draft November 1
Edit once again and send final draft November 15
Final editing and completion of project November 30

 

This table briefly outlines our upcoming due dates for our project to keep us on track

Moment of Significant Change

Through drawing out our emotion v.s skills graphs, we realized how similar we were feeling throughout different stages. In the last 8 weeks, we have done a lot of group works and assignments together. Overall, we had a fun time working together and tackling all the difficulties form our project especially when we just started our project. We were really excited to meet each other and to communicate with our project partner who was helpful and gave us a lot suggestions on how to start our project. However, things became tougher when we came across our first two blogs and proposal. We were repeatedly asked to resubmit our work, and even though we edited them several times, we still did not get a satisfactory grade, which was really frustrating. We thought it was the lack of skills and experience of writing blogs and proposals that led to our unexpected results. However, as we continue to go through this process we are learning what is needed of us and how to improve. The other thing that did not go well was planning our school visit, which should have been set up a few weeks ago before we started our first recipe draft. The emotion graph reflects more about our confidence level. When we first started our project, we were excited and confident in what we were going to do. However, the curve declined significantly when we got our feedback for the first blog, reflecting a decline in our confidence. Interestingly, our confidence was boosted when we uploaded the second blog. There is an increasing trend after we finished our project draft as we understand more and get more familiar with our project.

As shown in the skills and knowledge graph, there was a common pattern of increased growth. Surprisingly, some of us learnt a lot from getting feed back, while some of us got confused and unsure when things didn’t go our way. As we came closer to the due day of our project draft, we gained greater understanding, realized what we could have done better before, and recognize what we can do to improve our project in the future.

 

Our strategies for successful project completion are as following:

  • To communicate efficiently within our group to keep everyone updated regarding of the project process.
  • To continuously keep contact with our community partners asking for feedback.
  • To set regular group meetings working on editing our recipe book.
  • To make the most of our flexible learning time checking in with all of our group members and ensuring everyone is on the same track.
  • To compare our recipe book with previous one trying to find the strengths and limitations of our recipe book.
  • To monitor and assimilate all information into one document rather than have to amalgamate all the information to assure coherence among the project.
  • To set deadlines ahead of time to limit stress as final exams approach, starting to prepare for the group presentation, final report and infographic.
  • To keep positive attitude and mindset, and rise to the challenge.
  • To reflect on the feedback from the community partners and some unsolved challenges of this project and provide suggestions for future collaborators working on this project.

Spam prevention powered by Akismet