Skip to content

Instantly share code, notes, and snippets.

@ZoeKHarvey
Last active July 30, 2019 03:56
Show Gist options
  • Save ZoeKHarvey/643d9b2a55dce08f8043ddd6de0d0d40 to your computer and use it in GitHub Desktop.
Save ZoeKHarvey/643d9b2a55dce08f8043ddd6de0d0d40 to your computer and use it in GitHub Desktop.
I've learned that agile workflow is really important to be able to catch bugs or re-structure your work as you go. It pays off in the long run to be able to have a solid project after each step of the process.
How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)?
I was focused a lot on keeping communication solid with each team member and try to always be on the same page with what we're working on and what's next to work on.
I think next time I'll try to be more focused on getting my ideas accross and re-DTR'ing so that if someone starts going off track we can regroup and stay on the same page.
Team retros helps a lot to keep checking in and taking time to all reflect on where we are and how we've been doing with the project.
I tried to level out the positivity with actual feedback that we can use to work on. It's tricky when you know something could improve but you're not sure exactly how to word it. But that being said I think we did a good job with feedback and reforming our work style.
Communication has always been hard for me but I've been working on it. I think there were times when I could've been communicating feedback and re-DTR'ing more, but I now know how important it is.
@allisonreusinger
Copy link

Great details and takeaways on the project, especially around emphasizing communication in your future projects.

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