We all know them. Those holes that we know in hindsight that we fell into face forward. And how nice would it have been if we had known about them beforehand? We have listed a few obvious ones. You will be amazed at how often these things go wrong.
Pitfall: The test environment is not considered safe
Solution: Involve the examination committees (or equivalents within your organization) and the Security Officer from the start. Have both constantly indicate what the expectations, requirements and wishes are and ensure that these are met (or that a compromise is necessary for plausible reasons).
Pitfall: Teachers don't have time
Solution: Try to organize the teachers through representatives. That teacher with great influence who also knows something about IT. Help this teacher by making time available at management for the project activities.
Pitfall: Starting too fast
Solution: Speeding up is okay. As long as it’s a pilot, take every opportunity to experiment, stumble and learn. But don’t implement the solution until everyone is on board. There’s only one chance to make a first impression
Pitfall: Becoming overconfident
Solution: Stay humble. Start small and simple. You can always scale up in volume and complexity. Find easy keys to start with.
Pitfall: Involving dependencies in the project. “If we’re going to tackle this, can’t we also…” is often the beginning of the Gordian knot with which IT projects doom themselves.
Solution: It’s nice to be able to take some things with you right away, it hurts when those things become dependencies. Always consider whether the things you do are really necessary or whether they could be done later. Ask the question: “Do we need to do this now?” five times. Each time with the emphasis on a different word in the sentence.
