Students and employees at the Lucerne School of Computer Science and Information Technology are involved in various small and medium-sized projects. In some cases, these projects not only involve pure software development but also include aspects of product development.
Especially in these project assignments, lecturers and project partners not only expect the delivery of working software, but they also require an adequate and documented development process, traceable requirements, software architecture documentation, and proof that the software does what it is expected to do.
Nowadays, agility is a de facto standard for all processes. Many of the common process models used in the commercial software development industry (e.g., SAFe [1], Hermes [2], V-Model XT [3], Prince2 [4]) describe iterative and incremental development and ways to maximize customer feedback. To use these frameworks in small or medium-sized projects, they must be tailored, which requires a lot of skills and know-how about these models.
With this “agile@HSLU” guideline, the authors want to point out some key success practices, offer tips for successful project implementation and provide templates mainly for project documentation and secondary for product documentation.
This guideline does not cover all types of ICT projects. Namely infrastructure projects and projects to develop strategies are not being discussed.
