A 2-week, mentor-supervised industry simulation for technically trained freshers who already know their technology. Work in your selected Development, QA or DevOps role on one project using Scrum and Jira.
For eligible freshers who have already completed technical training. Technical screening applies. This is a simulation, not employment or a corporate internship.
2 WEEKS · 10 WORKING DAYS · ONE TEAM PROJECT
Know the skills. Practise the workflow.
Two focused, one-week sprints. Work in your chosen Development, QA or DevOps role while collaborating across the complete delivery lifecycle.
Before Day 1
Technical screening confirms your existing skills and track. Complete account and tool setup, then review the project brief. This program applies skills you already have; it is not a beginner technology course.
SPRINT 01
Understand. Design. Build.
Days 1–5 · First working increment
DAY 01
Project kickoff & sprint planning
Understand the business problem, user stories and acceptance criteria. Select role-specific tasks and plan the first sprint in Jira.
Output: prioritised backlog and individual task ownership.
DAY 02
Design & delivery setup
Walk through architecture, UI/API contracts and data flow. Developers design a feature; QA plans tests; DevOps prepares isolated environments and Git workflow.
Output: agreed design, test approach and environment readiness.
DAY 03
Execute your role
Build the first feature, create and execute tests, or configure the initial build pipeline. Use a daily stand-up to surface blockers and update Jira.
Output: code, test evidence or pipeline configuration.
DAY 04
Review, test & integrate
Review pull requests, validate the first integrated flow, report reproducible defects and check builds. Resolve issues against acceptance criteria.
Output: reviewed changes, defect records and test results.
DAY 05
Sprint review & retrospective
Demonstrate the first working increment. Explain your contribution, collect mentor feedback and agree improvements for the next sprint.
Output: sprint demo and an updated improvement backlog.
SPRINT 02
Integrate. Release. Demonstrate.
Days 6–10 · Completed project increment
DAY 06
Plan the next increment
Prioritise remaining features and defects. Agree test coverage, dependencies and release acceptance criteria, then take ownership of the next tasks.
Output: second sprint plan and release checklist.
DAY 07
Feature completion & automation
Implement assigned changes, strengthen API/UI checks where appropriate, or extend CI/CD. Review your work with the relevant technical mentor.
Output: integrated changes and role-specific automation evidence.
DAY 08
System testing & defect triage
Exercise end-to-end journeys, investigate failures and agree defect priorities. Fix, retest and run regression checks as a cross-functional team.
Output: traceable defects, retest evidence and regression results.
DAY 09
Deploy & verify
Deploy to an isolated demo environment. Practise smoke checks, logs, monitoring and rollback planning, with responsibilities matched to your track.
Output: demo release, deployment notes and verification checklist.
DAY 10
Final demo & individual review
Present the project and explain the work you personally delivered. Review Jira tasks, code/test/configuration evidence and feedback with your mentor.
Output: contribution summary and individual improvement plan.
Project scope and tools are matched to the cohort’s assessed skills. You contribute in your selected role and understand the other roles through collaboration; this is not mastery of every discipline in two weeks. Synthetic project data and isolated environments are used.