The project was executed using a tailored version of Prince2 project management methodology.
It was schedule driven and managing it demanded flexibility and creativity to produce what was needed, taking into consideration all the constraints present at the time: Time available to implement BFO at Gemini North (GN), two years.
The project had to be done in a matrix resources environment.
There were only three resources assigned exclusively to BFO.
The implementation of new capabilities had to be done without disrupting operations.
And we needed to succeed, introducing the new operational model that implied Telescope and instrumentation Operators (Science Operations Specialists - SOS) relying on technology to assess summit conditions.
To meet schedule we created a large number of concurrent smaller projects called Work Packages (WP).
To be reassured that we would successfully implement BFO, we initially spent a good portion of time and effort, collecting and learning about user’s needs. This was done through close interaction with SOSs, Observers, Engineers and Technicians.
Once we had a clear understanding of the requirements, we took the approach of implementing the "bare minimum" necessary technology that would meet them and that would be maintainable in the long term.
Another key element was the introduction of the "gradual descent" concept. In this, we increasingly provided tools to the SOSs and Observers to prevent them from going outside the control room during nighttime operations, giving them the opportunity of familiarizing themselves with the new tools over a time span of several months. Also, by using these tools at an early stage, Engineers and Technicians had more time for debugging, problem fixing and systems usage and servicing training as well.