Hello. I’m rotarymars.

Recently, I’ve been writing a lot of articles related to the robot, so this time, I’d like to write about our team’s development system.

Team structure

Our team is structured as follows.

Role	Number (Total)	Who
機体	1	ALPAKA
回路	2	K10-K10, rotarymars
ソフトウェア	2	K10-K10, rotarymars
ブログ	3	ALPAKA, K10-K10, rotarymars

It’s like this.

This means that on average, each member is responsible for 2.5 roles (we are looking for members).

Development system for the robot

Since there is only one person involved in the development of the robot, we are working in the most convenient system for one person.

I’d like to be able to participate more in the future, but it seems difficult to edit the robot at the same time due to various data.

Development system for the circuit

Since we are doing it with two people, we are trying to make it possible to communicate with each other.

We use kicad to design the circuit, so we upload the data to github.

This way, the data that the two people worked on is reflected when pulled.

Personally, I’m not satisfied with the fact that I can’t see where the edit was made in kicad visually.

Development system for the software

The software is also done with github, so we can communicate with each other.

Since the software is written in text, it is easier to see the diff than other development.

Development system for the blog

The blog is also managed with github.

We use jekyll to create the blog.

Development system for the team

We use atlassian for task management.

This is a task management tool for realizing agile software development, which lists tasks to be done by the team and makes it easier to estimate how much can be done within the deadline.

Conclusion

This time, I’ve written a short article, but I think the task management for the team is not well known, so I hope you’ll try it if you’re interested.

Thank you for reading.