-
Notifications
You must be signed in to change notification settings - Fork 0
Starting a Project
As a developer you will be responsible to adhering to the flow of development structured by Caliber and outlined by your Project Manager. Following this will ensure that we successfully meet deadlines and write clean, concise code, and write the appropriate tests.
Starting a Project will consist of learning about the structure of each Project, following the code submission procedures, and writing tests that cover your code. We have put this system in place to help you, not hinder your development. We have a zero-tolerance policy to ignoring or customizing the guide below.
Your Project Manager is responsible for setting up your project. If you are curious on how that happens, head over to the previous link. You are only responsible for understanding the structure and using it correctly.
Github is the tool you are currently on and the tool we will be using for everything from assigning tasks to doing code reviews.
Trello is simply just a fancy list manager that we will be using in a very specific way to show where you and the project's progress are.
Within each project repository are Milestones. These are the major problems or feature sets of a project. When you receive you project, the first thing you should do is review your Milestones. Your Project Manager will have created these.
These are the meat of the project, within each Milestone of a project, are Issues. They can be labeled as three different types of Issues. SPIKES, Coding Tasks, and Bugs. You will be dealing with all three as you move through a project.
These issues represent something you want