The Portfolio

The portfolio consists of the ICT products that you established in the course of the project. Think of the projectplan/PID, a requirements document, an advice report, an investigation of technologies, an architecture document, a test report, wire frames, code, task board, burn down charts, your blog, etc, etc. The portfolio should be grouped per competency (analysis, advice, management, design, implementation) or in chronologic order. All the products of the portfolio (including code) must be part of the submission. Thus, hyperlinks in the portfolio document (leeswijzer) should be relative within the submitted portfolio and should not refer to an environment external to what you submit. E.g. a link to a GIT archive or an electronic scrum-taskboard on a network is not allowed, in these cases take snapshots or take images/screenshots. The portfolio must help the jury to get an understanding of your work. It does not have to be fully complete (e.g. if all code is difficult to share, think of a few samples that give an indication of the most challenging parts).