Project Starting


This entry is part 6 of 7 in the series Project Management

Starting is the third phase of the five phases of project management, not the first phase as the name suggests.

We have a post here on the RACI Matrix. Also, here’s an article on the RACI matrix at CIO.com. It’s called The RACI matrix: Your blueprint for project success.

The Data Analyst

Suppose you are the data analyst in a project. You have stakeholders and you are also part of a team. The team consists of you, one other data analyst and a data engineer (or database administrator – DBA) who manages the database server and runs the SQL on that server. It’s important that you know who the stakeholders and other team members are in a project so that you can communicate with them effectively. Your data combined with the other data analyst’s data might reveal something interesting. It might casuse the VP to initiate another project.

As a data analyst you’ll want to ensure that you’re able to stay focused on your objective while still balancing stakeholder needs. Concentrate on what matters and not get distracted. There are three things you can focus on that will help you stay on task. One, who are the primary and secondary stakeholders? Two who is managing the data? And three where can you go for help. The primary stakeholder will be someone higher up in the organization, such as the Vice President. You secondary stakeholders are people such as fellow data analysts, the project manager and others.

The Project Manager

As a data analyst, who could you go to if you ran into a problem? Project managers manage the project timeline, provide guidance and resources, and set up efficient workflows. They have a big-picture view of the project. This makes them a great resource if you run into a problem. If you’re having trouble getting approvals for that access to resources, you can speak with your project manager to remove those barriers for you so that you can move forward with your project.

Communication in a Team

Each person brings their own skill sets and each has value. You don’t need to know everything. You could first set up a few low-stakes meetings to understand what each person brings to the table, and how the project will actually contribute to their careers. Is someone on the team pivoting to a new field and will this project help them go in their new direction? How do each of the members of the team define success? Another good idea is to repeat back what you think you heard someone say to be sure that you understood it. In discussions, always explore the different options available.

Series Navigation<< Project PlanningProject Performing >>

Leave a Reply