| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | w | From | Reflection | Relative Links | Completion | |||||||||||||||||||
2 | Type: Project Output || Decision Making || Teamwork || Stakeholder Engagement || Reflection | Recorder: Siyuan He | Tracker: Yuhao Zhai | |||||||||||||||||||||
3 | xxxxxx，xxxxx,xxxxxx (Font: Times New Roman;Size:12) | Self | TODO: | Processing/Done/ NA | ||||||||||||||||||||
4 | We have a lot of output at this stage, and there are many advantages I will not say much. The only downside is that there has been no/less progress on the data methodology that I think our clients have been waiting for. | Self | Developement Suggestions TODO: (Actually already in plan) 1. More progress on the data methodology 2. More code outputs 3. More attention to back-end development | |||||||||||||||||||||
5 | According to the needs of customers, we have designed a nutritionist-oriented web application, the prototype, and a corresponding database, but there are not many corresponding outputs in terms of code. I think this is what we should pay attention to in the future. | Self | ||||||||||||||||||||||
6 | Nice web prototype. Next, specific development actions should be carried out as soon as possible. Members of the web group and the database group need to negotiate to determine the APIs. | Self | ||||||||||||||||||||||
7 | This week we have finished a lot of work including front-end prototype design and development. What’s more we collected initial data for back-end development. I think in the future we should pay more attention to back-end development. | Self | ||||||||||||||||||||||
8 | We followed the plan and gave the appropriate output, which was great! Actionable suggestion: I noticed that our plan does not include anything about Showcase, and making a showcase is a lot of time work. This may be a potential risk: in the coming weeks, our team may work longer than expected. Without compromising the schedule, I suggest starting to prepare the showcase in advance and spreading the time beyond expectations over the next few weeks. Or use the buffer week as much as possible. | Self | TODO: 1. Include showcase in plan. (potential risk: need more work time) | |||||||||||||||||||||
9 | For this semester, I think our shadows are focusing on the web design & development phase. They have provided a competitive analysis and other documents to their client. After checking the file named with web demand analysis, they list those requirements clearly with working status. It would be better if they could add the start date and estimated end date (the date matches with the development plan in your git hub repo) into each requirement to show the plan or estimation time of completing that task. It would be much easier for the client to understand the detailed information about the plan from an overview perspective. | Shadow | TODO: 1. Add the start date and estimated end date into each requirement. | |||||||||||||||||||||
10 | Ensure that the prototype is designed to contain detailed functionality and that its features are described in detail. // // // // Ensure that the privacy of user information can be safeguarded. | Shadow | TODO: 1. Expand more low-level/detailed functionalities. | |||||||||||||||||||||
11 | The project output follows the requirements gathering heuristic for system design thinking research methods embracing agile development for building the user story map. A piece of feasible advice that can benefit existing efforts is to expand more low-level functionalities under given user stories. That would help further development to be estimated more accurately and efficiently. | Shadow | ||||||||||||||||||||||
12 | We are following the work plan to produce the delivery. // // Having finished the design, drawing the diagram and building the prototype. // // More emphasis will be put on the development process after this Audit. | Self | Well done! The Team followed the plan and produced the output. | |||||||||||||||||||||
13 | Before Audit 2, our project output is quite a lot: web prototype, form, and database design. | Self | ||||||||||||||||||||||
14 | The team’s outputs to stakeholders are increasing in value. | Client | ||||||||||||||||||||||
15 | The team has updated several analysis diagrams which is a good progress. Also they seems finish much of work in the system design that they could develop based on them. Seems all stick to their work plan. | Shadow | ||||||||||||||||||||||
16 | Landing page is neat and well structured – no much content in GIT Hub that I could see – but I was pleased to see the Gannt chart there. I struggled to navigate the google drive repository partly because of multiple browser issues and partly because I did not find it intuitive to navigate – noting some links appeared to have nothing in them and sometimes the content was not self explanatory. In contrast the audit presentations were very well structured and clearly explained the project outputs. The work plan with progress did not actually tell me how much progress you have made with those tasks – consider using the gannt chart to represent % complete of the tasks shown to indicate and manage progress against your key milestones. I do like your weekly newsletter but think you could usefully add to it if it had red amber green status indicator for overall project progress plus a brief description of what progress was made since last report and what the key issues you have faced are. Top 3 risks and what has been done to address them since last week would also focus the projects attention on ensuring that you are actively managing risks instead of just listing them. Clear evidence of what appears to be good structured analysis and design. However the client and team seem to reflect that not enough actual code has been produced so far. On the one hand this could be a question of managing stakeholder expectations (a risk worth analysing?) On the other it is sometimes necessary to do the analytical ground work first and there may have been access to stakeholder issues. On balance I would have expected a bit more by this stage of the project but you do seem to be tracking according to your high level milestones per SOW. But it is very hard to assess what progress was made on a week by week basis or what exactly the clients expectations were. The audit presentations were excellent but I do note a significant amount of reuse from first audit. At next audit you should focus more on what has been accomplished in the intervening period. | Tutor | Need discussion TODO: 1. Update navigation methods. (add more navigation information in landing page) 2. Update work plan with progress. (a new form) 3. Adjust the structure of the next audit presentation (focus more on output) | |||||||||||||||||||||
17 | Useful Feedbacks | From | Reflection | Relative Links | ||||||||||||||||||||
18 | Type: Project Output || Decision Making || Teamwork || Stakeholder Engagement || Reflection | Recorder:Xinyue Hu | Tracker: Yuhao Zhai | |||||||||||||||||||||
19 | It feels like we're still not brainstorming, and a lot of decisions are still made by just a few people. | Self | TODO: Everyone in our team should be involved in when making a decision | Processing/Done/ NA | ||||||||||||||||||||
20 | If we can try to confirm the feasibility and difficulty of the decision when assessing the risk, we can reduce the cost of trial & error as well as reduce redundant logs. | Self | TODO: If a decision with low feasibility then we'll drop it. | |||||||||||||||||||||
21 | It is better after reflecting from last Audit's suggestion. All the decision should be shared on the weekly group meeting, no matter it comes from data or web branches or from the general. | Self | TODO: We'll take time to review and reflect the work we've done before. | |||||||||||||||||||||
22 | The team have been structured in their responses to decisions and discussions. In some cases this has meant setting aside work that had already been done or particular projects of interest and focussing on current priorities. | Client | TODO: We'll take time to review and reflect the work we've done before. | |||||||||||||||||||||
23 | a column named status can be added to the risk log so that they can change some risks from active to close. It would be much easier for them to monitor & review the risk log. | Shadow | TODO: Add a statu column to risk log to track its statu. | |||||||||||||||||||||
24 | If the decision making mechanism is client-driven. Then, when it comes to "All Members" in the record, whether the client's decision/opinion is considered/involved or not can be further clearly clarified, especially relative to the development approach. | Shadow | TODO: We'll add the client's opinions into consideration when making decisions. | |||||||||||||||||||||
25 | 1.Decision logs should be just for key decisions and should not be used as a task log. 2.The problem with including all such minor points is the significant issues get lost in amongst all the unnecessary detail – how long would it take to review your current decision log and would you care if you were a future project about some of the items recorded? 3.One of your mitigations during development is to use dummy data which is fair but the fact that you have considered this issue and taken steps to address it is not recorded in your risk log currently. | Tutor | TODO:1.We'll clarify the tasks and the decisions and only record the important decision. 2. We'll summarise the issues we have met and put them into the newsletter 3.The risk of dummy data will take into consideration and we'll try to find a way to solve it. | |||||||||||||||||||||
26 | Useful Feedbacks | From | Reflection | Relative Links | ||||||||||||||||||||
27 | Type: Project Output || Decision Making || Teamwork || Stakeholder Engagement || Reflection | Recorder: Tianqi Tang | Tracker: Yuhao Zhai | |||||||||||||||||||||
28 | xxxxxx，xxxxx,xxxxxx (Font: Times New Roman;Size:12) | Self | TODO: | Processing/Done/ NA | ||||||||||||||||||||
29 | As a member of the team, I am satisfied with the teamwork. Tip： Important discussions and meetings within the Data group and Web group deserve to be recorded. The format of the record does not need to be too formal (it doesn’t need to be like meeting minutes), it just needs to be in the form of a memo to know what the other person is focusing on. Records can be uploaded to the meeting minutes folder. | Self | TODO: 1. Assign tasks more clearly, not to the team 2. The two groups communicate more frequently 3. Record the meetings of each group | |||||||||||||||||||||
30 | Too frequent communication within the group makes the development needs change all the time, which affects the process of output. Problems encountered at work may be raised in a one-time report. In mid to late development, maybe we can assign a member of the database team to the web team to assist in developing the backend and testing. | Self | ||||||||||||||||||||||
31 | The two groups in our team should communicate more often to exchange valuable ideas and unify the progress. | Self | ||||||||||||||||||||||
32 | Very good teamwork, but everyone’s tasks are not balanced, some people give a lot, some people give very little. | Self | e | |||||||||||||||||||||
33 | Our group have a great atmosphere of teamwork. // // Just one thing, each group member should notify the group if the task finished is a former task of the other. | Self | ||||||||||||||||||||||
34 | Our group will hold group meetings every week, carry out last week’s task inspection and next week’s task assignment, and everyone has a clear division of labor. | Self | ||||||||||||||||||||||
35 | Some of the team members don’t know the exat tasks. So, it should make it more clear what the task is, and who should finish it. | Self | ||||||||||||||||||||||
36 | Clearer identification of who is leading on parts of the project would be a help. However I appreciate that some team members are more comfortable speaking english than are others. | Client | TODO: A person in charge of each part shall be set and informed to Ric | |||||||||||||||||||||
37 | The team assigns tasks and responsibilities according to their experience in this project. Good to see collaborations between old and new members and implement the check ring concept in to help review work. A friendly suggestion regarding the check ring recording file is that the outer ring is not clearly identified as introduced in the audit presentation. How these can help in reviewing can be more clearly designed such as “Survey” item is only checked by the responsible inner ring. The difference between using ring check results can be more obvious than the normal review and checking process. | Shadow | N/A | |||||||||||||||||||||
38 | Every group member contributed to the project. Great Job ! By the way, It would be better if our shadows could make the meeting minutes’ format more consistent, which means if they would like to use excel to record meeting minutes, then all meeting minutes can be filled in that template. And it would be better to assign more of the paper check workload to other group members(In the check ring), which means everyone can involve in the project development. | Shadow | ||||||||||||||||||||||
39 | As a team, it is necessary for members to praise each other, but they also need to criticize each other. This allows for better cooperation. | Shadow | ||||||||||||||||||||||
40 | They have very organized meeting logs and agenda, indicating a good teamwork. | Shadow | ||||||||||||||||||||||
41 | Positives: Required information about teamwork was indicated in the audit presentation. // // // // Negatives: Teamwork information not captured in repository as is expected – e.g., Could not find the team charter, with roles, etc. Record keeping does not provided a basis for assessing individual contributions. Also, hard to assess productivity of team, overall, based on records kept. In the absence of a team charter I found the information I needed about who was responsible for what, how you communicate and work together from the audit presentations. For future projects do consider producing a charter at the outset as it helps address some of the principles of working together as a group from the start. But I would not suggest you create one now as you should really focus more on managing and control your projects progress against schedule and ensuring you are meeting client expectations It is hard to assess individuals contributions and the check rings plus feedback commentary might seem to indicate that work balance between members is not proportionate i.e. a few individuals appear to be doing most of the work. If true productivity as a group is likely to be somewhat lower. Breaking your project schedule down further and assigning tasks or groups of tasks to individuals in a Gannt format and monitoring percentage completes plus separately logging tracking hours put in by individuals against planned tasks could give you the means to both balance and distribute workload and also to track and assess individual contributions. | Tutor | TODO: 1. worklog 2. check ring charts need to be modified. | |||||||||||||||||||||
42 | Useful Feedbacks | From | Reflection | Relative Links | ||||||||||||||||||||
43 | Type: Project Output || Decision Making || Teamwork || Stakeholder Engagement || Reflection | Recorder: Hengtong Wu | Tracker: Shuyi Chen | |||||||||||||||||||||
44 | xxxxxx，xxxxx,xxxxxx (Font: Times New Roman;Size:12) | Self | TODO: | Processing/Done/ NA | ||||||||||||||||||||
45 | Can we increase the communication with the dietitian, many questions may take one to two weeks to be consulted and resolved. | Self | 1.More regular meetings with nutritionists, more timely consultation and problem solving 2.More people attend meetings and have client more involved in our work 3. Discuss front-end design more at meetings, and communicate with client to determine the design in advance | Processing/Done/ NA | ||||||||||||||||||||
46 | Over the past few weeks, due to some unexpected factors, our meetings with customers and nutritionist have not been very regular, and I think our team is not very timely in tracking customer needs. | Self | ||||||||||||||||||||||
47 | We have regular meeting with all the stakeholders. // // After setting up a work plan and updating the project process frequently and instantly, I think our client is feeling more engaged in our project. | Self | ||||||||||||||||||||||
48 | The team is communicating with stakeholders coherently. Maybe we can ask the client for some money to buy the server and the domain name | Self | ||||||||||||||||||||||
49 | It’s best to have everyone present at the client meeting. We hope customers can participate in our daily work, such as editing our product backlog and adding feedback to it | Self | ||||||||||||||||||||||
50 | Ric comes back from the trip and takes part in our meetings. He is a nice client. | Self | ||||||||||||||||||||||
51 | I think it will be better if we add more time to the discussion of Web UI design in a recent meeting. Because web design is a highly relevant part of the user experience, more time should be spent in meetings with clients and nutritionists to confirm their needs and incorporate their feedback on the current design. This will avoid spending too much time on changing the interface later. | Self | ||||||||||||||||||||||
52 | expectations of key stakeholder is only being clearly established now | Client | Timely clarity on key stakeholder's expectations | |||||||||||||||||||||
53 | Based on the client feedback, the team effectively contributes values and provides possible options to manage contact with the client when the regular meeting is not easily arranged. However, it would be better to show interactions when developing project outputs and the client feedback/evaluation on outputs | Shadow | 1.Demonstrate interaction that adjusts output based on client'feedback 2.Get detailed needs of potential users | |||||||||||||||||||||
54 | Based on their client’s feedback, I think their stakeholder engagement is good enough, no more feedback can be provided from my side. Keep on it! | Shadow | ||||||||||||||||||||||
55 | You can use questionnaires and other forms of research on potential customers to obtain their detailed needs and listen to the voice of the customer. | Shadow | ||||||||||||||||||||||
56 | They seems to have good communication with different skateholders, the client and nutritionists.They mentioned some issue in the changing requirements during the tutorial. Maybe some documents evaluating different options with an explanation can be helpful in the discussion with the client. Also seems they have sort of solved this kind of issue. | Shadow | ||||||||||||||||||||||
57 | The client clearly did not feel that their expectations of the project were being met earlier in the project. I did not find any evidence of active attempt to manage these expectations or discussions about what they expected by when. According to SOW milestones you actually appear to be roughly on schedule. The clients expectations for next stage would be worth exploring further although I note they seem to be a lot happier with recent evidence of progress. If you do experience ongoing access to stakeholder issues make sure you escalate immediately and raise it as an issue in tutorials and directly with your client and affected stakeholders. | Tutor | Understand the exceptions of client more accurately, determine the exceptions as soon as possible, meet them,and show it in team documents | |||||||||||||||||||||
58 | Useful Feedbacks | From | Reflection | Relative Links | ||||||||||||||||||||
59 | Type: Project Output || Decision Making || Teamwork || Stakeholder Engagement || Reflection | Recorder: Shiyun Zhu | Tracker: Shuyi Chen | |||||||||||||||||||||
60 | Feedback integration can be carried out on the second day after the feedback report is released, and a meeting can be held on the third day for discussion. This can speed up the process of action on reflection. | Self | TODO: According to Piazza, the audit report will be released on Tuesday morning of the week following the audit week, and we should have a reflection meeting on Wednesday night. -Y | |||||||||||||||||||||
61 | The team does well in analysing audit feedback and tag reports. For project output, the team has reflected on reporting problems once found by any member. But the following actions are performed on the WeChat platform. It would be better if the client would know the issue/challenge the team faces as well through Weekly NewsLetter / be reflected on meeting minutes. | Shadow | TODO： Document the team's reflections and challenges encountered in weekly newsletters. -Y will be record in weekly newsletters. | |||||||||||||||||||||
62 | We are very prompt about recording feedback and reflections. My suggestion is to quickly share the specifics of the reflection at the weekly meeting, rather than just saying “I recorded the reflection”. This way we all get feedback and reflections from all sides in a timely manner, which is good for the development of our team. | Self | TODO: Briefly share the content of last week's reflection logs, decision logs, and risk assements at the weekly meeting. Try to summarize in one sentence. | |||||||||||||||||||||
63 | After the discussion in last tutorial, we are more clear that not every feedback should be accepted. // // It should depend on the actual situation of each group. // // One thing is that, the action of the reflection should be set up more clear. For example, each part of the five evaluation should come into one TODO list followed by the reflection. | Self | The action of the reflection should be set up more clearly. | |||||||||||||||||||||
64 | Every reflection should take into action not just be written on paper. | Self | ||||||||||||||||||||||
65 | There is clear evidence in the feedback log of reflection not just from audits but from various meetings and discussions and also of acting on that feedback to improve project outcomes. Some of the suggestion for improving the feedback log from the shadows etc like adding a column to describe what has been learned from feedback and assigning action items If you agree with the feedback and later demonstrating that you have addressed the feedback are well worth considering. | Tutor | We need to pay more attention to the efficiency and quality of reflection to feedback from each channel and ensure that every valuable piece of feedback is responded to. | |||||||||||||||||||||
66 | After checking the reflection log, it would be better if they can include more information in a reflection column. From my understanding, the “reflection” column can be treated as an action item. Hence, it would be better if they can add a column to describe what they have learned from that feedback. For instance, row 28 in the reflection log describes a decision have been made by our shadow, you can add more information about how to avoid that case happening in the reflection log (That is knowledge or skill you learned from the reflection) | Shadow | Thank you for your suggestion, but after consideration, we have rejected this one for the following reasons. 1. we looked through the logs of some other groups and found that they did not record this item either. 2. we think that adding such a column( "add a column to describe what they have learned from that feedback")would add to the workload of the recorder and would be of low value to the stakeholders - this is not the current focus of our group. In the end, we will try to record detailed ACTION to make the reflection more feasible. | |||||||||||||||||||||
67 | the team’s work is improving, so i guess so. | Client | Narrative or positive evaluation only | |||||||||||||||||||||
68 | They have listened to a1’s feedback and are actively improving. | Shadow | ||||||||||||||||||||||
69 | They have a great detailed reflection document for audit feedback! | Shadow | ||||||||||||||||||||||
70 | I think this is a big improvement compared to the last audit. In the audit file of our team document, we conducted a special meeting based on the last audit, and sorted out the feedbacks from customers, tutors, shadows. team, and look for feedback that we think is important, and make corresponding improvements | Self | ||||||||||||||||||||||
71 | Every problem has a good reflection, every demand will be recorded and discussed. | Self | ||||||||||||||||||||||
72 | ||||||||||||||||||||||||
73 | ||||||||||||||||||||||||
74 | ||||||||||||||||||||||||
75 | ||||||||||||||||||||||||
76 | ||||||||||||||||||||||||
77 | ||||||||||||||||||||||||
78 | ||||||||||||||||||||||||
79 | ||||||||||||||||||||||||
80 | ||||||||||||||||||||||||
81 | ||||||||||||||||||||||||
82 | ||||||||||||||||||||||||
83 | ||||||||||||||||||||||||
84 | ||||||||||||||||||||||||
85 | ||||||||||||||||||||||||
86 | ||||||||||||||||||||||||
87 | ||||||||||||||||||||||||
88 | ||||||||||||||||||||||||
89 | ||||||||||||||||||||||||
90 | ||||||||||||||||||||||||
91 | ||||||||||||||||||||||||
92 | ||||||||||||||||||||||||
93 | ||||||||||||||||||||||||
94 | ||||||||||||||||||||||||
95 | ||||||||||||||||||||||||
96 | ||||||||||||||||||||||||
97 | ||||||||||||||||||||||||
98 | ||||||||||||||||||||||||
99 | ||||||||||||||||||||||||
100 | ||||||||||||||||||||||||