Print Friendly, PDF & Email

Scrum Agile Process Development Training: Scrum is a framework for effective team collaboration on complex products.  

Scrum is not an acronym. The term Scrum was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their ground-breaking 1986 paper “The New Product Development Game.” They borrowed the name from the game of rugby to stress the importance of teams in complex product development.

Today, Scrum is widely used by software development teams. According to the 12th annual State of Agile report, 70 percent of software teams use Scrum or a Scrum hybrid. Scrum has spread to other business functions including IT and marketing where there are projects that must move forward in the presence of complexity and ambiguity. Leadership teams are also basing their agile management practices on Scrum, often combining it with lean and Kanban practices (subgroups of agile project management).

Scrum is making its mark by addressing complexity in work and making information transparent. This permits people to inspect and adapt based on current conditions rather than predicted ones.

Additionally, Scrum allows teams to address common pitfalls of a waterfall development process, which includes:

  • Chaos resulting from constantly changing requirements
  • Underestimation of time
  • Resources and cost
  • Compromises on software quality
  • Inaccurate progress reporting

In Scrum development, transparency of common terms and standards is required to ensure that what is being delivered is what was expected.

Inspection – and a lot of it — ensures progress and detects variances early on so that adjustments can be made quickly. The four most common Scrum events for inspection and adaptation are:

  1. Sprint Planning — Planning team meetings are time-boxed events that determine which product backlog items will be delivered and how the work will be achieved.
  2. Stand Up — The Daily Stand-up is a short communication meeting (no more than 15 minutes) in which each team member quickly and transparently covers progress since the last stand-up, planned work before the next meeting, and any impediments that may be blocking his or her progress.
  3. Sprint Review – This is the “show-and-tell” or demonstration event for the team to present the work completed during the sprint. The Product Owner checks the work against pre-defined acceptance criteria and either accepts or rejects the work. The stakeholders or clients give feedback to ensure that the delivered increment met the business need.
  4. Sprint Retrospective – This is the final team meeting in the Sprint to determine what went well, what didn’t go well, and how the team can improve in the next Sprint. Attended by the team and the ScrumMaster, the Retrospective is an important opportunity for the team to focus on its overall performance and identify strategies for continuous improvement on its processes.

Scrum Agile Process Development Training

Tonex offers Agile Process Development Training (Scrum), a 2-day course where attendees become  immersed in learning Agile principles and the Scrum framework.

Who Should Attend

  • Managers
  • Students
  • Executives
  • Teams
  • Anyone interested in learning about Scrum

Why Tonex?

–Presenting highly customized learning solutions is what we do. For over 30 years Tonex has worked with organizations in improving their understanding and capabilities in topics often with new development, design, optimization, regulations and compliances that, frankly, can be difficult to comprehend.

–Reasonably priced classes taught by the best trainers is the reason all kinds of organizations from Fortune 500 companies to government’s most important agencies return for updates in courses and hands-on workshops.

–Ratings tabulated from student feedback post-course evaluations show an amazing 98 percent satisfaction score.

For more information, questions, comments, Contact us.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.