Course Information
Who Should AttendTeam members, Developers, Testers, Project Leads, Development Managers, lead Developers & anyone who is or will be part of an agile team |
DurationTwo Days
|
WhereYour Location |
- Contact Us
- Cost
- $6,500 per Course
Two day minimum and discounts apply for onsite training. Up to 25 students can attend this course.
The VersionOne Agile Bootcamp is a two day immersion based training experience that is meant to familiarize participants with the concepts, methods and practical techniques of agile software development. From the history of agile and the fundamentals of strategic planning, through story writing, execution and delivery, the Bootcamp has been designed to take teams through the complete cycle of a typical agile development project. Facilitated by experts with years of applied agile experience, your coach will quickly get participants working in teams and practicing agile, through carefully constructed hands-on exercises and games that are designed to accelerate learning and reinforce understanding of the Why behind the How and What of agile development.
Whether you are just getting started with your agile journey or youre an experienced team looking for an opportunity to reset; the Agile Bootcamp offers something for everyone. Because this session is only available as a private, on-site training engagement, all Bootcamp sessions are tailored to meet the unique needs of the customer. Before your session, our coaches will work directly with you to learn about your organization, the challenges you face and your agile goals. Using this, we will create for you a training agenda that is designed to be as meaningful and contextual as possible. Participants will leave the Agile Bootcamp with the practical knowledge required to begin immediately practicing agile development.
Below is a sample agenda that is typical of an Agile Bootcamp. As your training experience will be tailored by your coach to meet your specific needs, your actual agenda may vary.
- Introduction to Agile
- History of Agile
- Understanding the Agile Manifesto
- Overview of the Agile Methods
- How Agile methods are different
- Agile Roles
- Overview of Roles
- Leadership in Agile
- Agile Teams
- Key Concept: Self Organizing Teams
- Creating Effective and Empowered Teams
- Team Dynamics What to expect when forming teams
- Tips for Reaching Consensus
- Meeting Rules and Team Charters
- Strategic Agile Planning
- Vision & Strategy
- Road mapping
- Building the Product Backlog
- User Roles
- User Roles for Stories/Requirements
- Identifying User Roles
- Using Personas
- User Stories
- The 3 Parts of a User Story
- Acceptance Criteria
- Why Use User Stories
- Gathering Stories Trawling for Requirements
- Writing Good User Story Acceptance Criteria
- Prioritization
- Story Mapping
- User Roles
- Estimation
- Issues with Conventional Estimation
- The Difference of Agile Estimation
- Relative Sizing for Feature Estimation
- Release Planning
- Key Concept: Velocity
- Estimating Dates with Velocity
- Overview of Release Planning process
- How to Release Plan
- Schedule Based Release Planning
- Scope Based Release Planning
- Maintaining the Release Plan
- Iteration Planning
- The Importance of Defining Done
- Capacity Planning
- Iteration Planning Scheduling
- Iteration Planning Detail Planning
- Planning for Chaos
- Iteration Execution & Review
- The 3 Themes of Iteration Execution
- Conducting Daily Standups
- Foul Team Smells signs of a dysfunctional team
- Sprint Demos and Review
- Metrics and Reporting
- The cost of Metrics
- Troubles with Traditional Metrics
- Understanding Agile Metrics
- Retrospectives
- Conducting effective Retrospectives
