In the last challenge we learned that Agile project management is a key component of building a modern DevOps culture at your organization. If you are new to Agile or just want a refresher, we recommend you review the following articles:
To help you with Agile project management, GitHub includes Project Boards. Project boards help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs. Please review this introduction to Project Boards before proceeding with the challenge.
-
Create a basic kanban project board for the repository you created in the previous challenge (hint).
-
Delete the default notes added to the To do column.
-
Configure automation for the columns of the board as follows (hint):
- To do - move newly added issues to this column.
- In progress - move reopened issues and newly added/reopened pull requests to this column.
- Done - move closed issues and merged pull requests/closed pull request with no commits to this column.
-
Create an issue for this and each of the remaining challenges, and verify that the new issues appear in the To do column of the project board (hint).
-
Assign the
challenge 2
issue to another member of your team, and have them assign theirchallenge 2
issue to you. -
Close the
challenge 2
issue assigned to you, and verify that the closed issue appears in the Done column of the project board. -
Reopen the
challenge 2
issue, and verify that the reopened issue appears in the In Progress column of the project board. -
Close the
challenge 2
issue.
You should have experienced using GitHub Project Boards for Agile project management.