Pushing small changes to README.md

Notes/Week-1-Business/Day4_Training.md

@@ -321,7 +321,7 @@ as it displays the capabilities of a system in a way that is easy for non-techno
 
 
 ![alt text](../../Images/V-Model_Diagram.jpg "Diagram of V-Model Methodology")
-    
+
 ___
 
 **Agile**  (_**`Iterative`**_ → `Plan` → `Do` → `Check`)

Notes/Week-6/Day27_Training.md → Notes/Week-6-Quality-Gate/Day27_Training.md

@@ -21,16 +21,16 @@ so I have those answers before the interviewer even asks the question.
 
 We worked on MVC Flask framework with Python [**HERE**](https://github.com/JohnByrneJames/MVC_Flask/blob/5559831af312188750a974f53ba7a374c47fc4cb/Flask/app.py#L12)
 
-> 11:00AM [Late-Morning]
+> 11:00 AM [Late-Morning]
 
 ## **Interview Prep**
 **Agile and SCRUM**
 
 # 3 Amigos
  * **Primary Perspectives** to examine an increment of work before, during and after development.
-        * **Business** - problems trying to solve
-        * **Development** - how might we build a solution to solve that problem
-        * **Testing** - What could possibly happen
+     * **Business** - problems trying to solve
+     * **Development** - how might we build a solution to solve that problem
+      * **Testing** - What could possibly happen
 
 These three perspectives are held by different people with these perspectives, to collaborate to define
 `what` to `do`, and `agree` on how they know when it is done correctly. Resulting in clearer description 
@@ -207,7 +207,21 @@ to be added
         10. **Simplicity**
         11. **Self-organizing teams encourage great architectures, requirements, and designs**
         12. **Regular reflections on how to become more effective**
+
 >**"** There are many more things in agile and scrum for which resources have been provided and you have done
 > it practically like user story, epic etc. Have a solid answer ready for what is Agile? **"**
 
 **STAR** `Situation` `Task` `Action` and `Result` _Interview Technique_
+
+We went over MVC Flask in Python [**HERE**](https://github.com/JohnByrneJames/MVC_Flask)
+
+Now we have got to prepare for our interviews tomorrow so we practiced in 1 to 1 scenarios with our class mates.
+It went went and I am going to do it again tomorrow.
+
+**Interview time**
+* **11:40 AM - with Tim Mccarthy** 
+
+___
+**Homework**
+* Revise the Elevator pitch and try add some more enthusiasm into it
+* Revise the STAR replies to questions

Notes/Week-6-Quality-Gate/Interview_prep.md

@@ -0,0 +1,38 @@
+# Here I am going to go over the concepts that I need to revise for the Interview, including using **STAR**
+
+
+* **SITUATION** - _Set the stage, context to situation or challenge faced._
+    * **For example**, “In my last role as lead designer, my team was short-staffed and facing a 
+    significant backlog of work. The account managers were setting unrealistic deadlines, 
+    which was causing stress for my team and affecting morale.”
+* **TASK** - _Describe your responsibility or role in the situation or challenge_
+    * **For example**, “As a team leader, it was my role not only to ensure my team met 
+    our deadlines but also to communicate bandwidth to other departments and keep my team motivated.”
+* **ACTION** - _Explain how you handled the situation or overcame the challenge, if the action was carried out by
+    a team, focus on your efforts._
+    * **For example**, “I set up a formal creative request process including project timeline estimates 
+    to set better expectations. I scheduled weekly meetings with account managers to discuss my 
+    team’s bandwidth and share progress updates.”
+* **RESULT**  - _What was the outcome you reached? quantify success or provide concrete examples of the effects of
+    your efforts_
+    * **For example**, “By providing more transparency into my team’s processes and setting better 
+    expectations with the account managers, we were able to re-prioritize the design team’s to-do list
+     and complete everything in our backlog. The following quarter, we shortened our average project 
+     timeline by two days.”
+
+* Q. What is Agile and SCRUM?
+* A. Agile is a software development methodology based on an incremental, iterative approach. Agile
+projects are open to change that may happen throughout the projects, and encourage constant feedback from end-users,
+cross-functional teams working together to organise work into a backlog with priority. Where as SCRUM is a framework that
+defines a specific set of rules to follow when practicing Agile software development. SCRUM is one way to implement
+agile, with certain aspects such as the product backlog, sprint backlog, daily stand-ups or meetings, sprints and their 
+respected review and later retrospective review as well as the ability to increment the projects progress.
+
+> During my training at Sparta Global we were set the task of creating a program in python that would be capable of
+>carrying out specific functionality required by an airport, this included the completion of what are known as user-stories in
+>order to satisfy the requirements. I worked in a team of three and we set up a Kanban board in order to create an agile environment,
+>this allows us to use the SCRUM artefact's such as the product backlog, sprints and DOD to incrementally move through the project
+>making sure each user story was satisfied by breaking it down and adding it into our product backlog. Each day we would choose which items to
+>add to the daily sprint, these were to be completed in that day. By using a Agile methodology and SCRUM artefact's and events the project ran incredibly smooth and allowed
+>us to successfully complete all the user-stories 2 days before the deadline, this allowed the time to integrate the project into
+>a single and more functional entity.

README.md

@@ -11,6 +11,19 @@ ___
 ##### `Started :` **June 15 2020** :sunny:
 ##### `Ended :`  **Ongoing...** :warning:
 
+___
+## **Other Repositories** 
+* **Python OOP Repositories** 
+    1. **Abstraction** [HERE](https://github.com/JohnByrneJames/oop_abstraction) :sparkles:
+    2. **Encapsulation** [HERE](https://github.com/JohnByrneJames/oop_encapsulation) :lock:
+    3. **Polymorphism** [HERE](https://github.com/JohnByrneJames/oop_polymorphism) :recycle:
+    4. **Inheritance** [HERE](https://github.com/JohnByrneJames/oop_inheritance) :children_crossing:
+        * **OOP Calculator** [HERE](https://github.com/JohnByrneJames/oop_calculator)
+
+* **Airport Project** [HERE](https://github.com/JohnByrneJames/Airport_Project) :package:
+* **MVC_Flask** [HERE](https://github.com/JohnByrneJames/MVC_Flask) :iphone:
+* **TTD in Python** [HERE](https://github.com/JohnByrneJames/python_tdd_pytest) :building_construction:
+
 ___
 
 ## **Useful Links** 
@@ -38,4 +51,4 @@ ___
 - [x] **Week Four** - Python Continued... [:snake:](/Notes/Week-4-Python) TDD [:hammer_and_pick:](https://github.com/JohnByrneJames/python_tdd_pytest) 
 and JSON [:coffee:](/Python-Files/JSON): a little SQL with Python [:chart_with_upwards_trend:](/Python-Files/Database-Connection)  
 - [x] **Week Five** - Python Projects [:snake:](/Notes/Week-5-Project)
-- [ ] **Week Six** - 
+- [ ] **Week Six** - Quality Gate :construction: and Interviews :fire: