paper

To

From

Data

Subject

Motorola MBP667CONNECT Troubleshooting Project Reflection

Introduction

This report is aimed at reflecting on the Motorola MBP667CONNECT trouble shooting project. The reflection will look into the various project tasks that were being done by different people and determine if the skills they has matched the task. In addition to this introduction, the report will also have a project background section that explains my understanding of the project. The third section of the report is the body of the report and will focus on the project performance; explore what worked in the project and what did not work. Finally, the fourth section of the report will focus on the project strengths and weaknesses. In addition, it will also give recommendations on how future projects could be carried out. The major aim behind this reflection report is to evaluate the project in light of what was learned and what was not learned and give suggestions on what could be improved in future.

Project background

The idea behind the project was to troubleshoot and determine the various challenges with Motorola MBP667CONNECT. This is a device that allows parents to monitor what is going on in their homes. The community need here is to have a reliable home monitoring device. For the parents the project was going to solve the device failure problems and guarantee them service all through. This will enable them monitor their homes throughout. Fir the students and the University, the project offered a learning opportunity. The students are going to increase their knowledge on how to trouble shoot to solve the device problem. For the company, the project is beneficial in that they are likely to develop new ways of solving the device challenges. The project therefore has numerous benefits to the parents, iFixit, the University and the students. This projects as well involved costs to the stakeholders. For example, the students had to devout their time to the project while the University and the iFixit company incurred costs in terms of time and money invested in the project. To a great extent, this project met the community need of having a reliable home monitoring system. This is because the trouble shooting brought understanding of the problem and how the problem could be solved. I consider the project suitable for technical communication course because it puts into practice various technical communication issues like equipment reliability.

The body

This third section of the report will focus on project successes and failures in realizing the objectives and enhancing my learning. Ifixit and the university were the major organizations that were served by this project. The project stakeholders included the university, parents, students, ifixit and the community at large. The organizational communication need was to be able to monitor homes from a remote place. When the trouble shooting was done and the various problems with the device were fixed, the need was adequately addressed. In addition, the community client was responsive and I enjoyed working with them through the information they offered. In addition, the feedback they offered was as well helpful since it gave us insights of what could be improved. The relationship with them was symbiotic because working with us gave them trouble shooting skills they did not have before the project. The project primary audience was the community members and particularly the parents. With this in mind and considering that parents are geographically dispersed the project was implemented in phases that were geographically organized. The secondary audience for this project was the student, instructors and the ifixit organization. This group is considered relatively technologically connected and therefore communication was done through social medial platforms and also through phones such as instant message texting. What I learned about writing technical information is that it should be clear and concise. The challenge I has is that sometimes I would write a lot of things that were unnecessary and I has to reduce these things to acceptable levels. This knowledge will help me in my future employment to write instructions for some products or directions for some process. Then as I have learnt I will write concisely and clearly. The project usability test was successful. However, the participants interpreted instructions differently because some words were ambiguous. In future, effort will be made to ensure that there is clarity and conciseness in writing the instructions so that different participants do not interpret it differently. I can say that estimation of project task, timelines and completion of the project was quite good. 90 percent of the tasks were completed as planned and the 10 percent took a little more time than expected because of delay that were not expected during the project planning. Workload was equitably distributed and the project plan kept everyone at their task. My role in the project was assigning tasks and coordination of the project activities. I did this so well and as such I contributed enormously to the project success. Teamwork has its ups and downs but my main take away from the project is that if handled well, teamwork can help in realizing project results within a short time. Some of the challenges I faced while working with the project team included communication. It was not easy to pass a message for a team that sometimes was dispersed geographically. My advice to other students who might find themselves in a team is that they should share in the vision, objectives and aspirations of the team. They should also be able to share in team values because only then the team will make sense to them.

Conclusion

In my considered opinion, the project was largely successful because it met all its objectives. However, the project has challenges too. For instance, as indicated earlier, there was a challenge among team member communication. In addition, the primary audience of the project was quite diverse and reaching everyone was quite a challenge. There was some challenge with some participants reading and interpreting instructions. This was largely because of ambiguous language used in writing such instructions. My recommendations is that in future, the team communication should be established well in advanced in that the proper communication channels should be sought in advance to avoid communication breakdown. It was a successful project by all standards except for the few challenges encountered.