This document outlines best practices for project management in small teams using automated testing and code reviews. It recommends: 1. Requiring automated testing of all code changes. 2. Conducting code reviews between developers by creating merge requests in GitLab or GitHub. Developers make changes on branches, create merge requests, and code is automatically tested. If tests pass, another developer reviews the code and merges or provides feedback. This process improves code quality, reduces bugs, and allows for knowledge sharing between team members.

1. Best?! practices of
project management
for small teams
YOSHIDA Cake @ Appirits Inc.

2. Introduction

3. Worries
of
a project manager

4.
I'm afraiding
the quality of
our programs...

5.
I'm afraiding
the quality of
our programs...
But
can not touch
until the test phase...

6.
I'm afraiding
the quality of
our programs...
But
can not touch
until the test phase...
not kept clean code
in spite of
the small team...

7.
I'm afraiding
the quality of
our programs...
But
can not touch
until the test phase...
not kept clean code
in spite of
the small team...
But, have to prepare
a “coding style
guide”...?

8. HOWEVER!

9. All you need is
only just two.
herewith...

10.
Code quality
has improved!

11.
Program bugs also
much less!
Code quality
has improved!

12.
Program bugs also
much less!
could technical
exchange
between members?!
♪
Code quality
has improved!

13. only just two.

14. 1. Force the automatic
test for code
2. Code review between
the developers

15. 1. Force the automatic
test for code
2. Code review between
the developers

16. We can remove
forgetful testing.
That is great effect!

17. 1. Force the automatic
test for code
2. Code review between
the developers

18. Developers can
testing and pointing out
to source code
with each other.
=> Quality
improvement!

19. So,
HOW?

20. Automatic test &
Code review
by
Merge-Request*(Pull-Request)
in GitLab(GitHub)
* ... hereinafter also referred to as “MR”.

21. Wait...
How can I do this??

22. :Development
flow by
Merge-Request
Practical!

23. Tools
• Redmine: issue tracking tool
• Git: version control tool
• GitLab: git management tool
=> You can use GitHub instead of GitLab
when your project is open source.
• Jenkins: CI tool
(Using `jenkins-gitlab-merge-request-builder-plugin` to connect Gitlab.)
=> You can use Travis CI instead of Jenkins
when your project is open source.

24. Icons
Project
Manager
Developer A
Issue
Branch
Merge-
Request
Developer B
Automatic
Test
Manual
process
Automatic
process

25. RedmineGitGitLabJenkins Time
New
Requirement
=> Issue
Project
Manager

26. RedmineGitGitLabJenkins Time
New
Assign the issue
to A
Developer A

27. RedmineGitGitLabJenkins Time
New
In Progress
Start development!

28. RedmineGitGitLabJenkins Time
New
In Progress
Development in the branch named
“<The issue number>-<Slug>”.
（ex. 123-add-foo-bar-feature）
In Progress
(20%)

29. RedmineGitGitLabJenkins Time
New
In Progress
In Progress
(40%)
Development
In Progress
(20%)

30. RedmineGitGitLabJenkins
In Progress
(80%)
Development
New
In Progress
In Progress
(40%)
In Progress
(20%)
Time

31. RedmineGitGitLabJenkins Time
In Progress
(80%)
git push

32. RedmineGitGitLabJenkins Time
In Progress
(80%)
Merge-
Request
Create MR to
master branch

33. RedmineGitGitLabJenkins Time
In Progress
(80%)
Merge-
Request
Testing…
NG!
Automatic testing &
Notfy the result
!
Merge-
Request

34. RedmineGitGitLabJenkins Time
In Progress
(80%)
Merge-
Request
Testing…
NG!
Fix & git push
Merge-
Request

35. RedmineGitGitLabJenkins Time
In Progress
(80%)
Merge-
Request
Testing…
NG!
Testing…
OK!
Automatic testing &
Notify the result
!
Merge-
Request
Merge-
Request

36. RedmineGitGitLabJenkins Time
Merge-
Request
Assign the MR
to B
Resolved
(100%)
Assign the issue
to B
In Progress
(80%)
Developer B

37. RedmineGitGitLabJenkins Time
Merge-
Request
Resolved
(100%)
In Progress
(80%)
git pull <target branch>

38. RedmineGitGitLabJenkins Time
Merge-
Request
Resolved
(100%)
In Progress
(80%)
Manual testing &
Code review

39. RedmineGitGitLabJenkins Time
Merge-
Request
Resolved
(100%)
In Progress
(80%)
Feedback
NG
Assign the issue
to A
with failure reasons
!

40. RedmineGitGitLabJenkins Time
Feedback
Fix & git push

41. RedmineGitGitLabJenkins Time
Feedback
Testing…
OK!
Automatic testing &
Notify the result
!
Merge-
Request

42. RedmineGitGitLabJenkins Time
Feedback
Testing…
OK!
Merge-
Request
Resolved
Assign the issue
to B

43. RedmineGitGitLabJenkins Time
Feedback
Testing…
OK!
Merge-
Request
Resolved
git pull

44. RedmineGit
Manual testing &
Code review
GitLabJenkins Time

45. RedmineGitGitLabJenkins Time
OK
Merge-
Request
Accept merge!

46. RedmineGitGitLabJenkins Time
Resolved
Assign the issue
to project manager
Merge-
Request
Project
manager

47. RedmineGitGitLabJenkins Time
Resolved
Close the issue by
the author of the issue
Merge-
Request
Closed
OK

48. RedmineGitGitLabJenkins Time
Resolved
Merge-
Request
Closed
END

49. Proceed
in such a way.

50. This flow is useful as follows:
• Consistency in source code
(without “code style guide”)
• Bugs reduced
• Technical exchanged between
developers
• Transparency of progress

51. You may think to take time for
code review is nonsense.
But
By reducing the bad code within early,
you will be able to avoid
wasting time at later.

52. For that reason,
Please try!