Course Intro
Your team already knows how to build software. This course shows them how to do it with Claude working alongside them, in the jobs they actually do every day: planning, coding, testing, releasing and supporting customers.
We do not teach tools in isolation. From the first class to the last, everyone works on the same project, a web portal where business customers place orders. By the end, the team has planned it, built it, tested it, released it and handled problems on it, using Claude at each step.
Your own Claude Enterprise account and Jira are used throughout, so what people learn is exactly what they will use at work the next morning.
Key Learnings
• Use Claude every day for writing, analysis, planning and quick research
• Turn a rough idea into clear requirements, user stories and a sprint plan
• Connect Jira to Claude and work on tickets safely, with a person approving every change
• Write and change real code with Claude Code, and check that it works
• Set shared team rules so Claude behaves the same way for everyone
• Plan and run tests, and report bugs so that anyone can reproduce them
• Release the product, fix live problems and answer customer issues faster
Course Content
Every class is one hour: a short recap, a short explanation, then hands-on work on the project. Participants get about 30 minutes of practice work between classes.
Before the Course Starts
We help your admin get the basics in place so no class time is lost: Claude Enterprise accounts for everyone, Claude Code installed on each laptop, a shared code repository, and a practice Jira project that only the course uses.
Phase 1: Planning (Weeks 1 to 3)
For product owners, analysts and team leads. They finish with a clear plan and a ready-to-use project.
Module 1: Getting Started with Claude
• What Claude is good at and where it needs a human
• How to ask for what you want and get a useful answer
• What should never be pasted into Claude at work
Module 2: From Idea to Requirements
• Start from a one-page brief for the order portal
• Ask Claude to find gaps and questions the brief missed
• Write the requirements and user stories
Module 3: Working with Jira
• Connect Jira to Claude
• Create tasks from the requirements and tidy up the backlog
• Claude suggests, a person approves before anything is saved
Module 4: Design Decisions
• Compare two or three ways of building the portal
• Write down the decision and why it was made
• Draft how the system and its parts will talk to each other
Module 5: Estimates and Sprint Planning
• Break the work into tasks and estimate them
• List the risks and what each depends on
• Plan the first sprint and put it in Jira
Module 6: Setting Up the Project
• Create the project skeleton with Claude Code
• Write the first set of team rules for Claude
• Hand the plan over to the next team
By the end of this phase: a developer from the next team can pick up any first-sprint task without asking questions.
Phase 2: Building (Weeks 4 to 6)
For developers. They finish with a working portal that has tests.
Module 7: Claude Code Basics
• Install it and learn the main commands
• The working rhythm: look, plan, build, check, save
• What Claude is allowed to do on your machine
Module 8: Giving Claude the Right Context
• Teach Claude your project’s rules and habits
• Keep conversations short and focused
• Why the same question gets better answers with better context
Module 9: From Jira Ticket to Pull Request
• Open a ticket and start work on it from Claude Code
• Build the change, run the checks, raise a pull request
• Review what Claude wrote as you would review a colleague
Module 10: Checking the Work as You Go
• Write tests alongside the code
• Find and fix bugs using error messages and logs
• Know when to stop and take over yourself
Module 11: Shared Team Tools
• Save common tasks as reusable shortcuts
• Add automatic checks before code is saved
• Use helper assistants for review and research
Module 12: Cleaning Up and Reviewing
• Improve existing code safely
• Look for security problems
• Have every pull request reviewed automatically
By the end of this phase: a tester can install the portal from the instructions alone and try every feature.
Phase 3: Testing (Weeks 7 to 9)
For testers and QA. They finish with tests that run by themselves and a clear view of quality.
Module 13: Linking Tests to Requirements
• Pull the requirements from Jira
• Build a simple table showing which test covers which requirement
• Spot what is missing or unclear
Module 14: Designing Test Cases
• Normal cases, edge cases and cases that should fail
• Ask Claude for ideas, then keep only the good ones
• Prepare test data for customers, orders and roles
Module 15: Automating API Tests
• Create tests for the portal’s back-end
• Run them and understand failures
• Keep the tests tidy so others can maintain them
Module 16: Automating Browser Tests
• Test the full ordering journey as a customer would
• Make the tests stable
• Run them automatically on every change
Module 17: Reporting Bugs
• Reproduce a problem and write it up clearly
• Log it in Jira with steps and evidence
• Find the hidden problem we planted in the portal
Module 18: Deciding if It Is Ready
• Agree what “good enough to release” means
• Summarise test results, open bugs and risks
• Present a release recommendation
By the end of this phase: support can reproduce every open bug just from its ticket.
Phase 4: Release and Support (Weeks 10 to 12)
For support, implementation and operations. They finish with a released product and a way of working that lasts.
Module 19: Releasing the Portal
• Checklist and release notes
• Deploy to a test environment
• Quick checks after deployment
Module 20: Runbooks and Customer Set-up
• Write the steps for running and fixing the system
• Guides for setting up a new customer
• Keep the documents up to date as the product changes
Module 21: Finding the Cause of a Problem
• Work through two real-style incidents using logs and tickets
• Form a theory and test it
• Write a short summary of what happened
Module 22: Fixing a Live Problem
• Make a safe, small fix and release it quickly
• Update Jira and tell the people affected
• Look back at what could be done better
Module 23: Handling Customer Issues
• Sort incoming tickets and suggest replies
• Write help articles from solved cases
• Get a daily summary of the support queue
Module 24: Making It Stick
• Agree the team’s shared rules and reusable shortcuts
• Final demonstration of the whole portal
By the end of this phase: each team has shared Claude rules, a set of reusable shortcuts and one person who champions Claude.
The Project We Build Together
The group builds a portal where business customers log in, browse products, place orders and download invoices, and where staff approve orders and see simple reports. It is small enough to finish in 12 weeks and real enough to feel like day-to-day work. The trainer saves a finished copy of the project at the end of each phase, so if one team runs behind, the next team still starts from a solid base.
How Jira Fits In
• Planning: create tasks from requirements and plan the first sprint
• Building: start work from a ticket, raise a pull request and update the ticket
• Testing: read what each ticket should do and log bugs
• Support: link incidents and fixes to tickets and summarise the queue
Throughout the course Jira is a practice project. Claude can suggest changes, but a person always approves them.
What You Get
• A learning plan built around your own team and workflow
• Practical work in every class, not just slides
• A short demo at the end of each phase instead of a written exam
• All course material and the finished project to keep
• Certificate of completion
Who’s this course for
• Developers who want to work faster with Claude Code
• Testers and QA engineers who want to automate more of their work
• Support and implementation teams who handle customer issues and set-ups
• Product owners and team leads who plan and review the work
Course prerequisite
• Working knowledge of software development, testing or support (no prior experience with Claude is needed)
• A laptop for each participant, with Claude Code installed (we help your admin set this up)
• A Claude Enterprise account and access to a practice Jira project, both arranged with your admin before the course starts
International Student Fees:
350 DOLLARS
Job Interview Preparation (Soft Skills Questions & Answers)
Tough Open-Ended Job Interview Questions
What to Wear for Best Job Interview Attire
Job Interview Question- What are You Passionate About?
How to Prepare for a Job Promotion Interview
Stay connected even when you’re apart
Join our WhatsApp Channel – Get discount offers
500+ Free Certification Exam Practice Question and Answers
Your FREE eLEARNING Courses (Click Here)
Internships, Freelance and Full-Time Work opportunities
Join Internships and Referral Program (click for details)
Work as Freelancer or Full-Time Employee (click for details)
Hire an Intern
Flexible Class Options
Weekend Classes For Professionals SAT | SUN
Corporate Group Training Available
Online Classes – Live Virtual Class (L.V.C), Online Training
In the end goto code editor place this code
