-
Notifications
You must be signed in to change notification settings - Fork 1
Project Plan
For our agile process we will be completing one week sprints. At the beginning of each sprint we will conduct a sprint planning meeting. Where we will decide on features to be completed in the next sprint. At the end of each sprint we will conduct code reviews to insure the continued quality of the project. During significant team meetings we will write meeting minutes and put them on the meeting minutes Github wiki page. During each sprint we will be conducting daily stand-up meetings.
Features are discussed at weekly team planning meetings on Sundays and then are discussed with the client at weekly meetings on Tuesdays.
We will do code reviews and automated testing on each pull request into the development branch. Furthermore, for each feature of each sprint, two people will be assigned: one to implement and one to code review and verify that the functionality works and the tests run.
Each sprint is one week.
Once the minimum viable product is completed, which is currently planned to at the end of Fall quarter. Before then no working releases are planned to be released.
This list will be updated as we consider new risks to our project.
We will use git and GitHub. Each component of the project will be developed in its own repository. These repositories are listed as submodules of the (current) top-level repository for visibility.
All project planning will take place transparently with GitHub Issues and these Wiki pages.
All source code and non-private configuration files. This is platform dependent and will vary by component.
This section will be updated as the expectations, both from the client and the project manager, are given to us.
By the end of Fall Quarter, we will have a completed Minimum Viable Product (MVP).
To be decided.