Overview

Project Suez is a very large and complex project with multiple architectural and business decisions. The team in Belarus (“iTransition”) are responsible for producing the end result, however there is a good deal of oversight required from the development team in Windsor. The development team in Windsor has many other tasks currently in operation and interruptions can have a serious consequence, so any interruptions need to be minimised.

Proposal

The proposal to circumvent the interruptions is that James Seabrook is to act as a “gatekeeper” and fielder of questions to the development team on behalf of anybody outside the development team. This will have two benefits: firstly that developer's time will be better managed and secondly that James will obtain information about the project and its status which should help with answering questions further down the line.

The “gatekeeper” role will commence on Monday 19th April 2021. Every Monday morning the development team will meet to discuss the proposed work for the week along with how much time is necessary for those tasks. Any unresolved issues will also be discussed.

During the week people who wish to ask information of Mark Blair, Gurminder Singh, Danny Li will be requested to ask the question to James Seabrook instead and indicate the urgency. James will collate them and present them to the appropriate developer(s) for consideration on the following morning, or possibly the same day for very urgent matters.

Responsibilities

It is the responsibility of all people who wish to discuss a subject or ask questions of the development team to remember to communicate that topic to James Seabrook instead rather than directly to the developer. If by email the developer should not be added into the “cc” field as that will be likely to inadvertently cause an interruption.

James will collate questions and discussion topics in as much detail as possible and organise appropriate times for those discussions to take place, as well as taking comprehensive notes to be able to respond back where appropriate and to keep a record of project status and decisions made.

The development team will update James regularly if too many direct interruptions continue.

Conclusion

This is an initial attempt to alleviate the development team of ad-hoc interruptions and instead have a controlled flow of those questions and discussion points. The proposal here is simply that; it is not claimed to be the perfect solution and will be as flexible as possible. Any comments and suggestions about the process will be gratefully received.

Regular Notable Events

Monday

All: Development Team Discussion:

• plan for the week ahead

• work out meeting times for outstanding discussion points

Friday

Mark Blair: Release preparation normally every 2 weeks for release on Saturday. Calendar entry will be created.