This project is to be hosted, publicly, on GitHub. If you do not have a GitHub account you should set one up. You should also take the opportunity to set up ZenHub in order to add additional tracking into your project. Zenhub along with other tools (Travis CI) are required to be used for this project. These tools are free when used with open source projects.
Use the activities below as epics for your project and set each of them up as such within GitHub. You should breakdown the tasks associated with a given epics in order to better approximate timing (assigning time estimates will allow you to generate burndown graphs in Zenhub, which are required later in the project).
Typically such epics are broken down into one or more ‘sprints’ of fixed sizes. When using ZenHub ‘Milestones’ should be used to represent ‘sprints’. Each sprint consists of several tasks, which are adequately explained and assigned before the work is undertaken. The aforementioned steps are broken down loosely according to the Agile methodology, if you are not familiar check out the following http://glenngillen.com/thoughts/quickstart-guide-to-agile. For more information on setting up your Zenhub project, check out their site – specifically https://www.zenhub.com/blog/how-to-use-epics-and-milestones/.
As the design of the project is undertaken as a Microservice Architecture, each of the followings activities may act as their own project, it is up to you if you’d like to separate these in different folders in the same repo, branches, or repositories.
Note: However you complete this task, your repository will be viewed at the culmination of the project to ensure that you leveraged the methodology. That is to say, points may be deducted from your Activity One score if you failed to close and update tickets as you complete other aspects of the project.
This project is to be hosted, publicly, on GitHub. If you do not have a GitHub account you should set one up. You should also take the opportunity to set up ZenHub in order to add additional tracking into your project. Zenhub along with other tools (Travis CI) are required to be used for this project. These tools are free when used with open source projects. Use the activities below as epics for your project and set each of them up as such within GitHub. You should breakdown the tasks associated with a given epics in order to better approximate timing (assigning time estimates will allow you to generate burndown graphs in Zenhub, which are required later in the project). Typically such epics are broken down into one or more ‘sprints’ of fixed sizes. When using ZenHub ‘Milestones’ should be used to represent ‘sprints’. Each sprint consists of several tasks, which are adequately explained and assigned before the work is undertaken. The aforementioned steps are broken down loosely according to the Agile methodology, if you are not familiar check out the following http://glenngillen.com/thoughts/quickstart-guide-to-agile. For more information on setting up your Zenhub project, check out their site – specifically https://www.zenhub.com/blog/how-to-use-epics-and-milestones/. As the design of the project is undertaken as a Microservice Architecture, each of the followings activities may act as their own project, it is up to you if you’d like to separate these in different folders in the same repo, branches, or repositories. Note: However you complete this task, your repository will be viewed at the culmination of the project to ensure that you leveraged the methodology. That is to say, points may be deducted from your Activity One score if you failed to close and update tickets as you complete other aspects of the project.