PM Experiences - grippvh/G3_TestMe GitHub Wiki
How did you experience the tripple workload:
- project management agreements,
- handling documentation via GitHub,
- implementing the actual changes for the website
- As a team, we have never encountered problems with the distribution of responsibilities. A clear distribution of roles occurs quickly enough. As a result, our project is managed simply and efficiently.
- There were no people among us who knew how to work with Git. It was a really new and interesting experience for us. In a fairly short time, we were able to understand the working aspects of this platform and over time we became much more efficient to work on it.
- It was especially important to synchronize the changes correctly when writing the site. Through trial and error, we were able to come up with the best work option.
When was managing issues and changes a support and when was it a barrier?
For the most part, managing issues and changes was a suppor, because the entire team could work independently and do their part. But on the other hand, the most difficult thing was to synchronize changes that are made by different people in different branches. It took us some time to figure it out..
Did you feel your team benefited from the GitHub setup (project wiki, issues definition, Kanban)? Why or why not?
We certainly benefited from working with github, as we will continue to deal with it in the future, working in real projects. And of course, it is very convenient when you can assign responsibilities and monitor their implementation in kanban. And add new ones as the project progresses. As you can see from the history of our work, we were not immediately able to fully exploit the potential of the platform. However, now each member of our team understands the fundamental aspects of working with Git.