Build & Test Prep
Table of Contents
Team Vision for Build & Test Prep Phase
Coming into the semester, we really wanted to make sure we started strong and picked up right where we left of before leaving for Winter Break. Before the semester started, we planned to sit down with all the employees and walk them through the new IMS. We wanted to do this to allow them the chance to see the new IMS before they are asked to interact with it while at work. This was accomplished through a training meeting that was held one week before classes started. Through this meeting, we were able to walk all the employees through the IMS, as well as hear their opinions and thoughts first-hand. We also started to develop a feedback system to allow employees to share opinions/concerns/suggestions with us, even though we are not physically there with them at FoodShare.
After the meeting, we planned to continue to improve the categories that we have and continue to prep for the IMS launch to the employees. To accomplish these two things, we met with Sharon and discussed the new categories that we have created and well as discuss the ones that we removed. In regard to IMS improvements, we continued to develop the software, as well as reach out to RIT faculty for help on one specific problem that we could not seem to solve. Also, we reached out to RIT IT to start the process of getting a laptop/tablet that will be used by the employees to utilize the IMS. One last thing that we accomplished that we did not plan to was the reorganization of the customer-pick room. We reorganized the room again to allow the room to look fuller from the outside.
Test Plan Summary
Below shows the classification of all ERs into two different buckets: ERs ready to be tested vs ERs not ready to be tested. The team has formed a plan to complete all ready to be tested ERs. The ERs that are not ready to be tested, have the reasoning behind why they can't be tested yet, next to them in the visual. Once these action items are complete we can proceed with testing the ERs.
Risk and Problem Tracking
Below is a visual summarization of our team's risks. The two risks stated below have an importance of 81. The importance of each risk is calculated by multiplying the severity by the frequency. The score 81 is the highest possible ranking a risk can get. Therefore, the risks below need to be monitored heavily be the team.
For a complete list of risks which we have compiled thus far, please visit: Risk Management
Design Review Materials
Below is a visual summarization of the team's meeting with Sharon on 1/17.
Plans for next phase
Below is a visual for the team's plan for the next phase. The plan is broken down into the main project focuses.
Below is a visual for the team's IMS implementation plan. We talked with our customer and agreed on these dates and phases below. Our team took a phased approached instead of a "Big Bang" approach. By having three implementation phases the team can conduct more PDCA cycles. With more PDCA cycles comes more learning experiences for the team, and a more effective final product.