|
||||||||||||||||||
We've had a few questions come up about some of the environments the teams are working in, and also questions about why it takes so much time to implement Colleague. The two questions are actually linked. The Stages and Accounts First off, we have three stages of an implementation, and each stage takes place in a certain "account":
There are also other accounts (Conversion, Development, etc.) but they're outside of this discussion, so we won't touch on them.
Where we spend most of our Time Here's where the "time" issue is linked to the accounts. Most of a team's time during the implementation is spent in the Test account. The reason for this is that Colleague is an incredibly flexible system. We need understand how it will behave depending on how we set the many codes and parameters. It takes months and months to test it thoroughly.
Additionally, since Colleague is an integrated system, we need to check more than just our own module. We need to make sure our codes work properly in the other teams' modules too. Since we're implementing almost two dozen modules, that's a lot of cross-checking.
Given that much setup in that many environments (and we haven't even discussed conversion of data from the legacy systems), you start to see why we work in so many environments, and why it simply takes so much time.
Find out more about the CTC Colleague Implementation
|
||||||||||||||||||
| ||||||||||||||||||
