Corporate Trainings

SCRUM COACHING

A quick overview of Scrum. This e-learning module covers the rationale for Agile/Scrum, along with an overview of roles, meetings, and artifacts. The module ends with a challenging quiz which has been shown to increase scores on Scrum certification tests (such as Certified Scrum Master).
Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams of about seven people each.

It provides a structure of roles, meetings, rules, and artifacts. Teams are responsible for creating and adapting their processes within this framework.

Scrum uses fixed-length iterations, called Sprints, which are typically two weeks or 30 days long. Scrum teams attempt to build a potentially shippable (properly tested) product increment every iteration.

Scrum Reference Card Excerpt: An Alternative to Waterfall

Scrum’s incremental, iterative approach trades the traditional phases of “waterfall” development for the ability to develop a subset of high-value features first, incorporating feedback sooner.

The greatest potential benefit of Scrum is for complex work involving knowledge creation and collaboration, such as new product development. Scrum is usually associated with object-oriented software development. Its use has also spread to the development of products such as semiconductors, mortgages, and wheelchairs.

Scrum Reference Card Excerpt: Doing Scrum, or Pretending to Do Scrum?

Scrum’s relentless reality checks expose dysfunctional constraints in individuals, teams, and organizations. Many people claiming to do Scrum modify the parts that require breaking through organizational impediments and end up robbing themselves of most of the benefits.

Scrum Reference Card Excerpt: Product Owner

Single person responsible for maximizing the return on investment (ROI) of the development effort.
Responsible for product vision.
Constantly re-prioritizes the Product Backlog, adjusting any long-term expectations such as release plans.
Final arbiter of requirements questions.
Accepts or rejects each product increment.
Decides whether to ship.
Decides whether to continue development.
Considers stakeholder interests.
May contribute as a team member.