It's UWAweek 47

help3200

This forum is provided to promote discussion amongst students enrolled in CITS3200 Professional Computing.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 2 articles in this topic
Showing 2 of 129 articles.
Currently 1 other person reading this forum.


 UWA week 31 (2nd semester, week 2) ↓
SVG not supported

Login to reply

👍?
helpful
4:38pm Thu 1st Aug, ANONYMOUS

Hi Michael, In the timesheet's General Tasks page, are we supposed to enter our estimates for the time remaining for every task every week? I understand they should change over time as we reevaluate requirements, but since we're still gathering information about the scope of the project, it's difficult to accurately assign the time remaining for some tasks this early on (e.g. testing). Or are we only supposed to enter estimates for the tasks that we have started working on, (such as research and meetings) and add the estimates for other tasks in future weeks as we better understand the scope of our project? Thank you


 UWA week 32 (2nd semester, week 3) ↓
SVG not supported

Login to reply

👍?
helpful
12:03pm Thu 8th Aug, Michael W.

ANONYMOUS wrote:
> Hi Michael, > > In the timesheet's General Tasks page, are we supposed to enter our estimates for the time remaining for every task every week? I understand they should change over time as we reevaluate requirements, but since we're still gathering information about the scope of the project, it's difficult to accurately assign the time remaining for some tasks this early on (e.g. testing). > > Or are we only supposed to enter estimates for the tasks that we have started working on, (such as research and meetings) and add the estimates for other tasks in future weeks as we better understand the scope of our project? > > Thank you
Hi, Time remaining only needs to be updated each week based on the actual time spent versus what has been achieved. In the worst case it could grow! As you have just started, all entries will just have the estimates for time required. Cheers MichaelW 👨‍🎨

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy