### 12 February 2025 #### Project title: CJ migration to EE5 Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget: £270,000 Project Dates: Aug 2018 - Jan 2019 **Objective**: To implement a CRM system to replace a legacy one.  **Outcome**: The migration was delivered on time; however, the budget was higher than planned, and the work had to be stopped quite abruptly because of that. The main reason for that was that I was not included in the budget communications between the vendors and the company and thus only learned about the cost constraints very late in the project. The miscommunication issue, however, was properly discussed and addressed in the following projects. **Initiating**: I created the scope document, collected the pain points, identified key deliverables, timelines, and high-level constraints and assessed the risks. **Planning**: I collected project requirements and defined the project scope. I took part in vendor selection and sat in multiple vendor interviews. Based on the initial project quotes, I proposed that instead of migrating to a new system, we use the same system and perform an upgrade to the latest version. I calculated the project cost and developed the project schedule. During this phase, the stakeholders came up with the additional objective of delivering an updated visual design of the website, which I incorporated into the project plan. **Execution**: I managed the internal project team and handled communication between the external vendor and the internal organisation’s stakeholders. This phase included me working as a product owner in conjunction with the scrum master who would handle team and communications on the vendor’s side. **Monitoring and Controlling**: I validated the project scope and controlled quality. The challenge in this process was managing the scope creep - the new requirements from internal stakeholders that I registered as change requests to be delivered after the main body of work was completed. **Closing**: In the end, I presented the outcomes, obtained the stakeholder’s approvals, documented lessons learned and conducted the transition to the next project: refactoring and optimisation of the new platform. #### Project title: CJ Refactoring and Optimisation Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget: £75,000 Project Dates: Feb 2019 - Jan 2020 Project Description:  **Objective:** The project’s immediate objective was to fix the parts of the newly upgraded CMS publishing platform which were corrupted or did not pass regression tests during the previous migration procedure. **Outcome**: Delivery of an improved, refactored CMS. The additional benefit was that by the end of the project, the organisation formed a new division that had not existed before, a Digital Production Team (DTP). The DTP became indispensable in handling the customer’s incoming project and operations work, as well as refactoring and optimising the existing features. **Initiating**: I collected the requirements, identified the main categories of errors to be fixed, and assisted the team in identifying the priorities. I have established a team, based on people who were involved in the previous system migration and thus were familiar with the code. **Planning**: I assessed detailed project requirements along with the team members and led several collaborative and functional meetings between stakeholders and team members. **Execution**: I guided and motivated the team throughout the execution. I led weekly status meetings, noted down the Meeting Minutes and distributed them among the project team members. **Monitoring and Controlling**: I controlled quality and conducted feedback collection through stakeholder face-to-face interviews and via surveys. I have helped in assessing the project budget and resources, ensured the objectives were met and requested regular stakeholder review and feedback throughout the project. **Closing**: I have presented the outcomes to the stakeholders, and obtained the formal acceptance of the project results. I have held a retrospective meeting with the team and created documentation entries in the company’s knowledge base. I have continued to monitor the errors and oversaw the transition from the project into the business-as-usual. #### Project title: Young Russia Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget: £75,000 Project Dates: Jan 2020- Nov 2020 Project Description: **Objective:** To create a new website section that would look distinctly from the rest of the website and include a landing page, sub-category pages and new features such as new types of carousels and a custom navigation header. **Outcome**: The organisation at this point has assimilated the new production unit (DTP) in terms of communications and stakeholder expectations, so we were able to produce all the required features, within the time and budget agreed for the work.  **Initiating**: I have conducted the kickoff meeting with the team to identify key stakeholders and a high-level scope of the project. **Planning**: I developed a project management plan, which includes the project timeline, the three main releases, detailed deliverables, key risks and project scope. In the planning process, I have identified the new requirement to create a UI for the new website subsection. **Execution**: I have led the team through the three releases. The first release was seen as largely unsuccessful due to the poor technical optimisation resulting from confused requirements coming in an ad hoc way from different stakeholders, and therefore had to be largely reworked. I engaged with more stakeholder communication, insisting on more communication and budget transparency, and clarified the requirements. The second version used an entirely new visual design and was more successful in its implementation. The third and final release added the UI functionality. I have conducted user testing after each phase, and have worked with stakeholders to plan the project launch. **Monitoring and Controlling**: I monitored and controlled the project scope, schedule, and budget as much as I could, despite the communications and budget opacity described above. I ensured that the project’s key deliverables were met and requested the team and stakeholders’ reviews and feedback throughout the project.  **Closing**: Obtained approvals from the stakeholders to launch the three consecutive releases, presented the final version to executives and marketing, created the documentation, archived the project work files, ran the retrospective and collected the lessons learned. #### Project title: Elastic Search Integration Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget: £70,000 Project Dates: Mar 2020 - Mar 2021 Project Description:  **Objective:** To create a new search feature that would replace the old one. The new search needed to have a set of filtering options to display results by various website categories, and should have allowed to sort results by date and popularity. **Outcome**: Successful implementation of the search engine (Elastic Search plugin), including the identification of requirements, stakeholder approvals, and technical documentation. The project also encompassed new website sections, such as City and Country pages, which returned new pages based on the search by country and city tags, therefore including Elastic Search engine in their realisation.  **Initiating**: I have identified the project’s key stakeholders, worked with the head of marketing and the designer on the business case and key project milestones, and formulated the high-level risks, assumptions and constraints. For this project, all of the stakeholders had agreed that we were going to involve the external contractor we have been working with up to this moment, specifically the development team who did the platform migration, and who had the context for the new work to be carried out. **Planning**: I have collected the resource requirements and have discussed the project-specific responsibilities with the team members involved. I have created the feature backlog in collaboration with the vendor’s delivery manager. **Execution**: I have used weekly standup meetings to identify impediments, helped the team navigate those impediments, and run periodic stakeholder reviews. Shortly after the start of the project, it became clear that the time of the team would have to be split between this project and other work, so I decided to divide the project into several releases spread over a longer period of time. This has allowed the team to start with implementing the search first, and later focus on extending the other components that were relying on the search feature. For example, Country pages would orgasnise content entries based on the country tags, and the Advanced Search screen would allow the users to filter results based on content format or category. **Monitoring and Controlling**: Using push and pull communication for effective stakeholder communication. User acceptance testing and retrospectives at the end of each release or milestone. **Closing**: Presentation of the work done to the editorial and executive team and creating all necessary documentation. #### Project title: Calvert Journal Film Festival Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget:£50,000 Project Dates: Mar 2021- Dec 2021 Project Description: **Objective:** To deliver a new website section to host a series of 35 online screenings, with a landing page and a login area where tickets can be purchased to view the films. Includes production of the full collection of marketing materials: video and static visuals to appear on social channels and the customer’s website. **Outcome**: A successful integration of the film festival platform with the landing page on the customer’s website. The project enabled the screening of 35 films and reached 100,000 views globally. **Initiating**: I reviewed and analysed project details, including the scope document, stakeholder involvement, participating customer’s information, and film listing data. Established key project milestones aligned with customer expectations. When identifying key deliverables, timelines, risks and constraints, I conducted a make vs buy analysis, and came up with the proposal to adopt a third party festival platform, rather than building the feature ourselves. **Planning**: I evaluated the project requirements and objectives, led a kickoff meeting with functional leads and project team members to establish roles and expectations. Created a project schedule outlining key tasks, milestones, and deadlines. **Execution**: I shortlisted the film platform vendors and facilitated a series of demo sessions with them. Then I led and motivated the team throughout the execution, and conducted weekly production meetings. I зerformed weekly review meetings with senior stakeholders to keep them engaged. **Monitoring and Controlling**: I measured project performance using the critical path method and baselining, working with the project Gantt software. I assessed and monitored risks closely, and ensured that deliverables met stakeholders’ expectations by obtaining regular feedback and facilitated User Acceptance Testing sessions. **Closing**: I obtained feedback from relevant stakeholders, ran a retrospective with the team and documented lessons learned. I also later included the project details in the annual production report for project sponsors.  #### Project title: G Suite Server Migration Organisation: Calvert 22 Foundation Job title: Digital Project Manager Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 4 Project Budget: £30,000 Project Dates: Oct 2021- Mar 2022 Project Description: **Objectives** There were two key objectives in this project. First, to migrate the contents of the previous physical server in the customer’s offices to cloud storage (Google Drive) due to the physical server reaching its age limit and becoming a security risk. Second, implement a backup solution for customer’s Google Drive data. **Outcome**: Successful and timely delivery of both the new server and the backups. **Initiating**: I performed a project assessment based on the customer’s needs and pain points from current server usage and located key deliverables and milestones of the migration process. The two key risks were both connected to accidental loss of data. First, due the lack of server capacity which meant team had largely stopped using it and therefore data could be lost outside of the server. Secondly, following the data migration to Google Drive, the data loss risk required us to create the automated data backups to external storage (AWS S3).  **Planning**: I have reviewed and assessed the project requirements, constraints, and assumptions with stakeholders. I have collected requirements, defined the scope, and identified the team for this project which would consist of one outsourced DevOps engineer, the customer’s Finance Manager and the representative from the IT service company responsible for the maintenance of the customer’s old server. I have estimated the budget and developed the project schedule by decomposing and sequencing activities on the project Gantt. **Execution**: I have obtained and managed the project resources, held meetings with the DevOps engineer twice a week, and managed communication with the IT service contractor, who would provide security credentials for the data transfer and visit the customer’s office to collect the decommissioned hardware. Assisted DevOps in creating the automated data backup policy. **Monitoring and Controlling**: I monitored project progress, and communicated the updates on the weekly executive management meeting. Monitored the status of the identified risks, ensuring that the data was transferred safely. **Closing**: I obtained stakeholder’s acceptance and ran the team onboarding session to explain the implementation of the new server and how to use it to securely store the data. #### Project title: Launch of New East Digital Archive website (Transforming The Calvert Journal into a digital archive version) Organisation: Calvert 22 Foundation Job title: Project Manager/Product Owner Functional Reporting Area: IT Organisation Primary Focus: Training/ Education Approach/Methodology: Agile Project Team Size: 5-9  Project Budget: £85,000 Project Dates: Aug 2022- Dec 2022 Project Description: **Objective:** To transform the customer’s online publishing platform into a digital archive version, to preserve its legacy. The platform would have a different URL but could use the same infrastructure since the publishing outlet had been closed down. **Outcome**: The new archive version was produced and launched on schedule and within budget. **Initiating**: I gathered requirements and created the business case, then led meetings with the project sponsor to define high-level scope, schedule, assumptions, cost and stakeholders. **Planning**: I have gathered requirements and developed the Project Management Plan. I enlisted the trusted vendors, who did work for us in the past, to provide estimates. In collaboration with the vendors, I have finalised the Agile team members, scope, and activities and developed the project schedule. During this process, the objective was further refined to include three main functions of the new website: searching, sorting and browsing. These would be new and would replace the previous objectives of easy publishing and media management, which were more relevant when the CMS was used by the editors daily. **Execution**: Managed project team resources, project workflow and quality audits throughout execution. Held weekly meetings for status updates with team members and updated stakeholders regularly. Managed communications between stakeholders, team members and vendor’s delivery managers. **Monitoring and Controlling**: Monitored the project work and schedule. Organising UAT sessions with the customer to ensure the new features work as expected. **Closing**: Updated project documents, lessons learned and created final report. Conducted the retrospective and included recommendations on product maintenance going forward.