Wow, I can hardly believe our first project week at the Data School is already over! It feels like just yesterday we were starting our training, and now we’ve already worked on a real-life client project, applying all the skills we’ve learned so far to help them solve their business questions. It was an amazing experience, but also a challenging one, especially since we were working with clients for the first time. Looking back on it, here are some personal do’s and don’ts that I’d like to share with anyone starting their first project:

Do:

  • Make sure to have daily stand-ups. Our team didn’t have them during the first project week, and we realized too late how important they are for keeping everyone on the same page and tracking progress. They also help with accountability and efficiency.
  • Time management is crucial. We managed to deliver our end product, but we didn’t leave enough time for rehearsal, which made our presentation a bit rough around the edges. Setting strict deadlines for each task can help prevent that.
  • Define the project scope clearly from the outset. It helps to avoid misunderstandings and scope creep and keeps everyone focused on the same goals and objectives.
  • Follow up with stakeholders regularly to make sure you’re meeting their expectations. Our team lead sent confirmation emails summarizing our meetings with clients, which helped prevent any miscommunication.

Don’t:

  • Procrastination can be a project-killer. It’s important to stay focused, work consistently, and avoid leaving tasks until the last minute. We were lucky to have a responsible and accountable team who didn’t let procrastination get in the way of our progress.
  • Avoid overcommitting. Trying to do too much can lead to burnout, missed deadlines, and poor-quality work. It’s better to be realistic about what you can achieve within the given timeframe and prioritize tasks accordingly. In our case, time constraints prevented us from implementing all the ideas we had, but we made sure to document them as recommendations for future projects.
  • Listen to feedback and use it to improve the project. Ignoring feedback can mean missed opportunities for improvement. Evaluating feedback objectively and using it to make positive changes to the project can lead to better outcomes.

In conclusion, our first project week at the Data School was a valuable learning experience. It allowed us to apply our newly acquired skills to a real-life client project, but also exposed us to the challenges of working with clients for the first time. I hope that this can make you feel more prepared for you first project week. Good luck!

The Data School
Author: The Data School