17/09/2012 ->
I Created the Facebook group.
It is Time to meet the team.
23/09/2012 ->
I was voted to be the Project Manager.
I Created the GITHUB.
The team needs to start working together, I still don’t know either of them…
26/09/2012 ->
The team started working on D1. Chamila is working hard; I still don’t know who Dmitry is, and I’ve definitely seen Fiona.
D1 was easy. I unloaded the D1 draft.
27/09/2012 ->
The team needs to start working together, I still don’t know either of them…
26/09/2012 ->
The team started working on D1. Chamila is working hard; I still don’t know who Dmitry is, and I’ve definitely seen Fiona.
D1 was easy. I unloaded the D1 draft.
27/09/2012 ->
Yey free University GITHUB for 2
years.
Yeyx2 DREAMSPARK from the University will give us free Microsoft products.
The Windows interface is awful.
The command line is similar to svn, which is good.
Yeyx2 DREAMSPARK from the University will give us free Microsoft products.
The Windows interface is awful.
The command line is similar to svn, which is good.
9/10/2012 ->
We have been working on D2 on and off since we submitted the D1 draft, we need to start meeting regularly.
10/10/2012 ->
Organizing the team proves to be hard work. Some of the team members rarely show, others are often unavailable, and out of reach.
Dima had to organize the GITHUB as we decided but he didn’t do anything, I will do it.
Fiona updated the wiki.
We have been working on D2 on and off since we submitted the D1 draft, we need to start meeting regularly.
10/10/2012 ->
Organizing the team proves to be hard work. Some of the team members rarely show, others are often unavailable, and out of reach.
Dima had to organize the GITHUB as we decided but he didn’t do anything, I will do it.
Fiona updated the wiki.
Alex made the charts (they look
amazing).
14/10/2012 ->
Team meeting about the interview didn’t go as planned… we didn’t think of many good questions.
I am getting a bit afraid about how the team is working together- Cham is working regularly, Alex is working hard when he is available, Fiona rarely stays with the team and Dima is often somewhere and can’t be reached….
14/10/2012 ->
Team meeting about the interview didn’t go as planned… we didn’t think of many good questions.
I am getting a bit afraid about how the team is working together- Cham is working regularly, Alex is working hard when he is available, Fiona rarely stays with the team and Dima is often somewhere and can’t be reached….
26/10/2012 ->
No one in the team accept me has started their blogs. I hope this is not a big problem.
No one thought about the risk of bad time management. The other courses are giving regular information about the tasks, but we are leaving all of the work for the last moment, which is not good. We haven’t worked on PSD for the past week or so….
Cham starts organizing the team.
I am up for working during the weekend.
29/10/2012 ->
It’s time to start working on D3.
No one in the team accept me has started their blogs. I hope this is not a big problem.
No one thought about the risk of bad time management. The other courses are giving regular information about the tasks, but we are leaving all of the work for the last moment, which is not good. We haven’t worked on PSD for the past week or so….
Cham starts organizing the team.
I am up for working during the weekend.
29/10/2012 ->
It’s time to start working on D3.
We are moving our work to the Sir
Allan Williams, instead of the Boyd Orr, so we can have access to a bigger
white board that only the team is going to use.
30/10/2012 ->
30/10/2012 ->
I messed up the interview.
We learned a thou:
want a standard ad format for new system
needs to be limited to students and staff within CS
system not to cope with application, just with the advertising of internships
companies dont need to be notified by system that the advert isnt suitable
students still able to find interships outwith system
could have limit to the number of people who can accept certain interships (dont think that's part of the system though but not sure)- have a bit in the ad template for number of places available, possibly expiry date for applicatiotn
search system would be helpful but not vital
students should be able to notify coordinator through the system when they accept an offer
I started organizing D3 is a more fashionable way, for the team to use. UML diagrams are not as simple as I tought -> time to read through PSD lectures.
31/10/2012 ->
The team talked to other teams, to compare notes and there are differences…
Q&A notes :
-there should be a standard form offered for ads so that companies know what info is important/useful + jeremy said we could put a textbox for any additional comments
-if a student gets an internship that is not on the system they should be able to submit a form to tim with the info on it so he can approve it (things like project scope, contact details of manager, who the internship is with, is it paid, duration, when they'll be there etc) - similar to ad form but not the exact same
-maybe have some kind of deputy coordinator so if tim gets hit by a bus then someone else can be in charge til he's better - tim can add more admin people so they can do all the same stuff as him?
-students don't usually receive direct offers from companies - club 21 woman said companies usually tell her and she notifies students
-tim will receive the ads and if they're suitable he can publish them, if not he can send them back to the companies and they can edit it. after publication ads can no longer be edited by companies unless they withdraw the ad and then resubmit it.
-big companies will want to use their own application processes, just have a link in their ad, but smaller companies can have application through the system. club 21 ads will also not go through the system, they'll go through the club 21 application system.
-employers have different special passwords and usernames, they can email tim in order to get these.
-system shouldn’t keep track of students without placement but tim wants a way to be able to view status of people registered in system so he can shout at people himself - he also thought it would be good for him to be able to see who had applied to what and the status of people's applications were. jeremy also said something about wanting a downloadable csv file.
-tim should get some kind of notification when someone gets a placement, i think he said the student would do it themselves, maybe with the form he was talking about (^in the second point) he also kept talking about getting tweets when it happened (cos of how much he hates email)
-the system could steal info from my campus if we wanted to get address and things like that
- they said being able to give feedback on internships would be a good idea and probes useful to people for the next year but not an essential function.
-they said club 21 woman currently tells Tim about appropriate placements and that they'd like to keep it that way
- the ads will be removed by the coordinator or companies when they are filled or if they are out of date. ads could have closing dates and be taken down after that has passed.
-system needs to be accessible from outside uni to employers
-have some kind of mailing list (to replace the Moodle mailing list) so students get an email (Tim brought up tweets again) when new ads come up. Jeremy got very excited about having options for only getting one email a day about new ads instead of getting an email every time there is a new ad (Tim didn't agree cos he was being super grumpy and trying to spoil all the fun Jeremy was clearly having) Tim said students should only be able to opt out of this when they had found a placement.
-should be able to tag who placements are (un)suitable for, eg suitable for SE/ESE or only suitable for CS people or whatever.
-tim wants to be able to see everything (published/unpublished ads, who's applied for what etc) students should be able to see all published ads and companies should only be able to see things that they have submitted (club 21 woman thought this was a particularly good idea to stop all the companies being dicks)
-there shouldn't be a limited number of applicants per placement, but it would be good to have an option to say how many places were available
-if placement falls through - can be readvertised, and coordinator can remove the accept for the student but finding the affected student would be dealt with outwit the system.
We learned a thou:
want a standard ad format for new system
needs to be limited to students and staff within CS
system not to cope with application, just with the advertising of internships
companies dont need to be notified by system that the advert isnt suitable
students still able to find interships outwith system
could have limit to the number of people who can accept certain interships (dont think that's part of the system though but not sure)- have a bit in the ad template for number of places available, possibly expiry date for applicatiotn
search system would be helpful but not vital
students should be able to notify coordinator through the system when they accept an offer
I started organizing D3 is a more fashionable way, for the team to use. UML diagrams are not as simple as I tought -> time to read through PSD lectures.
31/10/2012 ->
The team talked to other teams, to compare notes and there are differences…
Q&A notes :
-there should be a standard form offered for ads so that companies know what info is important/useful + jeremy said we could put a textbox for any additional comments
-if a student gets an internship that is not on the system they should be able to submit a form to tim with the info on it so he can approve it (things like project scope, contact details of manager, who the internship is with, is it paid, duration, when they'll be there etc) - similar to ad form but not the exact same
-maybe have some kind of deputy coordinator so if tim gets hit by a bus then someone else can be in charge til he's better - tim can add more admin people so they can do all the same stuff as him?
-students don't usually receive direct offers from companies - club 21 woman said companies usually tell her and she notifies students
-tim will receive the ads and if they're suitable he can publish them, if not he can send them back to the companies and they can edit it. after publication ads can no longer be edited by companies unless they withdraw the ad and then resubmit it.
-big companies will want to use their own application processes, just have a link in their ad, but smaller companies can have application through the system. club 21 ads will also not go through the system, they'll go through the club 21 application system.
-employers have different special passwords and usernames, they can email tim in order to get these.
-system shouldn’t keep track of students without placement but tim wants a way to be able to view status of people registered in system so he can shout at people himself - he also thought it would be good for him to be able to see who had applied to what and the status of people's applications were. jeremy also said something about wanting a downloadable csv file.
-tim should get some kind of notification when someone gets a placement, i think he said the student would do it themselves, maybe with the form he was talking about (^in the second point) he also kept talking about getting tweets when it happened (cos of how much he hates email)
-the system could steal info from my campus if we wanted to get address and things like that
- they said being able to give feedback on internships would be a good idea and probes useful to people for the next year but not an essential function.
-they said club 21 woman currently tells Tim about appropriate placements and that they'd like to keep it that way
- the ads will be removed by the coordinator or companies when they are filled or if they are out of date. ads could have closing dates and be taken down after that has passed.
-system needs to be accessible from outside uni to employers
-have some kind of mailing list (to replace the Moodle mailing list) so students get an email (Tim brought up tweets again) when new ads come up. Jeremy got very excited about having options for only getting one email a day about new ads instead of getting an email every time there is a new ad (Tim didn't agree cos he was being super grumpy and trying to spoil all the fun Jeremy was clearly having) Tim said students should only be able to opt out of this when they had found a placement.
-should be able to tag who placements are (un)suitable for, eg suitable for SE/ESE or only suitable for CS people or whatever.
-tim wants to be able to see everything (published/unpublished ads, who's applied for what etc) students should be able to see all published ads and companies should only be able to see things that they have submitted (club 21 woman thought this was a particularly good idea to stop all the companies being dicks)
-there shouldn't be a limited number of applicants per placement, but it would be good to have an option to say how many places were available
-if placement falls through - can be readvertised, and coordinator can remove the accept for the student but finding the affected student would be dealt with outwit the system.
Fiona collected the data perfectly,
its time to update D3.
D3 is broken for no apparent reason… someone pushed before pulling and committing… we need to go a few versions back and rewrite everything….
There are major problems with umbrella.
D3 is broken for no apparent reason… someone pushed before pulling and committing… we need to go a few versions back and rewrite everything….
There are major problems with umbrella.
Alex has problems with his lap top,
we need to cover for him.
1/10/2012 ->
D3 Uploaded in in 3am we really need to start working on time. The UML diagrams took a lot of time.
I was ill and didn’t stay much on the computer that nigh. The team never assessed the risk of some of the members to be away -> we dynamically redistributed the tasks of the missing person between the members that are working.
5/10/2012 ->
I restructured Github so that it can have a BETA folder in which we work before we move the things to a FINAL folder, less troubles with the commits.
7/10/2012 ->
We had a team meeting with Tim, but it was only me and Fiona.
The team meeting was moved to later in the day, I won’t be able to attend because I have a doctor’s appointment, Alex and Cham are aware with my parts of the documentation.
16/11/2012 - >
Yesterday the team met and talked about what needs to be done:
4 days (until the deadline ) - fix all the
documentation
(D1 has little
mistakes, D2 needs to be updated, D3 needs to be rewritten)
6 days (gather info) - ask friends and ppl
about their requirements. Be sure what you write.
(We
are collaborating , not cheating !)
9 days (prototyping) - make the prototype of
the PSD project and submit on the 29th :)
(Cham will be a bash master at that point to
everything will be ok... i hope)
We don't have much time to do anything accept study... I am not complaining that's what we are here for. project management appears to be a tough job... now I understand why project managers are sad.
Alex was ill that
meeting.
Cham agreed to
look into bash so that he can be our bash expert.
Fiona is a
bit concerned about all the things we need to do relate to uni. (Time
management will be crucial).
Dima, silent
and mysterious as always - there are always good ideas in that head
of his but he rarely shares.
I am tired from
all the work and uni assignments.. can’t wait for
the 3rd of December when i can start working on some
projects of my own.
23/11/2012 ->
The prototype clarified lots of things on the project, so there will be lots of things to update in the D1-D4 documentations. Many of the things we tough the system was supposed to be is just things we imagined, but the client just wanted a simple thing that works well. There are lots of things we were not exactly clear how to do, but after the actual work on it, everything is clearer.
The use cases are things that must generally happen often and describe the system in terms of actions.
The risks are not RISKS, they are problems we face during the clarification of the system.
The prototype is just the main modules set up to demonstrate what our program might one day do, so that WE and the CLIENT can just see what’s going on.
There should be lots of client meetings if possible, the more output on our work we get the better understanding we get for the overall project.
The QA doesn't work on the actual project ONLY, they work on everything including the documentation!
The Managers’ work is hard; he needs to keep everything up to date including the people in the team.
The librarian needs to work a lot during the documenting stage, and he needs to hold lots of information, I understand why people fall in love with their smart phones.
The tools smith is the no only the know it all type of guy, he's also the do it all type of guy when there is a problem.
Clarification a bit late in the semester.
27/11/2012 ->
My posts are separated in a few different things and not in a single blog:
GITHUB
Blogger
Word Document
Ipad Notes
I am staring to collect data from all things.
Missing the Q&A was not a good thing, I cannot help with all the documentation points.
Fiona is collecting data perfectly and I feel very confident that the team didn’t miss anything important.
D3 -> needed changes; I restructured the whole document and changed the views. The new structure is easier to use by all the team members.
Some team members are waiting the for last moment to update their parts in the documentation, this has been happening since the beginning.
I restructured the GitHUB… it was a mess and nothing could be found in the folders.
I fell sick… Alex will cover the ChangeLog.
I started doing the rest of my tasks regarding the documentation.
29/11/2012 ->
I did the ChangeLogs. Restructured D3 and D2.
It is going to be an all-nighter in the labs working on the documentations… someone broke something.
Alex messed up the “&” symbol in D3 and that’s why the LaTEX was breaking.
Submission in 5am in the morning… the Dx documentations have been submited
No comments:
Post a Comment