|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ENKÄTER | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Visa resultatHär kan se resultatet från utvärderingen och exportera statistiken till ett annat program. Det går också att göra en enkel filtrering genom att klicka på svarsalternativen och kommentarerna eller en avancerad filtrering genom att använda knappen längst ned.
Agile development processes, Lp4 VT11, EDA397/DIT191Status: AvslutadÖppen för svar: 2011-05-26 - 2011-06-05 Antal svar: 43 Procent av deltagarna som svarat: 43% Kontaktperson: Rebecca S»
Your own effort1. How many hours per week did you spend on this course?*43 svarande
Genomsnitt: 2.79 (bidrar till totalt genomsnitt/jämförelseindex) 2. How large part of the teaching offered did you attend?*43 svarande
Genomsnitt: 4.2 (bidrar till totalt genomsnitt/jämförelseindex) Genomsnitt totalt för detta stycke: 3.5 Goals and goal fulfilment3. How understandable are the course goals?43 svarande
Genomsnitt: 2.9 4. Are the goals reasonable considering your background and the number of credits?35 svarande
Genomsnitt: 2.08 5. Did the examination assess whether you have reached the goals?43 svarande(på denna fråga var det möjligt att välja flera svarsalternativ)
- The final exam was well written. However, the mini-exams had a lot of weird questions, why does it matter whether rock climbing is like SE or not? Makes no sense, its the understanding of the metaphor thats important not the metaphor itself...» (To some extent) Teaching and course administration6. To what extent has the teaching been of help for your learning?42 svarande
Genomsnitt: 3 - Teacher is not easy to listen to. Talks very monotone and the entire lecture flows in one big chunks which makes it very hard to concentrate through the entire lecture, since one does not know when one part ends and the next one begins. Teacher is obviously a researcher and not a pedagogic. Would have been easier to receive list of requirements and then choose whether to listen to lecture or study alone. Also teacher goes too deep into explaining how research was done, thus easily loosing the interest of students.» (To some extent) 7. To what extent has the course literature and other material been of help for your learning?43 svarande
Genomsnitt: 2.58 - The main book chosen for the course was a little bit out of scope » (Small extent) 8. The use of Twitter added value to the course?43 svarande
Genomsnitt: 3.58 - I don"t have a twitter account and won"t make one just for this course. So, twitter was the same as checking out the course page for me.» (Disagree) 9. The use of video recordings added value to the course and/or your learning?43 svarande
Genomsnitt: 4.37 - Didnt fine time to listen to the recordings, but can be useful if the student is interested to learn more.» (Disagree) 10. How well did the course administration, web page, handouts etc work?42 svarande
Genomsnitt: 3.21 - Almost none information about if and when and where the mini exam would be held. Our group missed mini exams due to that the lab assistance didn"t visit our group during the mini exam day, which we on our hand didn"t know was that day.» (Very badly) Study climate11. How were the opportunities for asking questions and getting help?42 svarande
Genomsnitt: 3.45 - A group for the course could have been setup allowing the students to discuss on the various topics of the course, project and questioners » (Rather poor) 12. How well has cooperation between you and your fellow students worked?43 svarande
Genomsnitt: 3.53 - One of the best group work experiences. Robert does not specify ways he"d individually grade students within the group, and this generally improves group dynamics. » (Very well) Summarizing questions13. What is your general impression of the course?43 svarande
Genomsnitt: 4.06 - Teacher was very knowledgeable in the area. Not an agile project, more like 60% learning android, 30% testing and 10% agile. » (Fair) 14. What should definitely be preserved to next year?- SCRUM, lecture contents»- The project, because it gives experience with the practices, not just theory. » - The project.» - project: Android development with Agile methods» - Everything in general» - Practical experience of working in agile methodologies,workshops etc.» - Recordings of lectures, the coursebook, the idea of working on an android product» - project was good but i think pair programing get better result n´,because we want get experience at university and by this method shraing knowledage is more than Scrum meyhod » - Feldt» - The project with Agile methodology.» - The book, Robert, having a project, having a good and up to date page and so on, the "softer" subjects.» - robert field as course manager » - The practical part» - The project, perhaps the mini-exams, but they need better structure, and the exam.» - Scrum» - Obviously the project (Android), but a different project. Anything which would have been useful. Since the one which was developed in the project is going to be shunted and would be just a code repository. » - course material» - Course book + Project» - Android platform should be preserved.» - The group project for trying out different practices» 15. What should definitely be changed to next year?- ANDROID is a bad choice. This is not an android course. Please choose a platform everyone or most know.»- Since the focus of the course was on following processes there could be better follow-ups on that during customer meetings. Now, it felt more like we were focusing on the application which was fun but I don"t think that was the main purpose of the course.» - More guidance on TDD.» - There needs more introduction to TTD, and how one should work on it if it should be included within an Android project.» - Maybe do the project more structured (mandatory steps/checklist for processes and more interaction from the assistants) and a little smaller (from 15h per week to 10h maybe?). Spending 15h per week on the project were only 10-20% involved the process and the rest was coding seems a bit inefficient since the goal is to learn about the process and not coding. » - Use a platform that everyone have experience with. Maybe more formal meetings with the customers, i.e. scheduled meetings, so the meetings don"t get so rushed.» - Perhaps a bit more guidance about the process in the project.» - A couple of research papers» - There should be dedicated physical spaces to the groups when working on the agile projects as one of the requirements of these methodologies and also I would like to see XP and Kanban more in practice as part of our project experience as we had SCRUM.» - -The project size was a little mismatched with the group size, leading to some issues, possibly limiting the learning of agile practices. -Would be good to have a better introduction to TDD. I believe TDD is a good practice, but requires some work to get into it. I attended a good, extensive guest lecture on TDD by Micael Andersson from Volvo IT at GU this period. Maybe it"d be a good idea to invite him for this course next year?» - Not using Sikuli-testing (does not feel agile, seems out of scope, even if was a good practise)» - written exam is not sutable method to assess student .I prefer home exam just» - SVN, more lab assistants (or less time spent in each group, or more switching or whatever, we don’,t want to wait for four hours)» - The weekly test should be changed into home exam. Because students usually do not have enough time to attend it, while they are doing the project on workshop day.» - I might change a few bits and most of it is to get more out of the project. I think it"s great to have a project, and take it from start to finish and doing it using Scrum (or any other "agile-process"). But there is a few things that I think can improve the learning from the project further. First of all having such short iterations, especially a project that you did not work full time on, made waiting for the acceptance test and similar taking up a big portion of the project. Being restricted to not work outside the group with the project I think is a good thing but it made the impact of time lost on such things bigger and to keep up it was easy to "cheat" by not taking the time to trying out all practices and such. Maybe that is "agile" but some experiences were also lost because of it. Making the iterations two weeks I think would help, but of course then you have half the amount of iterations but I think this would still be preferred. The theme of the project also had some impact. The problem were sometimes a little "small" to make it possible to make a good division of work, and also learning a new platform that is different from what people is used to put a lot of focus and time on the platform and not the process. The project do not have to be complicated, but working on Android with such a small project made it hard to sometimes divide the work because a lot is happening in the same files/classes or whatever. The project can be something that is less "cramped" but still not more complicated, hard to explain, hope you got the point. But I think it should still be something that feel real and not something too much constructed and unrealistic. This is getting long so I might just take one more point, and that is the TDD parts. First of all the TDD workshop did not feel the best, especially comparing to the one that the TCP project had a few days after. It felt like there would be possible to bring in someone that have more experience with TDD because I think many students missed the point. TDD is not always the most easy and it is a new way of thinking and working. I think the best would have been having a better workshop on TDD, having a better concrete example and best is if it used the platform that was going to be developed on. Showing some best practices and making a small application basically from start to finish with a basic user story or two to show the whole process, and of course the best would be to have someone with the experience that can answer all the questions. It would take time yes, but I think this would serve much better. It is hard to show, teach and learn TDD in a few hours so these hours need to be good. And one last thing even though I said the previous was the last. Reading the book Cockburn talks about different levels of learning and understanding, and how this must affect the teaching on different levels. Given the fact that most students is basically on the first level and the first level need concrete examples, almost being told "do this and do that" I think some more concrete workshops on different things would have been good. Why not role play a small project while the class can observe? Playing out scrum meetings, customer interaction, and so on, for an iteration or two. I don"t know, maybe overkill, but even if I really liked the why in the course and having previous experience I could apply this to things I think many people missed the points sometimes and did not know where to start and what to do. Agile is about adapting and discovering how to best work, but being new on the first level of understanding there must be somewhere to start to be able to change. Being told and showed in the beginning of the project on how to do things like the scrum meeting and seeing how much that have changed in the end would have been a good thing to observe to see if the retrospectives were put to good use or not for example.» - the project part should be less intensiv 15 hours zas too much » - Better intro to testing/tdd + Showcase it on a real android project.» - I think theoretical part should have less weight in the marks (results) and/or be easier.» - I lacked "customer" participation in the sprint planning phases, of course this might be hard to handle with the large amount of students.» - Less tdd» - More check on the student groups» - The Time spent during the Lab sessions (or with the customer) during the 2 days in the week. In our project we wasted a lot of time during those 4 hours in each day. It can be reduced to 2 hours. We simply had to wait for the customer for Acceptance tests and user stories discussions for every week. This is complete waste of time when the student has two courses where he has to spend the time in a balanced way. » - A project based on a language we all know,familiar platform,so that we concentrate more on learning the principles of the course rather than learning the new platform like android» - Stick to promises, please!» - Labs.» - Remove miniexams!!! They added no value and the administration of them was poor. Or if you decide to keep them: provide clearer info about when and on what they will be and have more strict, observed "miniexam-time".» 16. Additional comments- Some students took the course with limited or no prior programming experience. These students came from a more management background. Which did not fit with the current course and its project. Please update the prerequisites for the course.»- This was one of the better courses I have read recently.» - The Program Manager for SEM created problems for students take this course as its not part of the original plan (by asking mandatory course instructors to be strict with conflicting schedules for example). This course should be mandatory. » - I think the projest take a more time and student that have 2 course cannot mange both them I got feedn´,back of some student they left another course because for project we need more work,mini exam was good but i think it was not useful bcz we donot have extra rtime to study ,written exam must be change because agile is not memorising we have to understand and research ,Home exam may be more useful of written exam » - Peer assessments were supposed to be anonymous but during workshop somehow the results were announced which was very bad because everyone could figure out who did not work and that person was ashamed in front of others.» - Really good course to learn Agile and enhance android programming skill.» - Even though the what should change box is filled to the brim and a little bit more I think the course was great and I had fun and learned a lot. I just think that the project could have been put to a little better use.» - a particular thanks to Robert Field » - Collective punishment for some people cheating on the first mini-exam is not ok.» - I think the importance to read the book and the location of the papers should be highlighted more in the introduction class. It took me several weeks to realize about the location of the papers, the slides were obviously not enough.» - Very tough but great course! It feels nice to have high demands on a course, it motivates to really study and learn!» - Better way of scheduling, planning and restriction on the number of students register for the course.» Additional commentsBeräknat jämförelseindex: 0.62 * obligatoriska frågor
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11%