Put your event plans into digital action with Happening, an event creation app to help manage correspondence with ease. Create your own digital invitations for any type of event your planning and watch the RSVPs roll in. Users can create, rsvp to, and browse other user's events. Try it out: https://the-spectacles.github.io/event-planner
Our team went to slow to go fast. Throughout the planning process, and the entire project, we utilized Trello to keep track of TODOs, future features, and steps in a process for a given feature. We spent a decent amount of time modeling and wireframing our plans for the app and had two discussions with the consultants to confirm that our approach to modeling would be successful and sustainable. Once we had our models properly white-boarded, we began coding our API.
After testing all CRUD actions on the backend, we built out a simple Handlebars templates for our auth, event, and rsvp actions. From there, we began testing the actions from the client. Throughout the week we tweaked our models based evovling wireframes, such as creating a custom route for a user's 'my events' view. After all client-side functional and AJAX calls were successfully implemented, we began styling the app and refactoring Handlebars templates and our index.html file for cleaner separation of code.
Our team decided to use the Feature Branch Git Workflow for complete transparency and version control participation among each member of the team. We pair-programmed throughout the entire project week, to ensure each team member saw each file of code and also equally contributed code.
On a typical day, our team would have morning stand up which then segued into creating our TODO list on a whiteboard and in Trello for the next 2-3 hours. After we reached the end of a TODO list we would recap what had been accomplished in the day so far by moving cards to the 'Done' list of our Trello board, and then focus on the next major TODO and breakout the steps to complete it. At the end of the day, we would recap what had been accomplished and add any additional steps or items still needed to be worked on into the Trello board for the next day.
Our team also utilized our slack channel to communicate ideas, helpful links for a problem, and updates to other team members if changes were being made outside of our determined working hours.
- All content is licensed under a CCBYNCSA 4.0 license.
- All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact firstname.lastname@example.org.