Introduction to Agile & Scrum

Delivering projects faster and smarter. Discover how agility acts as a growing force in executing strategic initiatives.

Instructor: Morgan Lee, PMI-ACP, CBAP, CBB, MTM | Gardiner Centre, Memorial University

The Scrum Values

Courage

Scrum Team members have courage to do the right thing and work on tough problems.

Focus

Everyone focuses on the work of the Sprint and the goals of the Scrum Team.

Commitment

People personally commit to achieving the goals of the Scrum Team.

Respect

Scrum Team members respect each other to be capable, independent people.

Openness

The Scrum Team and its stakeholders agree to be open about all the work and the challenges.

The Agile vs Traditional Triangle

Traditional (Waterfall)

Scope is fixed. Cost and Time are estimated.

Scope

Agile Triangle

Cost and Time (Schedule) are fixed. Scope is flexible to maximize Value.

Value

The Scrum Framework

A lightweight process framework for agile solution development consisting of Roles, Ceremonies, and Artifacts.

Product Owner

Maximizes the value of the product and manages the Product Backlog. Owns "what" is desired and "why".

Scrum Master

Keeper of the Scrum Process. Facilitates events, removes impediments, and coaches the team.

Development Team

Self-organizing, cross-functional experts who own "how" and "how quickly" the work is delivered.

Agile Estimation & User Stories

Techniques for sizing work and defining requirements iteratively.

The User Story Format

"As a [USER ROLE], I want to [ACTION] so I can [GOAL]"

INVEST Criteria

Independent
Negotiable
Valuable
Estimable
Small
Testable

The 3 C's

Card: A physical token giving tangible form.
Conversation: Dialogue between PO, dev team, and testers.
Confirmation: Acceptance criteria verifying the objective is reached (Definition of Done).

Interactive Planning Poker

Select a card to estimate relative effort using the Fibonacci sequence. NEVER estimate in exact hours/days!

Agile vs Waterfall vs Hybrid

Choosing the right methodology based on constraints and uncertainty.

Condition / Scenario	Agile	Waterfall	Hybrid
Requirements Clarity	User can't define exactly what is needed	Product can be accurately defined at the beginning	Some parts very well defined (e.g. banking security)
Consumer Involvement	Willing to be part of dev and testing process	Consumer expects a well-tested, reliable final product	Consumer has constraints but wants involvement
Dependencies	Easy to avoid; features built independently	Many strict dependencies (sequential)	Some unavoidable dependencies, but not all

Case Study: LEGO Universe vs Minecraft

LEGO Universe failed largely because it followed a rigid Waterfall approach—delayed launch, massive overhead, disconnected offshore teams, and strict constraints. Conversely, Minecraft succeeded wildly via extreme Agility: releasing early prototypes, embracing user feedback, and adapting rapidly.

Lesson: Embrace User Ecosystems

Case Study: Eastern Health (NLHS)

Improving ER efficiency required deploying an Electronic White Board. Given the complexity and critical nature of health data, a Hybrid approach shines here: strict upfront requirements for patient privacy and integrations (Waterfall), but iterative development of UI/UX features based on clinical staff feedback (Agile).

Lesson: Blend Rigor with Flexibility