Ibi’s First Week As A PMO Analyst
Thought I’ll update you on the my progress so far in my new role:
Day 1 – I had a lot of documentation and paper work to go through, I made sure I asked the right questions like:
a) Who are the key stakeholders what are their roles and responsibilities
b) Ask for the communication plan and reporting schedule
c) Ask how best the stakeholders likes to be engaged
d) Make sure you identify and ask to speak to colleagues doing a similar role, you will need them to bring you up to speed quickly.
e) it’s very important you build a rappour with the people you work with directly as they will hold your hands doing the 1st few days of starting your role. Be proactive and ensure you are included into all group emails and meetings as soon as possible. This will help you to understand what the business is trying to deliver and build your confidence.
Day 2 – I worked closely with my PM attending all scrum stand up meetings and taking notes.
* Tip – Remember to always take notes even if they don’t make any sense to you at the time as you go along in the project you have your notes to look on to help you remember what was discussed*.
I was also introduced to the technology team and given the opportunity to engage them on details of what we were delivering. Also had a look at the NFR’s Non functional requirements and created a spreadsheet with all the different BAs who worked on it, I assure you it was just a simple sheet with information on it.
Day 3 – I finally got my emails and logins so work started for me in ernest. First thing I did was to send an email out to the team introducing myself again and going over my role responsibilities and how I would be supporting them within the project. Role and responsibilities should have been discussed with your PM and fully understood before you send anything out. If you prefer you can have it written as it makes you accountable to your self.
* Tip – quickly establish where you can make an impact don’t hesitate to make recommendations where you can, not forcefully but with confidence*.
I also spent the better part of the day sorting out my admin and filing system, there’s no science to this whatever works for you is good enough. Had more meetings to attend overall a fantastic day and I left with a better knowledge on the organisational culture.
Day 4 – Was involved in a Release planning meeting where we looked at user stories that the delivery team was looking to start a new sprint on. We (B.A’s, PM and myself) had to review and RAG status them again as the developers had previously complained they where incomplete and had no acceptance criteria that the Testers could work with. Luckily for me I knew exactly what the were talking about and felt a lot more confident in the meeting.
*Tip – research as much as you can and believe me what you have learnt or are learning on the course is extremely relevant. You might find a few terms different but basically it’s the same process.
Day 5 – Was involved in a lot of adhoc tasks and requests to schedule meetings, laptop requests, etc.
I also sent out a comms update which i created with the PM to the business users updating them on the progress of the project and asking for further requirements if their needs have changed. I pulled together all the email responses and arranged new meetings with these users.
I hope this has been useful to someone.