01
Live Instruction
Structured lectures, live coding demonstrations, and interactive discussion.
Learning Experience
Professional Learning Methodology
How learners engage with instruction, projects, practitioner review, mentorship, and professional practice throughout every Wells programme.
- Live Instruction
- Small Cohorts
- Code Review
- Project Sprints
- Professional Standards
Inside The Cohort
A disciplined environment for active professional practice.
A typical week combines live instruction, workshops, practitioner review, project sprints, mentorship, and collaborative development.
Learners are expected to participate actively, submit work, receive feedback, and improve continuously. The cohort is structured for accountability and professional practice.
This is what participation feels like: present, engaged, and held to professional standards alongside practitioners and peers.
— Methodology Charter —
Professional capability is learned by doing — under guidance, with accountability.
Wells Tech Academy delivers learning through live, synchronous instruction — designed for engagement, application, and professional feedback.
The methodology mirrors how technology professionals work: structured instruction, hands-on application, collaborative review, and iterative delivery toward milestones.
Cohort members participate in a professional process — present, accountable, and held to the published Graduation Standard.
— Learning Architecture —
Learning Architecture
Six layers of professional instruction.
Every week operates through a consistent instructional architecture — each layer building capability through practice, review, and delivery.
02
Hands-On Labs
Dedicated application time with instructor support and immediate practice.
03
Code Review
Professional feedback on quality, readability, and maintainability.
04
Project Sprints
Time-boxed delivery toward curriculum milestones and capstone goals.
05
Peer Collaboration
Pair programming, team discussion, and cohort problem-solving.
06
Office Hours
Direct access to instructors for technical questions and mentorship.
Weekly Rhythm
A consistent structure for accountable progress.
The programme allocates 360 guided learning hours across six months, with 240 hours of structured independent study and project work.
Time Allocation
- Guided learning360 hours over six months
- Independent study & projects240 hours structured independent study
- Typical weekly commitmentApproximately twenty to twenty-three hours combined guided and independent work per active week, varying by formation stage.
01 · Live Sessions
Instructor-led lectures, demonstrations, and technical discussion — synchronised across the cohort.
02 · Lab Time
Hands-on application of concepts with instructor availability and peer collaboration.
03 · Code Review
Structured submission and feedback cycles on learner work against professional standards.
04 · Project Work
Sprint-based delivery toward weekly deliverables and phase milestones.
05 · Office Hours
Optional dedicated access for individual questions, clarification, and mentorship.
— Instructional Methods —
Instructional Methods
Detailed specification for each layer of the learning architecture.
01
Live Instructor-Led Sessions
Core instruction is delivered live and synchronously. Lectures combine conceptual explanation with live coding, demonstration, and interactive Q&A.
In Practice
Cohort members attend scheduled sessions, follow demonstrations, ask questions in real time, and participate in technical discussion.
Learner Responsibility
Attend sessions prepared, engage actively, and complete pre-session preparation where assigned.
02
Hands-On Labs
Dedicated lab periods follow instruction with immediate application. Instructors circulate for support while learners build muscle memory through practice.
In Practice
Labs translate concepts into working code within the same week they are introduced — reducing the gap between understanding and execution.
Learner Responsibility
Arrive with development environment ready, work through exercises, and seek support when blocked.
03
Code Reviews
Instructor-led review sessions examine submitted work against professional standards for quality, structure, and maintainability.
In Practice
Learners submit work for review, receive structured feedback, revise, and resubmit where standards require improvement.
Learner Responsibility
Submit work on schedule, engage with feedback constructively, and document engineering decisions.
04
Project Sprints
Time-boxed delivery periods mirror professional sprint culture — milestones, accountability, and retrospective reflection.
In Practice
Sprints align with curriculum deliverables. Learners plan, execute, and demonstrate progress within defined periods.
Learner Responsibility
Commit to sprint goals, communicate blockers early, and deliver against milestones.
05
Peer Collaboration
Pair programming, team exercises, and cohort discussion develop communication skills alongside technical capability.
In Practice
Learners work together on exercises and projects, review each other's approaches, and build professional collaboration habits.
Learner Responsibility
Contribute equitably, communicate clearly, and uphold cohort standards of respect and professionalism.
06
Office Hours
Regular access to instructors for individual technical questions, clarification, and mentorship beyond scheduled sessions.
In Practice
Office hours provide space for deeper discussion on exercises, projects, and engineering decisions.
Learner Responsibility
Come prepared with specific questions and work in progress to maximise the session.
— Participation —
Participation By Mode
How participation works across delivery modes.
Delivery specifications — mode comparison, locations, and logistics — are published on the programme specification. This section describes the learning experience within each mode.
Delivery specifications01
In-Person Participation
Immersive classroom and lab environments at Croydon or Gloucester with direct instructor access and face-to-face collaboration.
- Face-to-face live instruction and live coding
- On-site lab sessions and pair programming
- Immediate instructor feedback during sessions
- Cohort community and structured accountability
02
Live Online Participation
Synchronised cohort sessions from anywhere — the same live instruction, labs, and code reviews delivered remotely.
- Live video sessions with interactive participation
- Breakout rooms for collaborative exercises
- Remote code review and screen-sharing
- Recorded sessions for structured revision
03
Hybrid Participation
A combination of campus intensives and live online sessions — designed for learners who require schedule flexibility.
- Blended attendance across campus and remote sessions
- Consistent cohort membership across modes
- Coordinated schedule with admissions support
- Same instructional standards regardless of location
Learner Accountability
Standards are enacted through practice.
Assessment and progression standards are published on the programme specification. The learning experience describes how those standards operate in daily practice.
Assessment & progression standards01 · Attendance
Live sessions are mandatory. Participation is recorded and absences require advance notice with catch-up commitment.
02 · Submission
Weekly deliverables are submitted through version-controlled repositories on schedule. Late or incomplete work is addressed before progression.
03 · Code Review Cycles
Work moves through structured review — submit, receive feedback, revise, resubmit. Quality is non-negotiable.
04 · Sprint Accountability
Capstone and project phases operate on sprint commitments with defined milestones, demos, and retrospective reflection.
— Prospectus —
Institutional Prospectus