Teaching a New Hire Agile With LocalPM in One Afternoon
Teaching a New Hire Agile With LocalPM in One Afternoon
TLDR: LocalPM's simplicity makes it the perfect teaching tool for agile concepts, letting new hires learn by doing rather than sitting through slide decks.
When Maya joined the product team as a junior developer, she had heard of agile but never practiced it. Her previous experience was waterfall projects with Gantt charts and milestone reviews. The team lead, Derek, needed Maya to be productive in the current sprint. He did not have three days for a certification course or even a full day for training slides. He had one afternoon and LocalPM.
The Problem With Traditional Agile Training
Most agile training starts with theory. Twelve principles. Four values. The history of the Agile Manifesto. Scrum roles, ceremonies, and artifacts. By the time the training covers all the concepts, the new hire has a head full of terminology and no idea how to apply it. They understand what a sprint is in the abstract but have never created one, planned one, or closed one.
The gap between knowing agile vocabulary and practicing agile is where most onboarding fails. New hires nod along in training, then freeze when they sit down at the team's board for the first time. What column does this go in? What is the difference between a story and a task? How do I know when something is done?
Derek's One-Afternoon Approach
Derek structured the afternoon into four hands-on sessions, each about forty-five minutes, using LocalPM as the teaching environment.
Session 1: The Board. Derek opened LocalPM and created a practice project called "Maya's Onboarding." He set up four columns: Backlog, To Do, In Progress, and Done. He explained each column in one sentence: Backlog is everything that could be done. To Do is what we committed to doing this sprint. In Progress is what someone is actively working on. Done means it meets the acceptance criteria and needs no more work.
Then he had Maya create five story cards for tasks she actually needed to complete during her first week: set up her development environment, read the team's coding standards, complete HR paperwork, meet with each team member, and review the product backlog. She moved each card through the columns as the afternoon progressed, experiencing the flow firsthand.
Session 2: Stories and Acceptance Criteria. Derek showed Maya a real story from the team's current sprint. He walked through the title, description, acceptance criteria, story points, and assignee. Then he asked Maya to write a story for one of her onboarding tasks using the same format.
Maya wrote: "As a new developer, I want to set up my local development environment so that I can run the application and start contributing code." For acceptance criteria, she wrote: "The application runs locally, all tests pass, and I can make a change and see it reflected in the browser." Derek refined her criteria slightly and praised the attempt. She had just learned story writing by writing a story.
Session 3: Sprint Planning. Derek explained that a sprint is a fixed time period where the team commits to completing a set of stories. He showed Maya the team's current sprint in LocalPM: the start and end dates, the sprint goal, and the stories assigned to it.
Then he had Maya plan her own one-week "onboarding sprint." She selected her five stories, estimated each one with a simple small-medium-large scale, and wrote a sprint goal: "Complete all setup tasks so I can contribute to the team sprint starting next Monday." By planning her own sprint, she internalized the concept without memorizing a definition.
Session 4: Standup Practice. Derek explained that every morning, each team member answers three questions: What did I do yesterday? What will I do today? Is anything blocking me? He had Maya practice by giving a standup update based on her afternoon of work.
Maya said: "Yesterday I started onboarding. Today I set up my dev environment and created my onboarding board in LocalPM. I am blocked on getting access to the staging server." Derek pointed out that she had just done a perfect standup in thirty seconds. No training slides required.
Why This Approach Works
LocalPM is ideal for this kind of hands-on training because it removes tool complexity from the learning equation. There is no account to create, no permissions to configure, no administration overhead. Maya opened LocalPM in her browser and was productive in minutes. The tool did not get in the way of learning the concepts.
More importantly, Maya learned agile by practicing agile, not by studying it. She created stories, planned a sprint, moved cards across a board, and gave a standup update. Each concept was paired with an action, which creates stronger retention than passive learning.
Replicating This for Your Team
Any team lead can replicate Derek's approach. Create a practice project in LocalPM for the new hire. Use their actual onboarding tasks as the stories. Let them plan a one-week sprint and track their own work through the board. By the end of the week, they will have completed their onboarding tasks and internalized the agile workflow simultaneously.
The best onboarding does double duty: it gets the new hire set up while teaching them how the team works. LocalPM's zero-setup design makes this possible in a single afternoon. For the new hire's first independent setup, point them to setting up your first Kanban board. And for a comprehensive walkthrough, the complete LocalPM setup guide covers every step from project creation to first sprint.
Learn More
Ready to onboard your next hire with hands-on agile training? Check out the complete training series:
Watch the Project Management AI Playlist on YouTube
For more project management insights and resources, visit subthesis.com