Agile Development with Interns
summary
Company runs 5–10 interns each quarter for 10 weeks, hires 26 Newmont students so far, and documents a repeatable onboarding that shrinks from two weeks to 3-day onboarding; tooling includes CruiseControl and continuous integration with automated unit tests and sandbox DBs, plus a Dev QA document for every feature. Work is organized into 4‑week sprints with hard milestones so teams hit 100% completion and production-ready builds.
AI-written summary · about
chapters (14)
- 0:00Agile with interns
- 3:15Starting internship program
- 5:22Onboarding and design patterns
- 8:09Milestones and teamwork
- 10:41Dev-QA docs and knowledge
- 12:47Pair programming skills
- 14:34Early design and QA
- 15:40One-on-one feedback
- 16:21User stories and scope
- 17:25Technical debt and sprints
- 18:33Retrospectives reinvented
- 21:20Effective retrospectives
- 22:44Non-performing interns
- 24:55Q&A
related talks
12mAmazing internships!
10mMaking your interns succeed!
31mInternships: Good for the Intern, Great for the Team
24mElevating Young Developers: Best practices for seasoned developers on onboardings
26mThe Intern Effect
17mAre Your Interns Actually Sad? The Answer May...
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
27mSustainability Starts Early: Creating a Great Ops Internship