On-Site Training

Sometimes it’s hard to send people away from the office for days of training. Schedules may conflict, or it might be too expensive — especially if you have a team of people.

Our on-site training option brings our experts to you — on your schedule, at your location. It also allows us to plan your training in advance and tailor classes directly to your needs. You get your particular issues solved with learning targeted to your unique team environment. The entire team benefits immediately, and the cost per student is less than any other option on the market.

With Disruptive Agile’s real world Agile training, you’ll quickly grasp the principles, advantages, and disadvantages of various Agile development methods, including Scrum, Kanban and Extreme Programming (XP). In today’s economy more and more businesses are transitioning to Agile methods to take advantage of the increased efficiencies and its ability to adaptively adjust to requirement changes.

Disruptive Agile’s On-Site Training gives you first hand experience by organizing and participating in Agile teams, and by practicing the concepts you learn instantly in classroom projects then transitioning your team to work on your own real world projects. With Disruptive Agile’s on-site training the entire team sits together for 3 consecutive days.

• The first day is spent training on Agile and Scrum. It’s important that this training is followed by the entire team and that the trainer has some attention for the team-building side of this training day. Team Rules and Definition of Done are part of the Training day.

• The second day is spent expanding the backlog. The Product Owner should have already prepared the backlog and the team only needs to validate the quality of the backlog. Together the team and the Product Owner make the minimum necessary
infrastructure decisions and create enough backlog for the first sprint. The Product Owner has the vision / ideas and the team asks the right questions. In the ideal Sprint Zero, the quality of the backlog is high enough that a half day will be enough to determine that the user stories are good enough to poker and commit upon. This way, the second half of the day can be used to poker the highest prioritized changes.

• The third day is needed to end Sprint Zero. In other words, the third day should make sure Sprint 1 can be started the next day. Planning for Sprint 1 is also performed on this day.