Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save ayladharamsey/d2122b47e6ba3d979fb77779568618df to your computer and use it in GitHub Desktop.
Save ayladharamsey/d2122b47e6ba3d979fb77779568618df to your computer and use it in GitHub Desktop.
  1. I think that I learned alot about using the Agile framework. For the Agile framework, I think that the emphasis on tackling smaller tasks and ensuring that those tasks are production ready by testing often and early has helped me write cleaner code. It's difficult to review work generally because the task can seem somewhat daunting. This way, testing is an integral part of the process, but it seems a lot more manageable.

  2. We utilized Trello during this project. We held each other accountable by utilizing the feature that allows you to claim a task or assign a task to a specific person. We checked in each morning and evening to determine our progress and where we stood against our original benchmarks, and worked mostly in person, together.

  3. In this project, I assumed the role of a project manager. I set up our Trello board, estimated time per task, and tracked progress or hangups via Trello.

  4. In the future, I would like to use more of a traditional scrum sprint, but that is hard with these rapid cycles, it feels like a lot of time actually just managing when you're having to set up and take down multiple times over 6-7 days.

  5. For us, I think that we planned and retroed daily. We just would assess where we were stopping each day, and set our plan for the next day.

  6. Much of our feedback was handled in the actual doing of the project, as we utilized a lot of driver/nav. Very little of the project was tasked out individually. So as we would go along in the process, we would encounter smaller issues all the time. Much of our feedback was handled in the moment and more centric around a specific bug or problem.

  7. I think that in formalized settings like reviews or retros that I can be a lot more general with my feedback, and I need to learn how to be more specific with my feedback. When we were utilizing more of this constant review process, it was much easier for me to be more candid with my feedback, and easier to be specific because the actual thing being reviewed was something we were just working on or running into an error on.

I want to learn to be more specific with my feedback when being asked to give feedback a day or two after. I think a lot of the time I can forget the specifics or see them as less important now that time has passed.

@allisonreusinger
Copy link

Great reflections here, and I appreciate your next steps for improving in feedback. Nice work, Ayla!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment