Advertisement

A Case Study — Hindrances and Success Factors in Student Projects

  • Marta Kristin Larusdottir
Part of the IFIP – International Federation for Information Processing book series (IFIPAICT, volume 289)

Third year undergraduate students in Computer Science at Reykjavik University complete a practical project in which co-operation between the students and the industry is emphasized. The students form small groups and develop software for eighteen weeks at a company's site where they get access to all needed facilities. In this study the students were asked to state the hindrances they experienced. Data was gathered from eleven student groups both with interviews and on-line questionnaires three times during the project period. Furthermore a contact person at each company was interviewed one month after the delivery date and asked to rate the quality of the project work. Based on that rating the groups were divided in three categories, the best, the middle and the worst. The success factors characterizing the best groups were analysed. Also the customers were asked to rate what quality factors of the product they emphasized the most. The students did not experience many hindrances five weeks after the commencement of the project, but after nine weeks 73% of the groups named that understanding the requirements of the project was a hindrance. The methods of Human-Computer Interaction could be of great value for the students in these two periods, understanding the user, their tasks and the context of use. When only 4 weeks were left of the project the biggest hindrances for the groups were technical problems and lack of time. A study of the work of the best groups showed that the main success factors are: being very organized, keeping good co-operation in the group, and getting feedback from the customer and the users.

Keywords

Software Project Project Work Feedback Channel Project Period Student Project 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. 1.
    Standish Group, Chaos Report, 1994, (cited December 2007), http://www.standishgroup.com/sample_research/chaos_1994_1.php
  2. 2.
    J. Johnson, My Life Is Failure: 100 Things You Should Know to be a Successful Project Leader. Standish Group International, West Yarmouth, MA, 2006.Google Scholar
  3. 3.
    K. L Linberg, Software Developer Perceptions about Software Project Failure: A Case Study, Journal of Systems and Software, 49(2–3), pp.177–192(1999).CrossRefGoogle Scholar
  4. 4.
    Procaccino, J. Drew, Verner, June M. and Lorenzet, Steven J. Defining and Contributing to Software Development Success, Communication of the ACM, 49(8). pp 79–83 (2006).CrossRefGoogle Scholar
  5. 5.
    Dannelly, R. Stephen, DeNoia, Lynn, Student Opinions of Software Project Success, Proceedings of the 45th Annual Southeast Regional Conference, (Winston-Salem, North Carolina 2007), pp. 327–330.Google Scholar
  6. 6.
    J. M. Verner, N. Cerpa, Australian Software Development: What Software Project Management Practices Lead to Success?, in: Australian Software Engineering Conference (ASWEC'05), (2005), pp. 70–77.Google Scholar
  7. 7.
    R. Berntsson-Svensson, A. Aurum, Successful Software Project and Products: An Empirical Investigation, Proceedings of the 2006 ACM/IEEE International Symposium on Empirical Software Engineering, 2006, pp. 144 – 153.Google Scholar
  8. 8.
    ISO/IEC TR 9126, Software engineering — Product quality, 19-12-2000.Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2009

Authors and Affiliations

  1. 1.School of Computer ScienceReykjavik UniversityReykjavikIceland

Personalised recommendations