Learning and Capability Report Prepared by Dale Viljoen From Assignment Document “ Each team will gather evidence that the team is following a process and has developed some skills in the techniques we adopt and the tools to support them. This evidence, together with explanations and reflections will form the basis of your Team Learning and Capability Portfolio which is iteratively added to in the team Blackboard wiki.” -- Evidence ( “ that the team is following a process ” ) Communication - I (Dale Viljoen) have set up an entire communication platform for the team on Microsoft Teams. o - I have added a file system for all pdf iteration documents to allow for all team members to work on documents at the same time and for everyone to always have access to them : o - Lastly, I often add to the Project Wiki I created that simply shows how to do certain things and breaks down bigger tasks such as what to do in the assignment: o o Here is a example of the 4 th section: ▪ Continuous Integration - The process followed for CI ( continuous integration ) by our team is by using Github/Git via our public repository which can be found here: https://github.com/DaleJV/CISE - Team - 1 o The team all work on small features that can be complete in a single sprint or two and make frequent (most of t he time daily) saves to the feature branch they are working on o Once that feature is done, the branch is reviewed by the scrum master (Dale Viljoen) and if everyone is happy with it then it gets merged to master. o The branch then gets deleted. Continuous D eployment - As it stands in iteration 1, there is currently no set up continuous deployment. Architecture MERN - Mongo DB - Express. js - Node.js - React Tools: - Trello - Github /Git - Heroku - Visual Studio Developed Skills w ith Explanations ( “ developed some skills in the techniques we adopt and the tools to support them ” ) Dale As it stands for this iteration, no new skills have been developed. This is a result of my previous projects all using Microsoft Teams, Github and Trello as well as the fact that in pr evious worksheets all students did similar set up of development environment. • Routing with React o Although I had previously done routing with React, I did not spend much time thinking about how it worked o After implementing routing for the web applicatio n, as seen in the below code, I only now properly understood how it worked ▪ o I realized that the NavLink element is what created the navigation bar. The “to” section specifies the route that it needs to link to once pressed. The part that I just learnt, was that the “content” div is what specifies where a certain path takes the user. For example, if you press “Select the Practice” on the home page then it will check the “content” div to see which component it needs to return. • Documents related to Agile o I learnt a lot about documents such as roadmap and in my opinon most importantly the user story map. It is such a great tool that allowed me to see the project with the needs of the clients translated to user stories and the user stories then mapped out so that I could see the whole flow of the program opposed to a flat backlog of products. • Heroku o I ran into a handful of errors that taught me so much about Heroku. After dealing with them, I know properly understand exactly how the remote Heroku works and how it interacts with your local repository to deploy to web. o Here is a comment of what I dealt with with Heroku: ▪ The very first npm ERR, which was a few lines before the permission denied error, said npm ERR! code ELIFECYCLE.. What I did was deleted the frontend and the backend node_modules folder and did npm install in both folders. After doing that, I ran into a NO DISK SPACE error in the frontend. So, I checked, and my drive was completely full so I had to delete quite a few things. After that, I tried to push from my current branch to Heroku's main and it worked perfectly. ▪ I also had to change my entire project structure so that th e server was on the root level as heroku looked for the package.json folder there. Jake From a previous class , javascript experience, although not much . The MERN stack was almost completely knew to me as i had only heard it mentioned by classmates, so learning mon goDB, react, express and node was completely new, which has been a deep learning curve from what i was accustomed to . The development tools used however i have had previous experience with, especially trello and GitHub, heroku wa s quite new but it was also in my RnD project and lastly visual studio would be the tool i have the most experience with. Reflection