Regular projects have a Team size of at least two people, and a Project Lead person that is not part of the Team (or only for very well defined small tasks). Usually regular projects organize themselves according to the SyBIT Scrum process.
Regular Project Default Charter, Scrum-based
Non-agile project style where the project is launched using a classical set of milestones and the project needs to report only once during its duration and at the end. It is mandatory for classical projects that the end-user community that benefit from the project are very actively participating in the project itself so that the results are assured to be useful and in use.
Classical Project Default Charter, Milestone-based
Small projects have only one, max two persons in the project team and the Project Lead is one of them. The person in charge is responsible for the interaction with the Science Lead and the scientists, and in case of trouble needs to interact with the local SyBIT team head or the Process Master.
Small Project Default Charter Simplified
Deployed services are being supported actively. Users receive help concerning running the service, configurations, usage, and of course when they find bugs. Regular, Small and Classical projects can also be Support projects in addition, so they do not have an additional charter, but the project charter should describe how the interaction with the user community is set up, what the support channels are, etc.
Main type charter
Most projects are Regular or Small. Classical projects are not preferred due to the fact that corrective measures can not be taken regularly, so the risk of failure is higher. They are kept for the simple reason that agile development methods are not implemented by all SyBIT partners - it is a culture change which people have to want to implement and SyBIT cannot force this, especially at partner institutions where it is just one of many projects people participate in.