Student
As a LSBU student, I want to submit anonymous feedback after each lecture so that I can share honest thoughts without identification and help improve module delivery.
ePortfolio — CSI_4_PPR Professional Practice
Edgar CamaraVision Builders
BSc Computer Science (Cyber Security) at LSBU. This ePortfolio documents my academic progress, team collaboration, and project contributions across the Professional Practice module — with embedded PDF evidence for each week.
Module CodeCSI_4_PPR_25/26_S2
Module LeaderFrancis Babayemi
Submission DeadlineTuesday 03/03/26
Submission MethodLive Presentation + PPT via Moodle
01
About Me
Academic Profile
Final year BSc Computer Science (Cyber Security) student at London South Bank University. The Professional Practice module bridges academic learning with real-world team collaboration, project management, and professional skills development.
My career focus is on Security Operations — specifically targeting Junior SOC Analyst roles. I build hands-on experience through independent projects including SIEM implementations, a custom vulnerability scanner, and secure web applications.
Quick Stats
TARGET ROLEJunior SOC Analyst
UNIVERSITYLSBU
STUDENT ID4434651
TEAMVision Builders
FOCUSSIEM, Incident Response
CERTSGoogle Cybersecurity, TryHackMe
Background
I hold certifications from Google Cybersecurity and TryHackMe, alongside practical IT support experience. Within Vision Builders I contribute across frontend development, documentation, and agile sprint planning — bringing my cybersecurity perspective to the FAS project's privacy and security architecture decisions.
02
PDP Skills Overview
Key skills identified for development throughout this module, formally presented in the Week 2 PDP update. Each skill is linked to evidence gathered through weekly presentations, team collaboration, and project deliverables.
Personal Development Plan — Skills Dashboard
Current self-assessed proficiency levels across Professional, Technical, and Soft skill categories
Professional Skills
Professional
85%
Discipline
Character & professional development. Meeting deadlines consistently.
Professional
80%
Independent Learning
Self-directed study beyond curriculum to stay competitive in tech.
Professional
78%
Communication
Clear, consistent team communication. Good team chemistry noted Week 2.
Professional
70%
Agile Management
Scrum-inspired sprints, retrospectives, and backlog management.
Technical Skills
Technical
80%
Frontend Dev
HTML5, CSS3, JavaScript — responsive & accessible UI design.
Technical
75%
SIEM & Log Analysis
SIEM implementation, query writing, event correlation.
Technical
70%
Secure App Design
GDPR-aware data architecture, role-based access control.
Technical
65%
Vulnerability Assessment
Custom scanner, CVE analysis, risk reporting.
Professional Skills
Technical Skills
Developing Skills
03
Learning from Teamwork
Vision Builders was formed in Week 1 from students in the same tutorial group. The team adopted three core principles and operates using Agile/Scrum-inspired sprint planning, meeting weekly via Microsoft Teams and on-site at LSBU.
AM
Alexandra Marcu
4420667
SB
Shakshi Brijesh Patel
4428282
MG
Mythely Ganeshankugan
4503250
MZ
Mahshid Mohammadi
4401952
AJ
Alain De Jesus
4327230
EC
Edgar Camara
4434651 — Me
Respect
For each other's ideas and contributions. Essential for a diverse team with different backgrounds, skills, and perspectives.
Communicate
Clearly and consistently. Meetings via Microsoft Teams and on-site at LSBU booked meeting rooms. Most popular day: Friday.
Manage
Meet deadlines and complete tasks responsibly. Task allocation is skills-based, assigned organically as the team learns each member's strengths.
Team Agreement
A signed Team Agreement Form was submitted to the tutor in Week 3 (10/02/26). The agreement establishes shared expectations on workload, communication, and accountability across all 6 team members.
W1
Week 1 — Team Formation
Team formation, Vision Builders identity, core principles, logo rationale, and Wakelet setup. Delivered in the first tutorial session.
WEEK 01Team Formation & Platform Setup
- Vision Builders name introduced — Vision = creativity & shared goals; Builders = teamwork & contribution
- Logo: interconnected shapes (unity & diversity), upward arrow (progress), central lightbulb (creativity & problem-solving)
- Core principles established: Respect, Communicate, Manage
- Task allocation: skills-based, organic as team develops familiarity
- Wakelet setup completed successfully by all 6 members — no issues encountered
- Meeting schedule: Microsoft Teams + LSBU rooms. Most popular day: Friday
Week 1 — Vision Builders PRP Presentation (Original Slides)
W2
Week 2 — PDP Update
PDP skills update and feedback form design research. Covered Discipline, Independent Learning, and Communication as core development areas.
WEEK 02PDP Update & Feedback Form Research
- PDP Focus: Discipline, Independent Learning, Communication
- Feedback form: questionnaire-style survey, mix of rating system and open-ended questions
- Tool evaluation: Google Forms (not professional enough), Smart Survey templates identified
- Design: limited questions to essentials; ensure responsive across all devices
- Team note: "Behind schedule but we communicate well and have good chemistry"
Week 2 — Student Feedback Form Design (Original Document)
W3
Week 3 — Creative Thinking
Theme: The Fundamentals of Creative Thinking & Problem Solving. Applied norms and assumptions analysis to the FAS design, redefined the problem, and formally adopted Agile Scrum.
WEEK 03Norms, Assumptions & Problem Redefinition
- Features refined: True/False questions; Google Forms, Jot Survey, Smart Survey embed options
- Student profile questionnaire added — helps lecturers interpret feedback with user context
- Assumption 1: Surveys too long → minimise mandatory open-ended questions
- Assumption 2: No student context → solved by PDP-style profile questionnaire
- Problem Redefined: "Design a fast, inclusive, anonymous FAS enabling timely, evidence-based improvements to teaching"
- Agile / Scrum formally adopted — iterative sprints, regular check-ins
Week 3 — Vision Builders PRP Presentation (Original Slides)
W6
Week 6 — Final Presentation
Assessment 1 final team presentation. Delivered live on Tuesday 03/03/26. Slides submitted via Moodle by 18:00 the same day.
WEEK 06
Vision Builder FAS — Final Presentation
- Covers all 8 team marking criteria areas including Problem Overview, Research, Personas, Frontend & Backend, Team Dynamics
- Harvard referencing applied throughout — all sources cited and dated
- Each team member must actively participate — failure risks 30% mark penalty
Week 6 — Vision Builder FAS Final Presentation (Original Slides)
04
FAS Project Overview
Vision Builders will design a fast, inclusive, and anonymous Feedback Application System (FAS) that captures meaningful student feedback after every session and enables timely, evidence-based improvements to teaching and learning.
Problem Statement
Students need a quick, low-friction mechanism to submit feedback after each lecture or tutorial. Teaching staff lack structured, session-linked data to understand where module delivery can improve. Existing tools (Google Forms, Moodle) fail to provide the anonymity, analytics, or LSBU integration required.
🔐
User Roles & Access
Separate authenticated views for Students, Teaching Staff, and Administrators. LSBU credential integration.
👻
Anonymous Feedback
No personal identifiers stored with feedback. One submission per student per session enforced by design.
📅
Session-Based Forms
Feedback linked to specific module, session, date, and lecturer. Auto-activated after each session ends.
📝
Flexible Form Design
Mix of Likert scales, True/False, multiple choice, and limited open-ended questions. Customisable per module.
📊
Analytics Dashboard
Charts, average ratings, trend analysis. Personalised lecturer views with historical filtering.
🛡️
Security & GDPR
Encrypted storage, RBAC, full LSBU data protection compliance. Audit logs for administrators.
05
User Stories
User stories follow the Agile format: "As a [role], I want to [action] so that [benefit]." All stories were evaluated against the INVEST criteria.
I
Independent
Self-contained, releasable without depending on others
N
Negotiable
Captures essence of need, leaves room for conversation
V
Valuable
Delivers clear value to the end user or stakeholder
E
Estimable
Can be estimated to fit properly into sprints
S
Small
Completable in approximately 3–4 days
T
Testable
Confirmed via pre-written acceptance criteria
Student
As a student, I want to receive an automated reminder to complete feedback so that I don't miss the submission window.
Teaching Staff
As a lecturer, I want to view a session-specific feedback dashboard so that I can quickly identify teaching gaps and areas for improvement.
Teaching Staff
As a lecturer, I want to see historical feedback trends over time so that I can track whether changes are improving student satisfaction.
Administrator
As an administrator, I want to manage modules, sessions, and user accounts so that the system always reflects the current LSBU timetable and cohort.
EVIDENCEUser Stories — Full Document
User Stories — FAS Features (Original Document)
REFERENCEWhat is a User Story?
Reference document covering INVEST criteria, 3Cs framework, user story lifecycle, and story mapping techniques.
What is User Story? — Reference Document
06
Personal Reflections
Week 1 — Reflection
Team Formation & First Impressions
Joining Vision Builders was an exercise in organic collaboration — we were strangers who had to build trust quickly. The decision to base task allocation on natural skills felt right for the forming stage. Setting up Wakelet as a group was smooth and gave us a shared digital workspace from day one. Key learning: team chemistry matters as much as technical skill. The core principles we established (Respect, Communicate, Manage) directly reflect the real challenges any new team faces.
Week 2 — Reflection
Managing Behind Schedule — Communication as a Solution
We acknowledged in Week 2 that we were behind schedule. Rather than hiding this, we were transparent with our tutor. This was difficult but important — it reflects our Communicate principle. Key insight: good chemistry and clear communication can compensate for early delays, but only if the team stays honest. I took this as a personal lesson in professional transparency — one that applies equally to cybersecurity incident response: acknowledging problems early is always better than concealing them.
Week 3 — Reflection
Creative Thinking Applied to Real Problems
Week 3 pushed the team to challenge assumptions we hadn't realised we were making. The norms/assumptions exercise revealed we were designing for a user who already wants to give feedback — ignoring the majority who won't bother with long forms. Redesigning around minimum viable feedback input felt like genuine problem-solving. This shift — from feature list to user need — is something I want to carry into my cybersecurity work. Good security controls must also be designed around real user behaviour, not theoretical ideal users.
07
Artefacts & Evidence
All supporting documents produced throughout the module. PDFs are embedded directly in their respective week sections above.
Week 1 — Vision Builders PRP Presentation
Week 2 — Student Feedback Form Design
Week 3 — Vision Builders PRP Presentation
Week 6 — Vision Builder FAS Final Presentation
User Stories — FAS Features Documentation
What is User Story? — Reference Material
This ePortfolio — Self-Contained HTML File